Best/Safe way to Update - Google Pixel 2 XL Questions & Answers

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!

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.

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...

Prep for December patch

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

Help Updating to December Security Patch

I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.

[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!!

Categories

Resources