So everything is working fine, I even have the latest version of billie's TWRP, but the Magisk app notified me of an available update.
However, when I try to update, it just fails.
It's not causing me any problems, but I'm wondering if I'm the only one experiencing this issue.
Did you revert to the original package before updating magisk?
Also, are you referring to an update to the magisk APP itself, or to the magisk library?
Related
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
Bootloop after latest Magisk Update....now no root!
This popped up, so i updated.....been on that Rom for ages and i'm not a newbie....but 1 hour later STILL white LG logo!!!
pretty please help me out?
Not sure what to tell you, but I've been on 20.4 for a while now with no issues (VS996 if that matters).
I'd suggest going back into TWRP, reinstalling Magisk (maybe an older version like 18.3 as I've heard newer versions sometimes have issues), then letting Magisk update to 20.4 from there once you're back in. I recall that I think I had to do that when I first installed this ROM... I had to install Magisk a few times for it to "take". I may have even used Magisk Uninstaller before installing it the last time.
Has everyone received May Security Update???
For me it's showing as Already Updated to Latest Version, i am on 11.0.11.0. & i have magisk installed so is there any possibility that because of magisk i ain't getting updates???
sanam279 said:
Has everyone received May Security Update???
For me it's showing as Already Updated to Latest Version, i am on 11.0.11.0. & i have magisk installed so is there any possibility that because of magisk i ain't getting updates???
Click to expand...
Click to collapse
That is indeed the reason. You need to flash stock boot.img. not sure if magisk uninstaller does the trick also
sanam279 said:
Has everyone received May Security Update???
For me it's showing as Already Updated to Latest Version, i am on 11.0.11.0. & i have magisk installed so is there any possibility that because of magisk i ain't getting updates???
Click to expand...
Click to collapse
Magisk will not prevent getting OTA update in any way (only its installation). OTA update is rolled out in stages and your country might not be included yet.
sanam279 said:
Has everyone received May Security Update???
For me it's showing as Already Updated to Latest Version, i am on 11.0.11.0. & i have magisk installed so is there any possibility that because of magisk i ain't getting updates???
Click to expand...
Click to collapse
I have Magisk and I'm on 11.0.14.0.
Maybe a module is messing with the updates, try enable Magisk core mode only inside Magisk reboot and check again.
Edit: Just checked after writing and I did get may security update.
Also remember to follow the right way to update with Magisk.
https://topjohnwu.github.io/Magisk/ota.html
I had uninstalled magisk & flashed stock boot image, still no update
What may he the reason???
sanam279 said:
I had uninstalled magisk & flashed stock boot image, still no update
What may he the reason???
Click to expand...
Click to collapse
Side load ota or flash it with sdcard
V11.0.15.0.QFQMIXM OTA | TWRP
https://android.googleapis.com/pack.../91de26bec7a3d146b3e9d83b35da00d10075ea6f.zip
With latest update, ar core isn't working anymore
Rajendran Rasa said:
Side load ota or flash it with sdcard
V11.0.15.0.QFQMIXM OTA | TWRP
https://android.googleapis.com/pack.../91de26bec7a3d146b3e9d83b35da00d10075ea6f.zip
Click to expand...
Click to collapse
The file you linked, is it he ROM or just the May update?!
So sorry for my noobish; but, I am on CrDroid and for now I am studying the steps to return to Stock Android 10.
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.
I'm currently on Android 12 with unlocked bootloader and magisk root. This is a cph2417 model. My phone says I'm 70 days out on the update. When the update first came out I saw a bunch of comments saying not to take it but I haven't see much lately.
Has anyone had any success going to 13 and keeping root (if so, how)? Should I stay on 12?
I ended up flashing the full update from an app taken from oxygen updater, and that lost me root, but I just re-rooted right after using same direct install method. I think I kept all my modules, but I could be wrong. It is possible to keep root if you use the app from oxygen updater, I think it's called myapplication2, and then before clicking reboot after update finishes, you go to magisk and install to inactive slot. Then go back to app and reboot.
HutchOven said:
I'm currently on Android 12 with unlocked bootloader and magisk root. This is a cph2417 model. My phone says I'm 70 days out on the update. When the update first came out I saw a bunch of comments saying not to take it but I haven't see much lately.
Has anyone had any success going to 13 and keeping root (if so, how)? Should I stay on 12?
Click to expand...
Click to collapse
Yeah...
If you use the built-in update method via the settings app, the phone reboots automatically before you can re-root via magisk. Then, you must use fastboot to get root back.
However, you can avoid this if you:
Use Oxygen Updater app to download the update.
Use one of OP's local update apps (see below)
BEFORE REBOOTING, use the Magisk App to flash Magisk to the inactive slot.
Reboot.
The following is pulled from the instructions within Oxygen Updater:
"If the system's built-in “Local install” feature doesn't work for whatever reason, or if you're on global/NA firmware, you'll need to use OnePlus' separate app. Choose any, they're all developed & provided by OnePlus:
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android.apk
• https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
• https://oxygenos.oneplus.net/OnePlus_tools.apk
• https://oxygenos.oneplus.net/English_20220225101104.apk
• https://oxygenos.oneplus.net/outputbTGjgm62UO_20220218143830.apk"
JPower123 said:
I ended up..
Click to expand...
Click to collapse
notorious.dds said:
Yeah...
• ttps://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Click to expand...
Click to collapse
Thank you both, I got it to work. Here's what I did for anyone else.
1.Downloaded Oxygen updated from play store.
2. Downloaded the incremental update
3. Used 2nd link above to download the oxygen system update app and changed name to apk (delete .zip and the end) and installed.
4. Used that app to install the update
5. Once installed, before reboot I went to magisk and installed to inactive slot.
6. Reboot and good to go.