Pandemic said:

Anyone tried this on a Chromebook ? Just asking for a friend

Is it android variant? If not you shoul compile newflasher using cross compiler for that os

munjeni said:

Is it android variant? If not you shoul compile newflasher using cross compiler for that os

Yes it's far i inow an android variant bro.

munjeni said:

Than one of the arm binaries should work, probably arm64 but also if it is android variant maybe pie binary should work too

Where i can find it bro or someone can make it for me and share it ?

Pandemic said:

Where i can find it bro or someone can make it for me and share it ?

Inside newflasher_v52.zip from the first post! There is arm32, arm64 and arm64_pie, so 3 diferent binaries for arm platform, one of those 3 should work

munjeni said:

Inside newflasher_v52.zip from the first post! There is arm32, arm64 and arm64_pie, so 3 diferent binaries for arm platform, one of those 3 should work

Oke and bro can you please tell me how step by step so i can it easily to him ? Thanks

Forgot to attach the dump file​

Hm, I can't attach a file ?​

from the file:​

Anon1337 said:

Xperia 10 III
Tried flashing 3 different roms downloaded with XperiFirm.
Always ended up in boot loop.
Tried changing slot from b to a now the phone is hardbricked (and I mean hardbricked, no response to any keycombos or keypresses doesn't show in lsusb nothing).
Any ideas?

Locked bootloader ? Repair with xperia companion and try different usb cables.

Anon1337 said:

Unlocked bootloader. Can not repair with xperia comanion since the phone won't connect over USB. Different cables make no difference. Won't register even on a different computer.
The phone seems completely dead. Is there a hidden long press keycombo could try?

There must be at least red light when you connect usb cable! It looks like hardware isue! Maybe usb port on phone side? Check for dust! I had that problem some month ago, the cable simple could not fully enter the port, so after removing dust everything went ok

fineb said:

Hi,
I messed up my XZ2. it was on Stock ROM, rooted with Magisk and I wanted to pass the SafetyNet checks and used MagiskHide Props config to spoof the fingerprint, result was a non booting device .-(
I managed to boot into TWRP, but can't restore a backup from TWRP. Trying to flash the FW again is not successful, attached is a newflasher dump file.
The error is probably this line:
ERROR: boot_a: Hash of data does not match digest in descriptor.
but I don't know what to do now.
Any idea?
Thanks

Forgot to attach the dump file​

Hm, I can't attach a file ?​

from the file:​

VB: RWDeviceState: Succeed using rpmb!
Boot counter is 926
XBoot Init
Init XBootPALAPILib
Init TA API Lib
XBOOT (1310-7079_X_Boot_SDM845_LA2.0.1_Q_207)
[WARNING @ ta_interface.c:109]:
Unable to read TA unit 66667, error=4
[ERROR @ xboot_glue.c:107]:
read_ta returned err=-22
[ERROR @ xboot_glue.c:526]:
get_dk returned err=-22
Reading 321 bytes from RPMB, OK
Reading 321 bytes from RPMB, OK
XDeviceTreeAddrExtract start
no check attributes (Mode 3)
LoadImageAndAuth: 1615: CurrentSlot.Suffix=_a
Not updating rollbackindex as current slot is unbootable
Invalid vm-linux partition
load_and_verify_vbmeta:481: DEBUG: Loading vbmeta struct from partition 'vbmeta_a'.
load_and_verify_hash_partition:181: DEBUG: boot_a: Loading entire partition.
load_and_verify_hash_partition:236: ERROR: boot_a: Hash of data does not match digest in descriptor.
load_and_verify_hash_partition:181: DEBUG: dtbo_a: Loading entire partition.
load_and_verify_hash_partition:240: DEBUG: dtbo_a: success: Image verification completed
Loading Image Start : 2805 ms
Loading Image Done : 2805 ms
Total Image Read size : 4096 Bytes
Loading Image Start : 2806 ms
Loading Image Done : 2836 ms
Total Image Read size : 16080896 Bytes

Upload as zip file works

Click to expand...

Not updating rollbackindex as current slot is unbootable
Invalid vm-linux partition
load_and_verify_vbmeta:481: DEBUG: Loading vbmeta struct from partition 'vbmeta_a'.
load_and_verify_hash_partition:181: DEBUG: boot_a: Loading entire partition.
load_and_verify_hash_partition:236: ERROR: boot_a: Hash of data does not match digest in descriptor.

Looks like magisk messed your boot partition! You just need to reflash boot partition, but looks like whole slot is messed up so you will need to flash partition.sin too! If that not help reflash whole firmware including all .ta. all .sin, partition, bootdelivery. Never mix sin files trought two-few firmwares, always use one firmware and don't modify/delete anything. If you can't get it to work, post newflasher log

munjeni said:

Not updating rollbackindex as current slot is unbootable
Invalid vm-linux partition
load_and_verify_vbmeta:481: DEBUG: Loading vbmeta struct from partition 'vbmeta_a'.
load_and_verify_hash_partition:181: DEBUG: boot_a: Loading entire partition.
load_and_verify_hash_partition:236: ERROR: boot_a: Hash of data does not match digest in descriptor.

Looks like magisk messed your boot partition! You just need to reflash boot partition, but looks like whole slot is messed up so you will need to flash partition.sin too! If that not help reflash whole firmware including all .ta. all .sin, partition, bootdelivery. Never mix sin files trought two-few firmwares, always use one firmware and don't modify/delete anything. If you can't get it to work, post newflasher log

Click to expand...

thanks for the reply, I gave up trying to restore , made a complete wipe and now have the phone running with iode, looks pretty good

fineb said:

thanks for the reply, I gave up trying to restore , made a complete wipe and now have the phone running with iode, looks pretty good

hi @fineb I'm struggling trying to get my xa2 back to life. Have you already tried cam functionality and the NFC feature? cause I already tried lineage but lacks to work.
I'll appreciate your feedback. probably will get iode a try. thx.