|
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 . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source | Today's Posts | Search |
| LinkBack | Thread Tools | Display Modes |
02-07-2013, 20:07 | #1 (permalink) | |||
Product Manager Join Date: Apr 2006 Age: 55
Posts: 5,746
Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276 | Samsung Galaxy/Nexus eMMC - P1000, i9023, i9020T, M200S and variations 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:
Above listed models have two memory chips:
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:
click "Read Memory". If You get "error 0x28" on reading attempt, it means that eMMC is faulty and You have to replace it.
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:
Quote:
Quote:
Last edited by legija; 04-23-2013 at 11:50. | |||
The Following 31 Users Say Thank You to legija For This Useful Post: |
02-07-2013, 21:59 | #2 (permalink) |
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-07-2013, 22:15 | #3 (permalink) | |
Product Manager Join Date: Apr 2006 Age: 55
Posts: 5,746
Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276 | Quote:
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. | |
The Following 5 Users Say Thank You to legija For This Useful Post: |
02-08-2013, 21:14 | #4 (permalink) |
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. |
The Following 3 Users Say Thank You to legija For This Useful Post: |
02-08-2013, 21:49 | #5 (permalink) |
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-09-2013, 06:39 | #6 (permalink) |
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, 09:44 | #7 (permalink) | |
Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43
Posts: 7,259
Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475 | @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:
@I am Back Your Problem not have any related to this topic You need find firmware for reflash phone... | |
02-09-2013, 10:03 | #8 (permalink) |
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, 14:42 | #9 (permalink) | |
Product Manager Join Date: Apr 2006 Age: 55
Posts: 5,746
Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276 | Here's log from another faulty M200s: Quote:
| |
The Following 2 Users Say Thank You to legija For This Useful Post: |
02-09-2013, 16:49 | #10 (permalink) |
No Life Poster Join Date: Oct 2007 Location: places I repair phones
Posts: 2,033
Member: 621698 Status: Offline Thanks Meter: 406 | 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, 12:26 | #12 (permalink) |
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-10-2013, 18:27 | #14 (permalink) |
No Life Poster Join Date: Sep 2007 Location: algeria
Posts: 2,360
Member: 591880 Status: Offline Thanks Meter: 561 | i9023 cant get DL MODE !!! 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) |
The Following User Says Thank You to algerienbox For This Useful Post: |
Bookmarks |
| |
|