Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
markokrstic0507 said:
Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
Click to expand...
Click to collapse
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Badger50 said:
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Click to expand...
Click to collapse
Tnx for fast reply
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Strephon Alkhalikoi said:
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Click to expand...
Click to collapse
Roger that my friend. I've just seen some folks have trouble when updating after a few months :good:
@Badger50: Understood there. I should have known there was a reason for you mentioning it.
I had the same problem when i buy my used pixel 2 xl, i solved the problem by this way
visit: https://www.google.com/android/beta
and unsubscribe my device from beta program. After some hours i receive ota
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
markokrstic0507 said:
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
Click to expand...
Click to collapse
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
BabelHuber said:
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
Click to expand...
Click to collapse
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
markokrstic0507 said:
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
Click to expand...
Click to collapse
This has nothing to do with root, but with TWRP. Have you flashed it or not?
You can try to flash the boot.img again, too. Extract it from the factory image and flash it with fastboot. Of course this only helps if you have messed around with it.
If this doesn't work you can try a factory reset or flash the update manually. See https://developers.google.com/android/images for instructions.
Related
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.
I've got the OTA update waiting for me to select to get the November update but I don't want to risk losing the ability to unlock to bootloader if I ever want to in the future because I'm not sure of the bootloader unlockability for Bell bought devices. So if I unlock the bootloader do I lose anything, can I still get and take OTA updates from Google in the future?
You're phone will do a factory reset when unlocking the bootloader, so you'd want to back everything up. You can also still update with an unlocked bootloader.
Sent from my Pixel XL using Tapatalk
gonzo237 said:
You're phone will do a factory reset when unlocking the bootloader, so you'd want to back everything up. You can also still update with an unlocked bootloader.
Click to expand...
Click to collapse
But will you still be able to re root after the update is installed....Verizon?
canemaxx said:
But will you still be able to re root after the update is installed....Verizon?
Click to expand...
Click to collapse
Yes
cwalker0906 said:
Yes
Click to expand...
Click to collapse
I do have to unroot to update though correct? Sorry I been out of the game for a while. If I do a full unroot via SuperSU I will have to push SuperSU back to my phone after right?
canemaxx said:
I do have to unroot to update though correct? Sorry I been out of the game for a while. If I do a full unroot via SuperSU I will have to push SuperSU back to my phone after right?
Click to expand...
Click to collapse
No you can go to stock recovery and from your computer sideload the factory ota image of the updated software, its on the google dev site at the link below just go to the pixel xl section and the updates ota images are there.
https://developers.google.com/android/ota
M9guy said:
No you can go to stock recovery and from your computer sideload the factory ota image of the updated software, its on the google dev site at the link below just go to the pixel xl section and the updates ota images are there.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
First time side loading. Does side loading the newest stock image wipe everything? Or upgrade over it.
tommyntpham said:
First time side loading. Does side loading the newest stock image wipe everything? Or upgrade over it.
Click to expand...
Click to collapse
Sideloaded last night. Didn't wipe anything. Will lose root but rooted phone right after update completed with no issues.
Should I install the image for Verizon or would it be more safe to use one of the other images?
Just unlocked, rooted (w/Magisk), and installed TWRP about a week ago. I'm on the stock ROM with the Feb security update. The March security update is pushing to my phone but fails install due to the previous mentioned items. I'm reading that a few problems are popping up that are contributed to the update so I'm holding off on installing it for now. How can I get it to quit trying to install it and showing the notification in the status bar? You can't dismiss the notification and if you reboot it tries to install the update again..
How did you install TWRP and keep it across updates?
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update. A week or two later the March security update was released and pushed to my phone as an OTA but it fails install due to (and I'm guessing) the unlocked bootloader and root. Now I constantly have a failed install message in my notification bar and it won't go away. How can I keep the phone from attempting to install the OTA Update knowing it will fail?
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
altwu said:
the ota update is failing to install because your phone is rooted. the bootloader can be unlocked, but otas will fail to install if the os is not completely stock.
if you manually flash the march update, whether it's the ota or the full factory image, the notifications about an update being available or the failed install will go away.
Click to expand...
Click to collapse
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
When I got the notification to update, I just long pressed on it and hit the toggle to turn off notifications from whatever it was that it said it was coming from...Google play services I think?
Sent from my Pixel XL using XDA Labs
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
kboya said:
I flashed the full March Factory Image using the flash-all.bat script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
Did you try turning off automatic update in Developer mode.
No, to me that is a no no especially if you have Flashfire installed
Gulfstream 650 said:
I understand the reason it's failing. I don't really want to install the the OTA as I'm reading it has created additional problems. Is there anyway to keep the phone from checking for an update and subsequently failing and showing the notification?
Click to expand...
Click to collapse
kboya said:
I flashed the full March Factory Image using the bat.all script (-w removed to keep data), then fastbooted into twrp 3.2.0.0 and flashed magisk. No additional problems or any issues at all.
Click to expand...
Click to collapse
same here. no problems with the march update + magisk. i've never updated using an ota. i always flash the full factory image.
Gulfstream 650 said:
Thanks for the response! I'm not 100% sure what you're asking, but I installed TWRP and magisk while on 8.1.0 and the Feb 2018 security update.
Click to expand...
Click to collapse
Let me elaborate:
Right now, if you install TWRP permanently, you don't get any OTAs. So you must install a full image. When you install the full image, TWRP get's wiped. So you always have to install TWRP using your computer. That's a real hassle for me.
Or is there any easy way how you can install a full image, while keeping TWRP or reinstalling TWRP on top without using a computer?
fiverings said:
Did you try turning off automatic update in Developer mode.
Click to expand...
Click to collapse
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
kboya said:
I'm not sure if this is a question to me or the OP!
Me? No, there's no need as once flashed any OTA notification is redundant and no longer displayed. Anyway, I usually dl and flash the new factory image when it's posted online. The whole process takes maybe 20 mins including the dl time. Also, if there are any "new issues" with a release, as the OP is suggesting, it's just as easy to go back a month with the previous factory image (easier as it's already dl'd)
Click to expand...
Click to collapse
Good point, it's fairly easy to revert to the previous version if problems crop up. I'm going to go ahead and make the plunge. **edit** installed the March image and reinstalled TWRP and Magisk, so far so good.
Cool. Hope it stays that way.
I guess I have something to do when I get home. No update to platform tools.
https://developers.google.com/android/images
https://developers.google.com/android/ota
All seems good so far. Supposedly the charging issue is fixed...
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
moyses said:
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
Click to expand...
Click to collapse
if you're rooted, then the ota won't apply via the google system update. your rom has to be completely stock in order for it to work. your bootloader can be unlocked. i don't know about flashing the ota via twrp. i've never done it.
Bramton1 said:
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Click to expand...
Click to collapse
correct, they will not allow a user to downgrade. there isn't a downgrade method available for locked bootloaders.
Gulfstream 650 said:
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
Click to expand...
Click to collapse
if you flash the full factory image, yes, you can flash the may update over the march update. i don't know about the otas though. i always flash the full factory image.
Does anyone know if I can flash the OTA on my nonrooted Pixel XL through TWRP ?
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
rfkd said:
Hi, I just tried to install the September OTA update based on the Magisk OTA installation tips however the installation of the update fails during step 1. At least I am still rooted on the August patch level. How can I update my phone without losing data? I thought about reflashing system and trying the steps again but I don't know where to get the factory images for 9.6.6.0 (August) or 9.6.8.0 (September). This is my first A/B phone by the way. Thanks in advance.
Click to expand...
Click to collapse
You can check @BubuXP's reply here it might help you out. :good:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
rfkd said:
On this page only the ROM for 9.6.4.0 (July) can be downloaded. Later versions are not available anywhere? If not I have to flash July with fastboot, root again and retry the OTA update?
Click to expand...
Click to collapse
No, the only fastboot image at the moment is this. It should be not a problem downgrading, as long as the same Android version is involved (Oreo 8.1 in this case).
And yes, you can flash that fastboot image and then follow my guide to install Magisk, and then install the OTA update always following my guide, just to test that everything is working as intended.
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
rfkd said:
This did not work. Seems like using flash_all_except_storage.bat was not the right choice, my unlock pattern during booting is not accepted.
Click to expand...
Click to collapse
So you must use flash_all.bat, but you will lose your data. At the moment the data is in the phone memory, but is encrypted and you probably lost the decryption key when you flashed the other partitions, so not a great lose anyway.
I don't know if there is a way to get your data back.
Yes, I already did this. Had forgotten to disable the pattern.