Software update: FP4.TP2D.C.0112.20240313

[yvmuell]

Release date: 4th April 2024
Android version: 13
Software Version: FP4.TP2D.C.0112
Security Patch Level: 5th March 2024

Changes

• An issue that was causing the screen brightness to drop when entering the Camera settings has been solved.
• An issue that was causing the “Display network name” feature not to work as intended has been solved.
• An issue that was causing the battery capacity not to show correctly on third-party apps has been solved.
• An issue that was causing the Settings to be unresponsive when exiting Guest mode has been solved.

[bm90001]

The update was flawless and successful.

[OldRoutard]

OK here too, so far.

[Razem]

@yvmuell

An issue that was causing the “Display network name” feature not to work as intended has been solved.

Nice, this finally works as expected.

@yvmuell

An issue that was causing the battery capacity not to show correctly on third-party apps has been solved.

Cool, I was quite confused by this (it used to report 3300 mAh instead of 3905).

[Lars_Hennig]

For me installation fails after removing Magisk and reboot the phone. The error is too generic to guess what the root cause is.
After another reboot I still cannot install the update with the same error.

[zetrick]

Also on my side no issues (stock Android without any rooting).

[Geron]

Vanilla went through fine for me as well.

[Lars_Hennig]

The error is cause by a checksum mismatch and I am still searching for a way to work around that. Any idea is appreciated

04-07 09:55:17.932 1663 1663 E update_engine: [ERROR:partition_writer.cc(317)] 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. 04-07 09:55:17.933 1663 1663 E update_engine: [ERROR:partition_writer.cc(322)] Expected: sha256|hex = 26D983B114AFD6E18F1692BC60C3073A850711F90CDEA6B0FCCAE84526BB2883 04-07 09:55:17.934 1663 1663 E update_engine: [ERROR:partition_writer.cc(325)] Calculated: sha256|hex = DE99A29DA1F76EFF1C2E81030C84B235279397A1E8AAB3F89A43BCF2533F1590 04-07 09:55:17.935 1663 1663 E update_engine: [ERROR:partition_writer.cc(336)] Operation source (offset:size) in blocks: 0:824 04-07 09:55:17.936 1663 1663 E update_engine: [ERROR:partition_writer.cc(261)] source_fd != nullptr failed. 04-07 09:55:17.937 1663 1663 E update_engine: [ERROR:delta_performer.cc(844)] partition_writer_->PerformDiffOperation( operation, error, buffer_.data(), buffer_.size()) failed. 04-07 09:55:17.938 1663 1663 E update_engine: [ERROR:delta_performer.cc(199)] Failed to perform BROTLI_BSDIFF operation 0, which is the operation 0 in partition "xbl" 04-07 09:55:17.939 1663 1663 E update_engine: [ERROR:download_action.cc(227)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing

BTW, this happens also when I try to run the ota manually via sideload

[yvmuell]

Havent read the error codes, is it the same?

Software update: FP4.FP4I.A.175.20221207

Yeah, your product partition has a hash miss-match. What I find interesting is how verbose those messages are, I’ve seen several hash errors, but never with whole paragraphs of explanation So somehow one of your partitons changed. If you didn’t install Magisk or something similar, probably a bit flipped for some reason. That usually shouldn’t happen. You could try to flash only that one partition, but honestly I wouldn’t trust the rest of the system at this point, flashing it f…

FP5 however similar?

OTA TT45.A.141 fails to install

When I try to install the OTA update it fails and the updater shows a generic “installation problem” message at the top. When I plug my device to Android Studio and open logcat it shows the following: 2024-02-08 08:58:16.989 1568-1568/? E/update_engine: [ERROR:verified_source_fd.cc(50)] Unable to open ECC source partition /dev/block/bootdevice/by-name/boot_b: Success (0) 2024-02-08 08:58:16.990 1568-1568/? E/update_engine: [ERROR:partition_writer.cc(317)] The hash of the source data on disk fo…

[Lars_Hennig]

I guess I found the root cause: The system images in the two slots seemed to be different. After syncing those the update did not run into the error again.

EDIT: Not that backup process ended successfully. It’s always surprising again and again, how things work perfectly fine if you do it right

[hirnsushi]

Usual link to the ota.zip and a Magisk patched-boot.img in case someone needs it (forgot to pull a stock boot.img this time, sorry).

Have fun

[Kenny]

Anyone on EE UK got this update yet? I’ve no sign of it and I usually get these on the day of the FP notification. Updater says I’m up to date but it’s the last update Build code.

[kfair]

I am also still waiting for the latest update. My security update says I am still on January but I think I have had an update since then.

I am running FP4.TP29.C.0101.20240121 so maybe not judging by the last few digits.

[JulianR]

Same here: I’m also in the UK on EE (via 1p Mobile). Has anyone in the UK received the update? What should we do to get it? Thanks!

[Kenny]

Thanks - I suppose we wait for EE to get round to releasing it! Mine is on a two year agreement about to run out but I’ve stayed with EE SIM only. I’ll see if the update comes along next week when it changes over. If not I’ll try contacting them to see what’s happening. They’re usually very quick to release an update so it’s strange they haven’t this time.