Octal450

Hi, V3.2.1 r3: November Quality Update - Fixed: NAND-X/JR-P BB writing incorrectly - Fixed: Error finding file when creating Glitch XeLL - Fixed: JTAG XeLL not writing with PicoFlasher - Fixed: Corona BB writing issue Just a few bugfixes this time! The next version is not ready yet. Kind Regards, Josh

Hi, V3.2.1 r2: October Quality Update - Added: Ability to easily load XeLL images for donor use - Added: UI layout tweaks - Fixed: Several issues and desyncs with the CPU Key Database - Fixed: CB LDV might show an invalid number on encrypted CBs - Fixed: CB Pairing Data might show garbage when the data is invalid - Fixed: NAND-X/JR-P cancel loop issues - Fixed: Various bugs and usability issues - Changed: CB LDV and Pairing Data now blank when data is invalid - Changed: Cleanup the filesystem Kind Regards, Josh

Sorry, everything works for me. I haven't had any issues in over a year. it is likely an issue you with your PC, drivers, or possibly a one off bad xFlasher. Also, J-Runner with Extras September Update: V3.2.1: - Added: Improved and enhanced UI - Added: Ability to restore the filesystem to a clean state - Added: Auto select RGH3 if a RGH3 image is loaded - Added: Auto select XL USB or XL HDD if a nand with them is loaded - Added: Improved SMC Config Editor - Added: Easy restore defaults option for temperature targets - Added: CB LDV and Pairing Data information - Added: Detection if required folders are missing - Added: Xenon/Zephyr EXT_CLK Timings - Fixed: Many wrong CB LDVs in CB Fuse Table - Fixed: Possible ECC write bug - Fixed: Issues with Custom XeBuild option - Changed: Cleaned up some areas of the UI Kind Regards, Josh

As I said, it's not a JR issue. All I can do is catch the error more gracefully and display a more helpful/pleasant error box. Kind Regards, Josh

The firmware on there is incredibly buggy in my experience due to Windows issues or something. It's related to wiring or power sequence. It's not a JR issue. Kind Regards, Josh

My friend, it is auto-checked by J-Runner, see how he is checked That because it is only possible to build XDKbuild G2M 17489 images with the default files. Kind Regards, Josh

Hi, Please read here: xvistaman2005/XDKbuild: Sources used in making XDKbuild Patches and Tool (github.com) Kind Regards, Josh

Something is wrong with your pico, possibly the drivers. I will look at catching the error more gracefully. It's not an application side error. Kind Regards, Josh

ATTENTION: I have re-released the update with a critical fix for NAND-X/JR-P users. Apologies for the oversight - with such a complex update this slipped past me. This fixes reading/writing incorrect size issues. Any further problems - contact me immediately! Thank you. Kind Regards, Josh

But that’s not true. The peak temp had nothing to do with RROD and even Microsoft says so themselves. Anyone who says that is a pseudo engineer and does not understand how this works. The stock temps are perfectly safe. I will see if I can add a more pleasant message box for this. Kind Regards, Josh

Hi, It must be corrupt - as other images open up for me no problem. I will look into it more shortly. Btw - the default temp is PERFECTLY FINE AND SAFE. No need to adjust anything. Engineers are VERY SMART. Peak heat had nothing to do with the failures. Kind Regards, Josh

Hi, V3.2.0 is now available! This is a massive release with a huge number of enhancements, fixes, and a few new things. The biggest one for RGH installers will be optional auto-backup system for nands. V3.2.0 - Added: Improved and enhanced UI - Added: Auto folder/zip backup system (optional) - Added: Minor enhancements throughout the application - Added: CB combo box now pulls ALL CB versions from ini and sorts numerically - Added: Standalone ability to convert image to RGH3 - Added: Visual indicator for RGH3 nands - Added: Support for Corona BB - Added: More intelligent detection of nand type - Added: Improved folder scheme handling - Added: XL HDD support - Added: XL USB updated: Improved game compatibility - Fixed: Few RGH3 building issues - Fixed: CPU Key Database UI issues - Fixed: Kernel dropdown configuration bugs - Fixed: UI issues on high DPI monitors - Fixed: Buggy behavior with NAND-X/JR-P reading in certain modes - Fixed: Unnecessary delays during some operations - Fixed: Crashing issues on some systems when moving files after CPU Key entry - Fixed: Crash if entering CPU Key while reading/writing - Fixed: Invalid ability to load nand while the file is in use - Fixed: Some CBs had wrong reference LDV - Fixed: Out of sequence operation on nand initialization - Fixed: Progress bar stuck bug - Fixed: Various bugs and usability issues - Changed: Simplified some unneeded complexity - Changed: Don't revert hack type on CPU Key entry if the user changed it Kind Regards, Josh

Please send me the dump privately so I can check it. Kind Regards, Josh PS: I don't recommend you touch temps anyways. Leave them the way they are, everything is fine from the factory.

@BestNoob You must have some non vanilla folder. There is no default launch.ini in XeBuild folder! I suggest you delete it. Having no file means dashlaunch will use the defaults which is what we want. https://github.com/Octal450/J-Runner-with-Extras/releases/latest Please download again and you can see it. Kind Regards, Josh

Hello, thanks for the info. I will have you know that I never touched this settings - I'll check it. Also WB4G is never needed. The issues with winbond 4G consoles have long been correct. However the option exists still for legacy use. The main Winbond option is on the XeBuild tab. SPEAKING OF THE NEXT RELEASE As you probably noticed, the June/July releases were cancelled, this was because the changelist became very large, and we made major changes to the application to improve functionality, reliability, and fix bugs. The next major version is now in the testing phase and should be released soon. Thanks everyone! Kind Regards, Josh