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 05-02-2012, 15:39   #1 (permalink)
No Life Poster
 
ahmertelecom's Avatar
 
Join Date: Dec 2005
Location: PAKISTAN
Age: 35
Posts: 2,216
Member: 210880
Status: Offline
Sonork: 100.1577765
Thanks Meter: 151
htc trophy plz help


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

Connecting to the dead body...OK
Detected dead body ID: 0x202800E1 - WRONG!!!
ERROR: Current ID does not belong to the HTC Trophy family.

htc trophy dead via upgrading process now when i try to restructor phone shows this error plz help
  Reply With Quote
Old 05-02-2012, 22:55   #2 (permalink)
Product Supporter
 
BABAK NURI's Avatar
 
Join Date: Mar 2005
Location: Tehran.IR
Age: 43
Posts: 7,259
Member: 131131
Status: Offline
Sonork: 100.1606847
Thanks Meter: 4,475
Hi

Do You Have Latest Trophy.Dll...???


Please Goto "DCC Read/Write" Page
Press "Special Setting"
Select "ByPass ID Check"...Then Press "OK"
Resurrect Again
  Reply With Quote
Old 05-03-2012, 13:59   #3 (permalink)
No Life Poster
 
ahmertelecom's Avatar
 
Join Date: Dec 2005
Location: PAKISTAN
Age: 35
Posts: 2,216
Member: 210880
Status: Offline
Sonork: 100.1577765
Thanks Meter: 151
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [HTC Trophy V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x202800E1 - WRONG!!!
ERROR: Current ID does not belong to the HTC Trophy family.


restructor is new dll and bypassid checked but same error plz help



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

Connecting to the dead body...OK
Detected dead body ID: 0x202800E1 - IGNORED!
Set I/O Voltage reads as 3.00V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]
Settings Code: 0x00010000000000000000000000000000

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)

Invalid length. It should not be zero.

when i click read memory its shows this after flash phone is ok and brand new i only upgrade to 7.5 and phone dead
  Reply With Quote
Old 05-05-2012, 14:20   #4 (permalink)
No Life Poster
 
ahmertelecom's Avatar
 
Join Date: Dec 2005
Location: PAKISTAN
Age: 35
Posts: 2,216
Member: 210880
Status: Offline
Sonork: 100.1577765
Thanks Meter: 151
plz any body help me
  Reply With Quote
Old 05-05-2012, 15:41   #5 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 55
Posts: 5,746
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 28,276
Box Service -> Advanced Settings -> Disable IDCODE check.
  Reply With Quote
The Following User Says Thank You to legija For This Useful Post:
Old 05-07-2012, 13:39   #6 (permalink)
No Life Poster
 
ahmertelecom's Avatar
 
Join Date: Dec 2005
Location: PAKISTAN
Age: 35
Posts: 2,216
Member: 210880
Status: Offline
Sonork: 100.1577765
Thanks Meter: 151
elected Resurrector: [HTC Trophy V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x202800E1 - IGNORED!
Set I/O Voltage reads as 3.00V, 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...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000010000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000020000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000030000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000050000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000060000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000070000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000090000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000A0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000B0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000D0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000E0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000F0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000110000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000120000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000130000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000140000 is handled as Cut Excess.

after check idcodecheck show this error
  Reply With Quote
Old 05-07-2012, 13:43   #7 (permalink)
No Life Poster
 
ahmertelecom's Avatar
 
Join Date: Dec 2005
Location: PAKISTAN
Age: 35
Posts: 2,216
Member: 210880
Status: Offline
Sonork: 100.1577765
Thanks Meter: 151
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.
Resurrection complete!
phone still dead
  Reply With Quote
Old 05-16-2012, 02:04   #8 (permalink)
Junior Member
 
Join Date: Sep 2005
Age: 41
Posts: 21
Member: 180123
Status: Offline
Thanks Meter: 0
same problem

Quote:
Originally Posted by ahmertelecom View Post
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.
Resurrection complete!
phone still dead
same problem, enter in boot, but not connecting to usb
  Reply With Quote
Old 07-03-2012, 12:07   #9 (permalink)
Junior Member
 
Join Date: Aug 2006
Location: Poland
Posts: 25
Member: 337334
Status: Offline
Thanks Meter: 0
Someone solved problem?
  Reply With Quote
Old 07-03-2012, 23:43   #10 (permalink)
Product Supporter
 
BABAK NURI's Avatar
 
Join Date: Mar 2005
Location: Tehran.IR
Age: 43
Posts: 7,259
Member: 131131
Status: Offline
Sonork: 100.1606847
Thanks Meter: 4,475
Quote:
Originally Posted by mefistofilos View Post
Someone solved problem?
Hi
if you have same problem you need open new thread...explain your problem,,phone history and post log..
if you want help,i need more info
  Reply With Quote
Reply

Bookmarks


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
HELP!!! BACKGROUND SCREEN LOGO Michael Go Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 8 11-23-2017 08:11
my 8810 is phone locked ,can somebody please help duyphuc Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 18 12-23-2014 09:03
Eeprom dump lost, help needed. CAMILO Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 6 11-29-2010 19:04
Help with 6110 paulomt1 Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 05-25-2009 16:29
Winlock 1.10 - Help rdmfs Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 06-25-1999 08:21

 



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



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.33173 seconds with 9 queries

SEO by vBSEO