N7000 2nd Time Boot Repair Error 0x46

[dannyogolo]

This phone was dead boot.
I resurrected ok 1st time and phone entered download mode ok.
I tried to flash with 4-part file and Odin and it stopped at getting pit for mapping (or something like that)
Phone back to dead boot.
Now I try to resurrect again, but getting error:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.51
Selected Resurrector: [Samsung N7000 V1.0.4860.58267]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.85V, 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, 0x0002AA400000 Bytes = 10.66 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

No Resurrection Data is available for the eMMC Chip with Capacity = 10.66GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14.68GB

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x46 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x46 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x46 (0x000000). Trying to recover...FAILED

I used Jpin, so soldering is very ok, I can still do other things with Riff - Detect phone, etc.
Only resurrect cant work.

[legija]

It looks like some HW problem, most probably bad soldering.
The eMMC detected size is very strange.
Maybe it's not bad idea to inspect hardware for cracks, or eventually reball the eMMC and power chip.

[dannyogolo]

Sure its hardware?
As i wrote the 1st time, the resurection went perfect.
I think pit repartitioning made the 10GB partition when i tried to update phone with odin (but it failed).

Also when i do erase, it erase all ok!!!

Can you think of something else @legija ?

[legija]

Originally Posted by dannyogolo

Sure its hardware?
As i wrote the 1st time, the resurection went perfect.
I think pit repartitioning made the 10GB partition when i tried to update phone with odin (but it failed).

Also when i do erase, it erase all ok!!!

Can you think of something else @legija ?

eMMC capacity is calculated and reported by eMMC controller firmware, not the PIT file.

"Getting PIT for mapping . . ." was just Odin trying to read PIT partition, and it failed because there is some HW failure.

[dannyogolo]

After about 30 mins, I retried it again, and voila, Riff resurrected it.
BUT AGAIN, when I go to odin to flash, Getting pit for mapping, and stops there, AND PHONE IS BRICKED AGAIN.

So now I dont have eMMC capacity error, but after every brick, I have to wait 30 mins or more.

Any more ideas aside eMMC reballing ?

[BABAK NURI]

Hi
For 99% You need replace
So,You have only 1% for Reball

Just choose which one and Try

Thanks

[aZimBahar]

I Get one on this condition

samsung-kies-firmware-issue

i Try To Flash But After flash Start Will Come Error On Few Sec
Then I Try with n7000.pit But Flash now start then After few min i disconnect phone wont on

i try boot repair error

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.