Database Info

Oreo OTA update installation failed? kDownloadstateinitializationError

Anyone here experiencing the same thing? I'm on DP4 w build number OPP4.
Enrolled in beta and got a 38+ mb ota.
Whenever I try to update it gets stuck on installing then fails.
Tried to unenroll to go back to 7.1.2 but after the 700+ mb download it fails too. I believe there's a signing issue. Or a google server problem. Im on a Verizon pixel. Locked bootloader. Anyone has an OTA link? Or any suggestions to fix this? This is kinda frustrating lol
edt: manually downloaded the OTA zip and sideloaded it but kept getting this error "kDownloadstateinitializationError". I even tried the rollback 7.1.2 zip and it does the same.
anyone knows what it is? PS. I can't unlock my bootload because Ive got a verizon pixel and can't rma it

Not in a vz pixel but I had the same issue and eventually just went the factory image route
Sent from my Pixel using Tapatalk

I can't flash factory images because my bootloader is locked and can't unlock it =/

How to get previous OTA packages on TA-1025?

Hey guys,
I have flashed the MENA firmware from here for my TA-1000 and it shows TA-1025 in the settings. The trouble is that the security patch is Jun 2017 so I want to upgrade it by OTA, but when I'm searching for updates it only shows that Android Oreo is ready to be download. I don't want that. I like 7.1.2 instead.
So I got some OTA packages to flash by adb sideload or SD-card, unluckily when I used adb it showed the pre-version was not installed and failed to go on. I noticed that all packages was for TA-1021, but someone said it can work normally on TA-1025 too, so I get confused about that.
If you have some suggestions on that, plz let me know. Thanks a lot.

Device has failed verification and may not work properly after flash whit lock BL

Hi, yesterday I received the Troika terminal.
I set out to flash to the latest version instead of waiting for all the updates I detected.
Even with the bootloader locked, I installed the latest available via fastboot:
XT2013-2_TROIKA_RETEU_9.0_PSB29.39-49-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but it doesn't start
this is the error ... your device has failed verification and may not work properly
I ALWAYS BELIEVED THAT TO FLASH AN OFFICIAL ROM I DID NOT MISS THE UNLOCK OF THE BOOTLOADER.
AT LEAST ON THE G5 MOTORCYCLE IT WAS THAT
:crying:

Solved
I've flashed again but this time this rom PSBS29.39-49-7-1
*and has no longer given bootloader errors during flashing.
And it is working.
I leave the thread here to serve in the future.

have u tried to install retail android 10?

Furieuxariel said:
have u tried to install retail android 10?
Click to expand...
Click to collapse
Yes after solving it and being able to use the mobile again. (I like danger). xD
And he gave the same error again, getting stuck in the verification and not even going to recovery. I do not recommend updating to the only version currently available in lolinet.

* * * Thread Cleaned * * *
Please keep comments relevant to the topic, and not towards insulting other members.
Thank you.

Could you, please, post a step-by-step of what happened? It might help others.
So, bootloader was locked at all times, right? Then you flashed Android 10 (which exact version? could you post the name or a link)? Then you tried to go back to Android 9, but you selected and older version (I'm guessing probably older than the Android 10 Security Patch), and it wouldn't boot anymore? Is this what happened?
The difference between PSBS29.39-49-7 and PSBS29.39-49-7-1 is (if I'm not mistaken), exactly the Security Patch. The latter should be December, which means the first one is probably November.

Already updated to Android 12, now being asked if I want to update to 12 again

I have already updated to Android 12 but I just had a popup asking if I want to update to Android 12.
It is 1.69GB in size which from memory is the same size when I updated a few weeks ago.
What should I do next?

I will be testing that for you. I am already downloading the update and installing it.

Jpfonseca said:
I will be testing that for you. I am already downloading the update and installing it.
Click to expand...
Click to collapse
me too

Finished downloading. Installing now.

Strange, have the same updates, 1,88GB, I'll wait for you to check it out

Ditto here. please keep us updated.

At least it's not just me then

Thank god I found this, I was shocked to see the same update again. 1.69 GB for me, downloading now.

Same here, pixel 5 with android 12, asked to update again...

Nothing new, just verison changed to SP1A.211105.002.A1

same here ...pixel 4a 5g

Same here, Pixel 5 with android 12: it just asked to update again...

Mine installed ...
Previously : SP1A.211105.003
After : SP1A.211105.002.A1

According to their release details...
Pixel 4a 5G: Android 12 – SP1A.211105.003, SP1A.211105.002.A1 (Verizon, Verizon MVNO), SP1A.211105.004 (Telstra, Optus, Vodafone AU) – Factory image – OTA (2) (3)

Same here on a T-Mobile 4a 5G

Is there a way of asking Google directly what is going on?

voidby said:
Nothing new, just verison changed to SP1A.211105.002.A1
Click to expand...
Click to collapse
Same here. Before the update I was at SP1A.211105.002. I went ahead and took the update (reluctantly, but to get rid of the notification nag) and everything seems to be working ok. Then I went on Google's site and this verson is listed as 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)
My phone is NOT Verizon.
UPDATE: I just flashed the 12.0.0 (SP1A.211105.002, Nov 2021) factory image and I'm now back to where I was. Everything is working fine. I just feel a whole lot better with a version that is NOT for Verizon. I sure hope Google gets this straightened out.

Now I've checked again and the update is gone. Maybe it's better?

Just saw this on Twitter. Google knows they goofed, but we may never know what actually happened.
https://twitter.com/i/web/status/1458595873705926656

Just checked my phone and the update is not appearing now.
Glitch at their end.

Question OTA Updates Always Fail

I have an unlocked UK Exynos S22+ and so far every OTA update I've tried since I got it has failed.
Updates usually fail at 25% progress and give the error: "Unable to update firmware. Visit a samsung service centre."
The June and latest August update gave me this error: "partition super Reason SUPER: Build-id does not match with the reference" with the blue download mode screen.
I feel like my situation is a lot like this person's and I have no idea how to fix it because I did a clean flash of the last August update a few days ago and still it failed. So far the only workaround is to flash every update through Odin. Would appreciate any help I can get because having to reflash every month is very frustrating.
I am currently flashing the EUX firmware but I am in Asia right now so I don't know if that is affecting it.

When you can, take it to Samsung shop/store and let them have a look at it

raul6 said:
When you can, take it to Samsung shop/store and let them have a look at it
Click to expand...
Click to collapse
Once I get a chance I will. 2 updates have worked flawlessly so far out of 6. The April update when I first got the phone and the July update. So the phone is capable of updating fine it just...doesn't.