Print

[ToBbErT]

You really explained it clear and simple, thanks alot man!

cheers

This post has been edited by ToBbErT: Aug 23 2009, 09:35 PM

[Martinchris23]

QUOTE(ToBbErT @ Aug 23 2009, 09:34 PM)

You really explained it clear and simple, thanks alot man!

cheers

no probs. Now, if someone could let me know if it's possible to do this with an Infectus, I'd be very grateful  

[Hellzone]

Well the PCI Card does work... i think  (IMG:style_emoticons/default/uhh.gif)  Its just that NandPro Doesn't scan the right port
Im hooked into the power.

Here is what NandPro tells me

(IMG:http://img198.imageshack.us/img198/8953/checki.png)

When the driver is installed and i try and power the 360 with the port hooked up it doesn't power on, how ever when its unplugged the system boots right up
Any Ideas ?

This post has been edited by Hellzone: Aug 24 2009, 02:14 AM

[majinsoftware]

Xbox wont boot up with parrallel port connected.
Try changing the adress of the parrallel port card.

You can see the addresses it check on your image, go into device manager and see if you can set it as once of them.

Or if it has a bootable bios on computer powerup, Some times they do its like push CTRL+T, it should say anyway if it does.

Or you can ask Tiros to make a modified version that searches the address of you card.

This post has been edited by majinsoftware: Aug 24 2009, 02:39 AM

[Mhawk134]

Yeah I tired a PCI card just because I wasn't having any luck at first and everything I tired it never saw the card.  Good luck if you get that going let me know, but I gave up once I was able to use the diode method and it worked fine.

Hawk

[Hellzone]

Yeh im about to trash it, i doubled checked my wireing to make sure it was right.. and the diode dosent make any diffrence, would the 100ohm caps make any diffrence ? (IMG:style_emoticons/default/blink.gif)

This post has been edited by Hellzone: Aug 24 2009, 05:53 AM

[majinsoftware]

If that parallel ports 3.3V the resistors will make it have read errors.
Dont trash it, you just need to get nandpro to look on a different address. Wait a awhile and a new version should come out or some one will hex edit it to search on custom addresses.

[FrostyTheSnowman]

After much trial and error with building a few more of these cables, I just have a few notes on the wiring that I would like to add:

1. As said before by Hawk, if you are getting an incorrect FlashConfig please MAKE SURE that your diode is on the motherboard side of the cable and not inside/connected to your LPT port connector. (I tried this both ways, even when wired correctly the diode STILL NEEDS to be on the motherboard side of the cable, not at the LPT connector side of the cable, I would imagine that the diode being too close to the LPT port causes timing issues, which is why you need to do it this way)

2. If you have a really long cable (1 meter or more in length) then the 100 Ohm resistors will cause NandPro to not detect the NAND controller. If you are unable to detect the NAND controller and you are using a fairly long cable (1 meter or more in length) you NEED to remove the resistors, or else it will not work.

3. If you are having reading issues (dumps not matching or multiple read errors) try using shielded cable instead of non-shielded cable. And if you are using shielded cable, MAKE SURE the shielding of the cable is grounded at both ends. (i.e. ground one end of the shielding in your cable to the plating of the DB25 connector, and ground the other end of the shielding in your cable to the 360's chassis)

I hope these tips help. (IMG:style_emoticons/default/happy.gif)

This post has been edited by FrostyTheSnowman: Aug 24 2009, 07:18 AM

[mafiafan123]

linux using xell now but still no audio

[Mhawk134]

QUOTE(mafiafan123 @ Aug 24 2009, 02:10 AM)

linux using xell now but still no audio

Ha that video is old, check this one out it's actually running linux now.



Hawk

[mafiafan123]

QUOTE(Mhawk134 @ Aug 24 2009, 12:59 AM)

Ha that video is old, check this one out it's actually running linux now.



Hawk

lol u posted the video i ment to

[HeenHill]

I got everything wired up, except for one wire: Pin 5 on J2B1 (Orange 5 on the rightmost jtag in the picture)

Where does it lead?

Edit: Is it meant to go to pin 17 on the parallel port?

This post has been edited by HeenHill: Aug 24 2009, 01:01 PM

[Martinchris23]

QUOTE(HeenHill @ Aug 24 2009, 12:59 PM)

I got everything wired up, except for one wire: Pin 5 on J2B1 (Orange 5 on the rightmost jtag in the picture)

Where does it lead?

Edit: Is it meant to go to pin 17 on the parallel port?

Yes, it goes to pin 17 on the parallel port. The numbering is what confused me at first (as it refers to the position on the header) - it might have been clearer to do a simpler system showing pin 1 on parallel port = pin 1 on 360 etc, since the technical numbering is supplied with the nandpro download.

What I would suggest is once you've dumped the NAND, to run Degrader v1.1 with the 1BL key (DD88AD0C9ED669E7B56794FB68563EFA) and check to ensure that no bad blocks are showing. If they are, re-dump and try again. I didn't get any errors when dumping one of my NANDs but I got bad blocks when opening it up . I've got the CPU key and the KV.bin tho - just got to work out a way to recover it

[HeenHill]

QUOTE(Martinchris23 @ Aug 24 2009, 08:33 AM)

Yes, it goes to pin 17 on the parallel port. The numbering is what confused me at first (as it refers to the position on the header) - it might have been clearer to do a simpler system showing pin 1 on parallel port = pin 1 on 360 etc, since the technical numbering is supplied with the nandpro download.

All right, thanks. The colors didn't look the same to me, but I guess it was just an optical illusion since the numbers are black on the JTAG and white on the parallel port. Not the best diagram, but certainly not the worst.

[maximilian0017]

QUOTE(FrostyTheSnowman @ Aug 24 2009, 07:16 AM)

2. If you have a really long cable (1 meter or more in length) then the 100 Ohm resistors will cause NandPro to not detect the NAND controller. If you are unable to detect the NAND controller and you are using a fairly long cable (1 meter or more in length) you NEED to remove the resistors, or else it will not work.

Please correct me when i'm wrong but if someone is using a 5volt lpt port and has problems with the wiring they could potentially blow up their xbox with this tip.

Just measured 14 meters of awg26 thin utp cable as a test and it had only 2,4 ohms per wire.....

Personaly i would not leave out the resistors, just replace the 100 ohms with a smaller value like 50/20/10 ohms when having trouble.( if they ask more than €0,15 per resistor they are expensive, so take home some more when you are making a cable)

You can easely check the resistor values here if you get them husseled up:  
Resistor color code calculator

Also a simple multimeter will cost almost nothing at the hardware store,  easy to have around
You can also check if you have a 3.3volt or a 5volt port by mesuring pin d0-7
Pinout LPT port
Please measure d0-7 because the other pins mostly have 5v for compatibility reasons

If you want to check if your port is stil working/debug your cable try the following:
1. Open C++ PortIO and select HEX under format( C++ PortIO is installed with the Port95nt.exe)
2. Adres is the adres of your parralel port (0x378 for lpt1 etc, check under the lpt1 properties of the windows device manager)
3. If you change "value", do-d7 will change to:
0x00  d0-d7 0v
0xFF  d0-d7 3,3v
0x55  d0=3,3v, d1=0v, d2=3,3v, etc
0xAA  d0=0v, d1=3,3v, d2=0v, etc

If you connect your cable(best without xbox connected or at least disconnected from 110/220v) and check the voltages at the end, it is easy to check for shorts etc if you use all of the above values.
You can easely make more values by setting windows calculator to scientific and to BIN, input something like 11110000 and clicking on HEX