Sideloading OTA vs flashing full factory image

[savi0]

I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?

 

[Scythe]

There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.

 

[savi0]

Thanks for the info. Couple more questions:

1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.

 

[5.1]

Thanks for the info. Couple more questions:

1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.

Hello,

1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.

Cheers...

 

[sliding_billy]

Hello,

1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.

Cheers...

To clarify your meaning... The May Verizon OTA does or does not break root?

 

[5.1]

To clarify your meaning... The May Verizon OTA does or does not break root?

Hello,

Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).

Cheers...

 

[savi0]

To clarify your meaning... The May Verizon OTA does or does not break root?

Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.

Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

 

[5.1]

Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.

Hello,

If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...

Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.

Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.

If you want those, flash the April bootloader as stated in other threads talking about the issue...

Cheers...

 

[savi0]

First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.

If you want those, flash the April bootloader as stated in other threads talking about the issue...

Cheers...

Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.

You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.

 

[5.1]

Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.

You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.

Hey,

As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.

Cheers...

 

[sliding_billy]

Hello,

Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).

Cheers...

That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.

 

[5.1]

That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.

Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...

Normally, we won't have to wait too long to get back TWRP/Root.

Cheers...

 

[alluringreality]

I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.

Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/

 

[5.1]

Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/

Hello,

I don't understand what you mean when you say:

That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update

If you have issues, just sideload the latest OTA from Google here:

https://developers.google.com/android/ota

Instructions are available on this page.

Good luck...

 

[sliding_billy]

Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/

I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.

 

[alluringreality]

Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/

 

[PrettyPistol555]

Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.

You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.

Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?

Sorry, but this is getting Hella confusing.

I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip

Do I need to worry about anything flashing this build?

Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1

Wish there was a forum for us with Verizon Pixels and Unlocked BL's...

 

[GuestK00254]

Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?

Sorry, but this is getting Hella confusing.

I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip

Do I need to worry about anything flashing this build?

Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1

Wish there was a forum for us with Verizon Pixels and Unlocked BL's...

If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.

 

[PrettyPistol555]

If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.

The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?

Thanks for the reply! I appreciate it greatly.

 

[GuestK00254]

The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?

Thanks for the reply! I appreciate it greatly.

Yep.