Prep for December patch - Google Pixel 3 XL Questions & Answers

I have made a lot of changes to the November build such as TWRP, root with magisk, custom kernel and Tulsa mods to the systemUI and framework.
I am thinking that I will need to reset to factory default in order to get the December update. I have not done a factory reset yet.
Sounds like I use Flashall.bat with the - w option removed and the phone in Fastboot mode.
Do Magisk or TWRP need to be removed before Flashall?
Will there be a full December build or do I flash an old build and then take the updates?
Any other suggestions on the best way to update to the Dec build?

swieder711 said:
I have made a lot of changes to the November build such as TWRP, root with magisk, custom kernel and Tulsa mods to the systemUI and framework.
I am thinking that I will need to reset to factory default in order to get the December update. I have not done a factory reset yet.
Sounds like a use Flashall.bat with the - w option removed.
Will there be a full December build or do I flash an old build and then take the updates?
Any other suggestions on the best way to update to the Dec build?
Click to expand...
Click to collapse
There Dec flash-all batch file, without the -w, will over write all your modifications and that's all you should need to do. It's always best to backup everything you can just in case.
Sent from my [device_name] using XDA-Developers Legacy app

So can you not download the ota from Google's website and flash it in TWRP? Then just flash TWRP and root again before rebooting?

hatdrc said:
So can you not download the ota from Google's website and flash it in TWRP? Then just flash TWRP and root again before rebooting?
Click to expand...
Click to collapse
Not in TWRP, but you can ADB sideload it then reroot. The flash all after removing the-w also saves data and apps.

hatdrc said:
So can you not download the ota from Google's website and flash it in TWRP? Then just flash TWRP and root again before rebooting?
Click to expand...
Click to collapse
If you don't install the permanent TWRP, and just use the bootable image, you can place the OTA on your phone and use the stock recovery to install it. The OTA will install without wiping data.

spotmark said:
If you don't install the permanent TWRP, and just use the bootable image, you can place the OTA on your phone and use the stock recovery to install it. The OTA will install without wiping data.
Click to expand...
Click to collapse
Right, but then you need to reroot with a PC. I have TWRP permanent so I was hoping you could just boot into TWRP and flash it, then flash TWRP again and then root and be back to the way it is now.
So in my case I need to just download the images, remove -w and then flash. Temp boot TWRP and flash root. Don't think I'll put TWRP on permanently this time since that was the only reason I did the last time.
Thank you everyone for your help

Related

How to update OTA with Magisk (can I just sideload without risk of bootloops)?

So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
I'm on 8.0 October Security Patch. My main aim isn't to remove Magisk, but I guess I have to to update to the Nov patch, and then reinstall it
brpqzme said:
So I can't remove Magisk ("stock boot.img backup does not exist") so I was wondering if it was safe to sideload the November OTA (the whole 1GB file, not sure how to do just the 60MB delta update) and I assume that removes Magisk but keeps userdata, but does that cause any issues e.g bricks or bootloops?
Click to expand...
Click to collapse
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work download the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Homeboy76 said:
First, try the
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
If that doesn't work down the appropriate Factory Image for your phone.
Go to Android 8/Oreo and do #5 to save data.
Click to expand...
Click to collapse
brpqzme said:
I'll give this a shot now!
Do I need to disable any Modules before flashing the ZIP? Couldn't find a definite answer searching online
Click to expand...
Click to collapse
I don't know, but I don't think it would hurt to disable the modules.
Just don't lock the bootloader.
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
brpqzme said:
So in case anyone else reads this -
For some reason, flashing the MAGISK UNINSTALLER ZIP caused a soft brick (device would boot only into fastboot and then "NO COMMAND", not boot into OS).
I'd already downloading the factory images from your links, so I flashed BOOT.IMG onto both slots, A and B.
Device then booted back into the OS, no data lost etc. But Magisk w
Still wouldn't accept OTA.
Flashed OTA as per the link you gave with flashall, worked fine. Will flash Magisk through TWRP next.
Thanks
Click to expand...
Click to collapse
Please go to the link below and post the information about the problem Magisk-uninstaller-20171123.zip caused:
[2017.11.23] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Why? So, topjohnwu can fix it or tell you why it didn't work. The link above is where I got the 'Latest Uninstaller (Support v1+)' from.
Also it would help if you add the make and model of your phone, Magisk- version you were trying to uninstall.
Flashed OTA as per the link you gave with flashall
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
AlPoo said:
Posting here instead of creating a new thread.
Same issue as OP except i have TWRP installed as well, so SYS.img is altered as well so i can't take OTAs. Does the factory image also contain system flash?
On the OTA page, it says make sure your device is up to date, but im on October's image and cannot move to November's. Should i flash October and let it OTA to current or safe to flash November. Thinking of just going to 8.1 beta but one step at a time.
Click to expand...
Click to collapse
When you go to settings System Updates can you update?
If not Download the appropriate (October 2017) Factory Image for your phone.
Go to Android 8/Oreo and do #5 to SAVE data or #4 to WIPE data.
This will remove root and you should get the OTA.

How to update android on customized kernel?

I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
HushCha said:
I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
Click to expand...
Click to collapse
Use the search button, there even is an own thread for this here. Don't expect to get the information spoon-fed :laugh:
Download the ota zip file from Google and flash it via twrp.
Afterwards flash kernel, twrp and magisk BEFORE REBOOT
Sui77 said:
Download the ota zip file from Google and flash it via twrp.
Afterwards flash kernel, twrp and magisk BEFORE REBOOT
Click to expand...
Click to collapse
Twrp, kernel, then magisk is the proper order. Me, personally, I prefer to flash factory images with -w removed from flash-all.bat. It's always been reliable for me.
DuckRuckus said:
Twrp, kernel, then magisk is the proper order. Me, personally, I prefer to flash factory images with -w removed from flash-all.bat. It's always been reliable for me.
Click to expand...
Click to collapse
I agree I flash factory image now that twrp decrpts I then boot twrp img and flash magisk then I'm all set. I don't use a custom kernel.
HushCha said:
I using pixel 2xl running android p with kiriskura kernel.
It’s can’t update android via ota.
Does it has other way to update without wipe data ?
Click to expand...
Click to collapse
I use deuces script. It works great for me every time I upgrade.
Whats best about it is it upgrades both the slots. A lot of people mess up side a/side b and hork their phones. Deuces script fixes their installs, and upgrades with it are flawless.

Best/Safe way to Update

Good morning all,
I am on the first version of android 9 and would really like to update because of many bugs. I have root and FlashKernel that I installed by temp booting to TWRP (without install). That seems to have broken my OTA. What is a safe way to update to the latest version of the OTA?
joshuadjohnson22 said:
Good morning all,
I am on the first version of android 9 and would really like to update because of many bugs. I have root and FlashKernel that I installed by temp booting to TWRP (without install). That seems to have broken my OTA. What is a safe way to update to the latest version of the OTA?
Click to expand...
Click to collapse
Either temp boot into twrp again and flash the latest OTA zip, or, fastboot the factory image with the -w removed from the flash-all.bat file. Neither will wipe your data. Always a good idea as well to backup all your data before you begin, and to remove screen lock security and substratum themes so as not to have any unwanted problems :good:
Badger50 said:
Either temp boot into twrp again and flash the latest OTA zip, or, fastboot the factory image with the -w removed from the flash-all.bat file. Neither will wipe your data. Always a good idea as well to backup all your data before you begin, and to remove screen lock security and substratum themes so as not to have any unwanted problems :good:
Click to expand...
Click to collapse
Awesome, thanks! I figured that was all it took but I wanted to double check so my Sunday isn't spent unbricking. All went smooth. 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!!

Updating Pixel 3 XL and keeping root without wiping data

Hi, I have a Pixel 3 XL it has the February update and it's rooted and has TWRP installed. My question is can I update it via a flashable zip file so I can flash through TWRP? I don't want to lose any of my data because it's a pain setting everything back up. Back in the day I had Cynogen and usually kept up with the nightly updates as often as I could and it was a very simple process. I"m sure it's been asked but after doing some quick google searches all I found was to download the factory image and flash it with a custom flag but I really don't want to have to re-root it and all that again.
Well when you update just edit the flash-all.bat file and delete the -w within that and you won't delete your data. You will loose root and loose the installed twrp but you can easily reinstall and obtain root after the update is completed. Check the guides section of the boards as it has an excellent guide for rooting and updating with Google released updates.
GrandMstrBud said:
Hi, I have a Pixel 3 XL it has the February update and it's rooted and has TWRP installed. My question is can I update it via a flashable zip file so I can flash through TWRP? I don't want to lose any of my data because it's a pain setting everything back up. Back in the day I had Cynogen and usually kept up with the nightly updates as often as I could and it was a very simple process. I"m sure it's been asked but after doing some quick google searches all I found was to download the factory image and flash it with a custom flag but I really don't want to have to re-root it and all that again.
Click to expand...
Click to collapse
Flashing the Google image every month and editing the flash-all script is just what you have to do for A/B phones. The whole process takes less than 10 minutes once a month, and after some practice, probably 5 minutes. Pre-stage the latest TWRP and Magisk on your phone if it is not already there. Once you finish flashing the image, fastboot boot TWRP from your PC and then from your phone use TWRP to queue up both the TWRP and Magisk zipfiles and let her rip. If you use a custom kernel as well, you can do a 3-fer and queue up all three files in TWRP and it will flash all 3 in succession. Just make sure you are using the lastest version of the fastboot/adb binaries before you start. That is all.
Thanks guys, I had to refresh my memory on the process but all together maybe 20 minutes. Next time I'm guessing the process will take 10 minutes since I made some instructions for myself.
I only use temporary TWRP, so when it's time to update I just flash the OTA using stock recovery. No wipe or editing involved.
spotmark said:
I only use temporary TWRP, so when it's time to update I just flash the OTA using stock recovery. No wipe or editing involved.
Click to expand...
Click to collapse
Interesting.
You install Magisk, and at what step do you do that?
Thanks in advance.
Below works, but not always. Be near a computer when you do it and be prepared to use the flash-all without the -w.
1.Magisk Manager → Uninstall → Restore Images). Do not reboot or you will have Magisk uninstalled.
2. Now Update the system and let it install completely. Do not press the reboot button.
3. Go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk.
4.Once Magisk installation is done, press the reboot button in Magisk Manager.
Your phone may get into bootloop once, if that happens just restart the phone again.
statustray said:
Interesting.
You install Magisk, and at what step do you do that?
Thanks in advance.
Click to expand...
Click to collapse
After I flash the update, I boot the phone, and then into temporary TWRP and flash Magisk.

Categories

Resources