GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > RIFF Box Team > RIFFBOX

Reply
 
LinkBack Thread Tools Display Modes
Old 03-28-2015, 10:17   #1 (permalink)
No Life Poster
 
moonmoon8's Avatar
 
Join Date: May 2005
Location: Lahore
Posts: 506
Member: 144944
Status: Offline
Thanks Meter: 53
~~~ 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...
  Reply With Quote
Old 03-28-2015, 10:32   #2 (permalink)
No Life Poster
 
moonmoon8's Avatar
 
Join Date: May 2005
Location: Lahore
Posts: 506
Member: 144944
Status: Offline
Thanks Meter: 53
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
  Reply With Quote
Old 03-28-2015, 13:30   #3 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 57
Posts: 16,407
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
bro, F.A.Q. there are for to be read:

Quote:
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.
Quote:
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.
BR
allumts
  Reply With Quote
Old 03-30-2015, 08:05   #4 (permalink)
No Life Poster
 
moonmoon8's Avatar
 
Join Date: May 2005
Location: Lahore
Posts: 506
Member: 144944
Status: Offline
Thanks Meter: 53
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
  Reply With Quote
Old 03-31-2015, 15:14   #5 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 57
Posts: 16,407
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
If eMMc is ok and not is broken...with Linux SO having right Unbrick eMMc file can restore...use google and must need a little of knowledge about LINUX SO....

I've seen that Legjia have answered that is eMMc broken and need of replace...

You can only try with Linux...but is only one attempt....

BR
allumts
  Reply With Quote
The Following User Says Thank You to allumts For This Useful Post:
Old 04-02-2015, 09:21   #6 (permalink)
No Life Poster
 
moonmoon8's Avatar
 
Join Date: May 2005
Location: Lahore
Posts: 506
Member: 144944
Status: Offline
Thanks Meter: 53
Yep i have LINUX SDC knowledge
ok i will try on weekend
thanks Bro for support
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 03:15.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.15160 seconds with 8 queries

SEO by vBSEO