Development [FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices

Search This thread

shawn4sp

Member
Mar 1, 2022
18
2
System OTA updated to A.08 from A.05 successfully just now.
Previously, OTA update would fail.
Is this something new? Still has unlocked bootloader.
Strange.
 

penguinus

Senior Member
Nov 29, 2009
66
70
OnePlus 5
OnePlus 9RT
Does anyone have an error that can't send images on telegram?
Both a07 & a08
Found what causes an issue. It happens because of old fastboot version in firmware package, it does wipe before flashing incorrectly in some way.
In order to fix it, you should do wipe/factory reset in system settings or in recovery. Please note all data will be erased. Don't forget to do backup and restore it after wipe!
 
  • Like
Reactions: onizuka.csgo

Cathair2906

Senior Member
Sep 2, 2012
114
115
System OTA updated to A.08 from A.05 successfully just now.
Previously, OTA update would fail.
Is this something new? Still has unlocked bootloader.
Strange.
i still got no clue on this, i tried A.05 and A.07, both cannot install OTA...
 

Attachments

  • WhatsApp Image 2022-06-05 at 4.44.32 PM.jpeg
    WhatsApp Image 2022-06-05 at 4.44.32 PM.jpeg
    101.4 KB · Views: 21

Cathair2906

Senior Member
Sep 2, 2012
114
115
i used the logcat and found the reason why OTA fail

06-05 20:11:17.627 1996 1996 E update_engine: [0605/201117.627895:ERROR:delta_performer.cc(444)] Unable to open ECC source partition dsp on slot A, file /dev/block/bootdevice/by-name/dsp_a: Success (0)
06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.627977:ERROR:delta_performer.cc(1242)] 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.
06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.628023:ERROR:delta_performer.cc(1247)] Expected: sha256|hex = 46FE89355C4F4B1162A0464AF50B092417768BA9BC45E0B431DC2D949C3FF758
06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.628062:ERROR:delta_performer.cc(1250)] Calculated: sha256|hex = 804199F4965AC57C84ABC8EDBEB654765FE99713885AEFE55399186C03F58A24
06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.628106:ERROR:delta_performer.cc(1261)] Operation source (offset:size) in blocks: 0:2

06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.628155:ERROR:delta_performer.cc(307)] Failed to perform SOURCE_COPY operation 8160, which is the operation 0 in partition "dsp"
06-05 20:11:17.628 1996 1996 E update_engine: [0605/201117.628199:ERROR:download_action.cc(336)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-05 20:11:17.629 1996 1996 I update_engine: [0605/201117.629038:INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-05 20:11:17.629 1996 1996 I update_engine: [0605/201117.629102:INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
06-05 20:11:17.629 1996 1996 I update_engine: [0605/201117.629142:INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-05 20:11:17.656 1814 2375 D OplusFeatureBrightnessBarController: mDarkLevel: 0
06-05 20:11:17.703 1996 1996 I update_engine: [0605/201117.703072:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
06-05 20:11:17.703 1996 1996 I update_engine: [0605/201117.703321:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-05 20:11:17.703 1996 1996 I update_engine: [0605/201117.703377:INFO:update_attempter_android.cc(686)] Processing Done.
 

Valdem

Senior Member
Nov 3, 2015
72
55
OxygenOS OTA for this device is incremental and each of them can be installed only over the proper previous version. Most probably that you try to install incorect incremental OTA (doens't match required previous version).
I can do this assumption by you logcat messages (installer do check of correctness of current version because it use it for diff patch to new version). It reports about wrong checksum for one of partition. But there shoudn't be any issues if you use full installer from the OP and do OTA upgrade over it.
 

Valdem

Senior Member
Nov 3, 2015
72
55
FYI. Original post was updated with new version of A.08 firmware. @penguinus find the solution for issues with some application (telegram, gmail) which works with device filesystem. Issue is related to specific version of `platform-tools`, which used to flash device. Tools do device cleanup incorrectly. New version include fix for this issue.
Issue can be fixed without full flashing of this firmware. Just by factory reset of device from the menu.

!!!DO BACKUP!!! of you data before this operation. Do not use TWRP for this operation because TWRP storing dump of `userdata` partition and restoring it after factory reset most probably return the original issue.
 
  • Like
Reactions: raghu102

Cathair2906

Senior Member
Sep 2, 2012
114
115
OxygenOS OTA for this device is incremental and each of them can be installed only over the proper previous version. Most probably that you try to install incorect incremental OTA (doens't match required previous version).
I can do this assumption by you logcat messages (installer do check of correctness of current version because it use it for diff patch to new version). It reports about wrong checksum for one of partition. But there shoudn't be any issues if you use full installer from the OP and do OTA upgrade over it.
But the OTA files were downloaded by itself automatically, so is it OTA server issue? And will it be fix after install full installer in the future?
 

Valdem

Senior Member
Nov 3, 2015
72
55
But the OTA files were downloaded by itself automatically, so is it OTA server issue? And will it be fix after install full installer in the future?
From your logcat messages, it is obvious that checksum on a 'dsp' partition is not corresponds to an expected value. This means that this partition was modified (TBH I do not understand "why" and "who" did this). You will not be able to flash any OTA update till you have modified system's partitions on the device.
If your device is rooted, you will need to uninstall magisk before install OTA and re-install it after flashing OTA.

In your case you can restore system's partition by flashing the firmware from the original post. There is latest stable version A.08 available. It is possible to flash the firmware without wiping user data (using 'upgrade.bat' script).
 

Cathair2906

Senior Member
Sep 2, 2012
114
115
From your logcat messages, it is obvious that checksum on a 'dsp' partition is not corresponds to an expected value. This means that this partition was modified (TBH I do not understand "why" and "who" did this). You will not be able to flash any OTA update till you have modified system's partitions on the device.
If your device is rooted, you will need to uninstall magisk before install OTA and re-install it after flashing OTA.

In your case you can restore system's partition by flashing the firmware from the original post. There is latest stable version A.08 available. It is possible to flash the firmware without wiping user data (using 'upgrade.bat' script).
Actually i did flash the firmware from this post, and never rooted it...

I also able to relocked the bootloader, however OTA still failed.
 

Valdem

Senior Member
Nov 3, 2015
72
55
Actually i did flash the firmware from this post, and never rooted it...

I also able to relocked the bootloader, however OTA still failed.
Situation is really weird. Could you tell which current version of OxygenOS on your device now. And, if you remember, which version of ColorOS was on device before flashing OxygenOS.
Looks like integrity of this partition is not checked by the bootloader (it is why you was able to lock bootloader). However I don't know what is really happened with your `dsp` partition. Most probably it was not correctly flashed when you convert your device to OxygenOS.

If bootloader on your device is locked now - there is no way to fix this issue without wiping user data on device. Otherwise you can flash latest version firmware from the original post. To be sure that you doesn't have the same issue I would recommend to flash an A.07 version and do OTA upgrade to A.08 version. After successful upgrade to A.08 you can relock the bootloader.
 

Cathair2906

Senior Member
Sep 2, 2012
114
115
Situation is really weird. Could you tell which current version of OxygenOS on your device now. And, if you remember, which version of ColorOS was on device before flashing OxygenOS.
Looks like integrity of this partition is not checked by the bootloader (it is why you was able to lock bootloader). However I don't know what is really happened with your `dsp` partition. Most probably it was not correctly flashed when you convert your device to OxygenOS.

If bootloader on your device is locked now - there is no way to fix this issue without wiping user data on device. Otherwise you can flash latest version firmware from the original post. To be sure that you doesn't have the same issue I would recommend to flash an A.07 version and do OTA upgrade to A.08 version. After successful upgrade to A.08 you can relock the bootloader.
No worries, i can wipe the userdata and flash the latest A.08 once again.

I have forgotten which colorOS it was, but the first time i flashed was A.07 version, but cannot OTA
 
Last edited:

Cathair2906

Senior Member
Sep 2, 2012
114
115
No worries, i can wipe the userdata and flash the latest A.08 once again.

I have forgotten which colorOS it was, but the first time i flashed was A.07 version, but cannot OTA
interesting, after i unlocked and flashed the latest A.08 then flash A.07 once again, the OTA work successfully.....
 

Attachments

  • Screenshot_2022-06-07-20-40-18-38_f7aa348215f5d566f9e4ca860f474209.jpg
    Screenshot_2022-06-07-20-40-18-38_f7aa348215f5d566f9e4ca860f474209.jpg
    326.8 KB · Views: 18
  • Screenshot_2022-06-07-20-40-43-16_f7aa348215f5d566f9e4ca860f474209.jpg
    Screenshot_2022-06-07-20-40-43-16_f7aa348215f5d566f9e4ca860f474209.jpg
    346.6 KB · Views: 19

onizuka.csgo

Member
Jul 18, 2017
11
1
Problem: QUALCOMM CrashDump Mode: dm-verity device corrupted verity_ctr

I found a way to fix it
I realize that many people will encounter this error when Windows cannot automatically update drivers

2 drivers are required to install oxygen os
1. Oneplus driver in fastboot mode
2. Qualcomm driver in fastbootD mode

you can search google how to install
 
  • Haha
Reactions: g96818

Top Liked Posts