How To Guide Bypass "System update failed" - Update w/ Fastboot - ASUS ROG Phone 5 / 5s

Update notifications appeared, the update was recognized, but it failed instantly.
Spoiler: Error Stacktrace
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 without a wipe.
This post is for archival purposes or simply an alternative installation method
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
ASUS_Fastboot-Portable.zip | by twistedumbrella for ROG Phone 5
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
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]"

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

ChrisFeiveel said:
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
Click to expand...
Click to collapse
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.

Asus took 2 days just sending the form to "officially" investigate the issue. Nobody has time for their TPS Reports, so I found a way to install the update myself.

Updating to WW-18.0840.2104.56 with this method did not restore standard installation for WW18.0840.2106.86, but the scripts have been updated to fix the non-hlos image errors, which may fix updating for future versions.

We should unlock bootloader for this ?

jaleel (jelly) said:
We should unlock bootloader for this ?
Click to expand...
Click to collapse
No. You should not be using this method unless you are getting the specific error that the update fails. If your update is not failing, this may break it.

I'm having wifi problem I'm thinking to update but is not showing me I had changed to data in update but also it's was not recognise .. it seems like same version update will not show in update notification ..

If you already updated, the update is complete. Installing it a second time will not change anything in it.

I had download ota file from asus website keep in root storage then also not showing update .. oneplus will show update but asus seems not show

Make sure to reboot

twistedumbrella said:
Make sure to reboot
Click to expand...
Click to collapse
Some many times I had rebooted

jaleel (jelly) said:
Some many times I had rebooted
Click to expand...
Click to collapse
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.

BILLYB187 said:
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.
Click to expand...
Click to collapse
They usually skip a few incremental version numbers, so it may even work without causing issues for future 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.

JazonX said:
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.
Click to expand...
Click to collapse
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.

The more I think about it, this issue may have started when I did an update using the Magisk feature to preserve root using an inactive partition.
I wonder if there was some sort of corruption with the partition it selected after doing it a few times. Something to keep in mind when you update, I guess.

Related

aosp kitkat4.4 nexus 7(deb) not boot

hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional

messages has stopped

Hello,
I seem to be locked out of my native messages application where I can read sms and mms.
When i launch it, it loads up, i see for about a second the messages thread bu then i get fc.
Tried to do a sms backup and i still get an error.
Cleared cache and dalvik in recovery and no luck.
Thanks
Code:
Device: htc_europe HTCSensation (pyramid)
OS: 4.1.2
Kernel: 3.4.10-SebastianFM-1.0.4
Software: ViperS 5.2.1
Description: 3.19.401.101 CL157254 release-keys
Characteristics: default
App: 7.13
7:12:30: An Error has occurred during backup: not an error (code 0)
7:12:30: Releasing cpu wake lock
7:12:30: Count: 0
7:12:30: ERROR! Error Creating Backup File : not an error (code 0): android.database.sqlite.SQLiteException: not an error (code 0)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.content.ContentProviderProxy.query(ContentProviderNative.java)
at android.content.ContentResolver.query(ContentResolver.java)
at android.content.ContentResolver.query(ContentResolver.java)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.saveXml(BackupProcessor.java:1322)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:114)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:143)
at com.riteshsahu.BackupRestoreCommon.TaskRunner.run(TaskRunner.java:294)
at java.lang.Thread.run(Thread.java)
7:12:30: Could not load Columns from contentUri, creating from mandatory columns : not an error (code 0): android.database.sqlite.SQLiteException: not an error (code 0)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.content.ContentProviderProxy.query(ContentProviderNative.java)
at android.content.ContentResolver.query(ContentResolver.java)
at android.content.ContentResolver.query(ContentResolver.java)
at com.riteshsahu.BackupRestoreCommon.Common.loadColumnList(Common.java:136)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.saveXml(BackupProcessor.java:1317)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:114)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:143)
at com.riteshsahu.BackupRestoreCommon.TaskRunner.run(TaskRunner.java:294)
at java.lang.Thread.run(Thread.java)
7:12:30: External storage is ready
7:12:30: Trying to getExternalStorageState
7:12:30: Acquiring cpu wake lock
7:12:30: Creating new Backup File:/storage/sdcard0/SMSBackupRestore/sms-20140807071224.xml
7:12:30: Creating New Backup. File: /storage/sdcard0/SMSBackupRestore/sms-20140807071224.xml
7:11:6: AmazonAds failed to load: The configuration was unable to be loadedCODE]

Mate 9 bootloop after Xposed install

Hello there.
Long story short: I have a Mate 9 MHA-L09 running on latest Oreo update which was rooted (with bootloader unlocked of course) and worked fine. I've installed Xposed (without making a backup, nice job me …) and, unfortunately, I'm now stuck in bootloop.
I've tried following methods:
starting in fastboot mode to recover using HiSuite but my Mate 9 isn't supported.
Boot on TWRP and tried to wipe data cache and dalvik but it didn't work.
Tried to install Oreo and Nougat updates from TWRP (with 3 archives on SD card: update.zip, update_data_public.zip and update_all_hw.zip) however I'm also getting and error when trying to install the first zip file (error 7 - "update_huawei_pkg_from_ota_zip: update package from zip failed")
I also tried the HWOTA method but after starting in TWRP and connecting a USB cable, the script seems frozen.
Maybe I'm using an incorrect function of TWRP? Or there is an easier method?
Any help would be greatly appreciated.
Thanks guys!
Tried to install latest MHA-L09C33 firmware and got an error 9 on TWRP.
Here is the log: https://pastebin.com/Yc0bnbfk
I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?
Gynsu2000 said:
I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?
Click to expand...
Click to collapse
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Thanks for the update and the command.
MHA-L09 8.0.0.316(C33)
ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay
Gynsu2000 said:
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay
Click to expand...
Click to collapse
I guess you could try:
Extract update.app from update.zip
Download Huawei Update Extractor
Open Huawei Update Extractor and go to options and uncheck header check.
Open update.app in Huawei Update Extractor.
Right click on system and extract selected.
Do the same for vendor.
Flash both using fastboot, then try Pretoriano80s TWRP again.
(you could try to boot phone after flashing system and vendor)
Another solution could be to:
Unpack Pretoriano80s TWRP with Android Image Kitchen, copy ramdisk/sbin/busybox and paste to desktop or somewhere not in the ramdisk folder.
Unpack Blackballs twrp and put the previously copied busybox in ramdisk/sbin/ then repack image and flash.
Then try HuRUpdater again.
For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !
Gynsu2000 said:
For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !
Click to expand...
Click to collapse
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Have been able to upgrade latest Oreo firmware using @Blackball twrp.
Just follow the instructions on his page.
1.Now that you have your correct firmware downloaded and intact.
2.Rename to this (update.zip, update_all_hw.zip, update_data_public.zip )
3.Download this file from here https://drive.google.com/file/d/1YM-Bga-wAKOct971WrrKCsX2K3tFP6zF/view?usp=sharing
4.Create a folder and rename to HWOTA8 , copy the downloaded file and the 3 firmware files
5.Now copy the the whole folder to your external storage and boot phone to twrp recovery.
6.Install by locating this file hwota8_update in the HWOTA8 folder on your external storage.
7.When done it will reboot and firmware upgrade processing will take over.
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:
ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
First thing I checked: bootloader was still unlocked.
Second thing: TWRP -> Backup.
golastic said:
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:
Click to expand...
Click to collapse
Thanks for the heads up. Hopefully I will backup thing first on TWRP before toying around with the phone.
ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.
Gynsu2000 said:
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.
Click to expand...
Click to collapse
I would do a full update again, oeminfo won't change model in about. Either using HWOTA as someone posted above or use HuRUpdater
Also, use Magisk instead of supersu. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In the end I used HWOTA8 and it worked like a charm. Until I discovered that I wasn't able to access a mobile network: SIM card is detected (icon in status bar have it displayed), however I'm not prompted for the sim's pin. First thing I checked was the sim lock using the super code: it's not (SIMLOCK_DEACTIVE). Then I've tried a couple of sims from other carriers but none of them are working.
Unless you guys have an idea, I suppose I should bring it to warranty.

Problem with Nokia Lumia 630 flashing

How can I flash my Nokia Lumia 630?
I tried on WPInternals, but it says:
Flash failed! Error 0x1106: Security header validation failed
I also tried THOR2, which also failed. It says:
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 16.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Can someone help me?
I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals
- Windows Device Recovery Tool
- NaviFirm
- Thor
Result from thor:
> thor2 -mode ffureader -ffufile "C:\rm-914\XXX.ffu" -dump_gpt -filedir C:\dump
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode ffureader -ffufile C:\rm-914\XXX.ffu -dump_gpt -filedir C:\dump
Process started Wed Dec 29 17:13:00 2021
Logging to file C:\Users\Angelo\AppData\Local\Temp\thor2_win_20211229171300_ThreadId-13244.log
Debugging enabled for ffureader
Initiating do FFUReader operations
Version of FfuReader is 2015061501
Parsing FFU... Please wait...
Failed to parse FFU file. Header size: 0x00000000, Payload size: 0x0000000000000000, Chunk size: 0x00000000, Header offset: 0x00000000, Payload offset: 0x0000000000000000
File open failed
THOR2_ERROR_FFUREAD_CORRUPTED_FFU
THOR2 1.8.2.18 exited with error code 84204 (0x148EC)
Any ideas?
Angelo Marzolla said:
I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals...
Click to expand...
Click to collapse
I don't have bricked Nokia, but did you format the whole phone storage when Windows said it's broken? Because it can be the reason why your phone is bricked.

[SOLVED] OTA fails: "Manifest contains minor version 7, but all full payloads should have version 0."

I am trying to upgrade my newly acquired OnePlus 7Pro to the latest OxygenOS (which seems to be manadatory prior to installing LineageOS.) Unfortunately the OTA reproducibly fails. Adb logcat shows me this here:
04-07 22:59:10.876 1471 1471 E update_engine: [0407/225910.876000:ERROR:delta_performer.cc(1867)] Manifest contains minor version 7, but all full payloads should have version 0.
04-07 22:59:10.876 1471 1471 E update_engine: [0407/225910.876062:ERROR:download_action.cc(336)] Error ErrorCode::kUnsupportedMinorPayloadVersion (45) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
04-07 22:59:10.876 1471 1471 I update_engine: [0407/225910.876178:INFO:delta_performer.cc(324)] Discarding 133098 unused downloaded bytes
04-07 22:59:10.876 1471 1471 I update_engine: [0407/225910.876723:INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
04-07 22:59:10.876 1471 1471 I update_engine: [0407/225910.876826:INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
04-07 22:59:10.876 1471 1471 I update_engine: [0407/225910.876881:INFO:multi_range_http_fetcher.cc(131)] Terminating.
04-07 22:59:10.880 1471 1471 I update_engine: [0407/225910.880834:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kUnsupportedMinorPayloadVersion
04-07 22:59:10.880 1471 1471 I update_engine: [0407/225910.880972:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
I also downloaded what seems to be the latest available firmware from the OnePlus website and tried "local upgrade", but the updater does not see the file. As a last resort I might install the update in the recovery via sideload, but I'd prefer to do it in the canonical way so as to be sure that I won't damage the phone.
Can anyone give me a headsup?
Thanks!
Obviously there is a bug in their firmware repository. Ultimately I downloaded the correct file and manually flashed it. So for me, this is solved.
Actually, the file I downloaded from the vendor's home page is not the latest version of the firmware, based on Android 12 but it is still at Android 11.

Categories

Resources