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 02-01-2012, 11:30   #1 (permalink)
Freak Poster
 
plentong's Avatar
 
Join Date: Nov 2003
Location: Malaysia
Age: 37
Posts: 359
Member: 44095
Status: Offline
Thanks Meter: 34
Evo 3d x515m


when riff can support HTC evo 3d?
we need new model update.
thanks
  Reply With Quote
Old 02-02-2012, 07:32   #2 (permalink)
Freak Poster
 
Join Date: Apr 2005
Location: iran.ahwaz
Age: 37
Posts: 206
Member: 133927
Status: Offline
Thanks Meter: 20
Hi
i need repair boot for htc evo 3d.
  Reply With Quote
Old 02-02-2012, 13:30   #3 (permalink)
Junior Member
 
Join Date: Nov 2006
Posts: 2
Member: 400271
Status: Offline
Thanks Meter: 0
evo 3d boot reapair?

Help to repair boot...
  Reply With Quote
Old 03-14-2012, 17:28   #4 (permalink)
Freak Poster
 
yaracell's Avatar
 
Join Date: Dec 2010
Posts: 406
Member: 1474687
Status: Offline
Thanks Meter: 82
world first HTC EVO 3D Boot Repair done

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.31, JTAG Manager Version: 1.41
Selected Resurrector: [HTC EVO3D (PG86300) V1.0.4456.5060]
Connecting to the dead body...OK
Detected dead body ID: 0x104210E1 - CORRECT!
Set I/O Voltage reads as 1.80V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 9 MHz]
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: 0x0015/0x0000 (KLL00M, 0x000090000000 Bytes = 2.25 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KLL00M, 0x000000080000 Bytes = 0.50 MB)
Flashing the dead body...OK
Resurrection complete!
thnk riff team
  Reply With Quote
The Following 4 Users Say Thank You to yaracell For This Useful Post:
Show/Hide list of the thanked
Old 03-14-2012, 17:33   #5 (permalink)
No Life Poster
 
hassan1975's Avatar
 
Join Date: May 2003
Age: 45
Posts: 1,305
Member: 28819
Status: Offline
Thanks Meter: 221
that is very good my friend

good box & good team

ur first man make evo3d boot





B.R.
Mobitec
  Reply With Quote
Old 03-14-2012, 17:53   #6 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 51
Posts: 5,746
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 28,266
Obviously, it was us who repaired this phone first in the world.

So, Yaracell, You're 2nd there.
  Reply With Quote
The Following User Says Thank You to legija For This Useful Post:
Old 03-14-2012, 18:00   #7 (permalink)
Freak Poster
 
yaracell's Avatar
 
Join Date: Dec 2010
Posts: 406
Member: 1474687
Status: Offline
Thanks Meter: 82
u the boss mr legija
  Reply With Quote
Old 03-15-2012, 11:17   #8 (permalink)
Freak Poster
 
jay19x's Avatar
 
Join Date: Feb 2004
Location: Malaysia
Age: 36
Posts: 323
Member: 52755
Status: Offline
Thanks Meter: 10
Evo 3D problem?

Code:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.31, JTAG Manager Version: 1.41
Selected Resurrector: [HTC EVO3D (PG86300) V1.0.4456.5060]

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

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

WARNING: DCC Loader was unable to initialize FLASH1 chip. Error code: 0x00000036
ERROR: Selected FLASH1 Chip was not Recognized by the DCC Loader. Terminating.

ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
new type of flash chip?
  Reply With Quote
Old 03-15-2012, 11:24   #9 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 51
Posts: 5,746
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 28,266
It's more likely that eMMC is dead.

What's the phone history ?
  Reply With Quote
Old 03-15-2012, 12:43   #10 (permalink)
Freak Poster
 
jay19x's Avatar
 
Join Date: Feb 2004
Location: Malaysia
Age: 36
Posts: 323
Member: 52755
Status: Offline
Thanks Meter: 10
dunno, cant on. issit possible to change a new flash chip and ressurect by riff?
  Reply With Quote
Old 03-15-2012, 12:53   #11 (permalink)
Freak Poster
 
jay19x's Avatar
 
Join Date: Feb 2004
Location: Malaysia
Age: 36
Posts: 323
Member: 52755
Status: Offline
Thanks Meter: 10
Code:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.31, JTAG Manager Version: 1.41
Selected Resurrector: [HTC EVO3D (PG86300) V1.0.4456.5060]

Connecting to the dead body...OK
Detected dead body ID: 0x104210E1 - 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: 0x0015/0x0000 (KLL00M, 0x000090000000 Bytes = 2.25 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (KLL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
Resurrection complete!
another pcs success. maybe previous phone flash chip dead .
  Reply With Quote
Old 03-15-2012, 20:06   #12 (permalink)
Freak Poster
 
Join Date: Jul 2001
Location: bucharest
Age: 44
Posts: 232
Member: 5202
Status: Offline
Thanks Meter: 7
And i want to be the third person in the word....

My 3D evo gsm, was bricked by the customer.

First state, when i power on, i got endless boot with htc logo.

I can enter in fastboot, the hboot is 1.49.0018 s-on, unloked(htcdev.com), radio 10.14.9020.06_M, and can`t flash or recovery with any software, so i decide to use riff box.

Resurescrtion was ok, but after, the hboot is the same 1.49.0018.

The phone is in the same state, but relocked, the only change is the `shooter beats` logo with sound and the phone is restarting again and again....

After resurection i try few rom`s stock, but i got the same error, 140 or other, i dont remember....

Any ideea???



Regards..
  Reply With Quote
Old 03-15-2012, 20:10   #13 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 51
Posts: 5,746
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 28,266
Have You tried to update IMEI and write SuperCID ?
  Reply With Quote
The Following User Says Thank You to legija For This Useful Post:
Old 03-15-2012, 21:08   #14 (permalink)
Freak Poster
 
Join Date: Jul 2001
Location: bucharest
Age: 44
Posts: 232
Member: 5202
Status: Offline
Thanks Meter: 7
Not yet, only simple resurection.

Tomorow i will try and post the result...
  Reply With Quote
Old 03-15-2012, 22:22   #15 (permalink)
No Life Poster
 
BouRRi_GSM's Avatar
 
Join Date: Jan 2005
Location: TuNiSiA
Age: 39
Posts: 4,338
Member: 111457
Status: Offline
Thanks Meter: 962
@gabrielgsm
it seem u can enter fastboot mode,
so u can read original cid with adb using this command
fastboot getvar cid
or
fastboot getvar cidnum

u can even get current sw version using this command,
fastboot getvar version-main


br
  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
6150 Lock Problem Zeljko Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 10-16-2013 08:16
GId1 problem old_man Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 1 10-18-2006 15:21
6110 5.47 sw unlock problem gsms Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 11-21-1999 18:43
HELP: Problem with 5110 Xabi Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 1 07-16-1999 00:44

 



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



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

SEO by vBSEO