Let's put back our beloved decorative screw caps bases (MkII) over the 8 black screws...
Mother board back in place in metallic bottom case... Lets put back other screws, face button, etc...
Now, that we are on the other face of motherboard we have all wires with labels on it.
Time to solder them to the DB25 male white connector :
.N P Q T V 7 6 5 3 2 1 0. (12 pins)
M O U 4 + - (13 pins)
So a maximum of wires match the DB 25 female black connector vertical first pins raw, the closest to the Infectus mini-board (just need to bend them and solder to spot). Only 6 wires are to "extend" from second pins raw with a bit of metallic wire. You can see soldered bent pins in upper right corner of the photograph (Infectus mini-board stuck on top of female black DB25 connector with a double-sided tape).
(See photograph below)
Now we plug the DB25 male into the female. We put some electrical tape above Infectus mini-board (since drive will come on top and push it downward. Let's fix white male connector with a double sided tape (two layers, so it gets some flexibility), on top of the "Ana" chipset (covered with electrical tape), so the whole thing can bend under the drive, but not just run wildly anywhere inside the console case...
We also connect the thin PSP usb2.0 cable (may not be official after all, brand name is BigBen interactive) to the Infectus mini-board and take it all the way to the little slot of drive opening (so we can reach easily hard disk plug hole by running it between metal case and plastic case).
(See photograph below)
Put back drive on top of all this mess and power up!
Notes (skip them, it's just my few bad attempts to power up) :
- I got a "3rod" when I tried without the Infectus plugged. But I had "4" severed so it may have interfered with the firmware reading at boot time. I re-soldered "4" (D4) and pluggued Infectus and console could reboot correctly.
- I had Infectus Programmer software not able to recognize the Nand. After a check, it was "M" who was severed. After I resoldered it, all went ok, finally... Nand recognized as Hynix-something.
How to dump firmware :
From Infectus site you retrieve the PC driver for the device and the Programmer software (v0.0.3.4d).
When you connect the usb2 cable to your PC, you are asked for the driver twice. Select the files you downloaded and soon you have a new peripheral : Infectus Device.
When you start the software, you are warned you will have to update the Infectus mini board firmware and that you mustn't turn off power while such firmware update is in progress.
But the infectus firmware update doesn't start at all. You have first to select what you want.
Tools->Wizard helps you, but you can just select in menu "Actel firmware", the Nand programmer and start the update.
That will (I guess) put the firmware named "Loader 0.24" and the "Nand programmer" program in the Infectus mini board.
As said earlier, if you didn't wire the V spot, you are probably stuck at this point.
Programmer v0.0.3.4d seems to require V wire if you are to write into your Nand (according to posts seen in Infectus tech support forum), whereas previous versions could do it without it.
Once everything is ok, you should read the name of your 360 firmware Nand chipset at bottom of screen and the command "Read" is now available in the menu "Flash Command".
Dump your firmware (32768 sectors of 512+16 bytes each).
Note that the dump you get (even if you have bad sectors, revealed by statuses 0x0350 & 0x0310) is identical to the one you get with recent tmbinc's software dumper (tmbincdump.c with "writereg(COMMAND, 3);" -dump whatever is sector status but report bad ones with 0x0350 & 0x0310- instead of "writereg(COMMAND, 2);" -dump if not a bad sector and report unused/blank status 0x0380-) :http://www.xboxhacker.net/index.php?topic=7290.20
I haven't tried to reflash my firmware yet.
I hope it will work (thanks to wires not exceeding 10cm).
I will wait a bit before trying it... That was too much emotion for a "week-end"...
About removing R6T3 resistor :
Pro : You can dump, upgrade, reflash to go back to previous firmware... Because new firmwares don't brick the 360 if the efuses they are supposed to blow up are still unharmed.
Con : What prevents M$ from releasing new firmwares that brick 360 if efuses are unharmed? Nothing. (And be prepared to find them, eventually, on retail discs of Halo 3 and Blue Dragon...)
But not touching the resistor means you know how to edit your old firmware image so it accepts new blown efuses... That's a complete adventure!This post has been edited by openxdkman: Mar 28 2009, 09:49 PM