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 08-30-2013, 21:22   #1 (permalink)
Junior Member
 
Join Date: Apr 2011
Posts: 38
Member: 1555702
Status: Offline
Thanks Meter: 1
Workaround for Error code 0x30


Hi @ all,

is there a workaround to resolve

Quote:
Error code 0x30
Returned by the DCC Loader when it fails to perform specific write protection unlock procedure on some memory chips when it is required to be done
on Galaxy S T959v?

Code:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.51
Selected Resurrector: [Samsung T959V V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 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

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0060 (1024MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x000000000000
Already tried with different frequencies and I9000 resurrector.

Regards,
onkeltom
  Reply With Quote
Old 08-30-2013, 21:49   #2 (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
Nope, You need to replace NAND chip.
  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


 



All times are GMT +1. The time now is 10:33.



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.12871 seconds with 8 queries

SEO by vBSEO