Print

[Semiroundboss]

I have Nand-X (Updated to NandPro v3), Xecuter cool runner, Nand X to Cool Runner Jtag cable, and a install kit for my phat Falcon. Am I missing anything?

[kipper2k]

Some interesting finds when glitching Slim

 I was modding a Slim and decided to play around with wires etc. I tried both the TX coolrunner and my own board. Both boards performed pretty well the same and both needed the 50CM CPU_RST wire. One interesting thing i noticed was that the HDMI Cable had to be connected to the TV AND the TV needed to be on that input, sometimes i had to cycle through the inputs back to the HDMI input and that would cause it to glitch faster.

 When i was happy with it glitching (it was all over the place regarding boot up time, but it was glitching) i decided to box it up and i put the mobo back in the metal cage and then when i tested it again i was getting the constant fan reset sound every half second so something was wrong. After some more troubleshooting i decided to change my 50cm wire.  I swapped it out with a 50cm 30awg solid core wire and wound it into a 1.5" ring (i used a small can and then taped it to hold its shape).

  The wire itself is pretty thin and i applied some flux onto the CPU_RST pad on the motherboard, applied a little solder and then heated the pad and inserted the wire into the hole of the pad. I then taped the wire ring onto the motherboard and then retried the 360 which booted in less than 10 seconds. I then started putting it together bit by bit still retrying as i went and am happy to say that its all back together and boots 9 times out of 10 in less than 10 seconds. Normally the first time is about 7 seconds.

 So things that i noticed are;

 - CPU_RST wire not having a good connection. (Even though an ohmmeter tells you you have a connection).
 - Your TV has problems picking up the HDMI input from the 360 (which appears to be looking for a signal from TV)
 - If problems with HDMI, cycle through inputs back to HDMI once 360 turned on,or try using the component output to TV.
 - You do not need a stranded 50CM CPU_RST wire
 - A neat coiled CPU_RST wire works just fine. (use location shown in TX slim install guide)
 - All other wires can be as short as required
 
 Hope this is of some value to people.

[c14nz]

I edited kipper2k version of the slim pcb, now is a bit smaller and is only one side (top layer)



files: http://www.2shared.c...wslim_slim.html

kipper2k i hope it's ok

[kipper2k]

QUOTE(c14nz @ Jan 6 2012, 03:27 PM)

I edited kipper2k version of the slim pcb, now is a bit smaller and is only one side (top layer)



files: http://www.2shared.c...wslim_slim.html

kipper2k i hope it's ok

Thats fine, i posted the files so people could use, if it improves it, then even better .

 One thing worth mentioning, a duplicate pad could be added at the bottom (somewhere near pin 1 or 44 of the CPLD) so that when the board is laid in the 360 the wire from CPU_RST can go to the pad without the need to be routed to the furthest side of the board, its also handy for testing. (Also the Post_Out pad can be duplicated. (could be tough to do to maintain 1 sided board)

[deilzfcjk]

So here's a side by side comparison of the two slims i did this past 2 weeks. One has a Digilent Cmod clone(aka green pcb rev.A quijizhang007 ) and another is a Matrix Glitcher v1.

As you can see the Matrix Glitcher console on the left has the dvdrom on and squishing the wires down. It still boots. It is essentially in the state in will be in when the case is put back on.

The Digilent Cmod clone is assembled too, right now. I just didn't do it for this video. But it boots when the wires are squished and pushed down when the dvd rom is on too.

[Antman1]

QUOTE(kipper2k @ Jan 4 2012, 11:48 AM)

Some interesting finds when glitching Slim

 I was modding a Slim and decided to play around with wires etc. I tried both the TX coolrunner and my own board. Both boards performed pretty well the same and both needed the 50CM CPU_RST wire. One interesting thing i noticed was that the HDMI Cable had to be connected to the TV AND the TV needed to be on that input, sometimes i had to cycle through the inputs back to the HDMI input and that would cause it to glitch faster.

 When i was happy with it glitching (it was all over the place regarding boot up time, but it was glitching) i decided to box it up and i put the mobo back in the metal cage and then when i tested it again i was getting the constant fan reset sound every half second so something was wrong. After some more troubleshooting i decided to change my 50cm wire.  I swapped it out with a 50cm 30awg solid core wire and wound it into a 1.5" ring (i used a small can and then taped it to hold its shape).

  The wire itself is pretty thin and i applied some flux onto the CPU_RST pad on the motherboard, applied a little solder and then heated the pad and inserted the wire into the hole of the pad. I then taped the wire ring onto the motherboard and then retried the 360 which booted in less than 10 seconds. I then started putting it together bit by bit still retrying as i went and am happy to say that its all back together and boots 9 times out of 10 in less than 10 seconds. Normally the first time is about 7 seconds.

 So things that i noticed are;

 - CPU_RST wire not having a good connection. (Even though an ohmmeter tells you you have a connection).
 - Your TV has problems picking up the HDMI input from the 360 (which appears to be looking for a signal from TV)
 - If problems with HDMI, cycle through inputs back to HDMI once 360 turned on,or try using the component output to TV.
 - You do not need a stranded 50CM CPU_RST wire
 - A neat coiled CPU_RST wire works just fine. (use location shown in TX slim install guide)
 - All other wires can be as short as required
 
 Hope this is of some value to people.

I wanted to add a little bit of input on this.  I agree with Kippers analysis of the wiring and wanted to say my sweet spot for my wiring was on top of the board under the DVD Drive were the IntMemory unit goes.  I was able to boot 10 seconds or less.  Problem is that if you dual boot and leave the Glitch Board on all the times on either nand it will red light on the Stock Dash and boot the Glitch perfect everytime.  What I ended up doing was wrapping the "CPU_RST" wire around the CPU Heatsink and taping it off to look neat and the stock dash boots normally and fast and the Glitch dash takes 1 to 2 minutes and is sometimes fast but I dont care about speed of the Glitched Dash.  However if you want the speed if you do install the relay and let it turn the power off to the Glitch Board when you switch back to stock dash then Stock dash boots fine.

[steveo1978]

QUOTE(kipper2k @ Jan 4 2012, 12:48 PM)

 - Your TV has problems picking up the HDMI input from the 360 (which appears to be looking for a signal from TV)
 - If problems with HDMI, cycle through inputs back to HDMI once 360 turned on,or try using the component output to TV.

Yeah I have noticed the same thing on my Jasper.

If I do not switch over to the 360s HDMI input it takes a while for the 360 to glitch, but if I switch over to the 360s input then turn on the 360 it boots instant. I have also tested this by leaving it on a different input then turn on the 360 it will glitch as soon as I switch inputs.

[noraa]

Think what I am missing is this 1.8v line? Reading regulator was removed from the updated chips, was
thinking this was only used in programming, is this required for normal operation as well, pretty sure I misread
on this. Red line indication.

apologize to be super noob, thanks in advance for help!

[kipper2k]

QUOTE(noraa @ Jan 9 2012, 07:58 PM)

Think what I am missing is this 1.8v line? Reading regulator was removed from the updated chips, was
thinking this was only used in programming, is this required for normal operation as well, pretty sure I misread
on this. Red line indication.

apologize to be super noob, thanks in advance for help!

 Info sent to you, let me know if you need more help

QUOTE(dronecz @ Jan 8 2012, 10:25 PM)

Hello kipper2k,

I don´t know if I missed link for this board or you did not share it but could you post link for it  or schematic of it (of course in case that you want to share it   )?

Many thanks for anything.

 Here are the Eagle files for the powerboard.


Powerboard

[dronecz]

Hello,

I tryed make board from Kipper2k but I would like board which have all pins for the chip so I decide to try make my own board. Before I go more forward I would like to confirm (from those which know what they are doing) that my sheme is OK, so please look at picture at let me know if it´s ok.

Many thanks to all of you.

[hakunamatatapl]

Hello.

Its my first post, so heelo everyone. I build a chips, one from kipper2, one from technican3. They program well and working, but there is a problem. I have led on debug pin and its blink very fast, far from 0,5s. I try to check it witch my multimetr but i have nothing. I send pm to kipper and use com caps he suggest and still nothing. If You have some ideas, please share. Mass Effect 3 is near

[macrimichele]

QUOTE(c14nz @ Dec 26 2011, 07:13 PM)

i add a led for glitche signal and is made in eagle (it's based on Technitian3 design) pin 17 need a jumper to gnd

Amazing job!

Could you please link the 3-D component libraries you used?!

thank you Michele

[hiku82]

Hi, I'm new here.

Excuse me for my "newbie-ness".

I have bought an Xbox 360 slim in december. It turns out that it was manufactured in september.

I tried to have it "Glitched" but it had this new stuff in it which made it impossible for the guy to install Glitch hack.

Will there ever be a possibility that in the future it will be possible to hack it?  

Thanks in advance.

[c14nz]

eagle files brd+sch for my oprah S PCB

enjoy



macrimichele: all you need is here (eagle with sketchup plugin) http://eagleup.wordpress.com/

hiku82: HANA and SouthBridge have been put together into 1 chip on this new motherboard (no RGH for the moment for the new slim)

[hakunamatatapl]

Hello.

Have you test this chips ? I make 3 of them on jasper 512 and all of them gives me to short debug led blink and no boot.