~~~ HTC 8x PM2331000 (Resurrection Error) ~~~

Hi Legija Bro,
Need some Help in this case:
HTC 8x PM2331000 Model Resurrection Error

Here is LOG:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC 8X (PM2331000) V1.0.5280.13411]

Connecting to the dead body...OK
Detected dead body ID: 0x706B50E1 - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0065/0x006F (M MOR, 0x000008000000 Bytes = 128.00 MB)
ERROR: Read Failed with Error Code: 0x46. Terminating at 0x000003F00000

No Resurrection Data is available for the eMMC Chip with Capacity = 131072KB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,56GB

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x46 (0x000000). Trying to recover...

And This is JTAG Analyze

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [HTC 8X (PM2331000) V1.0.5280.13411]

Connecting to the target...OK
Set I/O Voltage reads as 1.80V, TCK Frequency is RTCK

Following devices are found on the JTAG chain:
Device on TAP #0: ID = 0x4F1F0F0F, IR Length = 0x04 bits
Device on TAP #1: ID = 0x706B50E1, IR Length = 0x0B bits
Total IR length: 0x000F bits

Analizing IDCODE(s) of the JTAG scan chain:
1. 0x706B50E1: Qualcomm MSM8960, H/W Rev. #7

bro, F.A.Q. there are for to be read:

1.11. Error code 0x46
Returned by box’s firmware when attempt to write ARM9 ICE Breaker register failed. See error code 0x45 for symptoms.

1.10. Error code 0x45
Returned by box’s firmware when attempt to read ARM9 ICE Breaker register failed. This happens when target unexpectedly loses power or connection with target gets broken. Additionally loose of power or connection break often happens during target’s h/w configuration stage – this stage is always performed by every resurrector prior uploading DCC loader code into memory. Thus it means embedded h/w initialize sequence is not thorough (or not compatible at all) for current device’s state or it is possible that target’s hardware is malfunctioning

Solution:
Connect NRST pin properly. In case that You have unsupported device, this error can be caused by wrong HW Init script selected.

Yes Bro You Are Right
thats why i posted this thread
its because of HTC 8x Crap Multi Models
Infect the real problem it was Security Unlocked Refurbished Model
That is the reason it got stuck into QDLoad Mode due to wrong Firmware Attempt
Now we need to correct DLL script to Handle Specific eMMC Version

Hope some way out for this problem!
Thanks for Reply

In this phone eMMC internal flash is not working. It has to be replaced.

Legija Bro.
Phone was OK before
just flash due to version change
Use this "ACDU_UEFI_PROV_KEY.nbh"
because phone already Security Unlocked and SuperCID
After Complete this KEY phone wont trun ON
Only QDL Mode
Its the all story

The Main Factor is:
Its not Detected By PM232000 & PM233000 Resurrection DLL
Only Detected By PM2331000 DLL

Where is shows wrong eMMC Size Error
May be DCC Loader Has Not Matching Partition Table

So Any More Suggection for This Problem???
Thanks

Well, log is pretty clear there, internal flash is not visible by eMMC firmware.
It doesn't mater if it was "ok" before, because this happens as a result of normal use.