Develop Bugs

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.

Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.

mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.

guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do

mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.

I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu

aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.

mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?

aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?

guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error

If I do a ROM update do I need to unSU and flash Magisk again?

Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.

aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?

guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?

aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).

guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.

Would using the wrong unSU version affect safetynet detection?

Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?

guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.

Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

Is there any app like titanium backup that don't require root?

It is a little annoying that I can't use OTA because of my custom recovery (TWRP).
As of now I need root for 1 thing: backing up my apps.
Is there any way to backup apps the same as in Titanium backup (with the data of the apps) but without root?
This way I could use the OTA to update the phone
Thanks,
orma

Try out Helium Backup. It's free on the app store. You need to install this app on a PC however to enable backing up.

I tried it, but some apps cannot be backed up and the one I need the most is also in the list.
Is there any other way?

Here's what to do, root your phone and then get flashfire. You'll be able to flash the ota with it maintaining root and a custom recovery if you use it. You can also create backups with flashfire. You get the best of both worlds. Don't forget you can also download the ota's from Google if you can't wait for them to be pushed to your phone. It's also easier this way.

Can't I just use TWRP to flash the ota image?
I already have it installed

You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.

jd1639 said:
You'll loose root and twrp for sure and I don't think it will flash because you have twrp installed.
Click to expand...
Click to collapse
I looked in the comments about the app and a lot of people say that it's not working in Android Oreo.
I want to use it to flash the new oreo September security update.
Should I still use it?

It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.

jd1639 said:
It's working on my 5x with Oreo. I flashed Oreo with it and the sept update.
Click to expand...
Click to collapse
okay, i will try and update. so i just download it from the playstore?

Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.

jd1639 said:
Yes. Some of its self explanatory. You're going to want to inject supersu, everoot, and in reboot have normal and preserve recovery checked.
Click to expand...
Click to collapse
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?

orma1 said:
I downloaded the zip file from google site to my nexus 5x and the app doesn't recognizes it to be flashed.
it does recognize the zip file of supersu (already have it installed)
what should i do?
Click to expand...
Click to collapse
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?

jd1639 said:
That doesn't make any sense. I've done this 20 or more times with various nexus devices. It's possible the file was corrupted while downloading. Can you find the file on your device. It'd try downloading it again.
You're using the flash zip or ota and not firmware package?
Click to expand...
Click to collapse
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota

orma1 said:
Downloaded it from here: https://developers.google.com/android/images
from factory images tab
edit: downloaded from the Full OTA Images tab and it does recognize it should i flash it?
i used flash zip or ota
Click to expand...
Click to collapse
Yes. The full ota is the right file.

jd1639 said:
Yes. The full ota is the right file.
Click to expand...
Click to collapse
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check

orma1 said:
I have those 3 options to check:
auto-mount
mount /system read/write
restore boot and recovery images
which one to check
Click to expand...
Click to collapse
Only have restore boot and recovery

jd1639 said:
Only have restore boot and recovery
Click to expand...
Click to collapse
sorry for all of those question but the description of this make it sound like it would install the stock recovery instead of twrp
the description: Attempt restore stock boot and recovery images before flashing. May be required for some OTAs. Disable for non-OTA updates.

When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting

jd1639 said:
When you hit the check mark on that screen you'll be brought to another screen. On that one you'll see reboot. Click on that and you'll have the option to preserve recovery. That's were it'll keep twrp on your device. So restore boot and recovery is the correct setting
Click to expand...
Click to collapse
oh ok Thank you very much!
edit: it worked fine Thanks

orma1 said:
oh ok Thank you very much!
Click to expand...
Click to collapse
No problem

How to _clean_ flash an update on a rooted OP5T without losing root or TWRP recovery

Hi all,
Good news is I get the "how to root" stuff. But one aspect remains a bit unclear.
I did search but I didn't find a clear answer. If I would clean flash a full update (signed flashable zip), do you loose TWRP and root?
If yes, is the only option to reinstall TWRP-recovery and reroot?
kr,
Jeroen

You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.

xocomaox said:
You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.
Click to expand...
Click to collapse
Method would be just flashing Su or Magisk from TWRP. A full unroot is the same as a clean flash I suppose?

Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.

xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:

Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
I just got mine. Already unlocked bootloader.. Flashing TWRP now.. Then I will flash the latest update to see how it goes.

Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
Okay, so I had TWRP installed and no Magisk. I took the OTA through System Update screen...
I lost TWRP and gained stock recovery back. Everything else went fine. So I guess system update wipes TWRP! Oh, well. Easy fix.

Wait for OTA updates this is normal. You need full ROM flashable zips. For the 5 there was a topic in which they got posted. Don't know yet for the 5T. But as you say rerooting is hardly a chore

xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?

Dazed No More said:
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?
Click to expand...
Click to collapse
Hmm, that is interesting. Try taking the OTA zip using the official method (but use TWRP file manager to move it in place).
Or just flash official system image. You can get it from this forum.

Losing TWRP
Help! Trying to install twrp. Able to flash, but after reboot, phone reverts back to original recovery. Also, while in twrp- was not able to do anything... Figure something to do with encryption? In twrp formatted data, then was able to back up... Thought it fixed the problem, but still reverting back to original.
Thanks.

[Rooted] Pixel 2XL and System Autoupdates?

I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)

b3rsus said:
I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)
Click to expand...
Click to collapse
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.

murphyjasonc said:
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.
Click to expand...
Click to collapse
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?

b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.

murphyjasonc said:
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.
Click to expand...
Click to collapse
Is it any difference with the sideload method?

b3rsus said:
Is it any difference with the sideload method?
Click to expand...
Click to collapse
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.

murphyjasonc said:
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.
Click to expand...
Click to collapse
Thank you very much!)

Probably will be useful for somebody.
How to update system on a rooted Pixel 2 XL with TWRP.
Code:
[LIST=1]
[*]Download OTA file, TWRP.zip and Magisk.zip to the phone
[*]Reboot to TWRP, install OTA archive
[*]Reboot to Bootloader
[*]fastboot boot twrp.img
[*]Install TWRP.zip and Magisk.zip
[*]Power off system from TWRP
[*]Run!
[/LIST]

b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
remove the -w from the bat file

wrecklesswun said:
remove the -w from the bat file
Click to expand...
Click to collapse
This!!

General 11.2.7.7.LE15AA Rolling Out

Already prompted to install 11.2.7.7. About to install/re-root.

Normal process for taking the OTA and keeping root worked without any issue.

are you doing both Direct & Inactive slot Install before Reboot?

dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
where did you get it?

dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
Can you give me the kernel patch file? magisk

Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?

Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà

Fre$h said:
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Click to expand...
Click to collapse
I just did that and nothing has changed. If someone can give the 11.2.7.7aa image, that would help alot

galaxys said:
are you doing both Direct & Inactive slot Install before Reboot?
Click to expand...
Click to collapse
Yes
vibrantliker said:
where did you get it?
Click to expand...
Click to collapse
Just through the normal system updater.
dimmed said:
Can you give me the kernel patch file? magisk
Click to expand...
Click to collapse
No, sorry, I don't do this.
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
I followed my normal process (I don't use any Magisk modules):
Magisk Uninstall->Restore Images (do not reboot)
Take OTA (do not reboot)
Install Magisk to both active and inactive
Reboot
Worked without issue, as always.

I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy

egandt said:
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
Click to expand...
Click to collapse
Yeah, I don't do any custom kernel stuff or magisk modules, I cannot personally comment. What I know, for me, is the process fails 100% of the time if I don't do the Magisk image restore and it succeeds 100% of the time if I do.

I am currently on 11.2.4.4 AA (Global), rooted. Can I upgrade to the EU ROM since they tend to get full updates while AA has not been? If so, do I just flash the 11.2.6.6 EU ROM or should I flash 11.2.4.4 EU ROM then flash a more up-to-date ROM? If I flash the EU ROM, would I loose anything?

As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.

Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Not sure if this was for someone specific for their unique circumstance. If this was just meant generally, then it is inaccurate.
I don't use Oxygen Updater. I just take the incremental OTA using the steps I mentioned.

Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Just letting you know, Oxygen Updater is stuck on 11.2.4.4, as is the OnePlus website.

dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA

Atul Menon said:
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Click to expand...
Click to collapse
Easy. You open magisk and restore stock boot. Don't reboot yet. Download and install update. Don't reboot yet. Open magisk and install to inactive slot. Reboot.

dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is

thirtythr33 said:
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
Click to expand...
Click to collapse
Works for me every time...that way just post it.

netgar said:
Works for me every time...that way just post it.
Click to expand...
Click to collapse
yeah my system reports 11.2.4.4, yet have an incremental update for 11.2.7.7, which is odd for a number of reasons. long story short I'm sure it will cause me issues to try applying an incremental update that is not in order, but idk why 11.2.7.7 is showing up on my system, bc 11.2.6.6 never installed (or the system doesn't report it did)