ANSWERED 74 bad blocks possible to remap in trinity nand?

[Martin C]

Can you post a pic of the soldering near the HANA too?

 

[Eazywolf]

Here is "hana solder".

 

[Martin C]

What tool did you use to build the NAND?

 

[Eazywolf]

First time i use multi builder v0.7, but after i flash it the built bin to nand and wont work , i remembered back to my dashboard version is 13604 second time i use multibuilder v0.4 to build nand, but nothing changed after flashing.

 

[Martin C]

Flash back your original NAND and make sure it still boots. You shouldn't need to disable anything on board.

 

[rallin0s]

Also I would recommend not running the ground or power wires directly over the Hana wire I have had problems with one console wired like that it had no video then moved the ground and it booted up no problem.

 

[Eazywolf]

I already made a pendrive with rawflash and the original nand, but when i tried starting the consol, do not start, no more green led on coolrunner, only the red light, and the green on the consol front. I looked the mainboard and i saw the standby clock wire is not so good...
Probably when i took the last photographs, i crashed it a little. No cut in the track, but i afraid of to use that solder point in the future.
I built a new point on to track, solder the wire, but nothing changed. No green led on coolrunner, only the "red light", and the center led light on the consol.
No picture on tv, no any other lifesign.
I attached the new photographs from my mainboard.

 

[Martin C]

So is it booting now with the original NAND back?

 

[Eazywolf]

I dont know, because i cant use the rawflash without xell. If i try to flash the nand with nand-x, no need to worry the strange non-matching blocks story, when i flash with nand-x and read back?
One more thing: after when you told me, i need to flash with original nand to check, it is boot or not, the consol do not start with the eject button, before i flash it with original. This is the cause why i stopped and dont flash. Is this not a new problem? Because it was possible to start with eject button, i nothing to do with nand and now it is not possible to start with eject button.
Flash the original nand with nand-x anyway?

 

[Martin C]

You MUST trim those wires down as you have too much exposed. Do this first, then flash back your original NAND.

 

[Eazywolf]

I trim the nand-x wires shorter, and flash the original nand, and read back and comapare with original, 74 non matching blocks found.
Now the problem is changed like the first time. E79 Error code, secondary error code 1033.
I am sure the original dumped nand is 100% ok, because i dumped it approximately a month earlier when my xbox 360 worked, i made four dump, all four comparesation match. Here are a new picture.

 

[Martin C]

dump what you wrote and compare it. Is it the same?

 

[Eazywolf]

No, its not. 74 non matching blocks found.

 

[Martin C]

So you have a write issue which is why you're getting E74.

Unplug the NAND-x wires (but leave the wires soldered to the board).

Check my NAND-x troubleshooting link in my sig and make sure your values match.

 

[Eazywolf]

My error code E79, no E74.
74 non matching blocks found any time when i dump the nand after flash. I go and check the troubleshooter!

 

[Eazywolf]

i Checked the readings many times, the results are very strange for me.

Pin1 read1 - 1,143v
Pin1 read2 - .030v
Pin1 read3 - .055v
Pin1 read4 - 0.7v

Pin2 read1 - 3,3v
Pin2 read2 - 3,3v
Pin2 read3 - 3,3v
Pin2 read4 - 3,3v

Pin3 read1 - .096v
Pin3 read2 - .052v
Pin3 read3 - .024v
Pin3 read4 - 0,5v

Pin4 read1 - lifting between 2,5 - 40 ohms
Pin4 read2 - 3,3 ohms
Pin4 read3 - 2,1 ohms
Pin4 read4 - 38,4 ohms

Pin5 all read - 3,05v (anytime read same result)

Pin6 read1 - 5,83 k ohms
Pin6 read2 - 6,05 k ohms
Pin6 read3 - 6,05 k ohms
Pin6 read4 - 6,05 k ohms

 

[Martin C]

ok, well you'll get some variance from points with resistance as they need to 'settle down'.

So try this:

nandpro usb: -r2 test1.bin 0 50
nandpro usb: -r2 test2.bin 0 50
nandpro usb: -r2 test3.bin 0 50
nandpro usb: -r2 test4.bin 0 50

fc /b test1.bin test2.bin
fc /b test2.bin test3.bin
fc /b test3.bin test4.bin

Let me know if you get any differences.

 

[alexhore]

Just a thought, if he dumped the nand a month ago has he perhaps took the recent dash update changing the ldv Value.

Edit, guess we will find out once he flashes the original nand back on.

 

[Eazywolf]

i did what you said, i made all file compare, after i dump. No difference between files.

 

[Martin C]

ok, so next try this:

nandpro usb: -r16 test1.bin
nandpro usb: -r16 test2.bin
nandpro usb: -r16 test3.bin
nandpro usb: -r16 test4.bin

run these through xnandhealer and let me know what you get.