Hi all, I made 4 upgrade from e-os 1.9 to 1.10
1st : MI8 dipper : OK
2nd : Lenovo tab YTX703F : OK
3rd : Samsung a5xelte : OK
4th : Oneplus8T kebab : fail 
installation error
unfortunately the kebab is my daily device
So 2 questions :
1-Am I the only one?
2-How can I get the logfile of the failing update process
Hi @PraksuQ , I have a similar issue (install error) with my Oneplus 8T kebab.
Could you tell me how to get the install logfile
Thanks in advance
thanks again for your kindness @PraksuQ.
My issue was similar to yours. As you say a more explicit message could be useful.
Just an update to your post, to fix that issue you have to use adb with both USB debug and rooted debug active on your device developper options and enter following command :
adb root
adb enable-verity
adb reboot
Obviously you have to launch again the update process.
hereunder my logcat file.
04-22 14:15:12.199 1449 1449 I update_engine: [INFO:payload_metadata.cc(221)] Metadata hash signature matches value in Omaha response.
04-22 14:15:12.205 1449 1449 I update_engine: [INFO:delta_performer.cc(1049)] Detected a ‘full’ payload.
04-22 14:15:12.208 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] dtbo does’t have version, skipping downgrade check.
04-22 14:15:12.212 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] recovery does’t have version, skipping downgrade check.
04-22 14:15:12.213 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta does’t have version, skipping downgrade check.
04-22 14:15:12.214 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta_system does’t have version, skipping downgrade check.
04-22 14:15:12.220 1449 1449 I update_engine: [INFO:delta_performer.cc(811)] Preparing partitions for new update. last hash = , new hash = NxhiHj6XhqdAaIKaPKX+RfSvMl2dZcEeyNF+PJQfGwc=NXo245miAOwwvRcgPrpGH5FoqUEEKcqbYaVqLoZSd7Q=
04-22 14:15:12.223 1449 1449 I update_engine: [INFO:delta_performer.cc(1394)] Resetting recorded hash for prepared partitions.
04-22 14:15:12.227 1449 1449 W update_engine: [WARNING:dynamic_partition_control_android.cc(441)] overlayfs overridesare active and can interfere with our resources.
04-22 14:15:12.227 1449 1449 W update_engine: run adb enable-verity to deactivate if required and try again.
04-22 14:15:12.228 1449 1449 I update_engine: EnsureMetadataMounted does nothing in Android mode.
04-22 14:15:12.230 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(762)] Erasing AVB footer of system_other partition before update.
04-22 14:15:12.231 1449 1449 E update_engine: [libfs_mgr]ReadFstabFromFile(): cannot open file: ‘/system/etc/fstab.postinstall’: No such file or directory
04-22 14:15:12.232 1449 1449 W update_engine: [WARNING:dynamic_partition_control_android.cc(636)] Cannot read fstab from /system/etc/fstab.postinstall: No such file or directory (2)
04-22 14:15:12.233 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(663)] AVB is not enabled on system_other. Skip erasing.
04-22 14:15:12.234 1449 1449 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.237 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(331)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
04-22 14:15:12.238 1449 1449 I update_engine: Update has been initiated, now canceling
04-22 14:15:12.239 1449 1449 I update_engine: Removing all update state.
04-22 14:15:12.240 1449 1449 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-22 14:15:12.242 1449 1449 W update_engine: Failed to get flashing status
04-22 14:15:12.243 1449 1449 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-22 14:15:12.245 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.246 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.247 685 685 I bootcontrolhal: set_snapshot_merge_status: MergeStatus = 0, current_slot = 1, returning: true
04-22 14:15:12.248 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.249 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.250 685 685 I bootcontrolhal: set_snapshot_merge_status: MergeStatus = 0, current_slot = 1, returning: true
04-22 14:15:12.252 1449 1449 E update_engine: Cannot create update snapshots with overlayfs setup. Run adb enable-verity, reboot, then try again.
04-22 14:15:12.254 1449 1449 E update_engine: [ERROR:dynamic_partition_control_android.cc(952)] Cannot create update snapshots: Error
04-22 14:15:12.255 1449 1449 E update_engine: [ERROR:dynamic_partition_control_android.cc(497)] PrepareSnapshotPartitionsForUpdate failed in Android mode
04-22 14:15:12.256 1449 1449 E update_engine: [ERROR:delta_performer.cc(822)] Unable to initialize partition metadatafor slot A
04-22 14:15:12.257 1449 1449 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer’s Write method when processing the received payload – Terminating processing
04-22 14:15:12.265 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
04-22 14:15:12.267 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
04-22 14:15:12.268 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
04-22 14:15:12.269 1449 1449 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
04-22 14:15:12.270 1449 1449 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
04-22 14:15:12.271 1449 1449 I update_engine: [INFO:update_attempter_android.cc(565)] Processing Done.
04-22 14:15:12.273 1449 1449 I update_engine: [INFO:metrics_reporter_android.cc(159)] Current update attempt downloads 0 bytes data
tout est ok
merci
Still not available for FP4.
Builds will be rolling out in a staggered manner over the next couple of days. It will be released for a few devices at a time.
@Manoj may be I’m wrong, but I think that an install error on both a Pixel redfin and a oneplus kebab are not coincidental.
Probably maintainer/dev team should have a look on these issues.
After solving that problem, everythink is OK on my Kebab device.
Thanks to the team for the work done.
Notes cannot be folded back as before. You can only add notes, since on the right there’s only a “+” sign. Very inconvenient to scroll through all the notes.
For what I know, is not because your phone is rooted. Maybe it depends on what channel (stable or dev).
But, as @Cabnedor and many others, me too I’m waiting for the OTA update, which arrives every time some days after others devices:
Don’t care, only wait.
Everything is working fine so far, update process without major problems (download v1.10 stuck first, after phone reboot it worked well).
Fairphone FP2
(no idea whats the ‘Device CodeName’ for FP2)
Update from 1.9-r-20230312268580
not rooted
Confirm - default camera app is fixed
Vendor Name: Samsung
Device name: Samsung S9 SM-G960F
Device CodeName: starlte
Version of /e/OS or Stock which existed previously: 1.9-q-20230312268823-dev-starlte
Is the device Rooted / Not rooted: Not rooted
Just update to 1.10-20230416280390-dev-starlte and everything work perfectly 
Installation time (without the downloading phase) took less than 3 min. Well done /e/ team !!!
Thank you.
Well, then in my case it’s easy: Device name = Device CodeName = FP2
Update went flawlessly, no problems discovered so far
Hi everybody,
on my side, I had to wait some days to have the update on my device while it was already available in the repo. But now it’s ok.
For the moment (today), I didn’t do so much tests but what is working fine:
Thanks to /e/OS team again & again!!
MIB
Can’t add murena account. Login fails. I’m using 2FA and have created an app password. Phone is almost useless now. Please help!
Please @shawn10thompson can you include the Android version in use; in this case probably best if possible to specify the (Edit, my lack of attention 
) can you confirm that e-1.10-s-20230413279105-dev-kiev.zip was responsible for this failure.
After a nearly entire April month without GPS more than 1 or 2 minutes in my 2 usual apps, updating to 1.10 (Q) on 22th didn’t help.
See https://gitlab.e.foundation/e/backlog/-/issues/5984.
Hi,
I just updated to e-1.10-s-20230413279105-dev-monet.zip and since then I have no internet connection. An exclamation mark is visible on the network icon.
I deleted the APNs, removed and reinstated my SIM card. I reinstalled the update. The problem persists.
When I restart sometimes I have Internet and then it disconnects.
Thanks for your feedback,
Vendor Name : XIAOMI
Device name : Mi10 lite
Device CodeName : Monet
Version of /e/OS : 1.10
Is the device Rooted / Not rooted : NOT