Help Couldnt install any custom rom whatsoever - Xiaomi Mi A2 / 6X Questions & Answers

heres a log
Installing zip file '/sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:AB zip
I:has_legacy_properties: Could not open /tmp/updater: No such file or directory!
I:Legacy property environment not used in updater.
Failed to parse build number in post-build-incremental=eng.rcstar.20190611.020532.
__bionic_open_tzdata: couldn't find any tzdata when looking for PAKST-5:30!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
[0617/224002:INFO:sideload_main.cc(207)] Update Engine Sideloading starting
[0617/224002:INFO:boot_control_recovery.cc(77)] Loaded boot_control HAL 'Boot control HAL' version 0.1 authored by 'Code Aurora Forum'.
[0617/224002:INFO:update_attempter_android.cc(207)] Using this install plan:
[0617/224002:INFO:install_plan.cc(77)] InstallPlan: new_update, source_slot: B, target_slot: A, url: file:///sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip, payload: (size: 730303102, metadata_size: 143458, metadata signature: , hash: B3621E6FF72FDADC09D057ABA4C33A710920E6009EC948044D95B047F1C524B3, payload type: unknown), hash_checks_mandatory: false, powerwash_required: false
[0617/224002:INFO:update_attempter_android.cc(391)] Marking booted slot as good.
[0617/224002:ERROR:boot_control_recovery.cc(175)] Unable to mark boot successful: Operation not permitted
[0617/224002:INFO:update_attempter_android.cc(406)] Scheduling an action processor start.
[0617/224002:INFO:action_processor.cc(46)] ActionProcessor: starting InstallPlanAction
[0617/224002:INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess
[0617/224002:INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction
[0617/224002:INFO:install_plan.cc(77)] InstallPlan: new_update, source_slot: B, target_slot: A, url: file:///sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip, payload: (size: 730303102, metadata_size: 143458, metadata signature: , hash: B3621E6FF72FDADC09D057ABA4C33A710920E6009EC948044D95B047F1C524B3, payload type: unknown), hash_checks_mandatory: false, powerwash_required: false
[0617/224002:INFO:download_action.cc(195)] Marking new slot as unbootable
[0617/224002:ERROR:boot_control_recovery.cc(155)] Unable to mark slot A as bootable: Operation not permitted
[0617/224002:WARNING:download_action.cc(197)] Unable to mark new slot A. Proceeding with the update anyway.
[0617/224002:INFO:multi_range_http_fetcher.cc(45)] starting first transfer
[0617/224002:INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 1106+730303102
Step 1/2[0617/224002:INFO:delta_performer.cc(201)] Completed 0/? operations, 16384/730303102 bytes downloaded (0%), overall progress 0%
[0617/224002:INFO:delta_performer.cc(544)] Manifest size in payload matches expected value from Omaha
[0617/224002:INFO:delta_performer.cc(1369)] Verifying metadata hash signature using public key: /etc/update_engine/update-payload-key.pub.pem
[0617/224002:INFO:delta_performer.cc(1411)] Metadata hash signature matches value in Omaha response.
[0617/224002:INFO:delta_performer.cc(1431)] Detected a 'full' payload.
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old boot sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new boot sha256: 7sseQdNxPzpof5gw06pO3kxbGAgrRWt0fLhFTqW1di4= size: 39817216
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old system sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new system sha256: oLanZrAGfJ7MqFRrqbwKe4Z1mCaK46v/ezPPJSp1Fi8= size: 3221225472
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo old vendor sha256: size: 0
[0617/224002:INFO:delta_performer.cc(382)] PartitionInfo new vendor sha256: gS4RsefgJ3Qh1ZSLK5t0ctCDRdVZHLSynExBqW/Iq7g= size: 2147483648
[0617/224002:INFO:delta_performer.cc(368)] Applying 19 operations to partition "boot"
[0617/224002:INFO:delta_performer.cc(661)] Starting to apply update payload operations
[0617/224004:INFO:delta_performer.cc(368)] Applying 1536 operations to partition "system"
[0617/224017:INFO:delta_performer.cc(201)] Completed 136/2579 operations (5%), 116850688/730303102 bytes downloaded (16%), overall progress 10%
[0617/224030:INFO:delta_performer.cc(201)] Completed 289/2579 operations (11%), 219103232/730303102 bytes downloaded (30%), overall progress 20%
[0617/224043:INFO:delta_performer.cc(201)] Completed 421/2579 operations (16%), 321339392/730303102 bytes downloaded (44%), overall progress 30%
[0617/224046:ERROR:xz_extent_writer.cc(89)] xz_dec_run returned XZ_DATA_ERROR
[0617/224046:ERROR:delta_performer.cc(937)] writer->Write(buffer_.data(), operation.data_length()) failed.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:extent_writer.h(38)] End() not called on ExtentWriter.
[0617/224046:ERROR:delta_performer.cc(288)] Failed to perform REPLACE_XZ operation 452, which is the operation 433 in partition "system"
[0617/224046:ERROR:download_action.cc(325)] Error ErrorCode::kDownloadOperationExecutionError (28) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
[0617/224046:INFO:delta_performer.cc(304)] Discarding 832792 unused downloaded bytes
[0617/224046:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
[0617/224046:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 200
[0617/224046:INFO:multi_range_http_fetcher.cc(126)] Terminating.
[0617/224046:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadOperationExecutionError
[0617/224046:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
[0617/224046:INFO:update_attempter_android.cc(294)] Processing Done.
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)Updater process ended with ERROR: 1
I:Install took 44 second(s).
Error installing zip file '/sdcard/Havoc-OS-v2.6-20190611-jasmine_sprout-Official.zip'
Updating partition details...
Iata backup size is 0MB, free: 46234MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
always shows me this error
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)Updater process ended with ERROR: 1"
ive tried installing this on stock pie as well as stock oreo always get this error
ps i can install stock rom via xiaomi flash
i have tried installing rom from different versions of twrp as well

Related

[Q] how to install liquidsmooth

I have the sprint n6. I am unlocked and rooted. The phone is decrypted. I have twrp for recovery. Everytime i try to flash this through twrp, it errors out. Do i have to sideload this? Ive tried looking through the board but didnt see anything. Thanks in advance for the help
What's the error for starts
What error? Is the rom downloaded fully and not corrupted?
Sent from my Nexus 6 using Tapatalk
Installing '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 1
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Error flashing zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Updating partition details...
Iata backup size is 1164MB, free: 21687MB.
That was the log from twrp
toast333 said:
Installing '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 1
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Error flashing zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Updating partition details...
Iata backup size is 1164MB, free: 21687MB.
That was the log from twrp
Click to expand...
Click to collapse
Before installing, did you wipe the system partition?
I thought I had. Lemme try that again.
There's a Q&A for LS right here http://forum.xda-developers.com/showthread.php?t=2977149

[Q] [SOLVED] Error flashing rom (blkdiscard failed invalid argument)

Hi all,
I got error blkdiscard failed invalid argument while flashing [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Many said that I had to extend partition to 1.2GB, which I already did. I can install Temasek rom with extended
partition, but failed with Bitti09 rom.
Here is what I have did before
-flash r11 cwm
-manually extend partition
-script extend partition
-flash TWRP
all step above failed to install [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Now running with audahadi Temasek rom.
Here is my log from TWRP
PHP:
Installing '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 4 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...blockimg version is 2
erasing 318848 blocks
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Error flashing zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Updating partition details...
Please help...
Finally I have solved this problem. Yes "blkdiscard failed: Invalid argument" is error of unsuitable partition space to install a rom.
Initially my partition was like this
system = 1242 MB (1.2GB)
system1= 100 MB
After google and reading most comment from partition thread, I found out there is three version of system partition size which is 730MB, 1242MB and 1337 MB.
I found that @audahadi partition script use
system = 1337 MB
system1= 5MB
Quote:
Originally Posted by audahadi
This Procedure May Will Brick Your Device!!!!!
Only for users who comfort with single partition layout only !!!
This is a script to partiton your system partition as like stated in OP. Tested with Clockworkmod recovery.
How to use? Just flash through recovery on either partition. Remember, this will wipe your system partition, do backup for safe or no if you like to live dangerously.
Repartition_MI3W_1_2GB.zip
Credit :
http://forum.xda-developers.com/show....php?t=2765846
http://forum.xda-developers.com/gala...-data-t2762594
Click to expand...
Click to collapse
So using that script, i have succeed install CM based rom.
sorry but could you please elaborate!! I don't get it.. how could I see my partitions?! and how can I change them?!
sorry for being noob.
Go to google play and install Disc Info app. You can see your partition
Sent from my MI 3W using XDA Forums
Can you give me the link for system = 1337 MB
system1= 5MB partition?
Here you go
http://forum.xda-developers.com/attachment.php?attachmentid=3321267&d=1432050198
Sent from my MI 3W using XDA Forums

[how to..] Unbrick nokia x2 readed as [RELINK HS-USB QD-LOADER 9008]

=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
sry for bad english
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
you're welcome
this also works with all Snapdragon devices
thinhx2 said:
Very easy http://forum.xda-developers.com/nokia-x2/help/how-to-recover-hard-bricked-nokia-x2-t3072157
But thank bro for tip
Click to expand...
Click to collapse
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2-QPST_2.7.422
3- QDLoader HS-USB Driver
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
download links for drivers not working.
jkenic said:
download links for drivers not working.
Click to expand...
Click to collapse
broken links updated
thx for informing me
jkenic said:
this does not work forr me. i am getting this error.
Failed using Sahara protocol
Exception:
Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownloadException: Failed using Sahara protocol ---> Nokia.Delta.Gemini.EmergencyDownload.SaharaException: Image transfer ended with failure: InvalidImageTypeReceived
at Nokia.Delta.Gemini.EmergencyDownload.Sahara.Download(String filePath)
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
--- End of inner exception stack trace ---
at Nokia.Delta.Gemini.EmergencyDownload.EmergencyDownload.SetToFirehoseMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
---------- Post added at 11:17 AM ---------- Previous post was at 11:09 AM ----------
download links for drivers not working.
Click to expand...
Click to collapse
bro has install nokia care suite?
thinhx2 said:
bro has install nokia care suite?
Click to expand...
Click to collapse
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
Ramy3r said:
broken links updated
thx for informing me
Click to expand...
Click to collapse
u re welcome but number 2 download link still not working.......
jkenic said:
it is the ncs that is giving me the error. i have done everything needed to be done to get my x2 back....
---------- Post added at 02:54 PM ---------- Previous post was at 02:39 PM ----------
u re welcome but number 2 download link still not working.......
Click to expand...
Click to collapse
sry fixed and add links from google drive
Ramy3r said:
=====how to flash dead Nokia x2 readed as [ RELINK HS-USB QD-LOADER 9008 ] instead of [ QHSUSB_BULK ]=====
all u need is:
1- Nokia x2 firmware files from here insert your product code ,click submit then download all the files in the list and put them together in one folder [i named it "RM-1013"]
2- QPST_2.7.422 or here
3- QDLoader HS-USB Driver or here
**remove the phone's battery and put it back after 5 seconds connect the phone with usb cable**
After downloading and installing all files
open start menu and type in search QFIL
open QFIL in "programmer path" map it to the firmware and select:
"rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn"
next press "Load XML" then type in file name *.xml press open and chose:
"rm1013_2.1.0.13_059V782_001_rawprogram_unsparse_ui.xml"
then it will automatically ask u for "Patch File"
type in file name *.xml press open and chose:
P12027803dpi600_label_layout.xml
last thing press Download and take a little rest while the rom is being downloaded to your Nokia x2 :silly:
Facing any problem ? list it below
**Note**
Works with all snapdragon devices
so if u have another device all u need to change is the firmware files
sry for bad english
Click to expand...
Click to collapse
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
jkenic said:
i go an error
Start Download
Program Path:C:\Users\EJINI\Desktop\New folder\RM-1013-1\rm1013_2.1.0.13_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
almost same with the nokia care suite.
Click to expand...
Click to collapse
Do u have any problems with ur operating system maybe its not running very well or u have some program that interferes with the download/flashing process
Sent from my Nokia_X2 using XDA Labs
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
jkenic said:
There's nothing wrong with the OS that I know of.... Maybe it's the phone...did not work with windows 10
Click to expand...
Click to collapse
Sry for late comment .. Win 10 has a lot of support issues like the error 0x000007 with some games and programs ... I recommend win 7 for best results
Sent from my Nokia_X2 using XDA Labs
Work with lumia devices?
thinhx2 said:
Work with lumia devices?
Click to expand...
Click to collapse
i tested this only on android devices i'm not sure about windows phone tbh
but if it has same files "firehose , rawprogram and label layout" included in firmware files then its possible
error
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Hoоdlum said:
Hi guys. Please help me with an error. If the firmware gets up in the middle of it.
Click to expand...
Click to collapse
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Ramy3r said:
First of all have you downloaded the full firmware files ? "66 files, 902 MB"
Sent from my Nokia X2 using XDA Labs
Click to expand...
Click to collapse
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Hoоdlum said:
66 Yes 902mb file, but it does not end here from another site. Here's why not swing.
Click to expand...
Click to collapse
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Ramy3r said:
Try again using the version I posted of qpst
Sent from my Nokia ara using XDA Labs
Click to expand...
Click to collapse
I downloaded from your site on the links firmware driver program. Error exact same stands in the middle.
That log
Code:
[FONT="Verdana"][B]Validating Application Configuration
Load APP Configuration
COM:-1
SAHARA:True
SAHARA:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
SEARCHPATH:C:\RM-1013
RAWPROGRAM:
rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH:
P12026702dpi600_label_layout.xml
ACKRAWDATAEVERYNUMPACKETS:True
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:True
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
READBACKMODE:0
RESETAFTERDOWNLOAD:True
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Process Index:0
Validating Download Configuration
Image Search Path: C:\RM-1013
RAWPROGRAM file path: C:\RM-1013\rm1013_2.1.0.12_059V786_001_rawprogram_unsparse_ui.xml
PATCH file path:C:\RM-1013\P12026702dpi600_label_layout.xml
Programmer Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
Start Download
Program Path:C:\RM-1013\rm1013_2.1.0.12_user_prog_emmc_firehose_8x10.mbn
COM Port number:9
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Enable Ack Raw Data Every 100Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:9
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Set TxBuffer 0xc000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x37226800
Download Image
PROGRAM: Replace the partition sectors number 0x20000 to file size in sector 0x125c3
PROGRAM: Partition 0, Sector: 16384, Length: 75203 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_NON-HLOS.bin
FireHose Log: start 16384, num 75203
FireHose Log: Write failed Sector 16480, Errno 2
FireHose Log: Finished sector address 16480
PROGRAM: Written Bytes 0x24b8600 (64)
Program Size: 36.72 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 147456, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 147456, num 492
FireHose Log: Write failed Sector 147456, Errno 2
FireHose Log: Finished sector address 147456
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1ec
PROGRAM: Partition 0, Sector: 148480, Length: 492 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sbl1.mbn
FireHose Log: start 148480, num 492
FireHose Log: Write failed Sector 148480, Errno 2
FireHose Log: Finished sector address 148480
PROGRAM: Written Bytes 0x3d800 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x100 to file size in sector 0x2d
PROGRAM: Partition 0, Sector: 149504, Length: 45 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_sdi.mbn
FireHose Log: start 149504, num 45
FireHose Log: Write failed Sector 149504, Errno 2
FireHose Log: Finished sector address 149504
PROGRAM: Written Bytes 0x5a00 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 180224, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 180224, num 938
FireHose Log: Write failed Sector 180224, Errno 2
FireHose Log: Finished sector address 180224
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x3aa
PROGRAM: Partition 0, Sector: 181248, Length: 938 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_emmc_appsboot.mbn
FireHose Log: start 181248, num 938
FireHose Log: Write failed Sector 181248, Errno 2
FireHose Log: Finished sector address 181248
PROGRAM: Written Bytes 0x75400 (64)
Program Size: 0.46 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 182272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 182272, num 296
FireHose Log: Write failed Sector 182272, Errno 2
FireHose Log: Finished sector address 182272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x128
PROGRAM: Partition 0, Sector: 183272, Length: 296 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_rpm.mbn
FireHose Log: start 183272, num 296
FireHose Log: Write failed Sector 183272, Errno 2
FireHose Log: Finished sector address 183272
PROGRAM: Written Bytes 0x25000 (64)
Program Size: 0.14 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x38d5
PROGRAM: Partition 0, Sector: 196608, Length: 14549 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_boot.img
FireHose Log: start 196608, num 14549
FireHose Log: Write failed Sector 196608, Errno 2
FireHose Log: Finished sector address 196608
PROGRAM: Written Bytes 0x71aa00 (64)
Program Size: 7.10 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 229376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 229376, num 663
FireHose Log: Write failed Sector 229376, Errno 2
FireHose Log: Finished sector address 229376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Replace the partition sectors number 0x3e8 to file size in sector 0x297
PROGRAM: Partition 0, Sector: 230376, Length: 663 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_tz.mbn
FireHose Log: start 230376, num 663
FireHose Log: Write failed Sector 230376, Errno 2
FireHose Log: Finished sector address 230376
PROGRAM: Written Bytes 0x52e00 (64)
Program Size: 0.32 MB
PROGRAM: Partition 0, Sector: 344064, Length: 262160 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_1.img
FireHose Log: start 344064, num 262160
FireHose Log: Write failed Sector 344064, Errno 2
FireHose Log: Finished sector address 344064
PROGRAM: Written Bytes 0x8002000 (64)
Program Size: 128.01 MB
PROGRAM: Partition 0, Sector: 606600, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_2.img
FireHose Log: start 606600, num 16
FireHose Log: Write failed Sector 606600, Errno 29
FireHose Log: Finished sector address 606600
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 610352, Length: 257992 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_3.img
FireHose Log: start 610352, num 257992
FireHose Log: Write failed Sector 610352, Errno 2
FireHose Log: Finished sector address 610352
PROGRAM: Written Bytes 0x7df9000 (64)
Program Size: 125.97 MB
PROGRAM: Partition 0, Sector: 868352, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_4.img
FireHose Log: start 868352, num 16
FireHose Log: Write failed Sector 868352, Errno 2
FireHose Log: Finished sector address 868352
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 872104, Length: 258384 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_5.img
FireHose Log: start 872104, num 258384
FireHose Log: Write failed Sector 872104, Errno 2
FireHose Log: Finished sector address 872104
PROGRAM: Written Bytes 0x7e2a000 (64)
Program Size: 126.16 MB
PROGRAM: Partition 0, Sector: 1130496, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_6.img
FireHose Log: start 1130496, num 16
FireHose Log: Write failed Sector 1130496, Errno 2
FireHose Log: Finished sector address 1130496
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1130888, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_7.img
FireHose Log: start 1130888, num 16
FireHose Log: Write failed Sector 1130888, Errno 2
FireHose Log: Finished sector address 1130888
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1134640, Length: 95712 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_8.img
FireHose Log: start 1134640, num 95712
FireHose Log: Write failed Sector 1134640, Errno 2
FireHose Log: Finished sector address 1134640
PROGRAM: Written Bytes 0x2ebc000 (64)
Program Size: 46.73 MB
PROGRAM: Partition 0, Sector: 1392640, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_9.img
FireHose Log: start 1392640, num 16
FireHose Log: Write failed Sector 1392640, Errno 2
FireHose Log: Finished sector address 1392640
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1654784, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_10.img
FireHose Log: start 1654784, num 16
FireHose Log: Write failed Sector 1654784, Errno 29
FireHose Log: Finished sector address 1654784
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1655176, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_system_11.img
FireHose Log: start 1655176, num 16
FireHose Log: Write failed Sector 1655176, Errno 29
FireHose Log: Finished sector address 1655176
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 1777664, Length: 11376 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_cache_1.img
FireHose Log: start 1777664, num 11376
FireHose Log: Write failed Sector 1777664, Errno 2
FireHose Log: Finished sector address 1777664
PROGRAM: Written Bytes 0x58e000 (64)
Program Size: 5.55 MB
PROGRAM: Replace the partition sectors number 0x5000 to file size in sector 0x3ca9
PROGRAM: Partition 0, Sector: 1974272, Length: 15529 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_recovery.img
FireHose Log: start 1974272, num 15529
FireHose Log: Write failed Sector 1974272, Errno 2
FireHose Log: Finished sector address 1974272
PROGRAM: Written Bytes 0x795200 (64)
Program Size: 7.58 MB
PROGRAM: Replace the partition sectors number 0x800 to file size in sector 0x1
PROGRAM: Partition 0, Sector: 1998848, Length: 1 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_user_misc_erase.img
FireHose Log: start 1998848, num 1
ReadFile last error: 0
PROGRAM: Written Bytes 0x200 (64)
Program Size: 0.00 MB
PROGRAM: Partition 0, Sector: 2015232, Length: 262136 Sectors, Sector Size: 512 Bytes
File: C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img
WriteFile last error: 0
PROGRAM: Send XML command fail code: 9
Failed to write C:\RM-1013\rm1013_2.1.0.12_059V786_001.custom_1.img to the device
Download Fail:FireHose Fail Failed to Upload the emmc images to the phone using Firehose.
Finish Download[/B][/FONT]

Need Belutooth partition backup of Moto one power device having January 1st Patch

Hi all,
Can anybody please share the twrp backup of bluetooth partition of Moto One Power device having the Pie January 1st Patch? My bluetooth partition got formatted while restoring the twrp backup and restore got failed. Now I'm not able to use the bluetooth. I have got the OTA with face unlock, But thile installing the OTA I started getting bluetooth partition block verification failed saying partition got mounted rw. And while restoring the earlier backup it got formatted :crying:
Got it fixed after a hell lot of research
Hi all,
Finally after searching a lot in net, flashed the bluetooth partition with the img file available in the following site ( Phenotypically ) -> mirrors[dot]lolinet[dot]com[slash]firmware[slash]moto[slash]chef[slash]official[slash]RETIN
The root cause for getting the partition formatted is gettiing the following error, to solve it I tried to restore bluetooth partition and it resulted currupt. Hope it may help somebody who will be get the same issue and stumble upon this page.
I was getting "Update Failed" error in Moto updator. While checking for the logs via adb observed the following error :
Code:
update_engine: [0306/081413.872062:INFO:delta_performer.cc(397)] Applying 8 operations to partition "bluetooth"
update_engine: [0306/081413.885946:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
update_engine: [0306/081413.886903:ERROR:delta_performer.cc(432)] Unable to open ECC source partition bluetooth on slot A, file /dev/block/bootdevice/by-name/bluetooth_a: Success
update_engine: [0306/081413.887044:ERROR:delta_performer.cc(1042)] 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.
update_engine: [0306/081413.887251:ERROR:delta_performer.cc(1047)] Expected: sha256|hex = 9F69430D4BED82B26E49AAA81E0F1E823687605099AD61F45A361A96E7BE6FEE
update_engine: [0306/081413.887321:ERROR:delta_performer.cc(1050)] Calculated: sha256|hex = 734059C0A03A2B2E61CBF3302F2982F3811FD243064D434A6CFC0FAEBDBC0E85
update_engine: [0306/081413.887393:ERROR:delta_performer.cc(1061)] Operation source (offset:size) in blocks: 0:1,6:2,34:1,101:30
update_engine: [0306/081413.887487:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2019-03-05 03:36:34.000 UTC.
update_engine: [0306/081413.887573:ERROR:delta_performer.cc(1340)] source_fd != nullptr failed.
update_engine: [0306/081413.887652:ERROR:delta_performer.cc(301)] Failed to perform BROTLI_BSDIFF operation 4604, which is the operation 0 in partition "bluetooth"
update_engine: [0306/081413.887721:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
update_engine: [0306/081413.888372:INFO:delta_performer.cc(317)] Discarding 301 unused downloaded bytes
update_engine: [0306/081413.894845:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
update_engine: [0306/081413.895113:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 206
update_engine: [0306/081413.895166:INFO:multi_range_http_fetcher.cc(126)] Terminating.
update_engine: [0306/081413.895224:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
update_engine: [0306/081413.895278:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
Since Moto One Power is having A/B Partition and seemless update support, It looks like the incremental security update was checking for the checksum of the corresponding partition before applying the incremental update. To fix this I flashed the bluetooth and other failing partitions with the apropriate images available in the above shared link.
Hi there, i'm facing the same issue. Can u please tell me which img to flash from stock firmware?

TWRP commandline backup problems

Hi.
I'm trying to backup data partition with cmdline due to a broken display (currently, LOS 17.1 is installed). However it doesn't work. It seems to having issues with /data/system_ce/0. Can anyone help? The backup worked with via display in the past. Here is some logfile output:
Code:
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37
Invalid encryption mode 'ice:aes-256-cts'
Backing up Data...
Backups of Data do not include any files in internal storage such as pictures or downloads.
Invalid encryption mode 'ice:aes-256-cts'
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.ext4.win000'
I:addFile '/data/server_configurable_flags' including root: 1
==> set selinux context: u:object_r:server_configurable_flags_data_file:s0
found policy '/data/server_configurable_flags' - '1DK' - 'c0cd60c87b2b4dfc'
I:addFile '/data/system_ce' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
I:addFile '/data/system_ce/0' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/0' - '1435bb0a12e56a60'
I:Error adding file '/data/system_ce/0' to '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copied file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/recovery.log
Backup Failed
The device uses FBE, but users are decrypted successfully:
Code:
User 0 Decrypted Successfully
I:All found users are decrypted.
Data successfully decrypted
I can pull data from every folder. Maybe it is an idea to pull the data manually? But which data/folders should be pulled?
Thanks everybody in advance for some responses and help.

Categories

Resources