Can I uninstall via recovery? - Android Q&A, Help & Troubleshooting

So Xposed has been doing me pretty well. Never had a problem until today.
Unfortunately, my most recent backup is right before I installed Xposed, and I've installed lots of apps and things since then, so I really dont wanna restore.
I installed the Xposed module, "Xposed Wallpaper" and it has rendered my phone useless. I was finally able to get into recovery and now I would like to remove the module. Is there a way to do this?
LG G2 - Sprint
CM11 Snapshot
TWRP recovery
Thanks!

Related

Xposed framework on my Samsung note 3?

I've read up on more recent versions of Samsung having trouble with the official xposed framework due to changes to ART. This has made me hesitant to install xposed framework or any xposed module on my phone because I can't afford a new phone and I really would prefer not to deal with a bootloop. My android version is 4.4.2. Would it be safe (I know there are risks involved no matter what) to install xposed framework on my phone?
Unfortunatly, Samsung will not provide any more updates to that device and I assume that you are on stock ROM and rooted. If you have TWRP you can create a backup of the whole system so in case you get stuck in a bootloop and you fix it (with odin or something) you can restore it and get all your data back. From my view, it is completely safe and since you are on kitkat you don't have to flash anything you'll just download the installer and hit install
If I helped you, hit "thanks"

Android Pay - How to get working?

I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
lexluthor said:
I'm running 47A from here:
http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's got systemless root, I'm using SuperSU and I have TWRP installed. No xposed.
I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).
If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.
So what exactly do I need to do in order to get Android Pay working?
Click to expand...
Click to collapse
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
iBolski said:
I'm not rooted (anymore), but with bumped TWRP and SuperSU, apparently you can work around this. It appears PokeMon GO is blocking rooted users due to people spoofing their GPS location via Xposed modules, etc. This article explains how to flash something called Magisk that apparently works for both Pokemon GO as well as Android Pay. Again, I'm not rooted so I have no idea if this will work or not, but he lays out the instructions pretty well. I believe that since you are already rooted and bumped with TWRP, and no Xposed, you just need to obtain Magisk and flash from within TWRP.
Hope this helps. I just happen to come across this article in my Feedly feed and remembered reading your post, so hopefully this helps you.
Let us know!
Click to expand...
Click to collapse
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
eagle132 said:
Hi iBolski,
Did you mean to include a link to an article about installing Magisk with an Verizon LG G3?
I've been looking for a way to install a stock unrooted rom for days but have been coming up short. Magisk would be ideal but I can't seem to find any threads that have a stock (unrooted) firmware image or a guide on how to unroot a pre-rooted firmware. I wish a tutorial specifically for a Bumped VS985 existed to set up a stock firmware or other ROM with Magisk because I have been having trouble piecing information together and am nervous about causing problems with my phone!
If anyone else has a Bump'd VS985 Verizon LG G3 with TWRP installed that is either unrooted or have Magisk running successfully with Android Pay or Pokemon GO, please let us know how you did it!
Thanks!!
EDIT: I just noticed that you yourself are running stock unrooted 46A iBolski... do you have TWRP installed or are you fully stock and accepted an OTA? If TWRP, does Android Pay or Pokemon Go work for you? And how'd ya get to where you are?
Click to expand...
Click to collapse
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
iBolski said:
Sorry about forgetting the link. I updated my previous reply with the article in question.
As to your answer, I do not have TWRP installed. I do have all the official OTAs applied.
Click to expand...
Click to collapse
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
eagle132 said:
Thanks for updating with the link. I did see that guide but am unsure about how to handle it with BUMP and what ROMs it works with.
If anyone else has a stock unrooted ROM or working Magisk with their TWRP/BUMP'd G3... please let us know!
Click to expand...
Click to collapse
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
eagle132 said:
As a follow up to my own post, I was able to pass the SafetyNet check (I used SafetyNet Helper from the Play Store to check) on my CloudyG3 2.5 LG G3 VS985. This was not without it's negatives however (no Xposed or root).
I simply flashed the Xposed Uninstaller and uninstalled the app, then from within the SuperSU app settings selected the option to permanently unroot. I did of course make a nandroid backup before doing this so restoring will not be an issue, but I do now get a green screen / pass to SafetyNet which should mean Android Pay and Pokemon Go will work.
Click to expand...
Click to collapse
Did you try Magisk at all? I am on Jasmine ROM (Android 5.1.1) and would love a way to still have Root & Xposed, but be able to pass SafetyNet for PokemonGO and Wallet
Question on XDABBEB's VS985 ROM
Considering that this phone will probably see no more OTA's, I'm ready to go back to root, but I don't want to break Android Pay. Also, I'm not going to use Kingroot. Don't trust it. So, I'll TOT back to 10B to flash XDABBEB VS985 ROM. But i have some questions regarding it (I haven't ran a custom ROM in almost a year).
Does anyone know if removing SuperSU from XDABBEB VS985 ROM will allow Android Pay to work? Curious if so, otherwise, I'll probably just stick with my stock 48A unrooted phone in order to keep Android Pay.
I also miss TiBu as my backup tool. Yes, LG Backup is nice and all, but TiBu is so much more flexible, including the scheduled backups that I like to do as well as pushing to my Google Drive for backing up the files. Also, TiBu doesn't store it in one giant backup file. I really wish LG Backup would store each app as a separate file, rather than one giant, humongous file. Also, if I do upgrade to a new phone that's not LG, LG Backup won't work for me, so I'll need TiBu (and of course, I have to make sure the new phone is rootable).
Thanks!
While I have not tried this (I plan to try magisk later this week) supposedly Reddit says we can use this bump script after applying magisk in order to make everything will boot. I'm reading mixed comments about if/which certain bootloader is needed to have this work (KitKat vs Lollipop vs Marshmallow) or which ROM to start with as a base (though I saw CM 13 mentioned). If anyone tries this, let me know. I'll post my results in the coming days.

Looking to install custom ROM (G925F)

So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
ProdigyThirteen said:
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
Click to expand...
Click to collapse
The first and most important thing to do is make a backup. A nandroid backup is fine but make sure you back up your EFS folder. If this gets corrupted you will corrupt your IMEI and have no signal permanently. So backup efs and store somewhere safe like your pc.
I recommend doing full wipe before installing a custom ROM just so it's a clean install.
After that your pretty much good to go.
You can use any ROM that's compatible for your model only. So any G925F ROMs will work fine. Most support a number of models like G925F/I/V etc.
Most s6 edge custom ROMs are stable and have very few issues, and if there are issues then generally there are fixes for them.
Nemesis and Noble are both good stable ROMs. Also Omega ROM is a good choice. But my favourite that I used for over a year is CarHD ROM. It's customisation is endless.
One more is AlexisROM. Good ROM used for a while.
Hope this helps.
callumbr1 said:
snip
Click to expand...
Click to collapse
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Edit: solved the MagiskHide not showing.. I'm an idiot and forgot it was under settings and not enabled by default.
ProdigyThirteen said:
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Click to expand...
Click to collapse
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
callumbr1 said:
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
Click to expand...
Click to collapse
Fixed the MagiskHide issue, but simply enabling hide on the apps that I want to use doesn't work. I tried reinstalling the ROM as you said, but it never gave the option to choose Magisk over SuperSU. Then when I switched from SuperSU to Magisk, SuperSU was removed normally, but Magisk is installed and saying I don't have root access. Flashed Magisk kernel from CarHD as TWRP wasn't allowing install of Magisk with the other that came stock, then flashed Magisk again. Magisk saying I now have root access, but Magisk isn't installed and when I try to install it, the app crashes. Currently checking Magisk threads for a solution for that.
Tried reinstalling Magisk and clearning data/cache to no avail... I still have root access, but can't install Magisk through the manager.
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
ProdigyThirteen said:
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
Click to expand...
Click to collapse
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
callumbr1 said:
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
Click to expand...
Click to collapse
Yeah, the manager is installed, but when I open it, it says there is an update available and under status says Magisk is not installed, v130 is available. There is no option to enable Magisk hide or any other extras available for download.
Screenshot of magisk
ProdigyThirteen said:
Screenshot of magisk
Click to expand...
Click to collapse
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
callumbr1 said:
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
Click to expand...
Click to collapse
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
ProdigyThirteen said:
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
Click to expand...
Click to collapse
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
callumbr1 said:
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
Click to expand...
Click to collapse
No app that removes system apps can remove Magisk Manager it seems... TB says "Failed to locate the apk file", NoBloat Free says it removed it, but even after rebooting it's still there. Flashing the uninstall doesn't remove it either. I would manually uninstall through root explorer, but there's a risk I delete the wrong file and screw something else up.
Edit: Found Magisk Manger in root/system/app/magisk, backed it up, deleted it, rebooted, seems to be gone. Will try intalling new APK
Fixed it. Had to manually delete the apk, then installed the updated version and now it's showing as magisk is installed perfectly fine. Thanks for all the help.
Third and hopefully final edit: Getting kernel is not seandroid enforcing. Tried uninstalling magisk, flashing stock kernel, reinstalling magisk and still getting it. But it doesn't seem to be messing with anything, can still boot fine, safetynet is still passing so all looks pretty good.
callumbr1 said:
snip
Click to expand...
Click to collapse
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
ProdigyThirteen said:
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
Click to expand...
Click to collapse
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
callumbr1 said:
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
Click to expand...
Click to collapse
Tried that, still getting abnormal/unsupported.
ProdigyThirteen said:
Tried that, still getting abnormal/unsupported.
Click to expand...
Click to collapse
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
callumbr1 said:
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
Click to expand...
Click to collapse
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
ProdigyThirteen said:
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
Click to expand...
Click to collapse
You can try Hacker kernel
https://forum.xda-developers.com/ga...l-hacker-kernel-s6-universal-t3254487/page234
Or arter kernel
http://arter97.com/browse/exynos7420/kernel/22.0/g925fi/
As for is it worth it? In my opinion yes 100%.
It depends really if you like the stock effects enough. Personally I love music and love been able to customise it. It sounds 10000x better in my opinion.

anyone with a functional Nougat Xposed on an LG G5?

LG G5 RS988.21c, running stock ROM w/ Nougat 7.0, unlocked bootloader w/ root by SuperSU
I got the PurifyOS Xposed up and running (https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221)... kind of. The installer APK showed itself as installed and active, but none of the modules seemed to function. Has anyone been able to get the (unstable) PurifyOS to work for their LG G5?
Now, in the Xposed Installer it states that topjohnwu's Systemless-via-Magisk Xposed works on LG (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268). Can someone confirm that to me? The install process isn't what I'm used and specifically the admonition under Magisk's install instructions to "Make sure to remove any other root, best to restore your boot image back to stock" isn't going to work for me as there isn't a stock RS988 21c boot image available.
Now, that said, I think that uninstalling SuperSU via the in-app uninstaller should work to clean up the boot image to stock in order to allow a clean-as-possible Magisk install, but that whole process currently seems daunting and I'm hoping someone is going to fly into this thread and utter the magic phrases that'll get my Xposed up and running without me having to stumble my way through the Magisk/Magisk Manager/Systemless Xposed process.
Help? If you have any experience with a successful and operational Xposed, please let me know, as well as what model LG G5 you're using. Thanks!

Google Pay After Following WTF Unlock/Magisk Guide

Hello all, I tried search the Q&A threads for any solution to my problem about Google Pay complaining about altered phone.
I have an unlocked US998 V30 variant (Nougat) that I almost never updated till now.
I followed the WTF guide using Magisk 18.0 and 20b KDZ file.
Then afterwards, I downloaded 20e, f, g, h TWRP files and flashed them via TWRP using zip queue.
In the same TWRP proces, I accidentally flashed Magisk 19.3 and that caused my phone to go into bootloop error.
I managed to fix this by going using hardware buttons to go back into TWRP, resetting everything and flashing Magisk 18.0 and the other two verity/rctd zips.
As I am reinstalling and resetting up everything, I had to update Google Play Services for Ebay (and other) apps to work (Not sure if this information is important).
When I got to trying to setup Google Pay, it complains about the phone being rooted and altered in some way.
I've tried removing phone permission from Google Play Service/Store (no go).
I've seen people suggest updating Magisk to 19.x, but I am wary of that after my bootloop fiasco.
Anyone have any suggestions or am I SOL on Google Pay?
At least on my VS996, you can upgrade Magisk outside of TWRP. In other words, have the Magisk Manager update itself, and Magisk directly (I think it's called "Direct Install").
I'm on 19.3 now without issues. This also solves the GPay issue, because nothing would let it work properly on 18.x in my experience... you have to be on 19.x for Gpay to work.
schwinn8 said:
At least on my VS996, you can upgrade Magisk outside of TWRP. In other words, have the Magisk Manager update itself, and Magisk directly (I think it's called "Direct Install").
I'm on 19.3 now without issues. This also solves the GPay issue, because nothing would let it work properly on 18.x in my experience... you have to be on 19.x for Gpay to work.
Click to expand...
Click to collapse
Can anyone else confirm this works with a US 998 Unlocked variant? I am not sure if I should upgrade my Magisk again and go through all that.
techsam2k8 said:
Can anyone else confirm this works with a US 998 Unlocked variant? I am not sure if I should upgrade my Magisk again and go through all that.
Click to expand...
Click to collapse
Yes, it works. As said, update Magisk through the app, IOW, when u boot the phone and Magisk says there's an update, do it.
Also, be sure to have gpay hidden from Magisk, in the 'Magisk Hide' section. Not sure if it matters but I also have google play services and google play store hidden.
Cheers
AsItLies said:
Yes, it works. As said, update Magisk through the app, IOW, when u boot the phone and Magisk says there's an update, do it.
Also, be sure to have gpay hidden from Magisk, in the 'Magisk Hide' section. Not sure if it matters but I also have google play services and google play store hidden.
Cheers
Click to expand...
Click to collapse
FWIW, I did not have the Magisk Hide anything, and Gpay is still working...
As the above mentioned posters said, installing it directly from Magisk Manager worked (19.3)!
However, after I rebooted, SafetyNet was failing and I found out it was due to Systemless Xposed Module.
Uninstalled that through the Magisk Manager, which worked and was able to successfully use Google Pay after hiding Magisk itself.
It is a shame I cannot use both Google Pay and Xposed at the same time.
techsam2k8 said:
It is a shame I cannot use both Google Pay and Xposed at the same time.
Click to expand...
Click to collapse
You can use Xposed and pass Safety Net. There's a guide I wrote.
You have to install THIS version of Xposed (called edXposed), enable it, then download specific Xposed modules which work with it.
Xposed and Safety Net Pass -- How To!
(with Gravity Box links)
There's link for Gravity Box, and you can look in the edXposed repository and see other Xposed mods in which you might be interested.
techsam2k8 said:
Then afterwards, I downloaded 20e, f, g, h TWRP files and flashed them via TWRP using zip queue.
In the same TWRP proces, I accidentally flashed Magisk 19.3 and that caused my phone to go into bootloop error.
Click to expand...
Click to collapse
That was not the issue.
1) If you made a backup in TWRP, all you had to do was delete boot and then restore boot from the backup.
2) You never flashed the Magisk uninstaller before updating magisk. This is a common issues going from V18-V19
Sent from my LG-H932 using XDA Labs

Categories

Resources