Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
Worst things that could happen are: OTA fails to install or you have to reinstall Magisk through fastbooting/T
WRP, so just try it.
I just flash full factory image and flash TWRP, Flash Kernel, and Magisk again, instead of waiting for OTA to be available through the phone.
freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
To be safe i would use the flash-all for December update. It will take to back to stock kernel and remove magisk. Then take the January ota. I think that is a sure way and doesn't take to many step.
Better to do flash all bat of January Factory Image, and reflashing magisk after that,
You can edit the flashing script, removing -w to prevent it wiping your data
I've tried it twice to no avail. I was able to go back to magisk and reinstall. I haven't lost anything. Ymmv...
I have magisk, and twrp installed on a pixel xl running android pie.
Whats the best way to install an ota update?
tails618 said:
I have magisk, and twrp installed on a pixel xl running android pie.
Whats the best way to install an ota update?
Click to expand...
Click to collapse
Sideload it.
I have lineageos 16.0 installed on this phone. And I am happy with it.
However, for a functionality, I need Xposed, and I read doing it as Magisk is healthier as it won't trip any detections.
I'm following the magisk tutorial's guide on Boot Image Patching, but I can't patch the OTA update that comes with LineageOS. I assume the OTA update zip from lineageos then does not count? Do i need to find the Sony stock image? Can anyone help out with that?
I see that the September update for the Pixel 3 XL moves us to Android 11.
I have been doing monthly upgrades of Android 10, but moving to 11 is going require a lot of work. I think Magisk canary supports 11. I dont see any support yet for EdXposed and Gravitybox. Since we just got TWRP, I wonder if that will still work with 11.
I plan to wait a few weeks before moving to 11. I hope that EdXposed, GB and TWRP will be updated by then.
What are other Pixel 3XL planning to do?
I tried the Magisk/OTA update to go from 10 to 11 but root didn't stick. Guess I did something wrong. Oh well... I'll patch the boot img later.
Same here. I have to wait until exposed is fully supported.
swieder711 said:
I see that the September update for the Pixel 3 XL moves us to Android 11.
I have been doing monthly upgrades of Android 10, but moving to 11 is going require a lot of work. I think Magisk canary supports 11. I dont see any support yet for EdXposed and Gravitybox. Since we just got TWRP, I wonder if that will still work with 11.
I plan to wait a few weeks before moving to 11. I hope that EdXposed, GB and TWRP will be updated by then.
What are other Pixel 3XL planning to do?
Click to expand...
Click to collapse
Magisk root via canary magisk manager worked fine for me today and have rebooted a few times
Delete
prot- said:
Magical root via canary magisk manager worked fine for me today and have rebooted a few times
Click to expand...
Click to collapse
Canary magisk manager worked for me too.
First Time it didn't show the Magisk-Version but i got root (Adblock worked). Now it shows the right Version (20424)
davion27 said:
Canary magisk manager worked for me too.
First Time it didn't show the Magisk-Version but i got root (Adblock worked). Now it shows the right Version (20424)
Click to expand...
Click to collapse
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
I got Android 11 on Tuesday by opening the system update page in settings.
paulyt989 said:
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
Click to expand...
Click to collapse
After Update to Android 11, i installed Canary Manager (nice blue layout!) and patched the boot.img. Steps are the same i always used to install the patched boot.img: "fastboot flash boot --slot all boot.img"
paulyt989 said:
should i install magisk canary on android 10 before I update to android 11? Currently on stable magisk with stock android 10? Are the steps also the same when using fastboot also?
Click to expand...
Click to collapse
[Guide] Root Pixel 3 XL Android 11 (R)
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.