I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
xSpartacusx said:
I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
Click to expand...
Click to collapse
You should be fine. While I haven't done it personally, I've seen several that have ??
Related
Long story short, I tried to sideload ota onto my 5x, and there was something wrong with my laptop usb port, half way thru installation interrupted because usb was disconnected. Now think just bricked the phon't e. I am still have stock recovery, non rooted. Cant even flash the image becuase I can't turn on the phone to select the “Enable OEM Unlock” checkbox to perform next step. Any help would be appreciated. Now I get "device is corrupted" msg. Can't do anything with the phone.
You need to flash the full OTA in stock recovery. This method does not require an unlocked bootloader. It is the N preview. I don't know if Google has ever released full OTA zips for any of the other updates.
After flashing it you need to enable oem unlock in developer options then unlock the bootloader via fastboot before you can clean back to M.
Details on how to do this and the OTA zip are in this official post:
http://developer.android.com/preview/download-ota.html
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
You need to flash the full OTA in stock recovery. This method does not require an unlocked bootloader. It is the N preview. I don't know if Google has ever released full OTA zips for any of the other updates.
After flashing it you need to enable oem unlock in developer options then unlock the bootloader via fastboot before you can clean back to M.
Details on how to do this and the OTA zip are in this official post:
http://developer.android.com/preview/download-ota.html
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
good deal, I already packed up the 5x and ready to ship it back to google and call it a day, was thinking to keep my moto g3 until the next nexus come round. Because if I gonna ship it back and won't go thru the trouble to wait for another to come in and what not. Gonna give this a try, if still doesn't work, it will on its way back to the google warehouse and my money back to my cc. Should be no prolem flashing this full ota right? when I flash the ota(the partial march update ota zip), there was another msg saying "unexpected contenets on partition."
jdaclutch said:
good deal, I already packed up the 5x and ready to ship it back to google and call it a day, was thinking to keep my moto g3 until the next nexus come round. Because if I gonna ship it back and won't go thru the trouble to wait for another to come in and what not. Gonna give this a try, if still doesn't work, it will on its way back to the google warehouse and my money back to my cc. Should be no prolem flashing this full ota right? when I flash the ota(the partial march update ota zip), there was another msg saying "unexpected contenets on partition."
Click to expand...
Click to collapse
Sorry I didn't get back to you sooner, Ive been out of the office (and coverage) all day. Flashing the full OTA should be like flashing the factory images. It will wipe out whatever is on those partitions and allow it to succeed. Good luck and let us know if it works.
Sent from my Nexus 5X using Tapatalk
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome
Hi there.
I used to have LineageOS on my Z2 Play, but I reverted back to stock firmware because I'm giving it to my parents and I want to avoid issues with it. During the process, I relocked the bootloader, but when I try to search for updates, it says it's already updated. However I'm still on February update and it's not sounding right. I'd like to get it back to automatic updates and stay away from fastboot flashing.
Is there any way to get OTA updates again?
zago27 said:
Hi there.
I used to have LineageOS on my Z2 Play, but I reverted back to stock firmware because I'm giving it to my parents and I want to avoid issues with it. During the process, I relocked the bootloader, but when I try to search for updates, it says it's already updated. However I'm still on February update and it's not sounding right. I'd like to get it back to automatic updates and stay away from fastboot flashing.
Is there any way to get OTA updates again?
Click to expand...
Click to collapse
First question is how did you lock the bootloader.
I will start this thread by saying I f*****up, recently my pixel 3 xl is giving me various issues like system glitches, so many app reloads , Trash battery, so what a person in right mind will do UNLOCK THE BOOT LOADER and install other rom.
Then when i boot up in new room, i got to know I cant use google pay of which I am a huge fan of.
Then I flashed back the stock rom from googles website using FLASHH-ALL.BAT still the google pay doesn't work.
I want to completely make my pixel 3 xl stock, and lock the boot loader and get rid of it as there are too many tradeoffs in performance.
Can someone please give me a guide how to completely make it stock and lock the bootloader ?(WITHOUT BRICKING IT):crying:
Panda1213 said:
I will start this thread by saying I f*****up, recently my pixel 3 xl is giving me various issues like system glitches, so many app reloads , Trash battery, so what a person in right mind will do UNLOCK THE BOOT LOADER and install other rom.
Then when i boot up in new room, i got to know I cant use google pay of which I am a huge fan of.
Then I flashed back the stock rom from googles website using FLASHH-ALL.BAT still the google pay doesn't work.
I want to completely make my pixel 3 xl stock, and lock the boot loader and get rid of it as there are too many tradeoffs in performance.
Can someone please give me a guide how to completely make it stock and lock the bootloader ?(WITHOUT BRICKING IT):crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117/
Read #3
You should try stock rom with custom kernel before locking.
Sent from my SM-P205 using Tapatalk
Panda1213 said:
I cant use google pay of which I am a huge fan of.
Click to expand...
Click to collapse
Take a look at this thread for instructions on getting GPay to work. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950. There are two methods. One is manual (the OP), and the other is using a Magisk module. https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176. I have been using the manual method since the day this was posted over 6 months ago. It has worked fine on Pixel 3, Pixel 3 XL and 3XL on various custom ROMs. All have worked on Pie and "Q."
I don't want to do anything related to root and magisk, i have a factory warranty but does brick cover in warranty if it happens after locking?
Flash full image and take one ota before locking. If ota fails you are not stock.
Sent from my Pixel 3 XL using Tapatalk
How to know I am 100% stock?
How to know if my phone is 100% stock, there are part a and b for rom or something, then there is boot loader. How to make it return to stock a 100%?