Android Pay use after rooting has been discussed in a few other threads, here on XDA, notably the 6P and 5X Nexi:
http://forum.xda-developers.com/nexus-6p/general/android-pay-root-t3309072
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
With our newly rooted H830s (courtesy of http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526), it'd be nice to collect our information here.
I am very interested in how Android Pay may or may not work after our TOT flash. Here's a quick tutorial:
SuperSU must install via a 'systemless' root method due to security changes with Marshmallow. Thus, when SuperSU is flashed in TWRP as described in the TOT root thread, it can only install this way. It should not affect the /system partition.
Android Pay uses the "Safetynet API" to detect for tampering/root. What they classify as tampering is not entirely clear. But they do check /system among other things. It looks like apps that have altered the /system partition in some way are detected via this method.
(more boring info here http://www.howtogeek.com/241012/saf...y-and-other-apps-dont-work-on-rooted-devices/ )
It must also check the permissions of the /su/bin folder, as it should have a 751 permission profile (which is the described fix in the TOT root original post).
That is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
Or, you can use root explorer to change the permissions octal to 751 for that folder.
It is set to this permission state in the rooted TOT upon first install. Obviously other root alterations you do may change it.
There are apps, such as Safetynet Helper sample (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample), which can utilize the API to see if the API is tripped.
Right after installing the TOT and getting everything to boot properly, the app shows everything is still kosher. I was able to run Android Pay, add credit cards, and have confirmed with a payment transaction.
I believe any root app that doesn't make permanent changes to /system in and of itself will probably keep Android Pay working. Obviously, for instance, if you have a terminal program app with root, and run some commands that alter your system partition/files, it may trip SafetyNet, though just having the app installed does not.
EDIT1: As of 7/25/16, a change was made to the SafetyNet API and it now detects systemless root. Android Pay no longer works on rooted devices, regardless of method. A new method will need to be developed.
EDIT2: As of 8/22/16, a workaround has been developed and tested!​Developer @topjohnwu has created Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382). This is a new way of integrating systemless changes into Android devices. This includes root, xposed, etc. The unique thing with Magisk is that you can instantly un-root your device, run Android Pay, and then reactivate root, all without rebooting. It is pretty seamless.
See the referenced thread for the latest information. It does take some work to install but it's fairly straightforward.
If you want to start from a clean install, @Gungrave223 has detailed the steps here:
http://forum.xda-developers.com/showpost.php?p=68353051&postcount=22
If you want to keep your data, it's just slightly more work. Assuming you are starting with a rooted install, here is a quick summary on how to do this:
0. You may want to first un-register the cards you have in Android Pay. Some banks apparently only allow a set # of installs before they block additional installs, thus requiring you to call the bank directly to have them reset that number. If Android Pay resets (unsure what security changes trigger this), it will forget your cards, thus leaving those cards registered on a phantom install. Un-registering first may prevent this.
1. Get the Magisk flashable zip, the Magisk-altered phh-superuser.zip, and the Magisk manager apk from the referenced thread.
2. Go to SuperSU and select full unroot. DO NOT restore the stock boot.img. DO NOT restore the default recovery. The phone should reboot and your root will be lost.
3. You should now restore the stock boot.img. This can be done without losing your data or re-encrypting your data. There are 2 ways.
Flash autoprime's stock boot.img zip file through TWRP (recommended), OR
Flash the TWRP-ed TOT file through LGUP, using the UPGRADE (not refurbish) setting
Why not just allow SuperSU to restore the stock boot.img in step 2? Because it will reboot instantly into system and start encrypting your data, with no way for you to intervene and boot into TWRP first!
4. You likely did not have data encryption on your initial rooted installation. If you want to keep yourself un-encrypted, you MUST immediately boot into TWRP before the next power on. If you do not, it will re-encrypt your data. This is the default behavior of the stock boot partition, which you just restored in the step above. You can make this easy for yourself by TWRP flashing autoprime's stock boot.zip and then immediately doing the next steps. Note: Magisk can be installed just fine on a phone with an encrypted data partition if you don't care about data encryption.
Flash the magisk.zip from the Magisk thread. This installs Magisk and also disables the forced encryption (just like the dm-verity zip)
Re-establish root by then flashing the special modified phh-superuser.zip
Note: Chainfire's SuperSU is NOT compatible if you want to use Android Pay
5. Reboot into system. You need to then install from the Playstore phh's superuser app. You also need to install the Magisk manager apk. Grant all your usual apps root permission in the superuser app.
6. Run Magisk Manager and grant it superuser access. You'll find a simple toggle to mount/unmount root. Unmount! Check that SafetyNet will pass. If you've done everything right, it will!
7. Run Android Pay. Add your card(s) back. Mount root back and go about your business.
8. When you want to use Android Pay, unmount root and run the app. Here's a tricky part (and currently a work in progress). We do not know how often or when Android Pay checks for root. We DO know that it does this when you initiate adding a new card. So you can try an Android Pay transaction. If it fails (they often do, even if you are unmounted root at that time), pretend to add a card, cancel it, and then do the transaction again. It should work now!
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
fatapia said:
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
Click to expand...
Click to collapse
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
waylo said:
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
Click to expand...
Click to collapse
Yup you got it, I had been running Xposed off Fluence for a while until I left my wallet at home and didn't feel like starving. So I downloaded the Xposed uninstaller only, ran it in recovery and then let it reboot and Pay was working again.
I followed the instructions for rooting in this thread, http://forum.xda-developers.com/tmo...p-step-guides-rooting-t-mobile-lg-g5-t3388272 and then the instructions here to change the permissions but an still having problems. The only app root app I installed after rooting was an app to export google play music with track names intact.
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
waylo said:
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
Click to expand...
Click to collapse
Yes, that is the app. I noticed MM was not supported after I had it installed
I have installed and run the safetynet app and it shows it gets tripped on the CTS profile
---------- Post added at 02:03 PM ---------- Previous post was at 01:40 PM ----------
I just realized I also had Adguard installed. I have uninstalled it and turned off suppersu and restarted but the phone still does not pass the CTS profile check
Wondering if any of those apps made some changes to /system that were not completely reversed.
Doesn't look like that music app does any permanent changes anyway, rather just copies cache not normally accessible into another folder.
Can you check the permission profile of your /su/bin folder?
Briefly looking at the Adguard website I can't make out how its root version works exactly.
What other apps are listed under your SuperSU app list? You're not running xposed, right?
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
eremeya said:
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
Click to expand...
Click to collapse
SafetyNet still failing after the permissions change?
It was today. I can try changing them again tonight when I'm at my computer and report back.
I have confirmed that the folder permissions are set to 751
eremeya said:
I have confirmed that the folder permissions are set to 751
Click to expand...
Click to collapse
Well if we can't track down the actual changes made, and you're interested in getting Android pay to work, you could try reflashing the system partition.
It looks like from reports on other threads (Nexus mostly), that something has changed with the SafetyNet check. Phones that were working just fine yesterday now fail. Most likely something server-side was patched so now Android Pay will not work with systemless root.
Details updated as I find them.
For those interested in this topic, a pretty major development has occurred at this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Essentially, this is a brand new way to implement root systemless, which can be toggled via an app, without rebooting. This does allow the SafetyNet api to remain untripped. The steps involved include flashing back to stock kernel/system, flashing the application .zips, and flashing special SuperSU or SuperUser .zips. I have not done any of this yet as it is still very early.
There are some reports, unfortunately, such as this post:
http://forum.xda-developers.com/showpost.php?p=68045722&postcount=121
which reports that despite SafetyNet passing, Android Pay still does not work (user is on Nexus 6P).
I have read of no G5 users doing this yet, but there is a V10 user who has. Stay tuned.
I've been watching the Magisk threads for the past week and decided to take the plunge today. Many Nexus phones seem to have a lot of trouble with Android Pay, but other makes seem to do better. There were confirmations from LG G4 owners. As of this writing Magisk is on v3.
The install steps from the Magisk thread are this:
1. Reflash a stock boot.img to reset your systemless root
2. Flash Magisk.zip
3. Flash modified phh-superuser.zip (not the official one). Chainfire's SuperSU does not currently have as much support, but there is a modified supersu zip as well.
4. Boot and install phh's superuser app from the App store.
5. A 'magisk manager' app is installed via the flashed .zips. This allows you to turn off root for a set # of minutes, without rebooting.
Given the unique way the G5 is rooted, with automatic encryption, I figured it might not be so simple to install this if I wanted to keep my data without a full wipe. It quickly became much more complicated than what I wanted. Here's exactly what happened.
First, I made a full boot+system+data backup.
Then, these were my thoughts/concerns:
I have Adaway installed with the systemless addon zip and SuperSU installed. Magisk installation requests flashing back the stock boot.img. What would this do to the supersu install and Adaway?
The adaway systemless zip makes a script file which is kept in the /su/su.d/ folder. I removed this.
The SuperSU has a complete uninstall feature. As part of this uninstall process, it asks if you want to restore the boot.img (yes--this stock one is backed-up after the initial supersu.zip flash during our initial root/TOT process) and/or the recovery (no, don't do this, but it probably would not have done anything as there is no stock recovery backup). I thought this would accomplish our goal. It does warn you that you may have re-encrypting of the data partition if you go this route.
And unfortunately, after rebooting, it automatically and immediately encrypted the data partition.
Well shoot. Correct me if I'm wrong, but an encrypted data partition cannot be worked on. It booted just fine, but without root.
I started having some doubts at this time so I decided to try to restore back to my initial setup. Through TWRP, I wiped the data partition and flashed the no-verity.zip, to hopefully stop any re-encryption.
Then, after figuring out how to mount system properly (TWRP defaulted to mount system as r/o), I restored my nandroid backup in its entirety.
But upon reboot, it went immediately into bootloader mode. And it continued to do this after every battery pull and power on. I had never heard of this before! Finally, I realized I could still boot into TWRP. I flashed the 10Dcomplete.zip made by autoprime, restoring the boot and system partitions to stock. And then I flashed the magisk v3.zip and the modified phh-superuser zip.
It finally rebooted into Android, with data intact! Oddly, my unlock pattern had changed without my knowledge, but the backup PIN worked. I installed the market phh Superuser. Magisk is installed properly and it passes SafetyNet, and I can add cards to the app. I'll test out Android Pay next opportunity I have.
If I had to do it all again and wanted to keep data intact, this is what I would do.
1. Autoprime did make a 10D boot flashable zip. So this would restore the stock boot.img as intended. There are some files to clean up, such as data/su.img, but that can be dealt with later.
2. I do not know if just flashing the stock boot.img would result in re-encrypting. It probably would. So, immediately after flashing the boot.img in TWRP I would flash magisk and the phh-superuser.
Alternatively, they say you should not dirty flash for things this complex. So consider starting completely new from a 10Dcomplete flash with wiped data.
I've learned that Magisk will work fine with an encrypted data partition, so if you are set on having that, it won't be a problem.
waylo said:
I have a thread here discussing Android Pay while rooted on our G5s:
http://forum.xda-developers.com/tmob...le-g5-t3395036
I thought I was the only one who cared about this kind of stuff!
Which version Magisk did you install?
I just did this 2 days ago but haven't had the opportunity to test AP yet.
What rooted apps are you running? AdAway?
Click to expand...
Click to collapse
To answer your question... I'm using v3 with his v2 of his modified phh superuser.
As for rooted apps...yes AdAways still works perfectly....TB...my one time use of System App Remover etc...
I haven't been able to test Android util tomorrow....but SafetyNet did pass when Magisk was disabled and failed when enabled.
I'll report back tomorrow after I go buy my weekly chicken at my local Fresh Mart.
I'm using the same install as you.
I tried it this AM for the first time and it failed.
On the Magisk-AP thread, someone has posited that maybe the AP app caches any root inquires during that boot. So if you test out AP and it fails while the root is active, it will remember that failure until the next reboot.
That could explain how so many people are getting weird inconsistent results. I'm testing out that theory later today.
Bah, still doesn't work, even if done immediately after a reboot =(
Related
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.
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
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
Ok so, I have known magisk for its root hide feature.....as systemless root method and, you know, first things you read about it
Now I'm realizing it's bigger than that......with modules!
wow, xposed wasn't f%&ing up our devices enough, now we need magisk modules too
joke, anyway....I once tried to flash it and resulted in bootloop (like 5/6 months ago) so it was closed story for me
BUT again....I see everyone asking for it, modules and stuff....
I know that unless you use special carrier features is not mandatory
So now....these are my questions to you, magisk power users:
1) Is it better/less invasive on the system than lastest superSU beta?
2) is it better for performance? or stability?
3) are there really useful modules? do many modules break things, decrease performance/stability as xposed does? (yes. I hate xposed)
thank you for your attention
Since no one else has given input yet, although I'm not very experienced with Magisk, I'm using it right now for the first time.
The most popular reason for using Magisk as far as I've noticed is so that you can successfully and easily hide that you're rooted so that you can use Android Pay, Pokemon Go and some other apps that check for that.
The only reason I'm using Magisk right now is because I'm running Viper10 ROM with it's all SuperSU option and although I believe my phone kept root after the Play Store SuperSU update to 2.80 and updating binaries/rebooting, the update to 2.81 broke SuperSU for me so badly that even flashing 2.8x or 2.79 SR3 SuperSU zips didn't restore root/SuperSU even after a dirty flash of the ROM.
I could've restored a TWRP backup but instead did a dirty flash of the ROM but with the full Magisk option and now root is restored.
Overall I like SuperSU better because I don't need any apps that won't run while detecting root, and I like SuperSU's ability to require a pin when granting superuser access.
By the way I really liked Xposed but I don't need it as much any more because of Nougat's custom tiles feature and the excellent ROMs available.
I'm really glad you asked this because I can' tseem to find a proper tutorial on how to install magisk and keep things such as my Banking app and other Finger print recognition software working correctly.
Have you found a tutorial which shows you how to do this?
gaiden0000 said:
I'm really glad you asked this because I can' tseem to find a proper tutorial on how to install magisk and keep things such as my Banking app and other Finger print recognition software working correctly.
Have you found a tutorial which shows you how to do this?
Click to expand...
Click to collapse
Instructions are in the Magisk thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you already have twrp then it's as easy as just flashing the zip file. For your banking app etc, after you've flashed Magisk from the above thread, you just need to open the Magisk Manager app, go to settings and enable Magisk Hide. Then go into the Magisk Hide menu and chose the apps want to hide root from.
Magisk is an amazing creation.
Although I am in no way a power user of Magisk, as I don't use it myself, at the moment. This doesn't mean I don't recognize the importance and brilliance of the Application and what it can do.
For awhile, it was mandatory to use Magisk ROMs for VoLTE/Wi-Fi Calling on Nougat firmware, but that was squashed (updater-script issues if I recall correctly. A great team effort though for those that fixed it).
Anyway, I guess my .2 cents is this. If you need a system-less set-up, for whatever reason. Be it Pokemon, or banking applications, etc...
Then Magisk is highly suggested, and really the only route. The modules that are being created are amazing.. However, they don't do anything that can't be done to the system itself. Unlike Xposed, which could do a lot of things (I also hate Xposed..) with its modules, this is different.
Such as this recent Magisk Module that was shared, I just went ahead and enabled it manually in my ROM.
Since I have no use for system-less I run my device the same way I always have. TWRP recovery and flashing custom ROMs. The latest SuperSU has fixed all root issues for myself on Sense based ROMs, and I like to use the stock LOS SuperUser on AOSP/LOS based ROMs.
I use multirom and it is an amazing creation, should check it out. Worth a peek.
Best of luck with whatever direction you decide to go.
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
StykerB said:
^title, I haven't done anything new and all of the sudden today my magisksu will not prompt when apps request root with the log only saying superuser denied. I googled it and found posts dating back to 2017 about issues with this (which seems to happen 100% of the time when I have issues). I've done the fixes people said worked for them (turning off adaptive battery, repackaging magisk manager, rolling back to older magisk, taking magisk manager off the optimizing battery list, installing some adb fastboot ndk module thing, reinstalling magisk, full uninstall and reinstall, reflashing /boot /system and /vendor back to factory image stock.) and no luck. Has anyone else fixed this without a factory reset/reflash? Also at the same time this issue popped up I'm also having a really annoying time getting apps to install from the play store, it'll download say for instance 2.50 MB/2.50 MB 100% and just sit there for literally minutes before the app randomly says it's installed after the screen blacks out.
Oh also I'm getting no errors at all in the magisk log even entry is an informative.
Update: I was able to get solidexplorer to request root successfully but it literally too 3 minutes of waiting for the prompt to appear. I'm also getting errors in the log "write failed with 32: broken pipe" which I also saw in that forum post from 2017.
Click to expand...
Click to collapse
Are you using Adware?
Edit: @StykerB My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
Are you using Adware?
Click to expand...
Click to collapse
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
TechnoSparks said:
Can you be specific?
-----
I don't have "adwares" but I have the same issue too. Surprisingly it persists when I reverted to last known good version. Which makes everything strange.
I could not afford a clean format at the moment. But until I have the time to do it (and hopefully it goes away), any suggestions to solve this would be extremely appreciated.
I am not using Pixel 3, but I use Nokia 6. Someone told me that it's a common Nokia issue, but being brought here at a very different device forum kind of prove a point that this is a bug that has to do with Magisk, and not Nokia-specific (or device-specific as for this case (maybe)) issue.
Click to expand...
Click to collapse
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Homeboy76 said:
My mistake. Read Magisk and MagiskHide Installation and Troubleshooting guide
'Root issues'
Click to expand...
Click to collapse
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
TechnoSparks said:
The page didnt help with my issue unfortunately
-------------------------------
I managed to solve my issue by actually formatting everything (including data). Painful 2 hrs for me lel. Now on 6.1 Manager and 7.3 Magisk and everything works as it should.
Since I formatted data, the issue may have something to do with magisk's leftover files.
Still, the problem with 18.x and 7.0 manager will always happen if i update. Fun fact: if you play around the root settings in Magisk Mgr, you may have a luck and the root prompt will appear. Unfortunately, the root prompt will only appear for the current boot. If you reboot, the problem is there again. Use this window of freedom to grant root to your apps.
Click to expand...
Click to collapse
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Tulsadiver said:
Just a thought and maybe you do it but after each update instead of just directly rerooting, run the magisk uninstaller first.
Flash update
Reboot
Boot back to bootloader
Install TWRP, your phones method
Flash Magisk uninstaller.zip
Flash custom kernel if applicable
Flash magisk.zip
Reboot
Click to expand...
Click to collapse
Already did that too my friend. But never mind. I am done for