xboxscene.org forums

Author Topic: Why Aren't We Using Buffered Jtags?  (Read 66 times)

Haruno

  • Archived User
  • Sr. Member
  • *
  • Posts: 270
Why Aren't We Using Buffered Jtags?
« on: February 07, 2010, 11:23:00 PM »

Maybe I'm misinterpreting and misreading everything but as far as I know, you're mentioning a superior method of the jtag hack which is simply the 3 wires you solder to certain parts of the motherboard.

Now what is the point of having it buffered at all when it gets the job done with 3 simple wires?

Unless of course you mean NAND dumping which doesn't involve jtag at all.
In which case, I still think this is pointless.
LPT is not as unreliable as you may think, and now we only need to dump the first 3 bytes of the nand, flash it with xellous and have the 360 take care of everything via ethernet.
Alternatively there's USB which works for many people as well.

Sorry if I'm just misunderstanding everything.
Logged

AllSewnUp

  • Archived User
  • Full Member
  • *
  • Posts: 114
Why Aren't We Using Buffered Jtags?
« Reply #1 on: February 08, 2010, 02:58:00 AM »

I think he is referring to basically a plug n play ready-made set up where you solder the usb or lpt input directing onto the motherboard without having the need for all the wiring for reading/writing the NAND.

I am sure xecuter is weeks away from dropping something like this with the solder spots already traced out and usb.


This really isn't too necessary since you can update XBR or Xell via usb stick and it is very easy to do.

But before that having an input like the cat5 would be useful.


You are right though the actual jtag wiring just 3 wires so I don't get why that would be a big deal.
Logged

UberDeev

  • Archived User
  • Newbie
  • *
  • Posts: 48
Why Aren't We Using Buffered Jtags?
« Reply #2 on: February 08, 2010, 12:34:00 PM »

Large block users can simply dump the first 2MB, flash Xellous, dump the entire nand through ethernet, and put together an original nand dump by writing the 2MB dump to the full dump.

I don't guess the need ever arose for anything like this. From what I've seen, most people don't have too many flash reliability issues.
Logged

Haruno

  • Archived User
  • Sr. Member
  • *
  • Posts: 270
Why Aren't We Using Buffered Jtags?
« Reply #3 on: February 08, 2010, 12:35:00 PM »

QUOTE(dokworm @ Feb 8 2010, 02:45 AM) View Post

For big-block users you are still dumping 70MB.


No you arent.

All you have to do is dump the first 3 bytes [the bootloader], replace it with xellous and everything else is done via 360 --> ethernet.

http://docs.google.c...mv5h_186pp2zddm
Logged

UberDeev

  • Archived User
  • Newbie
  • *
  • Posts: 48
Why Aren't We Using Buffered Jtags?
« Reply #4 on: February 08, 2010, 02:17:00 PM »

The first three bytes will give you the CB version, I believe, which is why many tutorials start out with that.
Logged

Haruno

  • Archived User
  • Sr. Member
  • *
  • Posts: 270
Why Aren't We Using Buffered Jtags?
« Reply #5 on: February 08, 2010, 07:46:00 PM »

In addition to that, the 70mb would be dumped NOT from lpt, and therefore not a big pain. As you said yourself, xellous takes care of it.

Logged

Badger101

  • Archived User
  • Newbie
  • *
  • Posts: 5
Why Aren't We Using Buffered Jtags?
« Reply #6 on: February 09, 2010, 06:12:00 AM »

QUOTE(AlexBoiler @ Feb 8 2010, 04:39 AM) View Post

Way before I enjoyed soldering all sorts of hacks into my 360, I was really into satellite hacking.  Though it eventually stopped being fun once it was easier to just use a PC to decrypt the stream than trying to hack a set-top box, for a while using the JTAG port on those boxes to read and write flash memory was the key to it.  

There were plenty of diagrams going around back then for simple JTAG readers using a few resistors hooked up to the parallel port, like the 360 scene is doing now.  We had the same problems a lot of users run in to getting reliable results.  It didn't take long for a simple buffered JTAG circuit to be distributed that could be cheaply built and that drastically improved flash reliability.

Any ideas why these aren't popular for the 360?  Surely there are other 360 tinkerers who remember the satellite scene of the early 2000s and all the JTAG problems we had at first.  Someone must've spoken up.  Or is the quick-and-dirty method, even with corrupted dumps, favored just because it's so damn cheap?


This is the one I use.

http://www.xboxhacke...p?topic=12257.0

It cuts down alot of errors, but allways dump a couple of times and compare.
Logged