Samsung Galaxy/Nexus eMMC - P1000, i9023, i9020T, M200S and variations - GSM-Forum

**legija** · 02-07-2013, 20:07

Hello dear RIFF Box users !

In order to diagnose possible problems with mass memory chips (internal disk) in above listed models, we've added ROM2/3 chip detection to DCC loaders.
This applies to following models:

Samsung Galaxy (P1000/i9000/T959, m110s, m180s)
Samsung Nexus (i9023, i92020, m200s, m200k)

Explanation:
Above listed models have two memory chips:

NAND chip which holds bootloader and part of system software (ROM1),
eMMC chip which holds user data and in Nexus phones complete OS (system software). (ROM2 and ROM3)

In case that eMMC is faulty, Galaxy models will hang on startup screen, or show message "Unable to mount x drive",
Nexus models will not start at all, or just will show black screen with low backlight.

To diagnose if eMMC is faulty or not, use the following method:

Galaxy models:

Select P1000 DLL, and on DCC TAB select ROM2, set any data length size,
click "Read Memory".
If You get "error 0x28" on reading attempt, it means that eMMC is faulty and You have to replace it.

Nexus models

Select i9020A DLL, and on DCC TAB select ROM2, set any data length size,
click "Read Memory".
If You get "error 0x28" on reading attempt, it means that eMMC is faulty and You have to replace it.

Examples:

Here is sample log from P1000 with working mass memory:

Quote:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.35, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung P1000 V1.0.4786.9062]

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 8 MHz
Settings Code: 0x20010B00000000000000000000100000

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/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

Reading FLASH1 address space from 0x000000000000 to 0x0000000FFFFF
Completed in 00:00:01.280 (Average Transfer Rate: 825.00 kB/s)

Here is log from device which has faulty mass memory chip:

Quote:

[08-Jan-13 18:12:03] Open serial port...OK
[08-Jan-13 18:12:03] Connecting to the RIFF Box...OK
[08-Jan-13 18:12:03] Firmware Version: 1.35, JTAG Manager Version: 1.48
[08-Jan-13 18:12:03] Selected Resurrector: [Samsung I9020 eMMC V1.0.4756.65088]
[08-Jan-13 18:12:03]
[08-Jan-13 18:12:03] Connecting to the dead body...OK
[08-Jan-13 18:12:03] Detected dead body ID: 0x1BA00477 - CORRECT!
[08-Jan-13 18:12:03] Set I/O Voltage reads as 2.81V, TCK Frequency is 8 MHz
[08-Jan-13 18:12:03] Settings Code: 0x20020B00000000000000000000000200
[08-Jan-13 18:12:03]
[08-Jan-13 18:12:03] Resurrection sequence started.
[08-Jan-13 18:12:03] Establish communication with the phone...OK
[08-Jan-13 18:12:03] Initializing internal hardware configuration...OK
[08-Jan-13 18:12:03] Uploading resurrector data into memory...OK
[08-Jan-13 18:12:03] Starting communication with resurrector...OK
[08-Jan-13 18:12:03]
[08-Jan-13 18:12:03] Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0060 (1024MB)
[08-Jan-13 18:12:03] WARNING: DCC Loader was unable to initialize FLASH2 chip. Error code: 0x00000036
[08-Jan-13 18:12:03]
[08-Jan-13 18:12:03] ERROR: Selected FLASH2 Chip was not Recognized by the DCC Loader. Terminating.

In this case mass memory is either not present or it developed failure. Only NAND chip (ROM1) functions will remain accessible.

Quote:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung M200S V1.0.4787.59328]
Restarting target (nRST Low then High)...OK

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 1 MHz
Settings Code: 0x20030600000000000000000000100000

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/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

Reading FLASH3 address space from 0x000000000000 to 0x0000000FFFFF
ERROR: Read Failed with Error Code: 0x28. Terminating at 0x000000000000

In this case eMMC is also faulty, and need to be replaced.

Aamir_Zia · 02-07-2013, 21:59

Ok . I want to ask some important stuff here

Since many samsung phones internal sd card is corrupted by format changing of internal sdcard ..
Like formatting internal sdcard format to EXT4 , if we flash converted Format Phones via odin without revert back to samsung default format , the internal ic got corrupted . This usually happens with Tegrak Kernel .

So can we format the internal sd card back to Samsung format ??

**legija** · 02-07-2013, 22:15

Quote:

Originally Posted by Aamir_Zia

Ok . I want to ask some important stuff here

Since many samsung phones internal sd card is corrupted by format changing of internal sdcard ..
Like formatting internal sdcard format to EXT4 , if we flash converted Format Phones via odin without revert back to samsung default format , the internal ic got corrupted . This usually happens with Tegrak Kernel .

So can we format the internal sd card back to Samsung format ??

Mass memory content can be accessed with eMMC plugin. This means, You can load it's image and partition table and modify it's content.

Tegrak kernel causes something unrelated to current issue, it causes "lockup bug" which is something different.

In that case - eMMC gets locked after bad address sectors are accessed causing either system freeze or restart. This can be solved either by kernel patch which was released on google code project, or by replacing locked eMMC.

**legija** · 02-08-2013, 21:14

Samsung_I9020A.dll, Samsung_I9020T.dll, Samsung_M200S.dll
-------------------------------------
- added internal eMMC support: it's detected as ROM2/ROM3 memories.

cabila · 02-08-2013, 21:49

Hi everyone.

Thanks for your continuos support to these models:

I have tested the first 4 faulties i9020T.

The results are this:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung I9020T V1.0.4787.59284]

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.81V, 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: 0x00EC/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

So, eMMC are OK. But no download mode.

This night I'll test 8 mainboards further.

There are a lot of work with this phone family.

I remember Dl mode is possible with I9000 Dll but we can't flash it with ODIN.

Thanks again.

.::PHONECRAKER::. · 02-09-2013, 06:39

yes my m200s also same problem,download mode ok but no fastboot to write firmware as you all no there is no firmware for this model to write with odin.
waiting for your solotion MR Legija
best regards

BABAK NURI · 02-09-2013, 09:44

@cabila

Detected eMMC with new dll is not meant to be healthy and working eMMC Chip
So,You Need Replace(usually),But Test Dump File Before Replace New Chip
---
And This is Reason For Start "Downloading" With I9000.dll
Mr.Legija:

Quote:

These phones (i902x, M200) have NAND and eMMC chips.
In NAND memory there is pbl and sbl + some other irrelevant data, but android kernel and whole system is stored in eMMC.
This is why it wont start, while in i9000, everything is stored in NAND, just userdata goes to eMMC.

====================================
@I am Back
Your Problem not have any related to this topic
You need find firmware for reflash phone...

.::PHONECRAKER::. · 02-09-2013, 10:03

Mr Babak I know my problem not related to this topic,My mean was that the phone problem is fastboot problem phone not goes to fastboot mode to write zip firmware in recovery mode.and want to ask you can be any working dump for this model to write?
dont you think writing dump doesnt solve our problem?
as I know by finding firmware also we are unable to flash this set with odin.
please tell me your sugestion how to solve this problem as I know many user have same problem
thnx in advanced

**legija** · 02-09-2013, 14:42

Here's log from another faulty M200s:

Quote:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung M200S V1.0.4787.59328]
Restarting target (nRST Low then High)...OK

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 1 MHz
Settings Code: 0x20030600000000000000000000100000

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/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

Reading FLASH3 address space from 0x000000000000 to 0x0000000FFFFF
ERROR: Read Failed with Error Code: 0x28. Terminating at 0x000000000000

As we can see, even if eMMC is detected properly, that don't mean it's fully working. This hapens in case where eMMC firmware controler enters lockup state due to bug related to bad sectors handling.

mymiela0419 · 02-09-2013, 16:49

Legija, First of all thank you for this wonderful update

I had a i9020T that got successfully boot repaired klast 2 weeks ago by RIFFBOX but when I turn it on the i9020T is still dead

DO you mean with new DLL file on riffbox it will fix this problem?
will i9020T be alive now with this new method?

TKDShangriLa · 02-10-2013, 08:02

Hello Legija please accept my sonork request need to talk with u through sonork!
100.1625395

shahzad-0004 · 02-10-2013, 12:26

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung M200S V1.0.4787.59328]

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.81V, 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: 0x00EC/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

Flashing the dead body...OK
Resurrection complete!

but phone still dead plz help me thanks

.::EXTREME::. · 02-10-2013, 13:09

eMMC

May be its hardware fault.

whats fone status from customer?

algerienbox · 02-10-2013, 18:27

repair boot OK:

Code:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung I9023 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 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: 0x00EC/0x0050 (512MB)

Flashing the dead body...OK
Resurrection complete!

read memory witn new p1000 DLL:

Code:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung P1000 V1.0.4786.9062]

Connecting to the dead body...OK
Detected dead body ID: 0x1BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 8 MHz
Settings Code: 0x05010B00000000000000000020000000

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/0x0050 (512MB)
Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB)
Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB)

Reading FLASH1 address space from 0x000000000000 to 0x00001FFFFFFF
Completed in 00:07:47.687 (Average Transfer Rate: 1156.06 kB/s)

Phone not goes into Downalod Mode with jig and without jig and there is No sound of connecting with PC !!!!!!

shahzad-0004 · 02-11-2013, 08:17

Quote:

Originally Posted by .::EXTREME::.

eMMC

May be its hardware fault.

whats fone status from customer?

flashing error than phone dead

please help me thanks

02-08-2013, 21:49	#5 (permalink)
cabila Junior Member Join Date: Aug 2007 Location: Spain, Comunidad Valenciana Posts: 19 Member: 573618 Status: Offline Sonork: 1624109 Thanks Meter: 0	i9020T Hi everyone. Thanks for your continuos support to these models: I have tested the first 4 faulties i9020T. The results are this: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung I9020T V1.0.4787.59284] Connecting to the dead body...OK Detected dead body ID: 0x1BA00477 - CORRECT! Set I/O Voltage reads as 2.81V, 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: 0x00EC/0x0050 (512MB) Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB) Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB) So, eMMC are OK. But no download mode. This night I'll test 8 mainboards further. There are a lot of work with this phone family. I remember Dl mode is possible with I9000 Dll but we can't flash it with ODIN. Thanks again.

02-10-2013, 12:26	#12 (permalink)
shahzad-0004 No Life Poster Join Date: May 2007 Age: 40 Posts: 1,316 Member: 515130 Status: Offline Thanks Meter: 304	Shw m200s(b) boot repair problem Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung M200S V1.0.4787.59328] Connecting to the dead body...OK Detected dead body ID: 0x1BA00477 - CORRECT! Set I/O Voltage reads as 2.81V, 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: 0x00EC/0x0050 (512MB) Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB) Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB) Flashing the dead body...OK Resurrection complete! but phone still dead plz help me thanks

02-07-2013, 21:59	#2 (permalink)
Aamir_Zia No Life Poster Join Date: Dec 2003 Location: Karachi Pakistan Age: 38 Posts: 6,770 Member: 47321 Status: Offline Sonork: 100.54032 Thanks Meter: 497	Ok . I want to ask some important stuff here Since many samsung phones internal sd card is corrupted by format changing of internal sdcard .. Like formatting internal sdcard format to EXT4 , if we flash converted Format Phones via odin without revert back to samsung default format , the internal ic got corrupted . This usually happens with Tegrak Kernel . So can we format the internal sd card back to Samsung format ??

02-08-2013, 21:14	#4 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	Samsung_I9020A.dll, Samsung_I9020T.dll, Samsung_M200S.dll ------------------------------------- - added internal eMMC support: it's detected as ROM2/ROM3 memories.

02-09-2013, 06:39	#6 (permalink)
.::PHONECRAKER::. Freak Poster Join Date: Jul 2011 Location: Gsm college Posts: 311 Member: 1610262 Status: Offline Sonork: 100.1608508 Thanks Meter: 44	yes my m200s also same problem,download mode ok but no fastboot to write firmware as you all no there is no firmware for this model to write with odin. waiting for your solotion MR Legija best regards

02-09-2013, 10:03	#8 (permalink)
.::PHONECRAKER::. Freak Poster Join Date: Jul 2011 Location: Gsm college Posts: 311 Member: 1610262 Status: Offline Sonork: 100.1608508 Thanks Meter: 44	Mr Babak I know my problem not related to this topic,My mean was that the phone problem is fastboot problem phone not goes to fastboot mode to write zip firmware in recovery mode.and want to ask you can be any working dump for this model to write? dont you think writing dump doesnt solve our problem? as I know by finding firmware also we are unable to flash this set with odin. please tell me your sugestion how to solve this problem as I know many user have same problem thnx in advanced

02-09-2013, 16:49	#10 (permalink)
mymiela0419 No Life Poster Join Date: Oct 2007 Location: places I repair phones Posts: 2,029 Member: 621698 Status: Offline Thanks Meter: 405	Legija, First of all thank you for this wonderful update I had a i9020T that got successfully boot repaired klast 2 weeks ago by RIFFBOX but when I turn it on the i9020T is still dead DO you mean with new DLL file on riffbox it will fix this problem? will i9020T be alive now with this new method?

02-10-2013, 08:02	#11 (permalink)
TKDShangriLa Freak Poster Join Date: Jun 2012 Location: @ Shangri-LA Posts: 168 Member: 1772475 Status: Offline Sonork: 100.1617312 Thanks Meter: 35	Hello Legija please accept my sonork request need to talk with u through sonork! 100.1625395

02-10-2013, 13:09	#13 (permalink)
.::EXTREME::. No Life Poster Join Date: Jul 2011 Location: ۞_ KERALA__۞_INDIA Posts: 3,352 Member: 1619462 Status: Offline Sonork: 100.1606509 Thanks Meter: 1,517	eMMC May be its hardware fault. whats fone status from customer?