Related
So i rooted my s6 thinking that it would be like a jailbreak and i was wrong.. can someone give me a link to a video or some info on how to unroot it. Thanks!
http://forum.xda-developers.com/showthread.php?t=3096000
Might be a place to start.
Normally this is something you look at before rooting you device so you know how to if you run into problems
Go into super su app and choose full unroot
I second what krelvinaz said, head over to that thread and start back to stock and start fresh
bash_array said:
Go into super su app and choose full unroot
Click to expand...
Click to collapse
I was going to use the SuperSu to do the Full unroot. If I did that, then installed the current Verizon OTA, could I then re-root using pingpong? Or does this OTA disable the ability to root again? I've read so many posts and articles from various sources, some say yes, some say no. The more I dig the more conflicting info I find.
The only reason I rooted in the first place was to swap out the mixer_paths.xml file. I'm curious if the OTA will wipe that moded file out. But that's probably another discussion.
Thanks
I rooted first and a day later took ota. After ota pingpong root just needed to "download data" or whatever then root worked fine.
Sent from my SM-G920V using XDA Free mobile app
jboogie555 said:
I rooted first and a day later took ota. After ota pingpong root just needed to "download data" or whatever then root worked fine.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
Really? Bummer, mine isn't taking the update. I've tried several times and it just fails after the download and after the reboot to install. Nothing bad happens after that, it just boots up like normal. Then it harasses me again and again to do the update.
http://forum.xda-developers.com/showpost.php?p=61279830
Easy process
DAS3D said:
Really? Bummer, mine isn't taking the update. I've tried several times and it just fails after the download and after the reboot to install. Nothing bad happens after that, it just boots up like normal. Then it harasses me again and again to do the update.
Click to expand...
Click to collapse
I think what you are talking about is you were rooted and tried to take the Ota and it wouldn't install correct? If that's the case, yeah you have to unroot or Odin the new version then reboot.
Sent from my Verizon Galaxy S6
Use the verizon upgrade utility that is on your phone when it's plugged in as an installer. Make sure your battery is charged all the way too.
Sent from my SM-G920V using XDA Free mobile app
MrWicked1 said:
I think what you are talking about is you were rooted and tried to take the Ota and it wouldn't install correct? If that's the case, yeah you have to unroot or Odin the new version then reboot.
Sent from my Verizon Galaxy S6
Click to expand...
Click to collapse
Thanks a lot for your help!
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
jboogie555 said:
Use the verizon upgrade utility that is on your phone when it's plugged in as an installer. Make sure your battery is charged all the way too.
Sent from my SM-G920V using XDA Free mobile app
Click to expand...
Click to collapse
That did the trick! Thanks so much. It worked just like it should have. Afterwards I did have to rerun pingpong, but that took about 2 seconds and I'm back to normal now with the update. Thanks a million!
I did that, as I usually do when I sell my phones.... It bricked it and I could reinstall stock.
Unrooting options
To summarize the unrooting options:
1. Unroot with SuperSu - By some reports this method does not work
2. Odin stock rom - Wipes the device and data, ?trips knox?
3. Use the Verizon Update Utility - Upgrades the devices to latest OTA
I am on 5.02 Stock (AOC3), rooted, Knox not tripped.
I am really not interested in wiping my device or updating to the latest OTA.
What I want to do is *temporarily* unroot to see if I can get Android Pay working again.
Has anyone had any luck with method 1 above? If android pay and your credit cards are activated/verified while unrooted, can you then re-root and still have Android Pay work?
I really miss using Android Pay... but not enough to lose root!!!
If you go into the superuser app and click the enable superuser to turn it off you can activate a card with android pay. You won't lose root this way.
I did that with my bank card and once my card was listed in Android pay I reenabled superuser and everything works fine.
I'm also using root cloaker but I don't know if it's needed.
Sent from my SM-G920V using XDA Free mobile app
Awesome!!! That was too easy.
Thank you, thank you, thank you!!!
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
sdpluth said:
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
Click to expand...
Click to collapse
Mine is still showing my card being attached, but I have not used it lately.
I am using root cloak plus, but I can't guarantee it works.
My knox is not tripped since I rooted with ping pong that didn't trip it.
sdpluth said:
@dobosininja
Is your android pay still working? I was able to use Android pay for only a short period ~1 day. Now I get the message "This card cannot be used right now" It doesn't matter what card I use or whether SuperSU is enabled. Maybe it is detecting SuperSU itself.
What app / procedure did you use for cloaking? Did it trip your knox?
Thanks!
Click to expand...
Click to collapse
If I'm correct, the Token needs to refresh from time to time. It may be that that process is detecting the root.
I'd try the Root Cloak he mentioned.
Late last year, with my HTC M8, I remember there was a systemless root SuperSU version that allowed me to have a stock rooted ROM and still use Android Pay. I read yesterday there is an experimental version of Xposed that is systemless and lets you use Android Pay with one reboot to turn Xposed off and no need to rebuild the app cache when turning it back on. Doubt there is a Samsung version of that yet but may come eventually. My question is if anyone has tried a stock ROM (or ordin to stock), systemless root, and been able to use Android Pay?
Yes. I am using stock LP with systemless root and Android Pay working perfectly.
theophile2 said:
Yes. I am using stock LP with systemless root and Android Pay working perfectly.
Click to expand...
Click to collapse
I went ahead an odin'd back to stock MM and then took the OTA update to latest. Then used odin to flash TWRP, twrp-3.0.2-0-M-nobleltespr.tar. Booted in recovery and flashed SuperSU, BETA-SuperSU-v2.74-2-20160519174328. Once that all was done I checked if my phone would still pass the SafetyNet check that Android Pay uses and it passed! So systemless root and stock android MM. Then I went ahead and tried the new systemless version of Xposed. http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 It flashed and works fine. I can disable xposed, reboot, and then I still pass the SafetyNet check (so pay should work but haven't tried yet). Enabling Xposed and rebooting is super quick and doesn't require a rebuild of the apps like it used to. I'm not sure what type of system modifications may cause the SafetyNet app to fail so all I've done so far is remove Voicemail (I use Google Voice) and have AdAway installed to block ads. I have the xTouchWiz, CrappaLinks, YouTube Ad Away, and Amplify Xposed modules installed and working.
Let me see if I understand this correctly. You're rooted without tripping knox?
hotspace said:
Let me see if I understand this correctly. You're rooted without tripping knox?
Click to expand...
Click to collapse
Definitely not! I haven't heard of a single person being able to root and not trip knox. I'm talking about Android Pay which doesn't care about Knox. Samsung Pay will not work.
I did make a purchase the other day with Android Pay too. Just needed to disable systemless xposed in the app, reboot, and then pay worked fine
Nice...Cool. is there a write-up anywhere on how you guys did this?
As for Samsung pay, I use Capital One and USAA. Neither of these guys participate...so I'm SOL and considering tripping knox. I can't use either of the secure payment methods.
hotspace said:
Nice...Cool. is there a write-up anywhere on how you guys did this?
As for Samsung pay, I use Capital One and USAA. Neither of these guys participate...so I'm SOL and considering tripping knox. I can't use either of the secure payment methods.
Click to expand...
Click to collapse
I pretty much described how I did it above. Just used odin to put the stock .tar on, then took OTA updates, then installed TWRP via ODIN, then SuperSU, and eventually systemless Xposed. All the info is around the sprint forum for more details on each step. Since you're already stock you can probably just skip right to TWRP. That step will trip knox!
For whatever it's worth, I found that I had to delete /su/xbin_bind before Android Pay would work. Here are the steps that worked for me:
celsian said:
For those who are confused, here are my steps for using Android Pay while rooted.
1. I reset my phone to factory defaults by installing all original software.
2. Unlocked the boot loader.
3. Installed TWRP, but kept it read only.
4. Installed Beta Super User 2.67
5. Through Android terminal after entering su and allowing terminal emulator root access:
6. rm -r /su/xbin_bind
7. chmod 751 /su/bin
Android Pay works, root is still active. Thanks all.
Click to expand...
Click to collapse
Doing it this way, Android Pay "just works" with root, no need to "unroot" or reboot or anything. Note, however, that I do not have Xposed installed, and henderjr is right that Android Pay will quit working with normal Xposed, and if you use systemless Xposed, you have to disable it before Android Pay will work.
theophile2 said:
For whatever it's worth, I found that I had to delete /su/xbin_bind before Android Pay would work. Here are the steps that worked for me:
Doing it this way, Android Pay "just works" with root, no need to "unroot" or reboot or anything. Note, however, that I do not have Xposed installed, and henderjr is right that Android Pay will quit working with normal Xposed, and if you use systemless Xposed, you have to disable it before Android Pay will work.
Click to expand...
Click to collapse
Yep all correct except newest SuperSU doesn't need any of those extra steps (xbin_bind deleted or chmod).
Sent from my SM-N920P using Tapatalk
will this work for note 5 from us cellular?
SM-N900R4 (OJ5)
i talked to bigbiff in #twrp on freenode and he said probably can use the sprint note 5 twrp for the us cellular n5.
this was the case for the note 3 from us cellular too. had to use the sprint twrp.
en11gma said:
will this work for note 5 from us cellular?
SM-N900R4 (OJ5)
i talked to bigbiff in #twrp on freenode and he said probably can use the sprint note 5 twrp for the us cellular n5.
this was the case for the note 3 from us cellular too. had to use the sprint twrp.
Click to expand...
Click to collapse
I tend to follow most posts in the Sprint Note 5 forum and haven't seen anyone say they tried or used Sprint TWRP on a US Cellular version so I really can't say. Give it a try maybe? I'd think the worst case scenario is you need to Odin back to stock. Not an expert though so that be on you if it bricked. For sure I'd get a stock tar available before you try.
henderjr said:
I tend to follow most posts in the Sprint Note 5 forum and haven't seen anyone say they tried or used Sprint TWRP on a US Cellular version so I really can't say. Give it a try maybe? I'd think the worst case scenario is you need to Odin back to stock. Not an expert though so that be on you if it bricked. For sure I'd get a stock tar available before you try.
Click to expand...
Click to collapse
yea im pretty sure us cellular note 5 users can use twrp that is sprints.
i did find a twrp us cellular recovery for PD6 (im on PE1 now) i might download PD6 stock firmware then flash that us cellular twrp recovery but worried about what kind of root to do
i dont think i want to perm disable samsung pay and i think if i use SuperSU (systemless root) that i might be able to save it.
can anyone confirm this?
to my understanding systemless root means i dont need to flash a custom kernel?
If you flash twrp samsung pay will never work again for you
If someone roots, I have heard that many apps stop working. My question is, if the device is then unrooted, will those apps still work considering the fact that knox will remain tripped? I'm not referring to Samsung Pay, but rather apps from the playstore.
Yes, using magisk you can run all of the applications...
Few may need workaround but possible
Sent from my SM-G955F using Tapatalk
`SBR` said:
Yes, using magisk you can run all of the applications...
Few may need workaround but possible
Click to expand...
Click to collapse
Right, but after unrooting will the apps work as normal? Since I cant use magisk if I decide to go back to stock
the_OZONE said:
Right, but after unrooting will the apps work as normal? Since I cant use magisk if I decide to go back to stock
Click to expand...
Click to collapse
Just stay stock if you want all the Samsung pay etc to work.
dynospectrum said:
Just stay stock if you want all the Samsung pay etc to work.
Click to expand...
Click to collapse
I hope I don't sound noob but coming from a 6p, i believe I am. I am new to samsung(even hated the idea of having one just as i hate iphones...) but was a gift and am lovin' it. I read a lot about rooting the s8+. Even got all the tools I found through a walkthrough to achieve root on my device. Many say it's not safe. The steps were flashing twrp through odin, then flashing magisk and the verity flash in twrp.
Hope i didn't tire you yet
Just a couple questions, is it actually safe to root my device? With the knox and whatnot(never had to worry about that before with the 6p)what apps will be affected by root and how to workaround that?
I have a g955fd btw
Thanks in advance
RockyAJ said:
I hope I don't sound noob but coming from a 6p, i believe I am. I am new to samsung(even hated the idea of having one just as i hate iphones...) but was a gift and am lovin' it. I read a lot about rooting the s8+. Even got all the tools I found through a walkthrough to achieve root on my device. Many say it's not safe. The steps were flashing twrp through odin, then flashing magisk and the verity flash in twrp.
Hope i didn't tire you yet
Just a couple questions, is it actually safe to root my device? With the knox and whatnot(never had to worry about that before with the 6p)what apps will be affected by root and how to workaround that?
I have a g955fd btw
Thanks in advance
Click to expand...
Click to collapse
Its safe but once Knox is tripped its tripped for good. As of now there's no way to use certain secure apps if Knox has been tripped. You won't be able to us Secure folders (private mode), S Health and allegedly Samsung pay (although this one works for me on my rooted s8+ with Magisk). There may be some other apps but those are the main ones I can think of.
Besides these apps most if not all other apps root check capabilities can be fooled or bypassed. Apps like Snapchat, Netflix and Poke Go etc.are normally blocked on rooted devices but work just fine with Magisk.
xeathpk said:
Its safe but once Knox is tripped its tripped for good. As of now there's no way to use certain secure apps if Knox has been tripped. You won't be able to us Secure folders (private mode), S Health and allegedly Samsung pay (although this one works for me on my rooted s8+ with Magisk). There may be some other apps but those are the main ones I can think of.
Besides these apps most if not all other apps root check capabilities can be fooled or bypassed. Apps like Snapchat, Netflix and Poke Go etc.are normally blocked on rooted devices but work just fine with Magisk.
Click to expand...
Click to collapse
So you recommend going for root?
RockyAJ said:
So you recommend going for root?
Click to expand...
Click to collapse
If you dont care about the apps I mentioned or possibly forfeiting your warranty then I don't see why not. Its definitely not required though. There's not too much incentive to root yet until rovo89 gets Xposed to work on android 7.0+, if ever. I just rooted to make full nandroid backups and save myself the trouble of rooting down the road. As of right now there's not too much added functionality in having root access besides a few small-ish tweaks here and there.
I see a lot of custom ROMs on https://forum.xda-developers.com/galaxy-s7/development but I am not sure which to use. My main goal is to remove all the builtin Samsung apps that I cannot disable/uninstall like Calendar and Internet. I started looking at SuperMan but then saw it has a lot of other enhancements too. I also want to avoid my device being rooted because I have to install apps that won't install if my phone is rooted (GFE/BlackBerry Work).
LineageOS or Resurrection Remix.
Just disable the Samsung apps you don't want. That's the only remedy for you.
SuperMan is probably the closest you'll get to stock. If that's too far off, I'm not really sure of any other options. You could temporarily root and try removing the offending apps, I'm not sure how much the system depends on them.
There's also the option of Magisk (Systemless) root, which shouldn't effect root-adverse apps.
I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.
Memovic said:
I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.
Click to expand...
Click to collapse
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.
imthenachoman said:
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.
Click to expand...
Click to collapse
Please take my advice:
Do NOT root your device.
Cause that has some side effects and nearly no benefits:
You won't be able to encrypt your phone again.
You'll have to install magisk to get some things to work
Do NOT install an AOKP based ROM cause there are severe bluetooth bugs.
Just install "BK Package Disabler (Samsung)" on stockrom and get rid of Samsungs bloatware.
PS:
I'm back to stockrom after installing LOS and I regret that step, cause it tripped the knox-bit.
Perhaps the BT bugs will be fixed in future; then I'll give LOS another shot.
Lol @ this lad above, get your facts straight.
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.
Memovic said:
Lol @ this lad above, get your facts straight.
Click to expand...
Click to collapse
Laughing isn't very polite.
On-topic:
How did you get your phone encrypted again?
What are the benefits of being rooted nowadays?
OK, TB would be one thing for me.
And... tinkering.
Do some Google-ing, should get the answers.
Memovic said:
Do some Google-ing, should get the answers.
Click to expand...
Click to collapse
Thanks for sharing your limitless wisdom :good:
if you want a rom as close to perfect, try helios 7.22.1
sammydoro said:
Please take my adviceo NOT root your device.
Click to expand...
Click to collapse
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Memovic said:
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.
Click to expand...
Click to collapse
Thank you! I will give it a shot.
imthenachoman said:
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Click to expand...
Click to collapse
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
OTA updates will not work anymore.
S-Pay (and others) is said to not work anymore.
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
If I am wrong at any point, pls correct me.
I only rooted to use LOS. But there are too many errors atm.
So I returned to stock and have to live with these issues.
So it depends on your usecase.
If you just want to debloat your stockrom, use BK- disabler.
If you want more, root it.
sammydoro said:
If you just want to debloat your stockrom, use BK- disabler.
Click to expand...
Click to collapse
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?
imthenachoman said:
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?
Click to expand...
Click to collapse
Yes. That is the purpose of the app.
And, in my opinion, it works reliable and comfortable.
sammydoro said:
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
Click to expand...
Click to collapse
I rooted, but my S Health is still working
sammydoro said:
OTA updates will not work anymore.
[/QOUTE]
Yes, that's good, so Samsung won't remove my root or any system apps I am using or adding system apps I removed.
sammydoro said:
S-Pay (and others) is said to not work anymore.
[/QOUTE]
S-Pay doesn't work in our country, so what? It's a fail project anyhow.
sammydoro said:
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
[/QOUTE]
sammydoro said:
If I am wrong at any point, pls correct me.
[/QOUTE]
done
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Running stock ROM not rooted, getting this error? .. bootloader is unlocked though
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Eric214 said:
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Click to expand...
Click to collapse
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
Strange... on my OP 6 with unlocked bootloader and Magisk root, Google Pay runs fine. And even Magisk Hide was not enabled for Google Pay (now it is).
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Eric214 said:
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Click to expand...
Click to collapse
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
please dont give users the wrong impression
Magisk DOES hide it.
i have an unlocked bootloader, TWRP, MAGISK, and a custom kernel installed
and ive been using google pay for the past week without issues.
Why would I give users wrong impression? It's happening to me!!! Just because it doesn't happen to you or others then it cannot be true?
I've also an unlocked bootloader, TWRP and Magisk installed and Magisk is not hiding specific apps. Simple as that.
hallo dare said:
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
Click to expand...
Click to collapse
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Eric214 said:
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Click to expand...
Click to collapse
I've gone and done a complete format and re-installation of everything and the same issue is present.
hallo dare said:
I've gone and done a complete format and re-installation of everything and the same issue is present.
Click to expand...
Click to collapse
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Eric214 said:
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Click to expand...
Click to collapse
Done that, but made no difference. Just reading on another thread that it appears to be an issue for many.
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Orito said:
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Click to expand...
Click to collapse
Thanks Orito,
Yeah I'll do just that. Can you please post the magisk you flashed and I'll try it please.
I flashed the 16.4.
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Orito said:
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Click to expand...
Click to collapse
Exactly what I've been doing. Thanks