Cerial_iQ

@Octal450 That's exactly the problem, if you already have a xebuild rgh1 image, you can't use it to generate another xebuild rgh1 image. For example, if we have a xebuild rgh1 16767 image and we want to generate a xebuild rgh1 17559 image to update, this is not possible. And if you don't have the retail nand, the only ways you can upgrade is: use the xebuild rgh1 16767 image with CB 6750 and build a retail image with CB compatible rgh1 and then use that retail image to build xebuild rgh1 17559 . For more experienced users, this does not present a major problem, but for the most novice I think it does. Sorry for not explaining myself properly in the previous post. Salu2

Hello @Octal450 In the J-Runner Pro Github the user laotoulyh said that in the latest version it was not possible to create xebuilds for rgh1 for jasper, I checked it in the latest version of J-Runner with Extras, and the same bug is also presented. https://github.com/X360Tools/J-Runner-Pro/issues/3 Thanks for your attention Salu2

Hello, although I am not Octal450, I will try to help. I have been using picoflasher for a few days, and I can say that you have to be careful when reading nands, because if the correct installation is not verified in the console, we will get corrupted readings. Verifying the installation is not really difficult, just follow these steps. Before trying to read the nand, press the button that is in box 1 a bad installation will show messages like the ones in box 2: "Unrecognized Flash Config": Indicates that some connected nand is detected, but the system is not identified. Try to check the wiring. "Console Not Found": Indicates that it does not detect anything connected to the picoflasher. Try connecting the power supply to the console first and then the picoflasher to the computer. or the picoflasher to the computer and then the power supply. and if this does not work check the wiring. "Corona 4GB (EMMC not connected)": similar to "Unrecognized Flash Config" but in Corona 4GB As seen in box 2, the wrong detection of the console will generate corrupt readings. But if pressing the button in box 1 correctly detects the console, the type of console detected will be displayed. like Box 3, these are: "Xenon, Zephyr, Falcon" "Jasper 16MB, Trinity" "Jasper 256MB" "Jasper 512MB" "Corona 16MB" "Corona 4GB" When the verification is correct, the readings will also be correct. Salu2 Cerial i.Q.

Hello @Octal450 Thanks for the latest update. I hope that users who use MTX SPI NAND Flasher will no longer have problems. I'll stay here and try to help if there is any problem. I was sent a Raspberry Pi Pico today, which means I now have a Picoflasher, but I'll still keep the MTX SPI NAND to help out where needed. Thank you Josh for your excellent work.

Hello @Octal450 After some days I finally tried to write from corona using nandpro2e, but without success. This is the result... But when replacing the version of nandpro with NandPro2b_Armv3, the write is done correctly... For now I will continue using that version. I'm also sorry to report that the latest version contains a bug trying to recognize 1MB (first 50 blocks) dumps of big block jasper. This is the bug... With earlier versions of J-Runner this problem does not exist. I know that dumps of this size are not common, but there are still users who read their nands by LPT. And to speed up the process, they read 1MB and then from xell they extract the rest of their nand. I hope you can check these problems. Thanks Josh

Hello, At the moment I can not test that nandpro2e works correctly in corona, I only tested in jasper (SB and BB) and falcon As I already mentioned, the best compatibility was obtained by using Nandpro2b_Armv3. So I think if you could choose between different versions of nandpro it would be the best. This is just a suggestion, although if nandpro2e is verified to work in corona without problems, this will not be necessary. Just note that you have to use the driver included in J-Runner with Extras for the MTX SPI NAND Flasher Thanks Josh 

Hello @Octal450 I inform you that the version of nandpro that incorporates the current version J-Runner with extras works with my MTX SPI NAND and its stock hex. After my pc had a driver problem, I reinstalled the MTX SPI NAND driver using the one included in the current version of J-Runner with extras, it worked fine with nandpro2e. Sorry I didn't notice. Thanks Josh for hard work

Happy New Year Thanks for your hard work. Don't worry, the nandpro solution can wait, I don't mind replacing the version that works for me. Thanks, again

Hello Thanks for correcting the false positive of the files, about the xell, this is not one of the programs that fail blaKCat nand dumper https://www42.zippyshare.com/v/IsXTaTWo/file.html I use this program to dump the nand from xell (only compatible with trinity or earlier), I know that there are other options such as "simple nand flasher" but since I also use an MTX SPI NAND, it makes it easier for me to work in jasper of big block since I only have to read 1MB and then read the rest of the nand via USB and thus save time. I'm also sorry to report that nandpro2e still doesn't work with my MTX SPI NAND with factory hex, this one for some unknown reason I can't flash it with another hex. So again I had to replace nandpro2e with NandPro2b_Armv3, and only then did it work. Greetings Cerial i.Q. blaKCat nand dumper.zip

Thanks Josh I have a problem with the new xell, some programs (xenon.elf) that worked perfectly with the old xell, with the new one they fail, you could check it. Thanks again PS: An apology for my bad English, but I'm using google translator

The problem seems to be that nandpro version 3 (nandpro3) is not fully compatible with MTX SPI NAND (does not allow writing correctly). The solution I found was to use version 2 of nandpro with Amr3 support (NandPro2b_Armv3) Here are all the versions of nandpro that I have: nandpro_multi (mediafire.com) Go to the folder where your J-Runner with extras is, the common folder and the NandPro folder. backup the nandpro.exe file elsewhere and then delete it from the NandPro folder, then extract the NandPro2b_Armv3.exe file to the NandPro folder and rename it to just nandpro.exe. Now test your MTX SPI NAND, it should already write correctly. I own two MTX SPI NANDs, one of which still has its stock HEX. and using that version of nandpro I have no problem reading or writing. If this is the solution for those who have problems with MTX SPI NAND. So my suggestion would be that in the next version of J-Runner with Extras it would be possible to select between different versions of nandpro to solve this type of problem. Thanks and regards. Cerial i.Q PS: An apology for my bad English, but I'm using google translator