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.
Related
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.
First of all Happy Easter to everyone !
The first detail to mention is I bought my phone with stock ROM 20151203 installed.
When release 20160217 was offered OTA instead of installing properly the only thing that showed up in my (unrooted) phone was the green Android logo laid down plus the message "Fehler !" (= Error !).
Fortunately the phone was neither bricked nor stuck in any kind of boot loop. After rebooting stock ROM 20151203 continued working and the OTA offer of release 20160217 never showed up again.
Since then I have rooted the phone (Linux Flash Tool v5.1552 / PhilZ recovery v3), installed SuperSU v2.65 and flashed TWRP v2.870.
Yesterday release 20160319 was offered OTA, but again my phone instead of installing the update simply continued with stock ROM 20151203 after rebooting.
So instead of installing OTA I saved the update.zip, extracted the directory (which had exactly the same name) "update.zip" from it and tried to flash that one with TWRP.
The resulting error message from TWRP is shown within the attached screenshot.
From my rookie point of view the error message seems to indicate the offered update file does not match with my device. But why would that be ?
Any hints on how to solve this OTA update issue are welcome !
Guess I found the reason for that incapacity to perform OTA updates:
Update package demanded a ROM release 20151203 or newer, while phone answered installed ROM release was 20150907 (too old).
This can only mean the online shop where I bought my phone sold me a dirty flashed device (v. 20151203 flashed upon v. 20150907) with the residual files from september release causing the incapacity to update OTA.
Anyway, I did a full wipe to blow all those unwanted dinosaur residuals off the phone storage and then installed the most recent Eragon release.
Problem solved and bye bye stock Roms...
dormilonX said:
First of all Happy Easter to everyone !
The first detail to mention is I bought my phone with stock ROM 20151203 installed.
When release 20160217 was offered OTA instead of installing properly the only thing that showed up in my (unrooted) phone was the green Android logo laid down plus the message "Fehler !" (= Error !).
Fortunately the phone was neither bricked nor stuck in any kind of boot loop. After rebooting stock ROM 20151203 continued working and the OTA offer of release 20160217 never showed up again.
Since then I have rooted the phone (Linux Flash Tool v5.1552 / PhilZ recovery v3), installed SuperSU v2.65 and flashed TWRP v2.870.
Yesterday release 20160319 was offered OTA, but again my phone instead of installing the update simply continued with stock ROM 20151203 after rebooting.
So instead of installing OTA I saved the update.zip, extracted the directory (which had exactly the same name) "update.zip" from it and tried to flash that one with TWRP.
The resulting error message from TWRP is shown within the attached screenshot.
From my rookie point of view the error message seems to indicate the offered update file does not match with my device. But why would that be ?
Any hints on how to solve this OTA update issue are welcome !
Click to expand...
Click to collapse
I am having the same issue.
Nexus 5x successfully installed LineageOS 14.1 02132017 build last week. I tried installing the weekly update today but the phone goes through the process of 'Preparing to update' then reboots to TWRP 3.0.2. Nothing happens after getting to TWRP, so I tried to run the install by pointing TWRP to /data/data/org.lineageos.update/app_updates and run the update but get the following:
'Zip file is corrupt!'
'Error installing zip file '@/cache/recovery/block.ma
etc
etc
etc
'Zip signature verification failed!'
I have deleted the file and downloaded again twice, but still receive the same message.
Any insight to what might be going wrong here?
Thanks,
jktrahan said:
Nexus 5x successfully installed LineageOS 14.1 02132017 build last week. I tried installing the weekly update today but the phone goes through the process of 'Preparing to update' then reboots to TWRP 3.0.2. Nothing happens after getting to TWRP, so I tried to run the install by pointing TWRP to /data/data/org.lineageos.update/app_updates and run the update but get the following:
'Zip file is corrupt!'
'Error installing zip file '@/cache/recovery/block.ma
etc
etc
etc
'Zip signature verification failed!'
I have deleted the file and downloaded again twice, but still receive the same message.
Any insight to what might be going wrong here?
Thanks,
Click to expand...
Click to collapse
Well known issue with build-signing. The devs are looking into it.
https://status.lineageos.org
Hello I am new to xda
I have Nexus 5x (bullhead) I recently installed Lineage OS 14.1 I had the same issue while installing updates in twrp it was showing zio is corrupt
So I used a trick I downloaded the ROM zip from Lineage OS downloads
and I installed it with twrp and then I have my phone updated
Hope this helps !
Wondering whether this is still an issue the devs are working on. Received my brand new 5X yesterday and immediately rooted, unlocked en put LineageOS on the thing.
First message was about the version mismatch, which I solved by re-flashing the vendor, radio and bootloader using the original factory image. Afterwards, I read that you should re-apply the LineageOS update. Which I did... and it ended up in TWRP with the log message in the OP.
I can manually install using the zip file... but does that mean I will never be able to automatically update?
Kaastosti said:
Wondering whether this is still an issue the devs are working on. Received my brand new 5X yesterday and immediately rooted, unlocked en put LineageOS on the thing.
Click to expand...
Click to collapse
It still is, at least on my 6p. Some nightlies will work, some won't. I haven't figured out the pattern.
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
Hi everyone,
I've been having issues updating my Pixel 3 XL since September 2020, when a security update came out. I tried to classicaly update my phone but kept getting the "Couldn't update - Installation problem" error. Since then I haven't been able to get any new feature.
Now that android 12 is out, I'd like to update my Pixel to have it, but the same error keeps showing up. I've tried to factory reset but still not working.
I'm not an experienced developer and this is my first experience, so all that I've tried is downloading the full OTA image (12.0.0 (SP1A.210812.015, Oct 2021), and sideload it. After doing that, it seems to work, but the android version remains the same after rebooting, CMD output is:
Code:
serving: 'D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip' (~94%) adb: failed to read command: No error
So, my question is if there is a safe way to get the latest version, and if possible keep getting all updates as it should normally work.
Thanks in advance for any help.