Develop Bugs

Update Failed With Magisc, Can't Pass SafteyNet

So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)

gudenau said:
So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)
Click to expand...
Click to collapse
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405

mwalt2 said:
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405
Click to expand...
Click to collapse
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.

gudenau said:
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.
Click to expand...
Click to collapse
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?

TonikJDK said:
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?
Click to expand...
Click to collapse
It passed before without Magisk. The latest update did something.

8.0 with Magisk OTA update to 8.1 bootloops

I was on the Nov 17 update (taimen-opd1.170816.025) with latest magisk 15.1 on beta chanel, when I followed the magisk steps to take an ota update. ie, restored boot, ran the ota update and let it complete stage 1. When the ota started stage 2, I went back to mgisk manager and disk an install to the second slot. After ota update completed stage 2, I let the phone reboot... and it went into boot loops.
How do I rescue my phone now, and get it back to the Nov 17 update or to the latest 8.1, preferably without losing data?

I read some stuff and it seemed like reverting back to the factory image without wiping data would be a good solution.
So I downloaded the factory image (taimen-opd1.170816.025), latest platform tools, edited the flash-all.bat to remove the "-w", then ran flash-all. This completed successfully.
But upon reboot, I get the colorful G screen, with the progress bar going along underneath it, and it's stuck at this screen for a long time now.
Help?!

try using the latest image 8.1 because i think it was upgraded to 8.1, so try using 8.1 factory image without wipe of course.

Try flashing just the boot.img and the dtbo.img

webbrowser said:
I read some stuff and it seemed like reverting back to the factory image without wiping data would be a good solution.
So I downloaded the factory image (taimen-opd1.170816.025), latest platform tools, edited the flash-all.bat to remove the "-w", then ran flash-all. This completed successfully.
But upon reboot, I get the colorful G screen, with the progress bar going along underneath it, and it's stuck at this screen for a long time now.
Help?!
Click to expand...
Click to collapse
Were you on 8.0 or 8.1 when you tried this?? Checking the build #, it looks like that factory image is 8.0. You can't downgrade unless you wipe all data.

yousif666 said:
try using the latest image 8.1 because i think it was upgraded to 8.1, so try using 8.1 factory image without wipe of course.
Click to expand...
Click to collapse
Badger50 said:
Were you on 8.0 or 8.1 when you tried this?? Checking the build #, it looks like that factory image is 8.0. You can't downgrade unless you wipe all data.
Click to expand...
Click to collapse
Oh! I was originally on 8.0. The OTA to 8.1 had completed both stages but didn't seem to work on reboot, so I thought it was not working and tried to flash the 8.0 images. But now I see that may be the cause of the problem. WIll try to flash 8.1 without wiping.
...
Hooray, it works! My phone is working again.
Any idea what was wrong with my steps for doing the OTA with magisk though? I was doing this.
webbrowser said:
I was on the Nov 17 update (8.0 taimen-opd1.170816.025) with latest magisk 15.1 on beta chanel, when I followed the magisk steps to take an ota update. ie, restored boot, ran the ota update and let it complete stage 1. When the ota started stage 2, I went back to mgisk manager and disk an install to the second slot. After ota update completed stage 2, I let the phone reboot... and it went into boot loops.
Click to expand...
Click to collapse
equlizer said:
Try flashing just the boot.img and the dtbo.img
Click to expand...
Click to collapse
Could this have been the problem with the ota update? Would this have rescued my 8.0 -> 8.1 bootloops? Are there any further instructions on this (e.g. which slots and how to flash these) since it doesn't use the flash-all.bat script?
\

webbrowser said:
Oh! I was originally on 8.0. The OTA to 8.1 had completed both stages but didn't seem to work on reboot, so I thought it was not working and tried to flash the 8.0 images. But now I see that may be the cause of the problem. WIll try to flash 8.1 without wiping.
...
Hooray, it works! My phone is working again.
Any idea what was wrong with my steps for doing the OTA with magisk though? I was doing this.
Could this have been the problem with the ota update? Would this have rescued my 8.0 -> 8.1 bootloops? Are there any further instructions on this (e.g. which slots and how to flash these) since it doesn't use the flash-all.bat script?
\
Click to expand...
Click to collapse
Hi, I had this same problem and it also happened with the jan security update.
I wish I knew what is going on because it seems like everyone else is updating with no problems, but I cannot.
Any input would be greatly appreciated

Maybe I'm missing something, but I don't get why people are going the OTA route when flashing the factory image is easier (fastboot flash-all.bat (with or without the -w), fastboot TWRP, flash TWRP zip (optional), flash cust kernel (optional), flash magisk (optional), reboot, profit.
No messing with slots, or anything.... what's the benefit of flashing OTA versus factory image?

The magisk ota route should be possible even without a computer. If it works reliably, I think it is more convenient.

Not sure if you guys get everything working or not. Mine definitely not working...
Originally I have my system on OPM1.171019.011 (8.1, Dec version) with Magisk root. Everything runs smoothly. However, I tried to flash (via FASTBOOT, I had my dtob.img fixed) OPM1.171019.013 (8.1, Jan/5 version). The Magisk root lost (of course) but system works ok.
Then I tried to use Magisk Manager to patch the boot.img (since there is no boot.img in Jan/5 OTA zip, I used the boot.img in OPM1.171019.011 (8.1, Dec version) for Magisk Manager to modify.
I flashed the modified boot.img but then my Pixel 2 XL is booting with Google logo with a horizontal line running underneath. It doesn't go into system. (boot loop?)
Did I missed anything here?
Thanks!
----- Update... My bad... I should download the factory image and get boot.img from there..... Sorry for bother...

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi

Flashed and working flawless.
Really thanks for this.
Awesome work bro.

Can you please upload the patched boot.img please? I dont see it in the above folder at all.

nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder

Working, thanks a lot @mauronofrio

I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene

I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.

@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.

RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it

Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.

Thanks, rooted successfully

?
To be honest need video tutorial asap?

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

January OTA update

Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted

Perfect

Grabbed the full factory image. Removed the -w in flash-all. Flashed, patched boot.img. Works great!

Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.

adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
No..root still working here after reboot.

adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
Working just fine here

adm1jtg said:
Anyone having trouble with root on Jan update getting lost after a rebooot?
Tried 3 times now and same result each time.
Load magisk patched boot image for January via fastboot
Root fully operational
Install a magisk module
Required reboot after installing above module
Phone is no longer rooted
Can anyone confirm or deny if they get the same.
Click to expand...
Click to collapse
UPDATE: thanks to the feedback i got it working... Turns out was a bad magisk module, updated and all is well. Thanks

thatsupnow said:
Hey guys like the title says this months update is ready. I'm wondering if I can do the restore stock boot img thru magisk even tho I'm using MVK kernel?? Will it send me into boot loop??
** No bootloop everything worked out just fine **
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks

Basically I was on November update with magisk and a custom kernel installed I couldn't take otas so how I fixed it was @mbk17 I had to flash the matching boot IMG in fastboot from the update I was on to get installation problem error to go away so I could take an ota.
Download matching factory image from goggles website
Then unzip the file
Then also unzip the image bonito zip
The boot IMG is inside second zip
Flash boot IMG in fastboot issue fixed :victory:

thatsupnow said:
Just a note tho, if you've rooted by patching the boot img you won't have a backup in magisk. You'll have to take the stock boot img from your current build and compress it with this file name stock_boot_0.img in a .gz compression then copy that to the /data folder in root storage. Then go into /sbin folder and go into .magisk folder, tap on config and change the SHA value to 0 and save it.
After that's done you can restore your stock boot thru magisk, take the OTA update, don't reboot yet, install magisk to the inactive slot, once done you can reboot and your good to go and still rooted
Click to expand...
Click to collapse
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
mbk17 said:
I've done all steps up until the OTA part. It keeps giving me "Couldn't update, Installation problem" after numerous tries. Both here and the Magisk guide say DO NOT reboot. Am I screwed if I reboot or just have to repeat the process?
Thanks
Click to expand...
Click to collapse
I know it's too late but in the future if you get this, you're still rooted until you reboot, so just reinstall magisk through direct install. Now when you reboot, you're still rooted.
That said, if you can't update through the ota, you're going to have to update through ADB, and you'll lose root anyway.

Bramton1 said:
Actually, there is an easier way. Get the stock boot.img for the current build, put it on your phone, and patch that boot.img through Magisk. It will backup that original boot.img before it patches it. Don't need to do anything with the patched boot.img, but when you restore images, it will take the backup you just created.
Tried that and didn't work. Kept saying backup didn't exist, hence why I posted this steps
Click to expand...
Click to collapse

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)