Develop Bugs

Running Magisk - ElementalX What's the best way to Manually Update

Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.

https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.

Best way to upgrade to O from current state? Stock 7.1.1 rooted.

So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!

If you don't want to wipe just update through factory image, just open the factory zip, open flash-all file and remove "-w" from last line, then execute it (update without wipe)
But I suggest to flash the stock factory image with the "-w" to make a clean install, flashing major release like 7.x -> 8.x is always better wipe to avoid potential issues.
But yes, you can first give a try without wipe and only if you find bugs try wiping. Your choice.

simply flash the OTA, then re-root

xraystyle said:
So I have a Play Store Pixel XL running stock 7.1.1, rooted, with TWRP 3.0.2-0-RC1 recovery.
Most upgrade guides I've read seem to assume stock recovery, or no root to start, or some such.
What do I need to do to get to Stock Android O, rooted? If I need to wipe the phone I can, but I'd prefer not to if I can avoid it.
Thanks!
Click to expand...
Click to collapse
Use full unroot in supersu. Then take ota. Then root again after upgrading to O

Thanks for the help everyone, you pointed be in the right direction.
In the event that it might help someone else, here's what I ended up doing:
1. I downloaded the OTA, booted into the TWRP I had currently installed, and then sideloaded the OTA.
2. I used ADB to push the newest TWRP flashable zip, the latest SuperSU, and the latest SU-Hide to /sdcard on the device.
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
4. Finally, I rebooted to recovery on the phone (latest TWRP now instead of stock), and flashed SuperSU and SU-Hide.
I'm now stock, rooted, on O. No wipe necessary, kept all my apps and data. So far the OS itself has been entirely stable. I had an issue or two with a few apps after the upgrade, but those were fixed with a quick re-install. Except for Better Terminal Emulator Pro, seems it doesn't want to work on Oreo and it's no longer under active development. It's fine though, there's other terminal emulators out there.
Thanks again for the help!

xraystyle said:
3. I then used the most recent TWRP bootable img, booted into it with fastboot, and used it to flash the TWRP zip I had previously pushed to the phone storage. I then had the OTA with the latest TWRP installed on the phone.
Click to expand...
Click to collapse
Which version of TWRP do you have TWRP working with Oreo 8.0?
I can boot into the modded TWRP 3.1 (fastboot boot twrp-3-1-pixel-bootable-mod.img) but AFAIK there is no working flashable recovery for 8.0 yet.

quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.

gordonlw said:
quick question, are the steps the same for stock root 7.1.2? I've never installed twrp. I've fastbooted to it to root and that's it. I'm familiar with that as I've sideloaded all the ota security updates and the re-rooted.
my main question is su-hide required? I have never done it and have no reason to that I'm aware of. Seems all the guides I see involve su-hide and flashing kernels etc. I've never changed kernels since having the pixel. Really just want root for adaway.
I plan to do a clean install of O and then hope to root with fastboot twrp to flash supersu.
Click to expand...
Click to collapse
That's how I did it. I don't use suhide.

Does the -w in the .bat file format or wipe the data? I want a clean clean , o-fresh in the morning feeling kind of wipe

toknitup420 said:
That's how I did it. I don't use suhide.
Click to expand...
Click to collapse
Thanks! What I ended up doing:
Decided to try and unroot and take the ota. super-su full unroot would not work. so I fastbooted to the mod twrp and flashed UPDATE-unSU. I then took the ota. then fastbooted to mod twrp and flashed super-su. worked perfect!

How to update from Magisk rooted 8.1.0 to 9.0 and then root with Magisk again?

I did some searching, but could not see a guide for moving from Magisk rooted 8.1.0 to Magisk rooted 9.0. I believe I need to uninstall Magisk, then install the update, but not sure of the exact process. Also, is it better to wipe the data when going from 8.1.0 to 9.0 or doesn't matter?
Thanks in advance!

There's two ways you can do this.
One, you can sideload the OTA using ADB (if on stock recovery), or you can flash the OTA through TWRP.
Two, you can download the factory image, and manually flash the bootloader and radio, then update /system WITHOUT the -w flag, if you don't want to wipe data.
Any time you flash a software update, whether it's the OTA or the factory image, it WILL overwrite /boot, so you will lose Magisk and any custom kernel and recovery. Simply boot TWRP using fastboot, flash Magisk (and TWRP and kernel if desired), and you'll be good to go.

No need to wipe data. My process for installing OTAs and re-rooting has always been the same and it's no different with the 9.0 update other than one exception I encountered (patching the boot image AFTER updating).
I prefer the boot image patching method:
Download the latest platform-tools from Google
Download both the OTA and full factory images
Extract boot.img from the factory image
If already rooted prior to updating, re-flash current stock boot image
Sideload OTA
Patch the extracted boot image with Magisk (make sure you're on the latest version; 16.7 beta channel)
Flash patched boot image
Normally I patch the boot image prior to sideloading the OTA but it resulted in an endless boot after the 9.0 update.

Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?

machx1111 said:
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
Click to expand...
Click to collapse
Here's a bit more specific guide for updating to 9.0
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77269862

Unable to install Magisk Zip on November update

Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks

Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Very strange, but it just worked, after the 20th time of doing the same thing. Who knows why

Hey, my issue with Magisk is a bit different. I've upgraded my Pixel 2 XL every month and flashed Magisk afterwords. What I keep running into for the past couple of months is that after I'm all done, I will get a notification that there's an update to Magisk, but it's the same version I already have. I've tried different versions from 16.7 to the beta 17.3 and I would always seem to lose root after a while and be prompted to download the update to Magisk. Any help is greatly appreciated! Thanks in advance.

I am having the same issue with magisk after updating to nov update. Did the flashall then booted twrp and flash magisk Not sure why
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse

Run the Magisk uninstaller first

run 17.1 or the uninstaller. i've had better luck with 17.1

I guess the issue is linked to the Active Edge Module!
Download "uninmod_magisk", install it via TWRP, execute it via Terminal in TWRP, delete the Active Edge Module.
Now you can boot and reinstall that module.

Magisk problems since most recent OTA

I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.

theburrus1 said:
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
Click to expand...
Click to collapse
It's only possible to install twrp if you also install a GSI. Twrp will not work on stock. Magisk is also incompatible with twrp, the two can never be installed together no matter what. This is a magisk problem. Magisk uses the recovery partition, so it can use mirrors to make changes (systemless root). Twrp also needs to occupy the same place, because twrp is a custom recovery. Because of this conflict, they can't coexist. Magisk needs you to boot into "recovery" to boot the normal OS with root, and twrp needs you to boot into recovery to operate normally. So it's one or the other.
Unless the developer of Magisk decides to use system root, all newer devices will continue to have this problem. I highly doubt that will change anytime soon. The foundation of Magisk is built on being systemless, and so are all the modules for it.
If you want to use magisk, install the app, and patch your boot.img with it as "recovery", then flash it with fastboot. You must always "reboot recovery" to keep root afterwards.