Develop Bugs

Manual OTA Update, version incorrect

I have recently went to manuallly apply the OTA update to my Nexus 5x for MMB29P (from MMB29K). I am indeed running MMB29K, I verified in About Phone. However, when attempting the sideload, I was greeted with this error:
Package expects build fingerprint of google/bullhead/bullhead:6.0.1/MMB29K/2419427:user/release-keys or google/bullhead/bullhead:6.0.1/MMB29P/2473553:user/release-keys: this device has google/bullhead/bullhead:6.0/MDB08M/2343240:user/release-keys.​
A couple of questions I guess.
Why would my phone be showing the wrong version when attempting to flash this OTA package?
Has anyone seen this before?
Would any suggest against applying OTA patches for each version leading up from what my phone thinks its running, to the one I am actually running, so whatever metadata this package is checking will be corrected?
Any other suggestions?

This thread can be closed. Turns out my vendor.img was never flashed, which is why the phone showed the wrong meta info when attempting to sideload the update package.

Unable to install March OTA Security Update

Hi there
I have the Sprout 4 phone and it is not rooted. Twice today my phone has downloaded the OTA update and then informs me that it will restart and install the latest security update. On both occasions, the phone restarts and then I end up with a dead android logo with an 'Error' message.
I have also tried to update it from a thread in the forum using stock recovery but this aborts fairly early in the installation process.
Any ideas/solutions?
Thanks in advance

chrome307 said:
Hi there
I have the Sprout 4 phone and it is not rooted. Twice today my phone has downloaded the OTA update and then informs me that it will restart and install the latest security update. On both occasions, the phone restarts and then I end up with a dead android logo with an 'Error' message.
I have also tried to update it from a thread in the forum using stock recovery but this aborts fairly early in the installation process.
Any ideas/solutions?
Thanks in advance
Click to expand...
Click to collapse
Try to clear the data of Google play services then install it again

@ Dsbhai
Thanks for the suggestion, I have tried it and I still encounter the same problem.
Still receiving the updates OTA from the server, but it fails to install each time.

I'm still unable to update my phone with this update and have even done a 'factory reset'. Initially I thought I had bricked the phone as it was stuck in the boot animation loop, however after awhile it did restart.
Is it possible to install the update using ADB or even with a Custom Recovery?

You may be able to update using a custom recovery
And as you have done a factory reset already why not flash the ROM through SP Flash tools and then update accordingly

Hi there
I'm reviving this old thread as I still have been unable to update the security patches from Google ie stuck on trying to install March 2016.
It's really really strange as each time I go online the March update is flagged up to be installed.
Can this be correct? Surely, Google stops the OTA links after a set time?
If anyone could provide me with some basic steps to undertake to get control of my phone back, it would be appreciated.
I'm still on stock 6.01 and have only the stock recovery options available to me.
Thanks for reading this post (again!).
BTW Why are the stock roms for sprout4 & 8 not listed here ??
http://forum.xda-developers.com/canvas-a1/help#romList

Updater process ended with ERROR 7- How can I fix this error?

Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23

Failing to adb sideload Android 12 Beta

Hi! Recently I tried to install android 12 on my Pixel. Well, I enrolled into android 12 beta program, and didn't recieve any OTA update. I thought: "Hmpf, Nothing can stop me from getting beta on my phone!", so I downloaded OTA image on my PC, and started trying to apply update. I was happy, percents of progress was ticking, and after a while, this happened:
Code:
C:\adb>adb sideload D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip
serving: 'D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip' (~94%) adb: failed to read command: No error
I panicked little bit, but remembered A/B thing. So now I guess my B slot is wasted (or not?). I presume it'll somehow heel itself, right?
So, main question is: Why I am unable to apply OTA via usb using PC?
p.s: thank god phone booted up, i quickly turned on oem unlocking, just in case :/

p.s2: So I tried applying current ota (like current version), and now it works perfectly fine. Phone booted to b slot, despite that that error appeared again. Now I think maybe my phone is wrong, since android R works good, but not android S. I guess it's just beta, so i'll try to wait patiently until release. But still, could you answer question? I still don't know what the hell it was.

Can you unlock your bootloader? Flashing full factory image works great, and 12 runs well afterwards.

Question Signature Verification Failed while Sideloading OTA Image

Ive got a Pixel 6 Pro that was running Proton AOSP 12.4.1. Wanted to flash back to the original Android ROM. I downloaded the correct one from the dev page at google and tried to sideload it, but it always stops at 47% and gives this "Signature Verification Failed, error 21". It says it is failing to verify whole-file signature. After spending a couple hours looking onine, I am coming up empty for resolutions. Anyone have any ideas? It has failed in the same way 10 straight times. I should mention I have redownloaded the file to ensure there is no corruption, and even tried different months of the file.

cregets said:
Ive got a Pixel 6 Pro that was running Proton AOSP 12.4.1. Wanted to flash back to the original Android ROM. I downloaded the correct one from the dev page at google and tried to sideload it, but it always stops at 47% and gives this "Signature Verification Failed, error 21". It says it is failing to verify whole-file signature. After spending a couple hours looking onine, I am coming up empty for resolutions. Anyone have any ideas? It has failed in the same way 10 straight times. I should mention I have redownloaded the file to ensure there is no corruption, and even tried different months of the file.
Click to expand...
Click to collapse
It sounds like you want to go back to stock? If so, one of the best ways is to use Android Flash Tool. Just need to have OEM unlocking enabled in Developer Options.
As an aside, among other things you can:
1. Flash the factory image via fastboot
2. Sideload the full OTA image

Lughnasadh said:
It sounds like you want to go back to stock? If so, one of the best ways is to use Android Flash Tool. Just need to have OEM unlocking enabled in Developer Options.
As an aside, among other things you can:
1. Flash the factory image via fastboot
2. Sideload the full OTA image
Click to expand...
Click to collapse
I've tried the Android Flash tool and for some reason, It will not run. It always says "Network Error
HEAD request failed: Unknown network error". Couldn't figure out why, tried 3 different browsers, and a reset of data on the phone, no help. Does it need to have a SIM card in it to flash from the site?
As for #1, I haven't tried that yet.
#2 is the method I am currently using and getting the "Signature Verification Failed, error 21"
Not sure what else to do. I've seen a few posts that recommend flashing the partition as I might have a bad partition, but that seems unlikely as the phone was functioning 100% correctly before attempting to reflash.

cregets said:
I've tried the Android Flash tool and for some reason, It will not run. It always says "Network Error
HEAD request failed: Unknown network error". Couldn't figure out why, tried 3 different browsers, and a reset of data on the phone, no help. Does it need to have a SIM card in it to flash from the site?
As for #1, I haven't tried that yet.
#2 is the method I am currently using and getting the "Signature Verification Failed, error 21"
Not sure what else to do. I've seen a few posts that recommend flashing the partition as I might have a bad partition, but that seems unlikely as the phone was functioning 100% correctly before attempting to reflash.
Click to expand...
Click to collapse
Try #1

Remember proton is A12 and only one factory image has the correct bootloader if you want to stay on A12. Research a lot!!! Because a mistake in how, what you flash if wrong will break your device. Search on A12 bootloader, A13 / A12 different slots.

+1...be cautious...google's bootloader anti-rollback ain't no joke for Pixel 6 series phones. It's a one way ticket back to google for repair (or local repair shop maybe). I found out the hard way after flashing the wrong patched boot.img. The trigger isn't 'armed' until you've booted into A13 once...THEN if for any reason, like booting the backup/update slot, even unintentionally, will brick your 6...it will turn itself off and not power back again, no matter what u try. So, yeah...tread carefully, thar be dragons!
edit: iirc, there is/was a way to turn off sig verification. I would make that a last resort tho...it's a key to help prevent installing 'tainted' app..

Flashing from Fastboot worked, ty for the help.