|
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 |
| LinkBack | Thread Tools | Display Modes |
07-25-2012, 15:24 | #17 (permalink) |
Insane Poster Join Date: Feb 2012 Location: Portugal, Funchal
Posts: 88
Member: 1720469 Status: Offline Thanks Meter: 12 | Then there is no solution for the EMMC Bug bricks I have received... all of then stop 1% Does anyone has a tutorial on how to remove the EMMC CHIP glue and where to find the EMMC CHIP replacement part? Regards Marco |
07-25-2012, 15:29 | #18 (permalink) |
Freak Poster Join Date: Oct 2001 Location: Moscow, Russia Age: 47
Posts: 284
Member: 6653 Status: Offline Sonork: 100.1597550 Thanks Meter: 26 | I have done all the steps 1 through 4, the phone still dead. I'm doing wrong? Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 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.79V, TCK Frequency is 8 MHz Settings Code: 0x22020B00000000000000000000008000 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) Writting FLASH2 memory from 0x000000000000 to 0x000000007FFF Completed in 00:00:04.250 (Average Transfer Rate: 7.53 kB/s) Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 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.79V, TCK Frequency is 8 MHz Settings Code: 0x22020B00000000008000000000008000 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) Writting FLASH2 memory from 0x000000008000 to 0x00000000FFFF Completed in 00:00:04.328 (Average Transfer Rate: 7.39 kB/s) Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 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.79V, TCK Frequency is 8 MHz Settings Code: 0x22020B00000000010000000000008000 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) Writting FLASH2 memory from 0x000000010000 to 0x000000017FFF Completed in 00:00:04.204 (Average Transfer Rate: 7.61 kB/s) Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 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.79V, TCK Frequency is 8 MHz Settings Code: 0x22020B00000000018000000000008000 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) Writting FLASH2 memory from 0x000000018000 to 0x00000001FFFF Completed in 00:00:04.188 (Average Transfer Rate: 7.64 kB/s) Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 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.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/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 <> 0x014000) |
07-25-2012, 16:03 | #19 (permalink) | |
Freak Poster Join Date: Aug 2010 Location: Ukraine, Lutsk
Posts: 243
Member: 1367150 Status: Offline Thanks Meter: 42 | When i try "initiate download mode" option all goes ok. BUT the phone CANT SEE by PC! Quote:
| |
07-31-2012, 22:41 | #24 (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 | Hi Please Note: This method only work any phone stop writing on 100%..... -- Not help for any phone with any other error,like stop on start or stop on 1% or etc --- For Repair phone with 1%,You need replace eMMC... i did test before......and phone resurrected and repaired after change eMMC....(but some case still need check some part in pcb after replace eMMC) |
08-01-2012, 11:45 | #26 (permalink) | |
Insane Poster Join Date: Oct 2002 Location: Russia Age: 45
Posts: 84
Member: 16794 Status: Offline Thanks Meter: 0 | Quote:
i9100 dead after custom upgrade. same info about situation: Hard Brick Bug on Galaxy S II and Note Leaked ICS Kernels – xda-developers in attach original cmm for i9100, may be help for developers. wait solution for Riff ... PS- after same operations with Riff my I9100 looks as usb device SEC S5PC210 Test B/D but then disappear after Legija instructions Last edited by L_DIM; 08-01-2012 at 11:54. | |
08-01-2012, 17:16 | #27 (permalink) | |
No Life Poster Join Date: Nov 2007 Location: Dubai.
Posts: 1,063
Member: 625961 Status: Offline Sonork: 100.1590447 Thanks Meter: 1,285 | Quote:
thanks riff team! its worked for me! this METHOD for phone stop writing on 100%.. Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.32, JTAG Manager Version: 1.41 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.80V, TCK Frequency is 8 MHz Settings Code: 0x22020B00000000018000000000008000 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 (VIS00M, 0x0003AB400000 Bytes = 14.68 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VIS00M, 0x000000080000 Bytes = 0.50 MB) Writting FLASH2 memory from 0x000000018000 to 0x00000001FFFF ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK Completed in 00:00:38.938 (Average Transfer Rate: 0.82 kB/s) B/R WAJID | |
08-04-2012, 06:58 | #29 (permalink) |
Freak Poster Join Date: Jun 2012
Posts: 109
Member: 1772418 Status: Offline Thanks Meter: 7 | Just in case some one tries it even if it stops at 0-1%... Does not work. I had 2 this week and tried skipping the part of the resurrection, manually placed the boot at ROM2 and did not work. Dont even try it, you are just kidding yourself like i did... But if you like a beta tester for this works i have 2 wired phones ready for trials... |
08-05-2012, 15:29 | #30 (permalink) |
Junior Member Join Date: Aug 2012
Posts: 1
Member: 1793770 Status: Offline Thanks Meter: 0 | Damaged EMMC for i9100 Can this repair the GT-I9100 that has a EMMC with bad sectors or rather with the BUG in the blocks ?... My i9100 is dead, no boot or sign of life from it. |
Bookmarks |
| |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Anybody know solution | Robi | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 1 | 12-10-2014 12:35 |
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 |
Solution for GSM phones!?!?!?!? | todosije | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 6 | 12-16-2010 05:52 |
!!!!!!TO ALL NOKIA 51XX/61XX SP LOCKS 1,2,3,4 SOLUTION latest news!!!!! | spterminator | Main Sales Section | 2 | 08-13-1999 05:55 |
Upload / Download eeprom program for 51xx/61xx | Ryu | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 3 | 07-07-1999 14:03 |
|