Octal450 91 Posted August 8, 2022 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 1 Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 8, 2022 @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 2 Quote Share this post Link to post Share on other sites
robbayani 0 Posted August 9, 2022 i get error warning when editing SMC on Corona v1/v2 4GB .. another my Slim S (Trinity) & Slim E(Corona v6) works well when edit SMC.. choose "Continue" takes me SMC editor, press "Save Config" but can't saving.. im just want change temperature.. Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 9, 2022 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. 1 Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 10, 2022 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 1 Quote Share this post Link to post Share on other sites
robbayani 0 Posted August 10, 2022 18 hours ago, Octal450 said: 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. i think default Temp is too hot, i'm not comfort.. im just down temperature little bit.. nanddump1.bin nanddump2.bin Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 10, 2022 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 Quote Share this post Link to post Share on other sites
robbayani 0 Posted August 11, 2022 20 hours ago, Octal450 said: 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 hahaa.. U are true.. both is corrupt NAND.. i'm just take 2 "best" Nand, because very dificult succesfully read Nand sequentially.. many times failed read Nand until 100%.. but this corrupt Nand succesfully to RGH3, and my console running well.. then succes tuning Temperature via Dashlaunch, all Target Temp 70 Celcius.. im still down Target Temp, because many times i read CpU/GPU too heat causing most RROD.. i know longetivity my Fan became short, because its work more extra.. Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 11, 2022 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 Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 12, 2022 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 Quote Share this post Link to post Share on other sites
fasttracker 1 Posted August 22, 2022 Every time I read, I get this error. I changed my computer, reinstalled the framework and vishual c. Changed the cable, tried 2 different pico boards. It did not help. System.TimeoutException: Время ожидания операции истекло. в System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) в System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) в System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) в JRunner.PicoFlasher.RecvUInt32(SerialPort serial) в JRunner.PicoFlasher.OpenSerial() в JRunner.PicoFlasher.Read(Int32 iterations, UInt32 start, UInt32 end) в JRunner.MainForm.btnReadClick() в JRunner.Panels.NandTools.btnRead_Click(Object sender, EventArgs e) в System.Windows.Forms.Control.OnClick(EventArgs e) в System.Windows.Forms.Button.OnClick(EventArgs e) в System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) в System.Windows.Forms.Control.WndProc(Message& m) в System.Windows.Forms.ButtonBase.WndProc(Message& m) в System.Windows.Forms.Button.WndProc(Message& m) в System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) в System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 22, 2022 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 Quote Share this post Link to post Share on other sites
fasttracker 1 Posted August 22, 2022 2 minutes ago, Octal450 said: 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 Thanks a lot. I will keep looking for a solution 1 Quote Share this post Link to post Share on other sites
felida 1651 Posted August 23, 2022 23 hours ago, Octal450 said: 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 Hey Josh, I shot you a PM about some info I had questions about the program. Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 23, 2022 Hi, Please read here: xvistaman2005/XDKbuild: Sources used in making XDKbuild Patches and Tool (github.com) Kind Regards, Josh Quote Share this post Link to post Share on other sites
felida 1651 Posted August 24, 2022 9 hours ago, Octal450 said: Hi, Please read here: xvistaman2005/XDKbuild: Sources used in making XDKbuild Patches and Tool (github.com) Kind Regards, Josh the XDKbuild option is grey'd out mate.. can not select that particular option Quote Share this post Link to post Share on other sites
Octal450 91 Posted August 24, 2022 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 Quote Share this post Link to post Share on other sites
felida 1651 Posted August 24, 2022 13 hours ago, Octal450 said: 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 that, sort of makes sense lol.. i guess no one would want to make a regular 17489 dash at this point without the dev portion lol.. i thought there was an option that needed to be done to enable the dev build option. my apologies on the misunderstanding, but that is why i asked lol Quote Share this post Link to post Share on other sites
AcidzModShop 0 Posted September 14, 2022 Picoflasher not working for 4GB Coronas System time out errors. Same as @fasttracker had posted. Tried 2 motherboards, reflashed pico, used 2 PC's, new wires from pico to xbox. Same result. Pico is working as it was used on a trinity a couple of days prior to using it for a corona, Has worked on a corona previously. Not sure to why this is happening. Any ideas? Quote Share this post Link to post Share on other sites
Octal450 91 Posted September 14, 2022 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 Quote Share this post Link to post Share on other sites
AcidzModShop 0 Posted September 14, 2022 I dont think its a wiring or power sequence issue, As its the same result on two consoles and it did work flawlessly on a trinity a couple days before. I'll try with a Win7 VM and see, was the only thing i didnt test. Quote Share this post Link to post Share on other sites
AcidzModShop 0 Posted September 14, 2022 See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at JRunner.PicoFlasher.OpenSerial() at JRunner.PicoFlasher.getFlashConfig() at JRunner.MainForm.xPanel_getmb() at JRunner.Panels.XeBuildPanel.btnGetMB_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.7.3221.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- JRunner Assembly Version: 3.2.0.0 Win32 Version: 3.2.0.0 CodeBase: file:///C:/Users/Acidz/Downloads/J-Runner-with-Extras/JRunner.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C 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.7.3221.0 built by: NET472REL1LAST_C 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.7.3221.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Configuration Quote Share this post Link to post Share on other sites
Octal450 91 Posted September 14, 2022 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 Quote Share this post Link to post Share on other sites
Bazatree 3 Posted September 18, 2022 On 11/27/2021 at 11:47 PM, Bazatree said: I am not sure if it is related to J-runner, drivers or X-Flasher, but I will write here. So the problem is, my X-Flasher doesn't really work that good in eMMC mode. In this mode it constantly looses the connection with the console and crashes J-runner. Sometimes I manage to dump 2MBs of NAND, sometimes 4, sometimes 40, but very rarely it allows me to dump/write the full NAND. Reveal hidden contents Crashed at 40MBs Freezed at 2MBs I noticed that X-Flasher usually looses the connection (USB Drive becomes Removable Disk) as soon as or very shortly after I click on write or read the NAND. Sometimes the console boots by itself while X-Flasher is dumping or writing the NAND and fans are spinning in a jet mode. J-Runner constantly crashes or writes hardware malfunction while dumping/writing in eMMC mode. It took me about two hours to dump and write the NAND. SPI mode works like a champ. X-Flasher - RevB. J-Runner - 3.0.3b Has anyone had this problem before? I kinda hate this eMMC mode on my xFlasher. As promised, here are my steps and wiring. I soldered xFlasher to Corona 4 GB like this: My steps are. Everything is unplugged. I connect xFlasher. I ground the crystal. Next step is I plug in the power to the console. Next step is, I plug in USB to xFlasher. And now the magic begins. -Sometimes J-Runner does see the xFlasher, but shows no info about the memory apart from "Drive name". Sometimes it says "Failed to get DiskGeometry" -Sometimes J-Runner does see the xFlasher and shows full info about the memory. -However there is a huge chance that it will stop dumping the nand. -Sometimes it unstucks after 20 seconds and continues to dump, however it won't do the second dump. -Sometimes it dumps for the second time, but stops somewhere again. -And I can't write nand, because it always says Hardware malfunction. Sometimes J-Runner doesn't even show the xFlasher logo. Sometimes it takes 1 min to show up the drive. It gives me a headache for a year. eMMC mode is just unstable and I hate it. What am I doing wrong? Just a small question, should I connect 4 and 6 points? I just solder to either 4 or 6. Quote Share this post Link to post Share on other sites
Octal450 91 Posted September 23, 2022 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 Quote Share this post Link to post Share on other sites
