I just updated to
Version
10.0.12.HD65AA
Updated on
August 11, 2020
Now I am having a problem with texts, is there a site where I can get the July update, and how do I go about making the downgrade. Can I do it through the phone update, or do I have to use TWRP or fastboot?
Thanks
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
Hi
I have updated my stock naugat to feb 2018 but now i want to sideload 8.0 so i have to go back to dec patch how can i do that?
Use caution if you do this, it's my understanding that a couple of users have done this, and were subsequently hard bricked.
In addition to dandrumheller's reply, I would not recommend downgrading and then try to apply the OTA Oreo update. This appears to be a nasty hardbrick and the blankflashes we have do not seem to work.
Safest way would be to wait for the official Oreo OTA or the official Oreo fastboot ROM, as I mentioned previously to you.
I manually installed android pie to german version G960FXXU2CRLI and now I lost my OTA updates. It still sits on january 1st
I am from Croatia and now I am looking at croatian pie version G960FXXU2CSB9. Should I install that firmware via Odin and do I need to factory reset my phone even if both are same android versions?
Will I receive OTA updates in the future if I update to G960FXXU2CSB9 ?
I have the same problem. I'm stuck on December 2018 security patch level after upgrading to Pie via Odin.
I just got a second hand Moto Z2 Play which is a XT1710-09 on android 7.1.1 with security patch level February 1, 2018 and reteu Software Channel with build number NPSS26.118-19-22.
It was already reset when I got it and after I done my initial setup I got a prompt to update to android 8.0, April 1, 2018, OPS27.76-12-25 but after I wait for the download to finish (tried on both wifi and mobile data) it says the update couldn't be validated and to try again.
I went ahead in the recovery and deleted cache and factory reset once again and I get the same issue. The bootloader also shows the software as being modified and not official.
Any tips ? I really wouldn't want to return the phone because I love it so far but if there's no solution I'll just have to go ahead and get my money back
Ich guess your bootloader ist unlocked? Well then you cant make ota Updates anymore, but you can Install a full rom via Fastboot.
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Hir0xM said:
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Click to expand...
Click to collapse
Yep, that's indeed the last one.
That's the one I have.
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/