[Q] Hardware Watchdog Crash - Sony Xperia T, TL, TX, V

I have a Sony Xperia TX. It randomly crashes and it reads - Phone crashed please wait for the crash reports to be saved.
it also say Hardware Watchdog crash stored on internel sdcard.
I am posting my crash reports from the CrashDump folder.
rdlog_init() created temp log file: /hhVMYg
[E] Could not open VT /dev/tty0: "No such file or directory"
Framebuffer initialized: 720x1280, 16bpp, 1.8MB
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 255 (masked to 255)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 255 (masked to 255)
[E] Failed to open /sys/class/timed_output/vibrator/enable: No such file or directory
RamdumpV3 app. Version: 1.0.A.0.57
Loading configuration from conf.xml
adding 1 mount point(s)
Mount of /dev/block/by-name/SDCard on /YMogkv with file system ext4 returned: SUCCESS
DUMP /YMogkv /dev/block/by-name/SDCard 179:15 ext4 READY
Cleaning up permission problems for CrashDump
Unable to open RTC device
No rtc time
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000 directory
[W] Failed to create /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000, retrying... No such device
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0 directory
ramdump log created at "/YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump.log"
Updating /YMogkv/CrashDump/crashinfo
opened memory device node /dev/mem (3) in O_RDWR | O_SYNC mode
Verify config
Reading cmdline file /proc/cmdline:
* Found: startup=6a58c
* Found: warmboot=6a594
* Found: androidboot.serialno= CB5A1JYRHT
RestartReason=0xabadbabe, restartReasonType=1
No buildinfo found, fallback to crash-notes.
Storing kernel log to: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump_system.log
Searching linux area 12 (0x80200000, 0x8d00000) for magic 0xCAFEBABE.
[W] Default build id checksum! Early kernel crash?
Found build info in crash notes: 7.0.A.3.193\hayabusa\userdebug
Found crash notes for crashing CPU! Crashing process:
[W] Skipping ram console search, crash type is 1
RESTART_REASON: 0xABADBABE (Hardware watchdog)
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
HWWD but can't read /proc/rdtags/addr_scm_regsave from rdtags: errno=2 <No such file or directory>
HWWD using hardcoded physical addr 0x2a03f658
CPU registers dump addr (phy) 0x00000000={0xea000006, 0xea000060, 0xea000063, ...}
HWWD found but no TZBSP_DUMP_CTX_MAGIC (found 0xea000006 expected 0x44434151)
RDTAG_DIR not set for this platform! Skipping rdtags dump!
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/productinfo
Creating dump file: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/tlcore
Platform: blue
Dump areas:
( 0) address=0x0006206c size=0x00000004 flags=0x00006000 name: WDT Reset... success!
( 1) address=0x09000000 size=0x00008000 flags=0x0000a000 name: MDSP Ram A... success!
( 2) address=0x09200000 size=0x00008000 flags=0x0000c000 name: MDSP Ram B... success!
( 3) address=0x09400000 size=0x0000f800 flags=0x0000e000 name: MDSP Ram C... success!
( 4) address=0x12000000 size=0x0002c000 flags=0x00010008 name: SPS RAM... success!
( 5) address=0x12040000 size=0x00004000 flags=0x00012000 name: SPS Buff RAM... success!
( 6) address=0x12800000 size=0x00008000 flags=0x00014000 name: SPS Pipe Mem... success!
( 7) address=0x28400000 size=0x00020000 flags=0x00016008 name: Lpass Memory... success!
( 8) address=0x2a000000 size=0x00010000 flags=0x00018008 name: System IMEM-A... success!
( 9) address=0x2a03f000 size=0x00001000 flags=0x0001c000 name: System IMEM-C... success!
(10) address=0x38000000 size=0x04000000 flags=0x00020008 name: SMI CS0... success!
(11) address=0x80000000 size=0x00200000 flags=0x00080088 name: EBI1_CH0_CS0(SMEM)... success!
(12) address=0x80200000 size=0x08d00000 flags=0x00080028 name: EBI1_CH0_CS0(LINUX)... success!
(13) address=0x88f00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(APPSBL)... success!
(14) address=0x89000000 size=0x04400000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 SW)... success!
(15) address=0x8d400000 size=0x00600000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 FW)... success!
(16) address=0x8da00000 size=0x01800000 flags=0x00080008 name: EBI1_CH0_CS0(LP_Audio_SS)... success!
(17) address=0x8f200000 size=0x00500000 flags=0x00080008 name: EBI1_CH0_CS0(WConnect_SS)... success!
(18) address=0x8f700000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(TZ Image)... success!
(19) address=0x8f780000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(Reserved)... success!
(20) address=0x8f800000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(FS Cache)... success!
(21) address=0x8fb00000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(RAM EFS)... success!
(22) address=0x8fe00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SPS Image)... success!
(23) address=0x8ff00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SBL3)... success!
(24) address=0x90000000 size=0x10000000 flags=0x00080028 name: EBI1_CH1_CS0(LINUX)... success!
(25) address=0xa0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH0_CS1(LINUX)... success!
(26) address=0xb0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH1_CS1(LINUX)... success!
(27) path=/dev/msm_etb_boot flags=0x00024008 name: ETB... Read from /dev/msm_etb_boot: 16384, written to dump: 1530
success!
(28) cmdlineParam=semcandroidboot.rpmcoderamcopy, address=0x00020000 size=0x00000000 flags=0x00002008 name: RPM Code RAM... Found cmdline specified dump area (semcandroidboot.rpmcoderamcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmcoderamcopy=
cmdLine area [email protected],0x20000
addr = 0x88f00000 size = 147456 orgAddr = 0x20000
success!
(29) cmdlineParam=semcandroidboot.rpmregistercopy, address=0x0002e000 size=0x00000000 flags=0x00004000 name: RPM Registers... Found cmdline specified dump area (semcandroidboot.rpmregistercopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmregistercopy=
cmdLine area [email protected],0x2E000
addr = 0x88f24000 size = 104 orgAddr = 0x2e000
success!
(30) cmdlineParam=semcandroidboot.rpmmsgramcopy, address=0x00108000 size=0x00000000 flags=0x00008000 name: RPM Msg RAM... Found cmdline specified dump area (semcandroidboot.rpmmsgramcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmmsgramcopy=
cmdLine area [email protected],0x108000
addr = 0x88f24100 size = 24575 orgAddr = 0x108000
success!
Updating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
Ramdump finished in 154s
Ramdump done! type: 1, name: , result: RAMDUMP_RESULT_OK (00)
SD card free space: 8495 MB
Closing graphics and flushing log files
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 0 (masked to 0)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 0 (masked to 0)
[E] Could not open VT /dev/tty0: "No such file or directory"
Can anyone help me fix this problem?

Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?

gregbradley said:
Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?
Click to expand...
Click to collapse
Not rooted
Bootlocker is not unlocked
The phone is out of the box and i did not change any ROM settings or Rooted it. Nothing has been changed.
I was surfing my gallery when this first happened.
after that it was like 2 to 3 times a day

Related

Extract data.img

Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre
Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.
In the past I've used the the emulator and specified my data.img to be loaded, then used adb to pull the wanted files...
C:\temp\android-sdk-windows\tools>emulator.exe -help
Android Emulator usage: emulator [options] [-qemu args]
options:
-sysdir <dir> search for system disk images in <dir>
-system <file> read initial system image from <file>
-datadir <dir> write user data into <dir>
-kernel <file> use specific emulated kernel
-ramdisk <file> ramdisk image (default <system>/ramdisk.img
-image <file> obsolete, use -system <file> instead
-init-data <file> initial data image (default <system>/userdata
.img
blunden said:
Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.
Click to expand...
Click to collapse
Worked with the new version.
Thanks.
pdais97 said:
Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre
Click to expand...
Click to collapse
gunzip -c ../your-ramdisk-file | cpio -i starting from 1F8B

sbl/boot strings

passing strings to a sbl i got some interesting text:
Code:
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: %s %s
ARIES
REV 03
Build On: %s %s
Jul 30 2010
09:53:23
boot_kernel
loadkernel
boot
command_loop
SBL>
%s: parse command error! (%s)
Autoboot (%d seconds) in progress, press any key to stop
Autoboot aborted..
__Re_partition
%s: undefined code for format.
%s: write virtual pit image.
%s: write bootloader images to NAND!
%s: format failed..
Re_partition
%s: magic code(0x%x)
loke_init
%s: file system init failed..
%s: j4fs_open success..
%s: j4fs_open failed..
%s: bye~ bye!
main
%s: booting stop.
%s: booting stop and power off..
I9000XXIL
console=ttySAC2,115200
/mnt/rsv
setting param.serialnr=0x%08x 0x%08x
setting param.board_rev=0x%x
bootmode=2
bootmode=3
setting param.cmdline=%s
argv[%d] : %s
value : %d
Invalide Parameter Name
setenv
valid magic and version 2 ...
invalid magic and version 2 ...
saveenv
save %s, size: %d
param.blk
save %s successfully.
PARAM Rev %d.%d
%s : %d
%s : %s
printenv
load_lfs_parameters
%s valid magic code and version.
load_lfs_parameters invalid magic code and version
boot parameter file does not exist ..
make new boot paremeter file ..
/mnt/rsv
load_debug_level
debug_level.inf
%s reading debug level from file successfully(0x%x).
debug level file does not exist ..
debug level value is incorrect!! Set default level (LOW)..
get_debug_level
%s current debug level is 0x%x.
There're no available commands.
* Help : %s
* Usage : %s
There's no command
Following commands are supported:
* %s
To get commands help, Type "help <command>"
help
Rebooting...
reset
Code:
open
close
erasepart
eraseall
loadkernel
showpart
bbm add partition start
addpart
delpart
savepart
fsr_bml open error
error return value %x
bbm_erase_all
some of them even look like commands, anyone knows if there is some use for this?
in boot.bin:
Code:
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Error Occurs During Boot. Please ReBoot.
FSR_BML_Init Error
BML_Open Error
BML_GetVolInfo Error
BML_LoadPIEntry Error! Part_ID: %d
+n1stVPN %d
+nPgsPerBlk %d
BML_Read Error
ERROR.. Bootable SBL doesn't exist ..
PBL found bootable SBL: Partition(%d).
The input address don't need a virtual-to-physical translation : %08lx
""DD
UPCH
LPCH
LPCH
UPCH
[B]e-fused[/B]
i wonder what e-fused is for, and if its related to e-fuse: http://en.wikipedia.org/wiki/EFUSE
How did you got this? UART, jtag?
that's a dump of the PBL and SBL from memory into a file, then the Linux "strings" command was run on the file.
I've used search for UPCH and found this thread.
1.
Any idea what UPCH means?
2.
I can't see Thanx button for luismanson...
Maybe my Browser...
Thanx in advance.
Best Regards
Please.
Any news about UPCH?
I need this for JTAG... maybe.
But I don't know what it is...
http://www.ort-jtag.com/blog/?e=10
For instance it is visible in this Video...
But I have an RIFF Box... not ORT... or Medusa seems also to "repair" UPCH...
It seems Bootloader related...
Thanx in advance.
Best Regards

Wi-fi and BT Failing to Start after Rooting Issues - No solutions worked till date!

Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed

How to fix ? Carrier ID = [EMPTY] [WARNING] Carrier ID Error sales_code empty

After flashing i have green screen with error :
security check fail : modem
On recovery logs i see this problem :
[Cheking pre-multi-scs2]
[start failed section]
sales_code = [EMPTY]
Carrier ID = [EMPTY]
[WARNING] Carrier ID Error
[WARNING] sales_code empty
Don't delete TA file.
What can i do to send "sales_code" and "carrier id" to device to fix this error?
I do not have backup of my EFS.
also all firmware have in PIT file record like this :
Partition Name: EFS
Flash FileName: efs.img.ext4
but in reality there is NO efs.img.ext4 file - in any of available firmware ...

Help Couldnt install any custom rom whatsoever

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

Categories

Resources