I'm rooted and sideload OTA's every 3-4 months. I've done this several times since the phone was released with no issues. Today, was going to be May - August updates. May went through with no problem. However, when I went to install the June OTA, it failed with the following error:
Update package is older than the current build, expected a build newer than timestamp 1586927258 but package has timestamp 1586827774 and downgrade not allowed.
Do you folks have any suggestions? I tried re-downloading, but that didn't work. I checked the SHA-256 Checksum and they're all correct per the Google Developer site. I could move on to the July OTA, but I've never skipped an OTA before and am not sure of the consequences. I'd rather not install factory image and have to set things up again if I can avoid it.
Quick and easy
Fastboot boot the latest TWRP 3.4.0-1 img and flash the August OTA
Skipping June & July OTAs isn't an issue?
Edmontonchef said:
Quick and easy
Fastboot boot the latest TWRP 3.4.0-1 img and flash the August OTA
Click to expand...
Click to collapse
jaybird779 said:
Skipping June & July OTAs isn't an issue?
Click to expand...
Click to collapse
Never had a problem, you could flash and boot those the same way first if it makes you feel better.
Are you sticking to stock or are you running a custom ROM?
This is a known problem with the June update. Notified Google, posted about it on Android Police, problem never fixed. Only way to get the June update was OTA.
Skip June, sideload July or August. Why not just sideload most up to date anyway? Curious. Running August no problem.
A new version of Platform Tools has been released since June.....you may want to download newest Platform Tools and give June another try before loading July or August.
Read Comments: https://www.androidpolice.com/2020/...ogle-pixels-are-here-with-plenty-of-bugfixes/
Related
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
RusherDude said:
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
Click to expand...
Click to collapse
OP request to close...
THREAD CLOSED
Maybe this was posted already, but my search skills seem to be failing me at the moment. :silly:
Is there a way to do an in place OTA update from pie to Android 10 Q keeping Magisk root?
Or do I have to do the old way and revert pie, take the OTA, then apply the patched boot.img?
Thanks for any help!
You could revert and take the update or revert and flash Q via fastboot. Either way you'll have to root again after.
Pixel 3 XL, Yep, Crashed It.....
..... Again.
What I usually do is grab the current months image (in this case november), move the boot.img to my device, patch it with Magisk, move it back to my computer. Grab the OTA for the current month, sideload via fastbootd, after successful reboot I just go back into fastboot and flash the patched_boot.img.
Sounds like a lot, but usually takes only a few minutes after the downloads are complete.
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
ilikecl said:
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
Click to expand...
Click to collapse
Has your Pixel taken the January 2020 update yet?
statustray said:
Has your Pixel taken the January 2020 update yet?
Click to expand...
Click to collapse
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
ilikecl said:
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
Click to expand...
Click to collapse
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
statustray said:
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
Click to expand...
Click to collapse
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
ilikecl said:
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
Click to expand...
Click to collapse
Yeah that very well could be. I'm going to check my better half's phone and see if her has taken a new OTA yet. We're both vzw with google edition phones - my model is Pixel 3 XL, and hers is Pixel (OG).
Thanks.
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 am rooted with Magisk and ADB sideload OTA's in the stock recovery every 3 months or so. I was doing May - August this week and got a timestamp error on June's update. Is it safe to just skip OTA's, or do they need to be successively applied? That is, do I need to install May > June > July > August, or can I safely sideload the August OTA image over the May build? Thanks!
The OTAs all contain the fixes from the prior months. You can sideload August over May without a problem.
I installed the June '23 update but I don't see the matching factory images I need to extract the boot image in order to root. Anyone seen it anywhere?
I think I may have downloaded a beta by mistake. Is it possible to root a beta version?
June update AFAIK hasn't been released. Rooting beta versions is possible however.
Double check the version/security update level you're on. In my experience, carriers apparently can sneak in their OTAs even if you're on Google's version of the software.
I didn't realize the June was being withheld. I saw June updates on Android Flash Tool and figured second Monday but that doesn't mean much anymore. I hope June is made available as I'm having some issues with no screen response when clicking links using Chrome and Facebook.