Samsung i9100/n70000 Programming Error at 0x000000000000 Solution!

[MUTUAL]

Originally Posted by BABAK NURI

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)

this days i get this error on every single phone
so its mean every single phone has ic problem?

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 (VIS00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VIS00M, 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 <> 0x010000)

[elmostapd1980]

i do all of that but cant repair phone

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung N7000 AP V1.0.4458.16492]

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

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 <> 0x010000)

[tayyab007]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung N7000 AP V1.0.4458.16492]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - 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: 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...OK
Resurrection complete!

what about this. phone still dead no errors.
best regards.

Originally Posted by legija

1% is not same as in topic.
You'll have to replace eMMC !

[FOCUS2]

This Solution is NOT working !
100% Tested NOT Working on N7000

[tayyab007]

my phone is resurrection completed 100% without any error. after that no download mode or any thing. i have do all the steps u mentioned in your post but the result is same. any help

thanks & regards.

[ham_sang]

Originally Posted by L_DIM

in client i9100 error 0x25 as in first post, but method don't help. brick.
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

Question: Why JTAG won’t work?
Quote:
Originally Posted by Ken Sumrall
As I mention above, the revision 0×19 firmware had a bug that after an emmc erase command, it could leave the internal data structures of the emmc chip in a bad state that cause the chip to lock up when a particular sector was accessed. The only fix was to wipe the chip, and update the firmware. I have code to do that, but I don’t know if I can share it. I’ll ask.

Other can do this but riff cant?

BR

[killionaire07]

oh **** is worked!! thank you so much bro!

[ikkks]

Originally Posted by killionaire07

oh **** is worked!! thank you so much bro!

can u explain which model u have done with this procedure many of us have same issue with i9100 and N7000 even me have same problem in N7000 nothing help with this procedure ......... it will b very helfull to others if u explain it clearly thank you

[MUTUAL]

Originally Posted by tayyab007

my phone is resurrection completed 100% without any error. after that no download mode or any thing. i have do all the steps u mentioned in your post but the result is same. any help

thanks & regards.

i have same problem my phone resurrection proper in the end i get this error i did all step what it show on but still not show download mode

[rajtelecom]

Originally Posted by tayyab007

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung N7000 AP V1.0.4458.16492]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - 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: 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...OK
Resurrection complete!

what about this. phone still dead no errors.
best regards.

is your problem solved or not........

[tayyab007]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung N7000 AP V1.0.4458.16492]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - 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: 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...OK
Resurrection complete!


best regards.

[call1985]

Thanks a lot for your help,it test ok for me .[IMG]http://b106.photo.store.qq.com/psb?/d91c2079-a1e4-4791-b054-d6d750a77a7c/ikjoSs4Gs6wBzix*.M3BF.VXBQv4kFzLqXTA8TBQrHA!/b/dHV0ND9LLQAA&bo=ngIFAb4![/IMG] http://b103.photo.store.qq.com/psb?/...QAA&bo=FAJfAm0!

[alex89]

there is a bin file like this but for i727? i have one with same symptoms but no download mode after 100% resurrect

[BABAK NURI]

Originally Posted by alex89

there is a bin file like this but for i727? i have one with same symptoms but no download mode after 100% resurrect

Hi
if resurrector can done,but not start DL_Mode,it's means fault eMMC Chip
But if error on 100%,You can extract original i727.tar file and use boot.bin

[alex89]

Originally Posted by BABAK NURI

Hi
if resurrector can done,but not start DL_Mode,it's means fault eMMC Chip
But if error on 100%,You can extract original i727.tar file and use boot.bin

if i use max speed it fails at the begining, if use 1mhz sometimes resurrects complet 100% others fail at various %