I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
vMAC said:
I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
Click to expand...
Click to collapse
On my phone, the file you are looking for does not exist at this location. Are you rooted and trying to take an OTA? If so the downloaded "incremental" OTA is never going to work. If you are bound and determined to use an OTA image, simply sideload the full OTA from recovery via adb, and if you are rooted why not just flash the full image via fastboot?
v12xke said:
On my phone, the file you are looking for does not exist at this location. Are you rooted and trying to take an OTA? If so the downloaded "incremental" OTA is never going to work. If you are bound and determined to use an OTA image, simply sideload the full OTA from recovery via adb, and if you are rooted why not just flash the full image via fastboot?
Click to expand...
Click to collapse
In the past I have been able to do the incremental OTA while rooted with Magisk without issue. Lately I have been having issues getting it to even acknowledge that an OTA is available. When checking my logcat it showed an attempt to locate that file and that is why I was checking to see if anyone had it.
The problem with doing a full image via fastboot is that I have to be tethered. I travel a lot and don't want to have to worry about getting to my home computer to get everything up to date. The previous ability to do an OTA with Magisk installed for my Pixel was perfect and efficient. Hoping to get back to that point.
vMAC said:
I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
Click to expand...
Click to collapse
I am on the December 5th update, rooted, and that file doesn't exist for me. Oddly enough, I don't have a pending update though. When I force it to check it tells me I am up to date.
Did you ever figure this out?
Related
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool
Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?
Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.
Sorry if this has been discussed elsewhere. I couldn't find anything about it specific to the pixel 3xl.
Has anyone tried Flashfire to install an OTA update?
I have it installed. It recognizes is an A/B partition device. I've seen that there are people that have done it on the pixel 2.
Just curious if anyone has given it a shot. If it was successful, what steps did they take?
Just looking to see if it's possible to take an OTA and maintain root with magisk using Flashfire.
I wouldnt mess with flashfire, it hasnt been updated in ages
I haven't had a chance to try it because my device doesn't get the OTA notifications right away and I get tired of waiting so I download and flash the factory image, but you could try topjonwu's OTA update instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
kmandel said:
I've been using the lazy method of rooting my 3XL from an arriving OTA.
https://topjohnwu.github.io/Magisk/tutorials.html
It works great, the problem is the OTA arriving. As was well publicized the December one never arrived, but the January one did. However, I never got the February so I'm still on January. I don't know if that was widespread. Finally, its now March 8 and I haven't gotten the March OTA., which is available on the factory image site. If I didn't get February automatically (and I do poll) I have to wonder if I will get March.
Is there a way to get the phone to treat a manually downloaded OTA the same way as one that was auto distributed? I know about the other ways to update and patch, but I like the OTA method.
Click to expand...
Click to collapse
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
ffchampmt said:
Your phone won't apply the OTA with a modified boot image (magisk modifies it).
If you want to get updates you'll need to manually flash the full system image with the -w removed from the bat file. Head over to the guides portion of the forum for instructions.
Click to expand...
Click to collapse
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
kmandel said:
If you look at the url at the top of the thread you will see that first you do is "Magisk Manager → Uninstall → Restore Images" before triggering the OTA install.
It does work fine, I've done it twice. The problem is that Google didn't download the OTA in December or February, and so far in March (though its early).
Click to expand...
Click to collapse
I did the Jan OTA update with Magisk and it worked great. I got tired of waiting for the Feb and Mar OTA's so I flashed the full Mar image yesterday. There's another thread with others having the same issue of not getting the OTA https://forum.xda-developers.com/pixel-3-xl/help/preparing-update-t4060613
This is happening to a lot of us. If you time it right you will see it say Preparing to update.....if you manually check before it has tried.
The preparing goes away and then it is stuck on you are up to date. Google found a way to pre check for root I think.
I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
I'm rooted on March's update. I can check for an OTA for you if that will help. I was not sure how to proceed without losing my root privledges!
---------- Post added at 05:39 PM ---------- Previous post was at 05:26 PM ----------
I just checked, it went to preparing and than it stopped. Hope that helps!
kmandel said:
I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
Click to expand...
Click to collapse
There is no super easy way to keep root with Magisk and the auto OTA.
Read #9. B. in this Guide.
Note: If you're using the XDA app: Tap the three dot menu => tap load in Browser => tap three dot menu tap open in Browser.
Homeboy76 said:
There is no super easy way to keep root with Magisk and the auto OTA.
Read #9. B. in this Guide.
Click to expand...
Click to collapse
#9B is exactly what I had been using and what I call the super easy way. The trouble is that I haven't got an auto downloaded OTA to use it with since January.
I'm not sure what you are telling me. Is there some way to use it with an OTA manually downloaded from the factory images?
kmandel said:
#9B is exactly what I had been using and what I call the super easy way. The trouble is that I haven't got an auto downloaded OTA to use it with since January.
I'm not sure what you are telling me. Is there some way to use it with an OTA manually downloaded from the factory images?
Click to expand...
Click to collapse
Edit: Suggestion: Re-Read #9.B.
Homeboy76 said:
If you have been using #9.B. to install the OTA image and keep root. You should know OTA updates must be turned off to do #9.B., and factory images are not the same as OTA images.
Suggestion: Re-Read #9.B. (all of it) again.
Click to expand...
Click to collapse
The toggle in Developer Options "Automatic System Updates, Apply updates when device restarts", refers to running the update automatically, not keeping Google from downloading the OTA either automatically or with a poll. I've always had the toggle as off.
As 9B says the toggle is "so it won’t install OTAs without your acknowledgement"
In the Months before December, and in January the OTA was auto downloaded and I had the option of installing it then, or later. I would just follow 9B at that point. This involves invoking "Settings → System → System Update" on the already downloaded OTA, but not letting it reboot until magisk does its magic.
On your other point, the factory image site has both the full system images and the OTAs. However, its not clear to me how I would trigger the manually downloaded OTA in the same way that "Settings → System → System Update" does with the auto/polled OTA downloaded by Google.
There is another thread on this were many if us are having the same issue while rooted. It seems Google is checking for root before it downloads now. And if you fail that check it isn't offered again. What I did this month was the Monday afternoon that it was released I unrooted, did not reboot and then manually checked for the update. It pulled 8t and applied....then I rerooted in Magisk to the other slot.
kmandel said:
I didn't get the automatic OTA for December, February, or March,and so far no April. Just January came automatically. My Pixel 3XL was bought from Google, but runs on T-mobil. It is rooted via Magisk. Polling just says I'm up to date with the Jan 1 patch.
Are others getting the auto OTA's, and if so whats different?
I know I can sideload but there is a super easy way to keep root with Magisk and the auto OTA. I got the OTA's before December. I know Google had trouble in December, and January was a makeup.
Click to expand...
Click to collapse
Not trying to be a wise guy, but if you know how to sideload and root, why not just do it? Is it worth waiting weeks just to save yourself ten minutes?
kmandel said:
The toggle in Developer Options "Automatic System Updates, Apply updates when device restarts", refers to running the update automatically, not keeping Google from downloading the OTA either automatically or with a poll. I've always had the toggle as off.
As 9B says the toggle is "so it won’t install OTAs without your acknowledgement"
In the Months before December, and in January the OTA was auto downloaded and I had the option of installing it then, or later. I would just follow 9B at that point. This involves invoking "Settings → System → System Update" on the already downloaded OTA, but not letting it reboot until magisk does its magic.
On your other point, the factory image site has both the full system images and the OTAs. However, its not clear to me how I would trigger the manually downloaded OTA in the same way that "Settings → System → System Update" does with the auto/polled OTA downloaded by Google.
Click to expand...
Click to collapse
My intention is to help not get into an argument concerning the specifics of #9.B.
If my response gave that impression, please accept my apology.
I edited my original post because of the A/B Devices portion of the instructions (#9.B.). The Pixel 3 XL is an A/B device.
In your original post, I belive you wanted to update the Pixel 3 XL firmware via OTA and keep root. I pointed you to a thread that provides a link to instructions to accomplish that (Update the Pixel 3 XL firmware via OTA and keep root) that was written by the developer of Magisk (topjohnwu).
You could do #4 'keep data' to install the factory image. Then do #9.A. to reroot. I only takes a few minutes.
TonikJDK said:
There is another thread on this were many if us are having the same issue while rooted. It seems Google is checking for root before it downloads now. And if you fail that check it isn't offered again. What I did this month was the Monday afternoon that it was released I unrooted, did not reboot and then manually checked for the update. It pulled 8t and applied....then I rerooted in Magisk to the other slot.
Click to expand...
Click to collapse
Thanks, thats what I was guessing, that it wouldn't download if it knew I was rooted. I wonder if there is a way to hide root from their check, unrooting is a bit speculative since there isn't a trivial way back if they don't download.
spotmark said:
Not trying to be a wise guy, but if you know how to sideload and root, why not just do it? Is it worth waiting weeks just to save yourself ten minutes?
Click to expand...
Click to collapse
Because its error prone. As far as I know there is no Android 10 Twrp for Pixel 3, and no reroot option other than 9B. The other route patching the boot img just seems messy .
kmandel said:
Thanks, thats what I was guessing, that it wouldn't download if it knew I was rooted. I wonder if there is a way to hide root from their check, unrooting is a bit speculative since there isn't a trivial way back if they don't download.
Click to expand...
Click to collapse
One point I may not have been clear on. Once you fail this new check for a month you are done until next month. It won't try again.
If you don't pull the update you can reroot right away with Magisk with the Direct Install method since you have not rebooted. Not ideal but not the end of the world.
kmandel said:
Because its error prone. As far as I know there is no Android 10 Twrp for Pixel 3, and no reroot option other than 9B. The other route patching the boot img just seems messy .
Click to expand...
Click to collapse
If you know how to ADB and fastboot, you don't need TWRP. The most usual reason for error is user error. Even then it's rare to brick a phone. Worst outcome is you lose your data and have to set your phone back up.
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
awarman said:
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
Click to expand...
Click to collapse
are you rooted?
Yes but I have removed root and tried, same thing. Cleared dalvik cache, same thing.
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
hallo dare said:
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Click to expand...
Click to collapse
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
awarman said:
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
Click to expand...
Click to collapse
You won't get incremental if rooted, only full updates.
hallo dare said:
You won't get incremental if rooted, only full updates.
Click to expand...
Click to collapse
So in theory, if I unroot then run OnePlus updater I should be able to get the update. Then reboot after. Correct?
Maybe I did something wrong, but I tried unrooting for the last OTA and still received the same error. I had to wait until the full version was on the OnePlus site, I think OnePlus updater grabs the zip from there too. It also took a month longer for the full zip to hit the OnePlus site.
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
I have global unlocked varient and when I first received it I just flashed BA/EU on both slots(local upgrade twice) and I've been able to get all full zip updates(via system updates and/or O2 updater app) staying rooted the whole time. I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Initially I was getting that error. Then I ran the uninstall in Magisk and chose to RESTORE IMAGES. I then just hit retry on the OTA from the phone settings (NOT Oxygen Updater) and the update installed. Initially this did not for 11.2.3.3 as it would still give the error after unrooting by uninstalling Magisk, then it worked for 11.2.4.4 and 11.2.5.5. So YMMV. You can look here for my update process as I was having an issue post-OTA:
No cell service after update to 11.2.4.4AA while keeping root
I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this: 1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES 2...
forum.xda-developers.com
jammin6996 said:
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
Click to expand...
Click to collapse
This worked, btw. Never had to do this with my OP8P. Hopefully this isn't a regular occurrence.
Shooter7889 said:
I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Click to expand...
Click to collapse
Not knowing that the AA variant would have dog**** updates from the start, and already having restored my old phone's data and not wanting to go through setup and restore again.
Edit: The goal is also to eventually get on crDroid anyway so it's whatever. I'm not resetting until there's an official crDroid build out.