Most guides here are about rooting with SuperSU. Last month I decided to go with Magisk instead, since development of SuperSU came to an end. I did a complete wipe, installed Stock (8.1.0, patch level June 2018) and Magisk, then restored my Apps with Titanium Backup. Happy ever after.
Now the July update is available and the tablet offers an OTA.
With SuperSU all OTAs ended in bricks, loops, whatever.
I'm curious what the prerequisites are for a successful OTA. Do I need to uninstall Magisk?
None.
Boot into TWRP
Sideload the OTA
Reboot to finalize update
Rebootinto TWRP
Install Magisk.zip to restore root
reboot
your done
Related
It's been awhile since I've used a custom recovery. Since I've had this phone I've used systemless root and flashfire to install OTA's and that has worked fairly well. Recently my phone bootlooped and google sent me a new one.
I just unlocked it, installed TWRP and Magisk, but was wondering what the best way to upgrade the phone would be.
1I've heard flashfire works with Magisk, but I never had much luck with custom recovery's and updating with flashfire.
If flashfire doesn't work, what would be the best way to update?
When 7.1.2 is released, could I just flash the system, radios, etc. from fastboot and then reflash magisk from TWRP and be upgraded?
I had to uninstall magisk, reboot, download the ota via the system menu and install it, then re-flash twrp, then boot recovery and flash magisk, then re-add my modules and re-enable systemless adblock
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!
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
Hi all,
I'm on the November update, rooted still with stock recovery, magisk 17.3, custom kernel, substratum and a few modules installed via magisk.
to get the December update installed, I am trying to figure out best way. Do I download the December update, then unzip to my adb folder where all tools are installed. Then, flash the update removing the "-w" to maintain data. Then, without rebooting, flash the twrp image, then magisk?
TheFuzz said:
Hi all,
I'm on the November update, rooted still with stock recovery, magisk 17.3, custom kernel, substratum and a few modules installed via magisk.
to get the December update installed, I am trying to figure out best way. Do I download the December update, then unzip to my adb folder where all tools are installed. Then, flash the update removing the "-w" to maintain data. Then, without rebooting, flash the twrp image, then magisk?
Click to expand...
Click to collapse
What you described is how I plan to upgrade. Clean install with -w removed. I made too many tweaks to try and unwind them manually (TWRP, Magisk, custom kernel, Tulsa mods, etc).
swieder711 said:
What you described is how I plan to upgrade. Clean install with -w removed. I made too many tweaks to try and unwind them manually (TWRP, Magisk, custom kernel, Tulsa mods, etc).
Click to expand...
Click to collapse
I've had some issues with some of the mods I've done so I'm thinking better to start fresh and build back what I like. I looked over the thread on how-to root pixel 3 with magisk and seems like following the first part, covering "if coming from rooted September software guide" seems the logical directions to follow?
Answered my own question with the incredible help of the how to guide!
Removed the -w did not uninstall any mods at all, left my phone exactly as it is on November update with all my themes and modules installed.
Flashed the update in fastboot, rebooted to operating system
Went back into TWRP img and flashed magisk 17.3 and rebooted. Everything was still on device and magisk modules were still working
Had to reinstall substratum theme which was a good thing because I had messed up a few things.
Flashed @Tulsadiver mods for home screen no search and app drawer, rebooted and all is good!
Off topic but can't find any information. Can you uninstall substratum themes from manager? I can't on mine. Same exact setup.
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
Since you are having problems with updating via OTA, suggest either using flash-all method or Android Flash Tool to update to March build. Then patch boot image using either Canary 24301 or Stable 24.3. Make sure to disable mods before rooting.
No such thing as a match update
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
I would use the Android flashtool and download the factory image , patch the boot image then flash it in fastboot. No loss of data, just make sure you don't check any of the boxes like 'wipe device' or 'lock bootloader' in flashtool settings
I just flashed March. Used all old school flashed with latest adb and fastboot
Disabled all the magisk modules just in case.
Patched March update boot file in Magisk
Had the update for Magisk and did not do it at this point, as I had heard people having issues with that.
booted into bootloader Flashall.bat removing -w
booted into phone, waited for update to finish in the notifications.
booted phone back into bootloader, installed magisk boot image
Booted phone back up
enabled all magisk modules
Updated magiskapp, then updated root via direct install
Rebooted phone
And all good