Octal450

Hi, Glad to hear! New release is out. V3.2.2 r3: - Added: Reworked Advanced XeBuild Options panel - Added: Updated XL HDD and XL USB patches - Added: Improved UI for some dialogs - Fixed: Minor UI issues - Fixed: Broken tooltips in XeBuild panel - Fixed: Tab ordering in certain areas - Fixed: Various bugs and usability issues Kind Regards, Josh

My friend, your dumps are corrupted. Common Pico issue. Usually bad soldering or it failed halfway thru. Kind Regards, Josh

Hi, The retail thing is not there yet. Maybe I'll try it if I get a moment to test it. Kind Regards, Josh

OK, thanks for the update. Seems to make sense. Kind Regards, Josh

I'll look into this. Wouldn't be a JR bug, but possibly an issue with XeBuild or 17559. J

My pleasure, thank you for the kind words and support. Kind Regards, Josh

You're welcome. No, it would be entirely pointless. Just use Windows. Beside, XeBuild only work on Windows, as do most of the hardware drivers, and lastly the entire application is based around Win32 and C# WinForms. So a port would be a rewrite and I don't think there's ANY logical reason to do it. Kind Regards, Josh

Hi, January Quality Update: Mostly bugfixes. V3.2.2 r2: - Added: Ability to abort PicoFlasher read/write with Esc - Added: Catch more Pico side errors gracefully - Added: UsbdSec patch support - Fixed: Older dash packages failing to load - Fixed: PicoFlasher 4GB console message mistake - Fixed: PicoFlasher not interacting with read/write status - Fixed: Checkbox UI bug - Fixed: Other minor bugs and issues Kind Regards, Josh

Hi. Yes. ECC is a misnomer. HAPPY NEW YEAR! V3.2.2 is our end of year release! Changelog: V3.2.2: - Added: Improved and enhanced UI - Added: New updater UI - Added: Improved updater logic - Added: Significant internal optimization - Added: 4GB writing now shows MB progress - Added: Proper OpenXenium CPLD flashing for xFlasher - Fixed: Sequencing issues in certain operations - Fixed: PicoFlasher JTAG XeLL writing issue - Fixed: Various bugs and usability issues Kind Regards, Josh

@xicret12 Hi, Problem, is your antivirus seems to be sandboxing the application or preventing it from accessing the files. Or - you are using files that you do not have right access for - or you have the files open somewhere in another software. Please try to exclude from your antivirus or make sure the files are not open elsewhere. Kind Regards, Josh

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