Care Unlock  
Your online unlock store
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. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

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) > Rocker Team products > RIFFBOX

Reply
 
LinkBack Thread Tools Display Modes
Old 07-17-2012, 23:44   #1 (permalink)
Junior Member
 
Join Date: Aug 2006
Location: Poland
Posts: 17
Member: 337334
Status: Offline
Thanks: 2
Thanked 0 Times in 0 Posts
HTC Mozart - Problem during resurection

Hi,

I've got some problem with HTC Mozart. I don't know history of the phone...
At the moment I can go to bootloader but can't flash it using RUU or special USB cable via bootloader.

Here is the log from RIFF :

Quote:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [HTC Mozart V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x202400E1 - CORRECT!
Set I/O Voltage reads as 3.02V, 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: 0x00EC/0x66BC (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...FAILED
WARNING: Programming Error (0x24) at 0x00001FE00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE10000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE20000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE30000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FE40000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE50000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE60000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE70000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FE80000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FE90000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FEA0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FEB0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FEC0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FED0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FEE0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FEF0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF10000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF20000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF30000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF40000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF50000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF60000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF70000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF80000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF90000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFA0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFB0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FFC0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFD0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFE0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFF0000 is handled as Cut Excess.
ERROR: Resurrection is not Completed due to Error: 0x2800
Box service --> Advanced settings --> Ignor IDCODE - DONE! But still the same problem...


Do apologize for my english. Still getting better
  Reply With Quote
Old 07-19-2012, 17:41   #2 (permalink)
Junior Member
 
Join Date: Aug 2006
Location: Poland
Posts: 17
Member: 337334
Status: Offline
Thanks: 2
Thanked 0 Times in 0 Posts
RIFF BOX Team? Can you help me?
  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


Similar Threads
thread Thread Starter Forum Replies Last Post
Sim card sleep mode problem with 6130 ratzfatz Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 4 05-22-2012 11:13
GId1 problem old_man Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 1 10-18-2006 15:21
6110 5.47 sw unlock problem gsms Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 3 11-21-1999 18:43
6150 Lock Problem Zeljko Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 1 09-11-1999 17:39
HELP: Problem with 5110 Xabi Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 1 07-16-1999 00:44


All times are GMT +1. The time now is 10:07.



Powered by Searchlight © 2013 Axivo Inc.
- GSM Hosting Ltd. - 1999-2013 -
Page generated in 0.29699 seconds with 11 queries

SEO by vBSEO