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-15-2012, 16:32   #1 (permalink)
Major Poster
 
Join Date: Sep 2005
Age: 38
Posts: 49
Member: 179277
Status: Offline
Thanks Meter: 5
htc cheif dead afert resurrection repair imei


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

Connecting to the dead body...OK
Detected dead body ID: 0xC01E00E1 - CORRECT!
Set I/O Voltage reads as 2.59V, 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: 0x00AD/0x55BA (256MB)

Flashing the dead body...OK
WARNING: Programming Error (0x24) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000020000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000060000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000A0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000E0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000120000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000140000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000160000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000180000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000001A0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000001C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000001E0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000200000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000220000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000240000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000260000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000280000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000002A0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000002C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000002E0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000300000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000320000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000400000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002BE0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002C00000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002C20000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002C60000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002C80000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002CA0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002CC0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000002CE0000 is handled as Cut Excess.
Resurrection complete!
  Reply With Quote
Old 05-15-2012, 17:43   #2 (permalink)
Major Poster
 
Join Date: Sep 2005
Age: 38
Posts: 49
Member: 179277
Status: Offline
Thanks Meter: 5
need full backup image. heellppp mr.
  Reply With Quote
Old 05-15-2012, 21:12   #3 (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
Can you Tell me about phone History?
  Reply With Quote
Old 05-15-2012, 21:29   #4 (permalink)
Major Poster
 
Join Date: Sep 2005
Age: 38
Posts: 49
Member: 179277
Status: Offline
Thanks Meter: 5
execute repair imei and see the error and now not on
  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
Working IMEI changed phone? Barjo Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 03-01-2015 11:49
what prog changes imei on 6110 and how do i do it? Ravetrancer Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 07-31-2012 20:09
Nokia 51xx/61xx imei changer ver. 1.10?????? Ravetrancer Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 8 04-06-2012 16:22
6110 imei changer !!!!!! Ravetrancer Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 5 11-21-2011 01:44

 



All times are GMT +1. The time now is 13:28.



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.14276 seconds with 10 queries

SEO by vBSEO