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 06-28-2012, 13:49   #1 (permalink)
Junior Member
 
Join Date: Aug 2011
Posts: 14
Member: 1631918
Status: Offline
Sonork: 198.168.1.1
Thanks Meter: 2
Samsung SHW-M250s repair dead boot Error Code = 0x3E


Help me !
Samsung Galaxy SII SHW-M250s repair dead boot Error Code = 0x3E

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

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.79V, TCK Frequency is 200 kHz

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, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)
  Reply With Quote
Old 07-06-2012, 05:06   #2 (permalink)
Junior Member
 
Join Date: Apr 2006
Posts: 4
Member: 261431
Status: Offline
Thanks Meter: 0
Me too. please help !
  Reply With Quote
Old 11-10-2012, 18:43   #3 (permalink)
No Life Poster
 
Join Date: Aug 2004
Location: sri lanka
Posts: 628
Member: 77437
Status: Offline
Sonork: 100.1582159
Thanks Meter: 93
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.45
Selected Resurrector: [Samsung i9100 V1.0.4582.4854]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, 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, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)


please help I have same problem
  Reply With Quote
Old 11-11-2012, 03:32   #4 (permalink)
Junior Member
 
Join Date: Nov 2012
Location: vietnames
Posts: 34
Member: 1837704
Status: Offline
Sonork: 100.1611674
Thanks Meter: 2
I have a tested with M250s

Quote:
[10/23/2012 9:33:53 PM] [START OPERATION_ID = RESURRECT]
[10/23/2012 9:35:22 PM] Open serial port...OK
[10/23/2012 9:35:22 PM] Connecting to the RIFF Box...OK
[10/23/2012 9:35:22 PM] Firmware Version: 1.34, JTAG Manager Version: 1.45
[10/23/2012 9:35:22 PM] Selected Resurrector: [Samsung i9100 V1.0.4582.4854]
[10/23/2012 9:35:22 PM]
[10/23/2012 9:35:22 PM] Connecting to the dead body...OK
[10/23/2012 9:35:22 PM] Detected dead body ID: 0x4BA00477 - CORRECT!
[10/23/2012 9:35:22 PM] Set I/O Voltage reads as 2.80V, TCK Frequency is 8 MHz
[10/23/2012 9:35:22 PM]
[10/23/2012 9:35:22 PM] Resurrection sequence started.
[10/23/2012 9:35:22 PM] Establish communication with the phone...OK
[10/23/2012 9:35:22 PM] Initializing internal hardware configuration...OK
[10/23/2012 9:35:22 PM] Uploading resurrector data into memory...OK
[10/23/2012 9:35:22 PM] Starting communication with resurrector...OK
[10/23/2012 9:35:22 PM]
[10/23/2012 9:35:22 PM] Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
[10/23/2012 9:35:22 PM] Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)
[10/23/2012 9:35:22 PM]
[10/23/2012 9:35:22 PM] Flashing the dead body...OK
[10/23/2012 9:35:22 PM] Resurrection complete!
[10/23/2012 9:35:22 PM] [FINISH OPERATION_ID = RESURRECT]
  Reply With Quote
Old 11-11-2012, 03:34   #5 (permalink)
No Life Poster
 
Mr.3.'s Avatar
 
Join Date: Feb 2009
Location: CMB/Ceylon
Posts: 8,096
Member: 962029
Status: Offline
Sonork: OEM Lock : ON
Thanks Meter: 4,127
Quote:
Originally Posted by ruwanjk View Post
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.45
Selected Resurrector: [Samsung i9100 V1.0.4582.4854]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, 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, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)


please help I have same problem
Check sticky thread.. Solution posted there
  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: Forgot my 6110 user lock code!! GByte9 Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 4 02-26-2016 14:52
PIN1/PIN2 CODE Jon Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 1 12-26-2012 04:40
where to find a working program all they have some errors ?? fondas Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 2 12-12-2012 13:26
The multiple errors of Winlock ... ??? Genata Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 0 09-20-1999 19:12
error (1002) simlock3.dll winopen fondas Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 0 08-28-1999 15:57

 



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



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

SEO by vBSEO