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 12-23-2013, 21:38   #1 (permalink)
Freak Poster
 
mastersgsm's Avatar
 
Join Date: Dec 2010
Location: Uzbekistan/Jizzakh
Posts: 425
Member: 1470188
Status: Offline
Sonork: 100.1638921
Thanks Meter: 88
It is EMMC problem???


samsung m250s log:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung M250S V1.0.4990.45084]
Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.86V, TCK Frequency is 100 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
WARNING: DCC Loader was unable to initialize FLASH1 chip. Error code: 0x00000048
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
  Reply With Quote
Old 12-23-2013, 21:57   #2 (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
as i can see,Yes .....But Why you select 100KHZ at TCK Speed? if you get some error when higher speed Please resolder all jtag wires and try with 8MHZ
--
Also Please Resurrect with latest I9100.dll (ver 10.48) and post log...(need with 8MHZ)

Thanks
  Reply With Quote
Old 12-23-2013, 22:40   #3 (permalink)
Freak Poster
 
mastersgsm's Avatar
 
Join Date: Dec 2010
Location: Uzbekistan/Jizzakh
Posts: 425
Member: 1470188
Status: Offline
Sonork: 100.1638921
Thanks Meter: 88
same problem
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung I9100 V1.0.4850.415]

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

WARNING: DCC Loader was unable to initialize FLASH1 chip. Error code: 0x00000048

No Resurrection Data is available for the eMMC Chip with Capacity = 0B
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB

ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
  Reply With Quote
Old 12-23-2013, 22:46   #4 (permalink)
Freak Poster
 
mastersgsm's Avatar
 
Join Date: Dec 2010
Location: Uzbekistan/Jizzakh
Posts: 425
Member: 1470188
Status: Offline
Sonork: 100.1638921
Thanks Meter: 88
after press power button phone is 60 ma, protsessor medium hot! phone did not fall within the very clean!

Last edited by mastersgsm; 12-23-2013 at 22:55.
  Reply With Quote
Old 12-24-2013, 05:45   #5 (permalink)
Freak Poster
 
ASKIYA's Avatar
 
Join Date: Jan 2011
Location: Washington USA
Posts: 309
Member: 1485377
Status: Offline
Sonork: 100.1623194
Thanks Meter: 52
Donate money to this user
No Resurrection Data is available for the eMMC Chip with Capacity = 0B

I think It is Emmc Problem
  Reply With Quote
Old 01-12-2014, 18:38   #6 (permalink)
No Life Poster
 
Join Date: Aug 2002
Location: Romania Buzau
Age: 54
Posts: 1,013
Member: 14468
Status: Offline
Thanks Meter: 50
I have the same error...
First this:
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/0x0100 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Selected Resurrection Data for the eMMC Chip with Capacity = 14.68GB

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000004000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000008000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000000C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000010000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000014000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000018000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000001C000 is handled as Cut Excess.

and then no emmc...

best regards
vali
  Reply With Quote
Old 03-11-2014, 22:23   #7 (permalink)
Freak Poster
 
Join Date: Feb 2005
Posts: 359
Member: 121375
Status: Offline
Thanks Meter: 25
Erase OK:
Quote:
[START OPERATION_ID = DCC_ERASE_MEMORY]
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung I9100 V1.0.4850.415]

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

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

Erasing FLASH1 memory from 0x000000000000 to 0x0003AB3FFFFF...OK
Completed in 00:04:58.125 (Average Transfer Rate: 51618.19 kB/s)
Write isn't OK:
Quote:
[START OPERATION_ID = RESURRECT]
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung I9100 V1.0.4850.415]

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

Selected Resurrection Data for the eMMC Chip with Capacity = 14,68GB

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000004000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000008000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000000C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000010000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000014000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000018000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000001C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000020000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000024000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000028000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000002C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000030000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000034000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000038000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000003C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001800000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001804000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001808000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000180C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001810000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001814000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001818000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000181C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001820000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001824000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001828000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000182C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001830000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001834000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001838000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000183C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001840000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001844000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001848000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000184C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001850000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001854000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001858000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000185C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001860000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001864000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001868000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000186C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001870000 is handled as Cut Excess.
ERROR: Forced to Terminate. Terminated at 0x000001870000
[FINISH OPERATION_ID = RESURRECT]
Is it hw(emmc) or dll problem?
  Reply With Quote
Old 03-12-2014, 13:46   #8 (permalink)
Freak Poster
 
mastersgsm's Avatar
 
Join Date: Dec 2010
Location: Uzbekistan/Jizzakh
Posts: 425
Member: 1470188
Status: Offline
Sonork: 100.1638921
Thanks Meter: 88
Quote:
Originally Posted by m.joco View Post
Erase OK:


Write isn't OK:


Is it hw(emmc) or dll problem?
it is emmc problem bro!
  Reply With Quote
The Following User Says Thank You to mastersgsm For This Useful Post:
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


 



All times are GMT +1. The time now is 08:41.



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

SEO by vBSEO