MTX tools output to the console

[Gualdimar]

Hello. First of all, thank you for your great contribution to the console mods!
J-Runner is a cool tool that includes everything you need to perform RGH in one window, but I've encountered some inconveniences.
nandpro and xsvf run in a separate window that closes automatically when they are finished. This prevents you from seeing the result of the operation. I have redirected the output to the J-Runners`s console, similar to the xebuild output.

Also, a few observations that are not related to this PR:

1. xsvf.exe, which is included in the J-Runner package, has version 1.0a. And the archive from the original se7ensins thread has version 1.1f. I haven't tested 1.0a, but 1.1f flashes 64 and 128 chips without any problems.
2. firmwares for MTX nand flasher matrix_64a.HEX and matrix_128.hex are identical. Both flash 64 and 128 chips(tested with xsvf.exe 1.1f). No need to include them both.
3. there is a way to install libusb0 drivers without any problems with signatures on modern systems. There is a tool called zadig that signs and installs the driver for the selected VID/PID on the fly. Version 2.0.1.154 is the latest with libusb0 1.2,5.0. There is also a cmd tool called wdi-simple, which I think can be used by J-Runner.

Screenshots

[Octal450]

Hi my friend,
Thanks for this. Regrettably I must inform you that I cannot test until I am home in December.

Once I am home, I will test everything and if it all looks good, will merge into dev for the next release.

Kind Regards,
Josh

[Pheeeeenom]

This was initially how I implemented it, for reasons I don't remember...this caused issues that I couldn't fix which is why we did it the way we did. (I'm talking about the console output)

[halotroop2288]

until I am home in December.

January bump

[Octal450]

Pls don't do that. Am aware of the existence of this.

Am busy person and this is extremely low priority issue. I didn't get to it during home due to that I could not found my Matrix flasher... and without it, I cannot test. Nobody else that I work with for testing had the flasher available so, I was not able to test anything.

Once I have the ability to test sufficiently, then I can merge if everything ok.

But again - it's a low priority issue so pls have your patience, try to understand.

Kind Regards,
Josh

[halotroop2288]

👍🏻 I'm not invested in this issue, let alone impatient about it. There just hasn't been an update comment since October, so I just wanted to be sure you hadn't forgotten, given the time-frame you provided.

Thank you for the update. That's good enough. ❤️

[Octal450]

OK fair enough. Just pls maybe not write "bump", because it comes off very impatient.
I am always accept anyone to ask, hey, have you gotten to this yet?

Thx,
Josh

[Octal450]

@mitchellwaite Did you implement this by chance?

J

[mitchellwaite]

The tool changes that @EEJSS made in Mena's branch were specifically for the xflasher, the really old-school flasher code we didn't touch.

I know there's some issues doing output redirection if the output is particularly large, I've got another project I can check and verify what the solution was.

[mitchellwaite]

I've got another project I can check and verify what the solution was.

solution was basically this, actually. Unless I'm missing something though the AutoWaitHandle does nothing at all in this instance. @Gualdimar i'd suggest merging up to latest dev and remove outputWaitHandle (or add a comment re: what it does... there aren't nearly enough code comments in J-Runner)

FYI @Octal450

[Octal450]

Thanks.

[Octal450]

Closing for now. Reopen if anything here still.
J

[Gualdimar]

Wow, it’s been a while!
Referring back to my original description, I implemented this change based on the logic in xebuild.cs, which executes a console application while redirecting its output to the J-Runner console. I don’t recall the specific details of every line, but since the current version of mtx-usb.cs still contains the same code, this PR remains valid.
Unfortunately, I don't have a Matrix flasher or an Xbox to test it anymore.

[Octal450]

I feel like there was a reason I did it this way but it's been so long that I can't recall.

Right, I'll get a MTX USB tested at some point and go from there.

I'll reopen this then for now since it's still valid.

Thank you for looping back @Gualdimar

Sorry everything took forever, I was on hiatus from Xbox stuff from late 2023-late 2025.