• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

How To Guide Bypass "System update failed" - Update w/ Fastboot

Search This thread
Manual Update w/ Fastboot

This process does not include a data wipe.
Wiping data should be done at your own discretion.

Grab payload_dumper (https://github.com/vm03/payload_dumper)
Download update from the Asus site (ie. WW-18.0840.2104.56)
Extract the payload.bin from update to the payload_dumper folder
Follow the instructions to run payload_dumper on the payload.bin

If you have fastboot installed (ie. Android SDK), skip this section

Download the ASUS_1.1.63-Fastboot.zip file
Extract the contents to the output folder of payload_dumper
This is the same fastboot included in the raw firmware files

Once fastboot is available, you may continue the update process

Download the flash_all.sh.zip file attached to this post
Extract the script to the output folder of payload_dumper
Reboot your phone into bootloader (volume up + power)
Connect your phone and run the script (Mac / Linux)

The following errors are perfectly normal and can be ignored:
(Script updated. Flashing non-hlos image should be resolved)
Code:
FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
Code:
Invalid sparse file format at header magic

Once the phone reboots, launch settings to verify the version number

Restoring Magisk

Copy the boot.img from payload_dumper output to the phone
Run Magisk and patch the file
Copy the patched file back to the computer
Flash the boot.img with "fastboot flash boot [file name]"


Background

Update notifications appeared, the update was recognized, but it would fail instantly. With days between responses from Asus, I didn't have time for their shenanigans.

Code:
06-26 06:38:27.804  1510  1510 E update_engine: DM_DEV_REMOVE failed for [vendor_b]: Device or resource busy
06-26 06:38:27.806  1510  1510 E update_engine: Could not delete snapshot device: vendor_b
06-26 06:38:27.807  1510  1510 E update_engine: DM_DEV_REMOVE failed for [product_b]: Device or resource busy
06-26 06:38:27.808  1510  1510 E update_engine: Could not delete snapshot device: product_b
06-26 06:38:27.809  1510  1510 E update_engine: DM_DEV_REMOVE failed for [system_ext_b]: Device or resource busy
06-26 06:38:27.810  1510  1510 E update_engine: Could not delete snapshot device: system_ext_b
06-26 06:38:27.811  1510  1510 E update_engine: DM_DEV_REMOVE failed for [odm_b]: Device or resource busy
06-26 06:38:27.812  1510  1510 E update_engine: Could not delete snapshot device: odm_b
06-26 06:38:27.813  1510  1510 E update_engine: Could not remove all snapshots
06-26 06:38:27.814  1510  1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(759)] Cannot begin new update.
06-26 06:38:27.815  1510  1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(463)] PrepareSnapshotPartitionsForUpdate failed in Android mode
06-26 06:38:27.816  1510  1510 E update_engine: [ERROR:delta_performer.cc(1411)] Unable to initialize partition metadata for slot A
06-26 06:38:27.816  1510  1510 I update_engine: [INFO:delta_performer.cc(1325)] [UpdateEngine] ParseManifestPartitions :  Orignal  required_size = 0
06-26 06:38:27.817  1510  1510 E update_engine: [ERROR:download_action.cc(336)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-26 06:38:27.817  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-26 06:38:27.818  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
06-26 06:38:27.818  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-26 06:38:27.822  1510  1510 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
06-26 06:38:27.822  1510  1510 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-26 06:38:27.823  1510  1510 I update_engine: [INFO:update_attempter_android.cc(523)] Processing Done.
06-26 06:38:27.824  2954  3366 I UpdateLauncher: status: 0, percent:0.0
06-26 06:38:27.826  2954  3366 I SeamlessUpdateNotifier: percent:0
06-26 06:38:27.826  1510  1510 I update_engine: [INFO:metrics_reporter_android.cc(131)] Current update attempt downloads 0 bytes data
06-26 06:38:27.828  2954  3366 I UpdateLauncher: errorCode: 7
06-26 06:38:27.830  2954  3366 I SeamlessUpdateNotifier: percent:-1
06-26 06:38:27.831  2954  3366 I SeamlessUpdateNotifier: show update fail dialog

I have since resolved the error by flashing a raw firmware that did not require wiping the device.
 

Attachments

  • ASUS_1.1.63-Fastboot.zip
    24.7 MB · Views: 89
  • flash_all.sh.zip
    851 bytes · Views: 22
Last edited:
Your rog flashed 5 times with the edl repair and then tried the update, maybe something was shot by the custom kernel that you tried to flash / boot
No idea how that is possible. I've only flashed the repair once and the kernel was stock. Possibly something I wasn't supposed to uninstall to perform updates.

Edit: updated manually so we'll see what happens next time.
 
Last edited:

BILLYB187

Senior Member
May 9, 2014
52
29
Some many times I had rebooted
Someone on zentalk stated that rolling the last number one number higher will prompt the install as well. The downside is if the next official comes in with that number you have to manual update again using the same method.

I have not tried this myself and have not seen any proof of work. Proceed at your own risk here.
 
  • Like
Reactions: twistedumbrella
Someone on zentalk stated that rolling the last number one number higher will prompt the install as well. The downside is if the next official comes in with that number you have to manual update again using the same method.

I have not tried this myself and have not seen any proof of work. Proceed at your own risk here.

They usually skip a few incremental version numbers, so it may even work without causing issues for future updates.
 

JazonX

Senior Member
Dec 16, 2009
1,799
713
Xiaomi Mi 11 Ultra
System update fails if the device fingerprint doesn't match the firmware fingerprint. By Fingerprint I mean Device ID embedded in Vendor Partition.

Eg: If you have Tencent Hardware with a WW Rom installed on it, and if you haven't edited the fingerprint (Device ID) of the device to WW, It will never accept WW OTA Files automatically, you will always have to use fastboot.


This file is located in the Vendor image, and you can edit it using root explorer.

You can read more here - Changing Fingerprint from CN to WW

Doing this once fixes it for good, and never again you'll have to use manual updates.
 
System update fails if the device fingerprint doesn't match the firmware fingerprint. By Fingerprint I mean Device ID embedded in Vendor Partition.

Eg: If you have Tencent Hardware with a WW Rom installed on it, and if you haven't edited the fingerprint (Device ID) of the device to WW, It will never accept WW OTA Files automatically, you will always have to use fastboot.


This file is located in the Vendor image, and you can edit it using root explorer.

You can read more here - Changing Fingerprint from CN to WW

Doing this once fixes it for good, and never again you'll have to use manual updates.

Actually, the manual updates will always be required if you unlock the bootloader. The Asus app may or may not be to blame for that.

Fingerprint issues are most often found on devices with the notification about mismatched firmware. This one was something with the active partition or the installer itself. Flashing raw firmware fixed it and restored regular installation.

I'm sure the info will be useful for anyone that thinks they would be able to fix a fingerprint issue by flashing firmware, though, since it won't solve it.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Manual Update w/ Fastboot

    This process does not include a data wipe.
    Wiping data should be done at your own discretion.

    Grab payload_dumper (https://github.com/vm03/payload_dumper)
    Download update from the Asus site (ie. WW-18.0840.2104.56)
    Extract the payload.bin from update to the payload_dumper folder
    Follow the instructions to run payload_dumper on the payload.bin

    If you have fastboot installed (ie. Android SDK), skip this section

    Download the ASUS_1.1.63-Fastboot.zip file
    Extract the contents to the output folder of payload_dumper
    This is the same fastboot included in the raw firmware files

    Once fastboot is available, you may continue the update process

    Download the flash_all.sh.zip file attached to this post
    Extract the script to the output folder of payload_dumper
    Reboot your phone into bootloader (volume up + power)
    Connect your phone and run the script (Mac / Linux)

    The following errors are perfectly normal and can be ignored:
    (Script updated. Flashing non-hlos image should be resolved)
    Code:
    FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
    Code:
    Invalid sparse file format at header magic

    Once the phone reboots, launch settings to verify the version number

    Restoring Magisk

    Copy the boot.img from payload_dumper output to the phone
    Run Magisk and patch the file
    Copy the patched file back to the computer
    Flash the boot.img with "fastboot flash boot [file name]"


    Background

    Update notifications appeared, the update was recognized, but it would fail instantly. With days between responses from Asus, I didn't have time for their shenanigans.

    Code:
    06-26 06:38:27.804  1510  1510 E update_engine: DM_DEV_REMOVE failed for [vendor_b]: Device or resource busy
    06-26 06:38:27.806  1510  1510 E update_engine: Could not delete snapshot device: vendor_b
    06-26 06:38:27.807  1510  1510 E update_engine: DM_DEV_REMOVE failed for [product_b]: Device or resource busy
    06-26 06:38:27.808  1510  1510 E update_engine: Could not delete snapshot device: product_b
    06-26 06:38:27.809  1510  1510 E update_engine: DM_DEV_REMOVE failed for [system_ext_b]: Device or resource busy
    06-26 06:38:27.810  1510  1510 E update_engine: Could not delete snapshot device: system_ext_b
    06-26 06:38:27.811  1510  1510 E update_engine: DM_DEV_REMOVE failed for [odm_b]: Device or resource busy
    06-26 06:38:27.812  1510  1510 E update_engine: Could not delete snapshot device: odm_b
    06-26 06:38:27.813  1510  1510 E update_engine: Could not remove all snapshots
    06-26 06:38:27.814  1510  1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(759)] Cannot begin new update.
    06-26 06:38:27.815  1510  1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(463)] PrepareSnapshotPartitionsForUpdate failed in Android mode
    06-26 06:38:27.816  1510  1510 E update_engine: [ERROR:delta_performer.cc(1411)] Unable to initialize partition metadata for slot A
    06-26 06:38:27.816  1510  1510 I update_engine: [INFO:delta_performer.cc(1325)] [UpdateEngine] ParseManifestPartitions :  Orignal  required_size = 0
    06-26 06:38:27.817  1510  1510 E update_engine: [ERROR:download_action.cc(336)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
    06-26 06:38:27.817  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
    06-26 06:38:27.818  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
    06-26 06:38:27.818  1510  1510 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
    06-26 06:38:27.822  1510  1510 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
    06-26 06:38:27.822  1510  1510 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
    06-26 06:38:27.823  1510  1510 I update_engine: [INFO:update_attempter_android.cc(523)] Processing Done.
    06-26 06:38:27.824  2954  3366 I UpdateLauncher: status: 0, percent:0.0
    06-26 06:38:27.826  2954  3366 I SeamlessUpdateNotifier: percent:0
    06-26 06:38:27.826  1510  1510 I update_engine: [INFO:metrics_reporter_android.cc(131)] Current update attempt downloads 0 bytes data
    06-26 06:38:27.828  2954  3366 I UpdateLauncher: errorCode: 7
    06-26 06:38:27.830  2954  3366 I SeamlessUpdateNotifier: percent:-1
    06-26 06:38:27.831  2954  3366 I SeamlessUpdateNotifier: show update fail dialog

    I have since resolved the error by flashing a raw firmware that did not require wiping the device.
    1
    Some many times I had rebooted
    Someone on zentalk stated that rolling the last number one number higher will prompt the install as well. The downside is if the next official comes in with that number you have to manual update again using the same method.

    I have not tried this myself and have not seen any proof of work. Proceed at your own risk here.