I get this error message:
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
Any ideas?
7cherubin said:
I get this error message:
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
Any ideas?
Click to expand...
Click to collapse
root and or twrp installed?
2WildFirE said:
root and or twrp installed?
Click to expand...
Click to collapse
Nope.
Never flashed TWRP.
However, I did have root. But I uninstalled it and performed a hard reset.
After that, I also locked the bootloader.
Then try flash matching boot.img after that update again.
? Bootloader isn't needed I update every month with open bootloader
7cherubin said:
I get this error message:
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
Any ideas?
Click to expand...
Click to collapse
+1 The same happens to me (stock boot flashed in slot b - september and a -august). No way to update.
Did you guys ever figure it out ? I'm having the exact same problem when trying to flash the November update from Stock Recovery (I tried that because normal OTA errors out). Thanks !
Hi @7cherubin would you send me the post to root TA-1012?
I have the same problem. TA-1004, trying to apply November security update.
After getting the "Installation problem" error message in the update UI, which is not very verbose, I checked the log with adb logcat. The following is what I have found:
Code:
update_engine: [1114/144758:INFO:delta_performer.cc(368)] Applying 8158 operations to partition "system"
update_engine: [1114/144758:ERROR:delta_performer.cc(1065)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
The phone's bootloader was unlocked using the official method.
TWRP has been installed, then removed (by flashing the stock boot image to both slots A and B).
The update seems to fail with or without TWRP.
Also, Magisk has been installed, then removed. Same result: update fails with or without Magisk.
Judging by the error message from the log, the problem is somehow related to the system partition and not the boot partition (where the boot image resides, and which would be affected by TWRP and/or Magisk).
The Nokia 8 doesn't seem to have a separate recovery partition, the recovery image is stored also on the boot partition (proof for this being that if you flash stock boot image, you get back the stock recovery).
Temporarily booting an image with fastboot boot <img> also doesn't work on this phone (at least if you are already on 8.1.0 with October security patch), so installing TWRP is only possible by flashing it to one of the boot slots and forcing the phone to boot from that particular slot.
Neither OST 6.0.4 nor OST 6.1.2 is able to flash the phone.
Sorry if this got too long, I am trying to stick in this post all the info that I have learned in the hopes that someone will have an idea how to fix this.
I had the same problem and had to go back to stock. I had only rooted and flashed the boot images, no TWRP. I had messed up at one point though and flashed both slots and that's where I think the problem lies. The boot images seem to be personalized to the device (keys ?) and the OTA checks for that so if you flash one with a prerooted image, then apply Magisk to the other one and ugrade on that one (after temporarily deactivating Magisk) then you're ok. After going back to stock I was able to verify this "theory", well at least it let me do the OTA multiple times.
Can someone post the link yo root TA-1012 ^_^
webvan said:
I had the same problem and had to go back to stock. I had only rooted and flashed the boot images, no TWRP. I had messed up at one point though and flashed both slots and that's where I think the problem lies. The boot images seem to be personalized to the device (keys ?) and the OTA checks for that so if you flash one with a prerooted image, then apply Magisk to the other one and ugrade on that one (after temporarily deactivating Magisk) then you're ok. After going back to stock I was able to verify this "theory", well at least it let me do the OTA multiple times.
Click to expand...
Click to collapse
Here is what I have, Nokia 8 TA-1004:
- on slot A I have Android 8.1.0 with October security patch
- on slot B I have Android 8.1.0 with September security patch
Neither of these would apply the OTA (slot A November patch, slot B October patch).
I got rid of previous root attempts by flashing:
- stock October boot image to slot A
- stock September boot image to slot B
At this point I am back to as stock as possible.
Then I tried to follow your suggestions, flashed:
- prerooted October boot image to slot A
- stock September boot image to slot B
Set the active slot to A.
Reboot.
Install Magisk from MagiskManager to the "other slot", this switches the active slot to B.
Reboot.
Check that Magisk is installed: yes. Check root with RootChecker: there is root.
Uninstall Magisk from MagiskManager with the Restore Images option, this should restore the stock boot image on the active slot, which at this point is B.
Without reboot, try to apply the OTA update to upgrade to November security patch.
Update fails. Here are a few relevant lines from the log (retrieved with adb logcat):
Code:
11-27 16:56:59.961 1107 1107 I update_engine: [1127/165659:INFO:delta_performer.cc(368)] Applying 5 operations to partition "abl"
11-27 16:56:59.965 1107 1107 I update_engine: [1127/165659:INFO:delta_performer.cc(661)] Starting to apply update payload operations
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(1065)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that
the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(1070)] Expected: sha256|hex = 1376DA9AFC602B63352F6611917129A8FEC841070A5A44B657826B25D3BAED0D
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(1073)] Calculated: sha256|hex = 658502232C3D562E1883E66BB2C4BED4F48E98CB02B983DC43DB6D9B05ABF939
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(1084)] Operation source (offset:size) in blocks: 1:1,3:1,36:14,51:16
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(1250)] ValidateSourceHash(source_hasher.raw_hash(), operation, error) failed.
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:delta_performer.cc(288)] Failed to perform SOURCE_BSDIFF operation 1, which is the operation 1 in partition "abl"
11-27 16:56:59.970 1107 1107 E update_engine: [1127/165659:ERROR:download_action.cc(325)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
Then I went back to stock boot images again, and tried the whole process the other way around: switching slots.
Stock image on slot A.
Prerooted image on slot B.
The rest of the process is the same as above.
This time I get a different error in the log:
Code:
11-27 17:07:30.788 1050 1050 I update_engine: [1127/170730:INFO:delta_performer.cc(368)] Applying 5 operations to partition "abl"
11-27 17:07:30.794 1050 1050 I update_engine: [1127/170730:INFO:delta_performer.cc(661)] Starting to apply update payload operations
11-27 17:07:30.834 1050 1050 I update_engine: [1127/170730:INFO:delta_performer.cc(368)] Applying 22 operations to partition "bluetooth"
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(1065)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that
the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(1070)] Expected: sha256|hex = 73D9DD6F7FCBA3C7A6900599BB66C5D321C9F77B74808FD1ADEB50DD8CE475D2
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(1073)] Calculated: sha256|hex = BEFE956EC57F320FA6F96067CCDF81DEF88D227A15D7E5412B2064A941E8E7BF
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(1084)] Operation source (offset:size) in blocks: 4:1,11:1
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(1250)] ValidateSourceHash(source_hasher.raw_hash(), operation, error) failed.
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:delta_performer.cc(288)] Failed to perform SOURCE_BSDIFF operation 11, which is the operation 6 in partition "bluetooth"
11-27 17:07:30.841 1050 1050 E update_engine: [1127/170730:ERROR:download_action.cc(325)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
As you can see in the first case it is complaining about the "abl" partition, in the second case it is complaining about the "bluetooth" partition.
webvan, what is your phone model? Is it TA-1004? What security patch levels were you working with in your case?
Mine is a TA-1052.
By "go back to stock" I meant fully reflashing the Oreo update with OTLA because like you nothing I tried with the boot images helped. Since I was rooted I did a backup with Titanium so it wasn't too painful.
I managed to update to 5.15d by sideloading using adb the full ROM (5.15) then sideloading 5.15a and 5.15b, I didn't sideload 5.15c I directly sideloaded 5.15d OTA update and it worked!
I have the same problem.
Slot A : stock boot with sp 2019-04 (5150)
Slot B (active): stock boot with sp 2019-05 (515A)
I tried to sideload OTA (515B with sp 2019-06) on slot B, while the "Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)" message appeared.
By checking the log report, it was just after the operations to partition "system" that I had the line "the hash of the source data on disk for this operation doesn't match the expected value."
Anyone has ideas? Thanks in advance.
Related
I have a unlocked TA-1004, rooted with Magisk (running stock recovery). Today I got the notification for the January Security patch.
I restored the boot image with Magisk and proceeded to download and install the OTA, however I'm getting an "Couldn't update - Installation problem" error.
After that I tried reinstalling Magisk, rebooting the phone, restoring the boot image again and retrying the update, it still fails.
Any ideas on what to do? (I didn't want to use a custom recovery solely for keeping the ability to receive further OTA updates, now for whatever reason I can't :S)
TA-1004 here, stock, updated to PIE via beta leak, can't install the update too
yandoo said:
TA-1004 here, stock, updated to PIE via beta leak, can't install the update too
Click to expand...
Click to collapse
I sideloaded the full version (not the beta leak), makes no sense either way tho
I'm having the same issue with a TA1012. Quite fast after downloading the update an error message and "Installationsproblem" in red font.
any solution yet?
ILoveAndroid77 said:
I'm having the same issue with a TA1012. Quite fast after downloading the update an error message and "Installationsproblem" in red font.
any solution yet?
Click to expand...
Click to collapse
I have same issue on my Nokia 8 (TA-1004).
Is Anyone have solution for this?
ADB output shows
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785297:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785480:ERROR:delta_performer.cc(995)] Expected: sha256|hex = 945B60FBC44A481C5F003C140ABBEC14F0CE2C8E142E9843BE83F67905453399
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785520:ERROR:delta_performer.cc(998)] Calculated: sha256|hex = CB0DA98B7D9BC6DF8B98A6323A3079588EA975088DBAB0461404E90809FC67F6
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785563:ERROR:delta_performer.cc(1009)] Operation source (offset:size) in blocks: 0:1,2140:877,3018:10099
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785628:ERROR:delta_performer.cc(1191)] ValidateSourceHash(source_hash, operation, source_fd_, error) failed.
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785670:ERROR:delta_performer.cc(298)] Failed to perform BROTLI_BSDIFF operation 27, which is the operation 0 in partition "boot"
01-31 12:40:06.785 1128 1128 E update_engine: [0131/124006.785711:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
Pie (installed via OTA) is on slot B.
On slot A should be the may oreo NB1-488B-0-00WW-B04.nb0. I went back to this with OST and I think the OTA update for pie is not intended to upgrade Oreo May.
Is there a full stock pie image that we could install via OST?
How about your other slot, what's installed there?
1- download this Firmware NB1-488B-0-00WW-B04.qlz Via this link https://bit.ly/2CZS4Z2
2- Flash via NOST https://github.com/StollD/NOST/releases
3- download and flash thes ota update via adb sideload https://bit.ly/2Rs4y0Y
Now you can install January security patch Without any problems
iyadengle said:
1- download this Firmware NB1-488B-0-00WW-B04.qlz Via this link https://bit.ly/2CZS4Z2
Click to expand...
Click to collapse
Does not work - following this link I receive a microsoft sharepoint login site of helmholtzschule. Don't have credentials.
But i think I did this some weeks ago. This should be the full may oreo rom?
iyadengle said:
3- download and flash thes ota update via adb sideload https://bit.ly/2Rs4y0Y
Click to expand...
Click to collapse
Whats this update?
What I did with my phone: install May oreao. after booting and setup it directly went to the pie update.
So i think i have first pie rom on slot B and may on slot A. And may oreo slot A can not be updated with a 76Mb OTA to pie.
If I follow your steps, shouldn't I have the same result as now?
Got a solution for me, described here: https://forum.xda-developers.com/showpost.php?p=78811216&postcount=4
Has anyone gotten OTA updates to work using the magisk a/b tutorial? I've never gotten it to take an OTA, I usually have to find a recent firmware download and reflash, then go through all the OTAs until I'm done, then reroot with magisk. There's got to be a better way to do it.
I'm wondering if the problem is that I'm installing magisk via TWRP (not flashing twrp, just booting to it). Anyone have any advice?
I do not get OTAs because of unlocked bootloader. But at least I just installed an update to slot B, rebooted to A and rooted B with the Magisk app successfully.
As long as I find updates here, that's ok, I think. Updates do not come often. It's not a Xiaomi in beta test mode.
You can get OTA with an unlocked bootloader. My bootloader has been unlocked since shortly after I got my phone. I might end up doing what you suggest; I know how to get the OTA package from the logs on the phone, so I could just download the OTA and install myself. I was just hoping to get the super snazzy method that magisk allows working.
This latest update was weird. I tried my usual technique (reflash everything without wiping userdata to the last stock ROM, which removes magisk, then update with OTA), but it failed. The new version's ROM was uploaded though, so I could just use that one.
I tried something different this time in that I used the "patch boot image" method instead of installing through TWRP. I'll see if that makes a difference or not next time the updates occur.
And you're right, at least I only have to fiddle with it once a month or so.
This is from/for Lineage 15.1: https://forum.xda-developers.com/showpost.php?p=78722460&postcount=830
Sounds like you need to reflash TWRP after every update but magisk sticks.
I have gotten exactly one OTA with unlocked BL, a security patch for 8.1.
Since then, installation of every downloaded OTA failed.
I once had pulled the OTA file to my PC, but I failed to turn it into a flashable image. I have posted a question about it in the X4 forums.
EDIT: it was 8.0. => click
dougo007 said:
This is from/for Lineage 15.1: https://forum.xda-developers.com/showpost.php?p=78722460&postcount=830
Sounds like you need to reflash TWRP after every update but magisk sticks.
Click to expand...
Click to collapse
I don't have TWRP flashed anymore (I wasn't using it for anything). The problem is that it's not taking the OTA update at all. It says update failed due to unspecified error. When I look through the logs, I see that it's failing because the system partition hash isn't matching what's expected, despite me not modifying the system partiton at all (as far as I know). All I use magisk for is root for adblocking (adguard) and call recording (call recorder), and I used the vanced module from the repo. I don't think any of that should make my /system not match, but I'm not really sure.
oz42 said:
I have gotten exactly one OTA with unlocked BL, a security patch for 8.1.
Since then, installation of every downloaded OTA failed.
I once had pulled the OTA file to my PC, but I failed to turn it into a flashable image. I have posted a question about it in the X4 forums.
Click to expand...
Click to collapse
As far as I know, you can't just directly flash OTAs. You have to go into TWRP and do the sideload thing, though I could be mistaken. It's been a long time since I've tried doing it that way.
tjololo12 said:
As far as I know, you can't just directly flash OTAs. You have to go into TWRP and do the sideload thing, though I could be mistaken. It's been a long time since I've tried doing it that way.
Click to expand...
Click to collapse
I am ~90% sure that OEM OTAs (it sounds like that is what you are discussing) are installed via ADB sideload.
tjololo12 said:
When I look through the logs, I see that it's failing because the system partition hash isn't matching what's expected
Click to expand...
Click to collapse
I wonder if there's a way we can bake in the updated hash value of the system partition to trick the OTA into loading. which log file did you find this in?
trevorcobb said:
I wonder if there's a way we can bake in the updated hash value of the system partition to trick the OTA into loading. which log file did you find this in?
Click to expand...
Click to collapse
I'm not sure honestly, I just did "adb logcat" and watched it while I ran the update. I'm perfectly willing to help you or anyone troubleshoot this. I have a version of Android I can flash before the last update, if you want me to look into something. Otherwise, we can wait until the next one.
Good thread so far. Anyone find a solid work around for this last OTA?
Sent from my moto x4 using Tapatalk
trevorcobb said:
I wonder if there's a way we can bake in the updated hash value of the system partition to trick the OTA into loading. which log file did you find this in?
Click to expand...
Click to collapse
Here's the section from adb logcat
Code:
04-02 07:39:11.716 1447 1447 I update_engine: [0402/073911.715938:INFO:delta_performer.cc(385)] Opening /dev/block/bootdevice/by-name/boot_a partition without O_DSYNC
04-02 07:39:11.716 1447 1447 I update_engine: [0402/073911.716773:INFO:delta_performer.cc(129)] Caching writes.
04-02 07:39:11.716 1447 1447 I update_engine: [0402/073911.716954:INFO:delta_performer.cc(397)] Applying 2 operations to partition "boot"
<unrelated things here>
04-02 07:39:13.065 1447 1447 E update_engine: [0402/073913.065604:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
04-02 07:39:13.065 1447 1447 E update_engine: [0402/073913.065821:ERROR:delta_performer.cc(432)] Unable to open ECC source partition boot on slot B, file /dev/block/bootdevice/by-name/boot_b: Invalid argum
ent
04-02 07:39:13.065 1447 1447 E update_engine: [0402/073913.065902:ERROR:delta_performer.cc(1042)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean th
at the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
04-02 07:39:13.065 1447 1447 E update_engine: [0402/073913.065954:ERROR:delta_performer.cc(1047)] Expected: sha256|hex = AD67C3189DCBFF888499FF8E6D9CCF77D162421ABBB684AD93CD4D74B29D742D
04-02 07:39:13.066 1447 1447 E update_engine: [0402/073913.066004:ERROR:delta_performer.cc(1050)] Calculated: sha256|hex = CF6389937B1AD2F683C710FDA74CA518851F8DF71372C5E4A1349092E3CE25DE
04-02 07:39:13.066 1447 1447 E update_engine: [0402/073913.066057:ERROR:delta_performer.cc(1061)] Operation source (offset:size) in blocks: 0:3336,3576:1985
04-02 07:39:13.066 1447 1447 E update_engine: [0402/073913.066130:ERROR:delta_performer.cc(1345)] source_fd != nullptr failed.
04-02 07:39:13.066 1447 1447 E update_engine: [0402/073913.066183:ERROR:delta_performer.cc(301)] Failed to perform BROTLI_BSDIFF operation 244, which is the operation 0 in partition "boot"
04-02 07:39:13.066 1447 1447 E update_engine: [0402/073913.066238:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the
received payload -- Terminating processing
04-02 07:39:13.075 1447 1447 I update_engine: [0402/073913.075061:INFO:delta_performer.cc(317)] Discarding 18435331 unused downloaded bytes
04-02 07:39:13.077 1447 1447 I update_engine: [0402/073913.077715:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
04-02 07:39:13.077 1447 1447 I update_engine: [0402/073913.077897:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 206
04-02 07:39:13.077 1447 1447 I update_engine: [0402/073913.077950:INFO:multi_range_http_fetcher.cc(126)] Terminating.
04-02 07:39:13.078 1447 1447 I update_engine: [0402/073913.078002:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
04-02 07:39:13.078 1447 1447 I update_engine: [0402/073913.078056:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
04-02 07:39:13.078 1447 1447 I update_engine: [0402/073913.078106:INFO:update_attempter_android.cc(470)] Processing Done.
04-02 07:39:13.079 1447 1447 I update_engine: [0402/073913.079041:INFO:update_attempter_android.cc(495)] Resetting update progress.
04-02 07:39:13.079 1447 1447 D NetdClient: setNetworkForTarget(0)
04-02 07:39:13.079 8128 17008 D OtaApp : UpdateEngineCallbackImplementation: StatusUpdate 0 percentage 0.0
04-02 07:39:13.080 1447 1447 I update_engine: [0402/073913.080598:INFO:update_attempter_android.cc(655)] metrics:({
04-02 07:39:13.080 1447 1447 I update_engine: "downloadPercentageAdminApn": 0.0,
04-02 07:39:13.080 1447 1447 I update_engine: "downloadPercentageCellular": 0.0,
04-02 07:39:13.080 1447 1447 I update_engine: "downloadPercentageWifi": 5.0,
04-02 07:39:13.080 1447 1447 I update_engine: "downloadTotalSize": 20279759,
04-02 07:39:13.080 1447 1447 I update_engine: "downloadTotalTime": 4435.0,
04-02 07:39:13.080 1447 1447 I update_engine: "errorCode": 20,
04-02 07:39:13.080 1447 1447 I update_engine: "networkId": 634765889549.0,
04-02 07:39:13.080 1447 1447 I update_engine: "networkType": "WIFI",
04-02 07:39:13.080 1447 1447 I update_engine: "sessionAttemptNumber": 1.0,
04-02 07:39:13.080 1447 1447 I update_engine: "sessionAttemptResult": 1,
04-02 07:39:13.080 1447 1447 I update_engine: "sessionDownloadDuration": 121005476.0
04-02 07:39:13.080 1447 1447 I update_engine: })
Does that help track things down? Any other way I can help look into things?
There's already a method explained in the FAQs thread for installing official OTAs on rooted stock. TWRP has to be reinstalled after though.
Are you just trying to search for a more efficient solution?
Neffy27 said:
There's already a method explained in the FAQs thread for installing official OTAs on rooted stock. TWRP has to be reinstalled after though.
Are you just trying to search for a more efficient solution?
Click to expand...
Click to collapse
Exactly what post in the FAQ are you referring to??
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Exactly what post in the FAQ are you referring to??
Click to expand...
Click to collapse
Here...
Neffy27 said:
...
12. I am rooted and now Official OTAs don't install
This is a known issue with no fix. Your only option is to wait for copy of latest firmware to be available and manually flash it without the erase userdata to keep your data. Another option is if you are receiving the OTA notification, manually re-flash current firmware build without the erase userdata to keep your data and proceed to accept the OTA (You will have to re-install TWRP/re-root.)
...
Click to expand...
Click to collapse
Hi all,
Can anybody please share the twrp backup of bluetooth partition of Moto One Power device having the Pie January 1st Patch? My bluetooth partition got formatted while restoring the twrp backup and restore got failed. Now I'm not able to use the bluetooth. I have got the OTA with face unlock, But thile installing the OTA I started getting bluetooth partition block verification failed saying partition got mounted rw. And while restoring the earlier backup it got formatted :crying:
Got it fixed after a hell lot of research
Hi all,
Finally after searching a lot in net, flashed the bluetooth partition with the img file available in the following site ( Phenotypically ) -> mirrors[dot]lolinet[dot]com[slash]firmware[slash]moto[slash]chef[slash]official[slash]RETIN
The root cause for getting the partition formatted is gettiing the following error, to solve it I tried to restore bluetooth partition and it resulted currupt. Hope it may help somebody who will be get the same issue and stumble upon this page.
I was getting "Update Failed" error in Moto updator. While checking for the logs via adb observed the following error :
Code:
update_engine: [0306/081413.872062:INFO:delta_performer.cc(397)] Applying 8 operations to partition "bluetooth"
update_engine: [0306/081413.885946:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
update_engine: [0306/081413.886903:ERROR:delta_performer.cc(432)] Unable to open ECC source partition bluetooth on slot A, file /dev/block/bootdevice/by-name/bluetooth_a: Success
update_engine: [0306/081413.887044:ERROR:delta_performer.cc(1042)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
update_engine: [0306/081413.887251:ERROR:delta_performer.cc(1047)] Expected: sha256|hex = 9F69430D4BED82B26E49AAA81E0F1E823687605099AD61F45A361A96E7BE6FEE
update_engine: [0306/081413.887321:ERROR:delta_performer.cc(1050)] Calculated: sha256|hex = 734059C0A03A2B2E61CBF3302F2982F3811FD243064D434A6CFC0FAEBDBC0E85
update_engine: [0306/081413.887393:ERROR:delta_performer.cc(1061)] Operation source (offset:size) in blocks: 0:1,6:2,34:1,101:30
update_engine: [0306/081413.887487:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2019-03-05 03:36:34.000 UTC.
update_engine: [0306/081413.887573:ERROR:delta_performer.cc(1340)] source_fd != nullptr failed.
update_engine: [0306/081413.887652:ERROR:delta_performer.cc(301)] Failed to perform BROTLI_BSDIFF operation 4604, which is the operation 0 in partition "bluetooth"
update_engine: [0306/081413.887721:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
update_engine: [0306/081413.888372:INFO:delta_performer.cc(317)] Discarding 301 unused downloaded bytes
update_engine: [0306/081413.894845:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
update_engine: [0306/081413.895113:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 206
update_engine: [0306/081413.895166:INFO:multi_range_http_fetcher.cc(126)] Terminating.
update_engine: [0306/081413.895224:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
update_engine: [0306/081413.895278:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
Since Moto One Power is having A/B Partition and seemless update support, It looks like the incremental security update was checking for the checksum of the corresponding partition before applying the incremental update. To fix this I flashed the bluetooth and other failing partitions with the apropriate images available in the above shared link.
Hi there, i'm facing the same issue. Can u please tell me which img to flash from stock firmware?
heres a log
Installing zip file '/sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:AB zip
I:has_legacy_properties: Could not open /tmp/updater: No such file or directory!
I:Legacy property environment not used in updater.
Failed to parse build number in post-build-incremental=eng.rcstar.20190611.020532.
__bionic_open_tzdata: couldn't find any tzdata when looking for PAKST-5:30!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
[0617/224002:INFO:sideload_main.cc(207)] Update Engine Sideloading starting
[0617/224002:INFO:boot_control_recovery.cc(77)] Loaded boot_control HAL 'Boot control HAL' version 0.1 authored by 'Code Aurora Forum'.
[0617/224002:INFO:update_attempter_android.cc(207)] Using this install plan:
[0617/224002:INFO:install_plan.cc(77)] InstallPlan: new_update, source_slot: B, target_slot: A, url: file:///sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip, payload: (size: 730303102, metadata_size: 143458, metadata signature: , hash: B3621E6FF72FDADC09D057ABA4C33A710920E6009EC948044D95B047F1C524B3, payload type: unknown), hash_checks_mandatory: false, powerwash_required: false
[0617/224002:INFO:update_attempter_android.cc(391)] Marking booted slot as good.
[0617/224002:ERROR:boot_control_recovery.cc(175)] Unable to mark boot successful: Operation not permitted
[0617/224002:INFO:update_attempter_android.cc(406)] Scheduling an action processor start.
[0617/224002:INFO:action_processor.cc(46)] ActionProcessor: starting InstallPlanAction
[0617/224002:INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess
[0617/224002:INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction
[0617/224002:INFO:install_plan.cc(77)] InstallPlan: new_update, source_slot: B, target_slot: A, url: file:///sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip, payload: (size: 730303102, metadata_size: 143458, metadata signature: , hash: B3621E6FF72FDADC09D057ABA4C33A710920E6009EC948044D95B047F1C524B3, payload type: unknown), hash_checks_mandatory: false, powerwash_required: false
[0617/224002:INFO:download_action.cc(195)] Marking new slot as unbootable
[0617/224002:ERROR:boot_control_recovery.cc(155)] Unable to mark slot A as bootable: Operation not permitted
[0617/224002:WARNING:download_action.cc(197)] Unable to mark new slot A. Proceeding with the update anyway.
[0617/224002:INFO:multi_range_http_fetcher.cc(45)] starting first transfer
[0617/224002:INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 1106+730303102
Step 1/2[0617/224002:INFO:delta_performer.cc(201)] Completed 0/? operations, 16384/730303102 bytes downloaded (0%), overall progress 0%
[0617/224002:INFO:delta_performer.cc(544)] Manifest size in payload matches expected value from Omaha
[0617/224002:INFO:delta_performer.cc(1369)] Verifying metadata hash signature using public key: /etc/update_engine/update-payload-key.pub.pem
[0617/224002:INFO:delta_performer.cc(1411)] Metadata hash signature matches value in Omaha response.
[0617/224002:INFO:delta_performer.cc(1431)] Detected a 'full' payload.
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old boot sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new boot sha256: 7sseQdNxPzpof5gw06pO3kxbGAgrRWt0fLhFTqW1di4= size: 39817216
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old system sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new system sha256: oLanZrAGfJ7MqFRrqbwKe4Z1mCaK46v/ezPPJSp1Fi8= size: 3221225472
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old vendor sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new vendor sha256: gS4RsefgJ3Qh1ZSLK5t0ctCDRdVZHLSynExBqW/Iq7g= size: 2147483648
[0617/224002:INFO:delta_performer.cc(368)] Applying 19 operations to partition "boot"
[0617/224002:INFO:delta_performer.cc(661)] Starting to apply update payload operations
[0617/224004:INFO:delta_performer.cc(368)] Applying 1536 operations to partition "system"
[0617/224017:INFO:delta_performer.cc(201)] Completed 136/2579 operations (5%), 116850688/730303102 bytes downloaded (16%), overall progress 10%
[0617/224030:INFO:delta_performer.cc(201)] Completed 289/2579 operations (11%), 219103232/730303102 bytes downloaded (30%), overall progress 20%
[0617/224043:INFO:delta_performer.cc(201)] Completed 421/2579 operations (16%), 321339392/730303102 bytes downloaded (44%), overall progress 30%
[0617/224046:ERROR:xz_extent_writer.cc(89)] xz_dec_run returned XZ_DATA_ERROR
[0617/224046:ERROR:delta_performer.cc(937)] writer->Write(buffer_.data(), operation.data_length()) failed.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:delta_performer.cc(288)] Failed to perform REPLACE_XZ operation 452, which is the operation 433 in partition "system"
[0617/224046:ERROR:download_action.cc(325)] Error ErrorCode::kDownloadOperationExecutionError (28) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
[0617/224046:INFO:delta_performer.cc(304)] Discarding 832792 unused downloaded bytes
[0617/224046:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
[0617/224046:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 200
[0617/224046:INFO:multi_range_http_fetcher.cc(126)] Terminating.
[0617/224046:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadOperationExecutionError
[0617/224046:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
[0617/224046:INFO:update_attempter_android.cc(294)] Processing Done.
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)Updater process ended with ERROR: 1
I:Install took 44 second(s).
Error installing zip file '/sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip'
Updating partition details...
Iata backup size is 0MB, free: 46234MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
always shows me this error
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)Updater process ended with ERROR: 1"
ive tried installing this on stock pie as well as stock oreo always get this error
ps i can install stock rom via xiaomi flash
i have tried installing rom from different versions of twrp as well
Hi there! I'm trying to flash LineageOS-microG version (https://lineage.microg.org), but after successful (?) installation WiFi isn't working, I'm getting an error "Failed or timed out awaiting driver ready":
Code:
09-25 19:15:36.920 894 894 E WifiHAL : Timed out wating on Driver ready ...
09-25 19:15:36.921 894 894 E [email protected]: Failed or timed out awaiting driver ready
09-25 19:15:36.921 894 894 E [email protected]: Failed to start legacy HAL: TIMED_OUT
09-25 19:15:36.929 1307 3910 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
09-25 19:15:36.929 1307 3910 E WifiVendorHal: Failed to create STA iface
09-25 19:15:36.929 1307 3910 E WifiNative: Failed to create iface in vendor HAL
09-25 19:15:36.930 1307 3910 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
I've downloaded latest "-microG-bramble-recovery.img" and "-microG-bramble.zip" form https://download.lineage.microg.org/bramble/, flashed recovery, rebooted into it and flashed zip as described in official LineageOS wiki https://wiki.lineageos.org/devices/bramble/install#installing-lineageos-from-recovery.
After rebooting and post-install setup WiFi is not working :/
Official LineageOS images works fine. So, what I'm doing wrong?
I've also unpacked "payload.bin" from this image https://download.lineage.microg.org/bramble/lineage-18.1-20210914-microG-bramble.zip with some python script https://github.com/cyxx/extract_android_ota_payload and there are some noticeable differences in official and microG LineageOS editions:
LineageOS-microG payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
280M ./system_ext.img
553M ./product.img
710M ./vendor.img
1,1G ./system.img
2,8G .
Official LineageOS payload.bin:
Code:
4,0K ./vbmeta_system.img
8,0K ./vbmeta.img
44K ./devcfg.img
56K ./qupfw.img
80K ./xbl_config.img
88K ./featenabler.img
124K ./uefisecapp.img
192K ./aop.img
236K ./keymaster.img
404K ./hyp.img
1,0M ./abl.img
2,9M ./tz.img
3,5M ./xbl.img
16M ./dtbo.img
96M ./boot.img
96M ./vendor_boot.img
147M ./modem.img
280M ./system_ext.img
710M ./vendor.img
948M ./product.img
2,6G ./system.img
4,9G .
Does this mean that LineageOS-microG images are broken in some way or something?
Thanks!
I had the same issues with newer versions for Pixel 5, only initial 18.1 works fine. LineageOS for microG have huge issues with connectivity for redfin, they even don't have reachable support anywhere...
Update: I just managed to install a version of Lineage-18.1-20211021-microg-redfin-recovery.img (newest) with a fully operating MicroG and a working flawlessly WiFi/cellular connectivity - I used CalyxOS installer (to update Pixel 5 firmware during the installation), then I unlocked the bootloader (in CalyxOS dev. options and later in fastboot by typing "fastboot flashing unlock" through adb), and get rid of Calyx by making a wipe and install LineageOS recovery and LineageOS for microG image.
CalyxOS has installation module for Pixel 4, so I hope it could be helpful for you.
I have the same problem. The last build of Los4microG that works is the from May 21. Would a simple firmware update do the trick as well?