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 01-18-2012, 11:20   #1 (permalink)
No Life Poster
 
crackp0d's Avatar
 
Join Date: Aug 2007
Location: @crackp0d
Age: 36
Posts: 512
Member: 571377
Status: Offline
Sonork: 100.1608017
Thanks Meter: 136
Samsung Galaxy S II SGH-I9100 Resurrection problem


Hi Riff team

I have one Samsung S II SGH-I9100 Resurrection problem

See this

pen serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.30, JTAG Manager Version: 1.38
Selected Resurrector: [Samsung i9100]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.79V, TCK Frequency is 8 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/0x0001 (VYL00M, 0x03AB400000 Bytes)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0000080000 Bytes)

Flashing the dead body...
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x0000000000


How to fix this problem I did try with all TCK Frequency but same error
  Reply With Quote
Old 01-18-2012, 22:28   #2 (permalink)
Freak Poster
 
Join Date: Jan 2011
Posts: 355
Member: 1501506
Status: Offline
Thanks Meter: 47
This is a NAND chip hardware problem. I've personally had about 5 in 200 PCS with this issue. You can read from the chip fine but not write to it. This was proven with multiple boxes as well so it's not just a bug.
  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
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 19: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 13:43.



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

SEO by vBSEO