octal450 / j-runner-with-extras Goto Github PK

trying to RGH a Trinity with a aceV3 i am able to do everything tell i get to the point i have to create the XeBuild. it crashes no mater what i do and in compatibily mode
Error.log

Is your feature request related to a problem or missing feature? Please describe.
There are no native Linux or MacOSX builds of J-Runner w/ Extras

Describe the solution you'd like
J-Runner w/ Extras builds using the Mono .net implementation.

Describe the bug
Loading a BB ECC and clicking Reload causes a bad block to be detected at 0x1

To Reproduce
Create any BB ECC and click Reload

Expected behavior
Nothing should be reported bad

System (please complete the following information):

• OS: Any
• Version: V3.3.0 r3 + next

Additional context
Began due to initialization of ECC being allowed in V3.3.0(?)

Describe the bug
UI crashes when trying to create XeBuild with selected drives patches and "other patches".

If skipping drive patches and other patches build works as expected.

To Reproduce
Steps to reproduce the behaviour:

1. Load source file (nand.bin)
2. Select kernel 17559, Glitch2, RGH3 25mhz
3. Go to tab "Patches" and select "Both XL", "UsbdSec" and "Key fix"
4. UI takes a second then force closes

Expected behaviour
A build is done?

Screenshots

System (please complete the following information):

• OS: Windows
• Version: 11 Pro

Additional context
Error.log;

System.IO.IOException: Det går inte att skapa en fil som redan finns.
vid System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
vid System.IO.__Error.WinIOError()
vid System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
vid JRunner.Classes.xebuild.copyXLBoth()
vid JRunner.Classes.xebuild.createxebuild(Boolean custom)
vid JRunner.Panels.XeBuildPanel.createxebuild_v2(Boolean custom, PrivateN nand, Boolean fullDataClean)
vid JRunner.MainForm.b__186_0()
vid System.Threading.ThreadHelper.ThreadStart_Context(Object state)
vid System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
vid System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
vid System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
vid System.Threading.ThreadHelper.ThreadStart()

Describe the bug
Hello Octal450
Thank you for amazing job with J-runner with extras. But I found a bug with Big block 512mb jasper.
Everything works until you try to write BB (64mb) nand. Instead of 15 min write time it will finish in 3 min (like 16mb nands do).
When you write this nand with older j-runner version, it will write full BB 64mb nand and console works.

This problem occurs with XeBuild image and stock nand too. I didn't try any other BB nands or 48mb(corona 4gb) nands yet.
I found it immediately as I saw write time. But there are a lot of other not so experienced people out there, that won't notice something is wrong. I hope you can fix that in latest update.

If you need some additional info or nand dump, feel free to contact me.
Have a nice day.

Nightmare0

On Corona RGH images, certain keys related functions don't work properly (notably XeKeysSetKey for title keys, meaning games that use it for decryption don't work, e.g. Rock Band games suffer from the "no preview audio"/"endless loading" bug). I made a patch for this, and it would be useful to have an XeBuild option in the GUI, or to enable by default when building Corona freeboot 17559 images.

The patch in hex format:

00003B8C 00000001 389F0010
0000611C 00000001 387C0010

This bug is caused by, somewhere and somehow, the 1BL key copy at 0x16510 (17559) being blanked out on Corona. I've mitigated this issue by patching HvxKeysSetKey (for title keys) and HvxKeysExecute to instead direct those reads to the first 1BL key copy at 0x163F0 (17559). I haven't been able to extensively test this on actual Corona hardware, so that is definitely something that needs doing before implementing. (I have since had a friend test on Corona and can confirm the Rock Band issue is fixed.) There could also be other places the bad copy is used, but it looks like they're in firmware update routines so aren't needed.

I'd have submitted a pull request, but I can't seem to get J-Runner to want to build, and I'm not sure whether it would be best to have this as an option that has to be enabled, or to enable it by default when building Corona images.

DVD-ROM DG-16D5S not reading Xbox games after creating XeBuild and flashing.
Problem in version 3.2.1, in 3.2.0 works properly.
Checked DG-16D4S it works in both versions.

Checked on:

• OS: RGH 3.0 Trinity 16MB/Corona 4GB
• Version DVD-ROM: DG-16D5S

Describe the bug
xFlasher: Checking Console...
Unable to load DLL 'common\xflasher\xFlasher.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

doesn't appear to be an issue with jrunner.

To Reproduce

Expected behaviour
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS: windows
• Version: 10

Additional context
Add any other context about the problem here.

First i should admit am expert in rhg3 i have done phats, slim S and slim E am familia with alot of mother boards and their ram chips around gpu.

Common ram chips are samsung and some with NNNN kind few are winbound, now i came across a new ram(sorry i got new phone so the photo of it is gone with old 4n but the dump is in pc i will send for review) it was on trinity mother board, when i wrote xell to this console it didnt boot to xell, i tried bothe 10k and 3k resistor but nothing, its what triggered me to check what is new with this console compared to others its when i saw that the ram chip is of different kind. Am like mayb these needs a new tab as it is with winbound chips to be successfull and boot to xell.

I will add link to my drive below since we cant send dumpfiles here, i doh know if the dump alone will be enough otherwise i sent back the console to the owner, if its a must i can try to ask it back tho its miles away, but yah mayb from the dump you will be able to get the info of the ram chip and make it work with rhg3 as it is with winbound chips in your next release thanks

https://drive.google.com/file/d/14L7fg9WLOX47tMyyS-Dn7PB_-RLaU_Sb/view?usp=drivesdk

i have my xflasher connected and on jrunner it doesn't even show and i just got my xflasher today and i downloaded the drivers and still nothing and i also have even tried 3 different pcs
please help!

if someone can help me ill really be grateful

Describe the bug
Upon loading J runner 3.3.0 r3 the software hangs at the "checking for updates" splash screen for two minutes every times it launched
Program is run as administrator, problem started with the last update

To Reproduce
Steps to reproduce the behaviour:
Launch the program

Expected behaviour
To not hang for so long

System (please complete the following information):

• OS: windows 10 Pro - Test mode
• Version: 10586

Describe the bug
The pop -up content is not fully displayed

To Reproduce
Steps to reproduce the behaviour:

1. Click on Create Donor
2. You will get the content that is lost or blocked
3. Click on Next
4. You will get the content that is lost or blocked

Expected behaviour
I need to see options and descriptions to operate.

Screenshots

System (please complete the following information):

• OS: windows10 and windows11
• Version: 3.2.0 and 3.2.1

Additional context
I have a general version of NAND (RGH2), because there is no CPUKEY in NAND, I need to synthesize a RGH3，I used the mirror created by the default Create Donor, so that the Xbox360 cannot be started.

Hi Josh,

Thank you for your improved J-runner. I've been using this tool always.

For some reason, when booting into Xell-reloaded for the 1st time after writing ecc into NAND, my monitor just shows a blank screen.
(Finally the Xell-reloaded is the culprit, I'm quite sure of that.)

So every time I boot xbox360 I use "Scan IP Range" to get CPU key.

Though cpu key can be fetched eventually, but the target IP address J-runner scanned is nowhere to know.

Can you please let J-runner shows target IP address in console when finished scanning?

Hello Josh

Like last time with Jasper BB, I think there is another write issue with Trinity.

This week I was doing two trinity upgrade from RGH2-->RGH3
First one was quick and easy, because I dumped NAND in console with Simple nand flasher, created new RGH3 XeBuild image and wrote back with simple nand flasher. After that I reworked installation and everything worked.

With second Trinity I forgot to write new XeBuild image and desoldered old CR3. Never mind... I made RGH3 conversion, wrote new XeBuild with JR-P v2 and... nothing. Console turns off one second after power on. After few hours of resoldering, I tried to install CR3 back. Didn't work. No green light. cpu_rst was working and reseting, post_out was working (even tried postfix adapter). Both checked with multimeter.
Tried CR4 XL and Ace v3 as well. No green light, could't get console to boot.
With each modchip I tried XeBuild and .ecc with no success.

After all this shit I tried to build Trinity RGH3 .ecc in your latest build (V3.2.1 r3) and wrote it with older J-runner version.
Started up, console didn't turned off this time, installed RGH3 and got Xell
Created XeBuild from first nand dump and console is working.

Sorry for wall of text. But I wanted to describe you why I assume there is something wrong with Trinity writing with JR-P v2

Now I have two more stock Trinity boards, not conversions. So I will do two new installs.

If there is any way I can help you to find this bug, tell me how.

David

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behaviour
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS:
• Version:

Additional context
Add any other context about the problem here.

i try launching it in windows xp and 7 and 8 mode didnt launch
i see it in task manager open and close

Describe the bug
I believe the Xenon XeLL generated image is incorrectly generated or written incorrectly by PicoFlasher

To Reproduce
Steps to reproduce the behaviour:

1. Read Nand
2. Create XeLL
3. Write XeLL
4. Doesn't boot.
5. If I read back the NAND from this point in J-Runner and overwrite the first section (0x14A000) with the contents of xenon.bin directly in a HEX editor and write this NAND, then it will boot XeLL. There were differences in the NAND's after I did this so it wasn't writing a clean xenon.bin, I suspect something is going wrong here?

I posted on Reddit about it because others were also having the same issue: https://www.reddit.com/r/360hacks/comments/1al3b2t/comment/kv52y66/?utm_source=share&utm_medium=web2x&context=3

When I try to read some nand the program freezes and the following comes out.

Windows 10 updated

Consulte el final de este mensaje para obtener más detalles sobre cómo invocar a la depuración
Just-In-Time (JIT) en lugar de a este cuadro de diálogo.

************** Texto de la excepción **************
System.TimeoutException: Se excedió el tiempo de espera de la operación.
en System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout)
en System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count)
en System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count)
en JRunner.PicoFlasher.RecvUInt32(SerialPort serial)
en JRunner.PicoFlasher.getFlashConfig()
en JRunner.MainForm.xPanel_getmb()
en JRunner.Panels.XeBuildPanel.btnGetMB_Click(Object sender, EventArgs e)
en System.Windows.Forms.Control.OnClick(EventArgs e)
en System.Windows.Forms.Button.OnClick(EventArgs e)
en System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
en System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.ButtonBase.WndProc(Message& m)
en System.Windows.Forms.Button.WndProc(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Ensamblados cargados **************
mscorlib
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4470.0 built by: NET48REL1LAST_C
Código base: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

JRunner
Versión del ensamblado: 3.1.2.0
Versión Win32: 3.1.2.0
Código base: file:///D:/Program%20Files%20(x86)/Xbox%20360/J-Runner%20with%20Extras/JRunner.exe

System.Windows.Forms
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4488.0 built by: NET48REL1LAST_C
Código base: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4488.0 built by: NET48REL1LAST_C
Código base: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Versión del ensamblado: 4.0.0.0
Versión Win32: 4.8.4390.0 built by: NET48REL1LAST_C
Código base: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Xml

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behaviour
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS:
• Version:

Additional context
Add any other context about the problem here.

Describe the bug
If i try to manually load my nanddump.bin (Console type: Trinity) J-Runner seems to randomly crash.

Sometimes it works, sometimes not.

If i select the console type and glitch before loading the nanddump.bin there is a higher success rate, but it can still crash.

To Reproduce
Steps to reproduce the behaviour:

1. Click load source
2. Select nanddump.bin and open it.

Expected behaviour
Sometimes when i open nanddump.bin it do select console type and glitch by itself (that is the expected behaviour), but most of the times it crash instead.

System (please complete the following information):

• OS: Windows 10 x64 22H2
• Version: J-Runner 3.3.0 r2 (I don't know if you want my Windows version or J-Runner version here 🤔 )

Additional context
Here are two crash logs. They don't look the same, so i have included them both.

Is your feature request related to a problem or missing feature? Please describe.
The Tigard is an FTDI-based hardware multitool. J-Runner detects this as a X-Flasher in SPI mode, and with the correct wiring this board can be used to read/write the 360 nand just like the original X-Flasher. It would be useful for some who already have such hardware to know how to use it to flash their 360.

Describe the solution you'd like
Document somewhere the possibility and method of using a tigard to flash (possibly just linking here).

Additional context

1. Plugging in the Tigard should cause J-Runner to recognize an X-Flasher in SPI mode.
2. Ensure the Tigard is set to V3.3 mode and SPI/JTAG mode rather than SWD/I2C mode.
3. Connect the SPI breakout cable to the 1x8 pins (NOT the 2x4 specifically-designated SPI pins, as these use the second 'B' interface of the tigard)
4. Connect the GND, SCK, CS, CIPO, and COPI leads to their labeled wires.
5. Connect the SMC_DBG_EN (J2C3 Pad 6) to the wire labeled SRST, and SMC_RST_XDK_N (J2C3 Pad 5) to the wire labeled TRST (guessed, this worked first try).
6. Use J-Runner as if using a normal X-Flasher.

Pic of my awful setup:

I don't have any eMMC/4G boards to test the other mode on.

Describe the bug
After building a XE nand file selecting XL HDD for a JTAG unit the Internal hard drives no longer load after the nand update. Getting a black screen or XBOX360 lock up on boot screen with no error messages. This issue happened after Jrunner updated to latest version with updated XL HDD patches. Tried using non XL HDD and reflashed and my other internal hard drive worked fine. Tried a 4TB and 8TB SSD drives and reformatted with XL HDD on FatXplorer tool and tried again with the XL HDD patch nand with same results on current version of JRunner.

Expected behaviour
XL HDD patch should boot hard drives over 2TB after being formatted with FatXplorer tool

System (please complete the following information):

• OS: Windows 11
• Version: V3.3.0 r2

Additional context
I can confirm i used another JTAG xbox 360 console with XL HDD patches does not work from Jrunner version: V3.3.0 r2

Describe the bug
Across 5 different 360s that I have performed RGH on over the past year or so (some 1.2, some 3.0), I'm seeing the same visual text glitching on the main menu after flashing XeBuild images (kernel 17559) created from NAND dumps from the console. When scrolling through the menu items, letters in the settings listing will be swapped with different characters for a few frames, returning back to the correct characters after. Creating a donor NAND with the extracted keyvault and SMC config, then flashing through xell, causes this issue to go away. XeBuild images created from dumped NAND also show this issue when flashed through xell. Multiple dumps of each NAND have been taken, and compared, and are identical. This occurs across multiple displays at all available resolutions.

To Reproduce
Steps to reproduce the behavior:

1. Dump console NAND (picoflasher was used for all NAND dumps)
2. Flash xell + get CPU key
3. Generate XeBuild image from NAND dump
4. Flash using NAND flasher or from xell
5. Go to 'Console Settings' on dashboard, scroll up and down through settings
6. Characters will 'swap' with other characters

Expected behaviour
Scrolling through console settings should not exhibit text glitches.

System (please complete the following information):

• Console/RGH Revisions: Jasper (Kronos) RGH3, Jasper (Kronos) RGH 1.2, Falcon (RGH 1.2) Corona (4GB) RGH3

Additional context
As far as I can tell, no core functionality is altered, but would like to report this in case some corruption of the NAND may lead to other issues down the line. Potentially an issue with dumping via picoflasher, but I doubt it is an issue with the systems since it seems to be so easily reproducible across different units.

Describe the bug
Both the J-Runner and the standalone convert to RGH3 application crash on 32 bit windows, I think targeting
the .net components to x86 will solve this issue. I use a Lenovo 100s laptop at my workbench because of it's
small size but it is only supported by Window 10 32 bit because of a weird 32 bit only EFI.

I have confirmed this bug to exist on 32 bit Windows 7 also, both applications work as expected on 64 bit
Windows 7 and 10.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
crash.txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The specified executable is not a valid application for this OS platform.
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at RGH2_to_3_GUI.RGH2to3.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

RGH2 to 3 GUI
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Adam/Desktop/RGH2To3/RGH2%20to%203%20GUI.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

plese exe support for old versions please

I have always ran my Jrunner on an old Vista computer but with the latest update the program just stops working. I do love my old Vista laptop, is there some way to make it compatible? Thanks for everything 360 these last years, it has been a blast!

Describe the bug
i'm updating an old modification - slim corona and fats

dumped the nand with Simple 360 NAND Flasher ,
imported the dump on jrunner and it will not make a new xebuild image it says "Converting Image to RGH3...
Failed: The image is either already RGH3, or an unsupported image type"

To Reproduce
Steps to reproduce the behaviour:

1. dump nand (lower dash)
2. ftp over output folder (flashdmp and cpukey)
3. import on jrunner , click rgh3 see error
   KV type : type2 (hashed - unchecked, master key not available)

xeBuild Finished. Have a nice day.

Converting Image to RGH3...
Failed: The image is either already RGH3, or an unsupported image type

Expected behaviour
it converts like normal
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS: win10
• Version: 21h2/1904.2251

Additional context
Add any other context about the problem here.
i convert the image from the original script and it works just fine.

Describe the bug
I am trying to create an xebuild image of dashboard 6717 on a corona RGH3.

I dumped the nand with the xell reloaded web interface, then loaded it into jrunner but whenever I try to create a 6717 xebuild image it errors.

To Reproduce
Steps to reproduce the behaviour:

1. download nand using the xell web interface (eg: 192.168.???.??)
2. load in jrunner
3. change xebuild Kernel Version to 6717
4. click Create XeBuild
5. error in output

The specified console bootloader list (coronabl) is missing from the ini (D:\J-Runner-with-Extras\xeBuild\6717\_glitch2.ini)

OS: win10
Version: 21h2

Additional context
9199 works fine.

Hi there,

I installed 2 different pico on my trinity and each time I get the message "Console not found"

Can you please let me know if it is a known issue?

I checked also my solder pins 2 times

Regards,
Jeff

jasper works 100% read and write
falcon get a error saying PicoFlasher firmware is too old so cant read it .

Describe the bug

If selecting "Both XL" under "Drive patches" and options "UsbdSec" and "Key Fix" under "Other patches" then trying to Create XeBuild the "Other patches" are deselected, but only if "Both XL" has been selected.

This behavior makes it uncertain if other patches has been applied or not.

To Reproduce

1. Load source
2. Select "Both XL" and both patches under "Other patches"
3. Create XeBuild
4. Click OK on prompt asking about "Both XL"
5. Other patches has been deselected according to console

Expected Behavior

Other patches should not be automatically deselected after build if "Both XL" has been applied.

Screenshots

Before creating XeBuild:

After creation:

System version

Windows 11

J-Runner version

3.3.0 r3

Additional context

Console log
Initializing updflash-17599.bin, please wait...
Glitch2 selected
RGH3 selected
Nand Initialization Finished
Both XL selected
UsbdSec selected
Corona Key Fix selected
XeBuild Initialized
Kernel Selected: 17559
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.21.810
---------------------------------------------------------------
base path changed to C:\Users\Rob\Downloads\J-Runner-with-Extras_2\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Rob\Downloads\J-Runner-with-Extras_2\#\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17559.0
Console   : Corona
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : #
ConsoleId : #
MoboSerial: #
Mfg Date  : 11/21/2013
CPU Key   : #
1BL Key   : #
DVD Key   : #
CF LDV    : 3
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Converting Image to RGH3...
RGH3 Conversion Finished!
Saved to C:\Users\Rob\Downloads\J-Runner-with-Extras_2\#
Image is Ready
Initializing updflash.bin, please wait...
Nand includes Both XL patches
UsbdSec deselected
Corona Key Fix deselected
Nand Initialization Finished

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

1. 'patch the nand using jranner and flash it with 360 simple nand flasher'
2. 'press the eject button with the ethernet cable plugged in'
3. 'xell freezes on the dhcp part'

Expected behaviour
xell should work

Screenshots

Additional context
this is an RGH3 corona 4GB system, xell works if the ethernet cable remains unplugged.

Describe the bug
After creating a ECC, which gets loaded into source, and after writting ECC and getting CPU key, source does not auto default back to nanddump.

To Reproduce
Steps to reproduce the behaviour:

1. Create ECC
2. Write ECC
3. Enter CPU key into jrunner
4. Nanddump is not loaded into source but instead the ecc file is still loaded into source.

Expected behaviour
Nanddump should be auto loaded back into source after getting cpu key from xell

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS: windows 10
• Version: latest at the time of writing.

Additional context
Add any other context about the problem here.

Describe the bug
Mismatched nanddump1.bin and nanddump2.bin on Corona16MB with PicoFlasher ver v3.0

To Reproduce
Steps to reproduce the behaviour:

1. Click on "?" ->
   Checking Console...
   0x00043000
   Corona 16MB
2. Click on "Read Nand"
   Reading Nand to C:\Users\xxx\Downloads\XBox360\J-Runner with Extras\output\nanddump1.bin
   Read Successful!

Initializing nanddump1.bin, please wait...
Nand Initialization Finished

Reading Nand to C:\Users\xxx\Downloads\XBox360\J-Runner with Extras\output\nanddump2.bin
Read Successful!

[Mismatched]
Comparing...
0x0064
0x01C2
0x027C

Expected behaviour
nanddump1 and nanddump2 should match???

Screenshots
https://i.imgur.com/Knr11TP.png

System (please complete the following information):

• OS: Windows 10
• Version:

Additional context

Describe the bug

Log:
Checking Console...
Corona: 4GB (eMMC connected)
PicoFlasher has encountered an error
Try to unplug and replug the device
System.TimeoutException

To Reproduce

No response

Expected Behavior

Any solution?

Screenshots

No response

System version

Windows 10

J-Runner version

Last Version

Additional context

No response

Describe the bug
Im using the TX demon, it allows me to have dual nand and read/write to them via usb.

To Reproduce
Steps to reproduce the behavior:
I click Read Nand. it gives me Device Not found

Expected behavior
I should be able to read my nand using the tx demon, i tried with an old version of jrunner that is working fine.

Screenshots

System (please complete the following information):

• OS: win10
• Version: 21H2

Additional context
none

Describe the bug
Every time i try to build an XDK nand XeLL gets skipped. it says "WARNING: skipping xell, there doesn't appear to be enough room!", i've tried with the dump of my nand before i made any modifications and with a dump of the nand i made after making a retail 17559 xebuild. Is this intended or a bug? it makes switching from xdk to retail more annoying and no way to recover from a softbrick without hardware flashing it.

To Reproduce
Steps to reproduce the behaviour:

1. Load any nand dump as source
2. Choose kernel version 17489 on options
3. Click create xebuild
4. The warning appears just after it start to build

Expected behaviour
No warning and xell working on the kay combination at boot like it does on 17559

Screenshots
not needed imo

System (please complete the following information):

• OS: Windows 11 22621.963
• Version: Jrunner 3.2.2

Additional context
A bit off topic but ive found a related bug to this: i cannot change region of the development environment, every time i try it reboots and it stays on europe, i even tried manually changing it on xebuild before creating it and nothing, its not really important tho.

Describe the bug
Kernel versions are not properly sorted. They follow the string sorting instead of integer sorting. This would keep the newer dash versions on the bottom of the list

Expected behaviour
A properly sorted list would be 6717, 7371, 9199, 17489, 17559

Screenshots

Describe the bug

Tried downgrading to kinect dashboard but cannot boot anything except xell.

To Reproduce

1. Have a Xbox 360 Slim Trinity (Mine is a trinity and have found some reddit threads with the same error and they had trinitys)
2. Open JRunner
3. Create XeBuild with Dash 13604
4. Run Xell from Eject
5. Flash new Nand
6. Black screen from reboot

Expected Behavior

Fully Functioning Kinect Dash with RGH3

Screenshots

No response

System version

Windows n10

J-Runner version

3.3.0

Additional context

No response

Describe the bug

I can read NAND, create XeLL, but writing XeLL fails every time.

To Reproduce

1. Solder up RGH 3 and Raspberry Pi Pico as described for Trinity motherboards as described in this guide
2. Install PicoFlasher 3.0 on the pico (or 2.0, neither work)
3. ? button identifies console Flash Config: 0x00023010 Jasper, Trinity: 16MB
4. Read NAND 2x, succeeds, comparison succeeds, selects glitch and RGH values
5. Create XeLL, succeeds immediately
6. Write XeLL

Expected Behavior

XeLL is written and I can proceed.

Screenshots

J-Runner with Extras
Session: 07/28/2024 20:04:06
Version: 3.3.0 r3
Status: Up to date

WARNING - Working Folder!
Your working folder is not empty, click Show Working Folder to view its contents

Initializing nanddump1.bin, please wait...
Glitch2 selected
RGH3 selected
Nand Initialization Finished

XeLL image created

Checking Console...
Flash Config: 0x00023010

Writing glitch.ecc to Nand
PicoFlasher has encountered an error
Try to unplug and replug the device
System.IO.IOException

System version

Windows 10 Home

J-Runner version

3.3.0 r3

Additional context

No response

Is your feature request related to a problem or missing feature? Please describe.

I believe it could be possible to replace xbkrnl.exe and xam.xex of older dashboards with a 17559 hacked kernel version and allow it to boot newer games while using older dashboards and launching games via xex menu at least if not regularly naturally replacing the kernel should also replace the hypervisor.. so with updated kernel + hypervisor + xam it should work right? can you confirm this I haven't tried it yet myself but I have a triple nand with external nand wires to test

Describe the solution you'd like

.

Additional context

No response