Develop Bugs

[Q] GNex OTA from 4.1.2 to 4.2 failed, phone bricked :(

Hi guys,
I had my GNex 4.1.2 with SuperSU root survival installed, when upgrading from 4.1.1 to 4.1.2 all went fine. But now, upgrade from 4.1.2 to 4.2 via standard OTA failed and I cannot get through the boot screen with Google text and image of opened lock. Any help would be appreciated.
Thanks.

Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!

manumanfred said:
Are you using Takju/Yakju or what version?
Download 4.2 factory image for Nexus: https://developers.google.com/android/nexus/images
you need to have fastboot files!
extract files from the .tar to fastboot folder and open batch (.bat) and it does flashing itself.
then download OTA!
Click to expand...
Click to collapse
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?

gabriel31337 said:
I have YAKJU. Your procedure will resurrect my phone with all the apps and settings, or will it wipe it to factory defaults?
Click to expand...
Click to collapse
If you don't want to lose data then you may need to flash manually!
I'm not sure does this keep all data but I think it will keep if just not using fastboot -w command..
Download the factory image and extract files from it to fastboot folder then also extract files from the .zip in .tar package to fastboot folder!
then open CMD (Command prompt) and then write cd /your fastbot folderdestination/ Example: cd C:\GalaxyNexusRootNew
and then when those is done then use exactly these commands:
Code:
fastboot flash bootloader bootloader-maguro-primelc03.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-maguro-i9250xxlh1.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
and finally:
Code:
fastboot reboot
and if that does not work then
Code:
fastboot-reboot

manumanfred said:
Code:
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.

easy way
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.

gabriel31337 said:
Is this step necessary? I didn't do it as I have found in different sources that this might wipe the user data which I didn't want.
Click to expand...
Click to collapse
not actually, it may boot well but may cause some issue so later in CWM wipe dalvik cache and cache

themaskofwraith said:
download toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310
install it, follow the onscreen instructions (use options 9 for download and install stock rom, after selecting your device) , have a cup of coffee, ur phone will be ready to use.
Click to expand...
Click to collapse
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.

gabriel31337 said:
The question still remains - will this wipe the user data and installed applications? I have upgraded to 4.2.1 now and it seems to be running fine, just used fastboot flash all the img files except userdata.img. Seems to be OK.
Click to expand...
Click to collapse
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..

manumanfred said:
you can also flash only system.img and boot.img and nothing else or flash Clockworkmod recovery and connect to PC and then use ADB to sideload ROM or use toolkit what is easy to use and on toolkit is many options so I think you can leave userdata away with that..
Click to expand...
Click to collapse
I don't want to mess with CWM or anything else non factory (apart from SuperSU ). I have restored the phone to 4.2.1 and rooted, apps and data have survived so I'm very happy again. Thanks a lot for your guidance. :good:

[Q] How to update to 5.0.1 from a rooted 5.0 ?

Hello everyone,
Need some help here, i don't want to factoy flash again, i have a nexus 7 2013 wifi on Lollipop (5.0) rooted with a custom kernel and TWRP.
How to update with the new OTA to 5.0.1, without loosing data and without having FC after the flash ?
Is there a way to flash it with TWRP or with Nexus Root Toolkit ?

I read that i can download the 5.01 system image from Google, extract the system.img from it and flash it in fasboot and i will conserve my data and be updated to 5.0.1.
Is that correct and without issues?

^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.

Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?

yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
Is running fastboot format cache necessary?

^I'm no expert but I can't see why not to run it, not going to hurt anything and could possibly save you some problems later.
anhhuy1605 I'd just go to the factory images page download it and do a full clean install. I would not recommend trying to upgrade from KK and keeping data. Though I'm sure it's worked fine for lots of people.

yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
It's all done, i flashed only the system.img then TWRP and elementalx, i can't live without the DT2W.
Thank You for your very detailed post.

anhhuy1605 said:
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
Click to expand...
Click to collapse
First thing first:
1. Uninstall any mod and busybox and xposed (Make sur that your system is clean) thant Unroot with supersu
2. Flash the stock boot (kernel) and stock recovery
3. Sideload the ota for 5.0 and flash it
Hopefully it will be allright but don't forget to backup your data with titanium backup to your computer.

Hello eddy0147,
from where did you get the system.img for 5.0.1?
eddy0147 said:
It's all done, i flashed only the system.img then ...
Click to expand...
Click to collapse
Thanks!
tungdil

tungdil said:
Hello eddy0147,
from where did you get the system.img for 5.0.1?
Thanks!
tungdil
Click to expand...
Click to collapse
If you decompress the new Factory Image from here : https://developers.google.com/android/nexus/images
You're welcome

Thank you very much! :good:
Actually I expected that this factory image would also only contain a system.new.dat just like the LRX21P did before. That's why I din't even have a look at it. I just downloaded and extracted it, and could convert it to a mountable image (using simg2img)
Cheers,
tungdil
P.S.: Just finished flashing Stock 5.0.1 as secondary ROM with MultiROM after building a flashable zip using this system.img. Thanks again eddy0147 for the hint :good:

Nexus 5x Recovery Startup Loop

Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help

RingPvP said:
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
Click to expand...
Click to collapse
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk

The_Automator said:
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help

RingPvP said:
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
Click to expand...
Click to collapse
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk

The_Automator said:
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.

RingPvP said:
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
Click to expand...
Click to collapse
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.

The_Automator said:
If you can boot into bootloader than the simplest thing to do is to download the nexus 5x image from googles factory image site. Extract that zip into your fastboot folder and double click flash all.bat. This will restore youre ur phone to factory defaults on the latest factory image. Alternatively you can just extract the boot image and use fastboot flash boot boot.img (but for this method youd have to download the factory image you already have installed which is why googlea self installer (flash-all.bat) would be easier
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already

RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
usually the folder you would want to place the image into is the platform tools folder and you would want to place the files in the directory (not a sub directory) and the mda89e is the first release the newest release from google is
6.0.0 (MDB08M) Link f5233f827a44f99e26722e349f3c9445 5867cc27a23257a47688fe180ec272f1152ddde2
But within the factory image there should be a zip called something like image-bullhead-MDB08M.zip open that zip and extract just the boot.img to your platform tools folder. Then you should be able to use
fastboot flash boot boot.img

RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
In your case, it should be: C:\Program Files (x86)\Android\android-sdk\platform-tools\bullhead-mda89e
In this folder your should see fastboot.exe

The_Automator said:
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
Click to expand...
Click to collapse
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .

RingPvP said:
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
Click to expand...
Click to collapse
Happy to help glad you got your phone sorted
Sent from my Nexus 5X using Tapatalk

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.

Applying OTA while running Magisk and a custom kernel

Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!

ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...

ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.

peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.

otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same

trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/

xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:

v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.

I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot

v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??

sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?

sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?