when i dump my 256MB nand with demon, it dumps the whole thing, there is no option to only dump 64MB image...... Where previous versions with nandX would dump only 64MB. Any advice, because it is extra work to convert it to a 64MB image. Really do like the demon read write times though..... it dumps the whole 256MB in less then 5 minutes, unlike my nandX which was taking over 7 minutes to dump the 64MB.
Bug Reports / Suggestions - J-Runner build (287)
- Thread starter BraveH43
- Start date
- Status
stefanounick
VIP Member
to save space on my computer....... i like to keep my stock nand dumps, just in case, but am running out of space. 64MB is less then 256..... and most of that is just game saves. also the full dump option is greyed out, so I couldnt disable it even if i wanted.
Last edited:
stefanounick
VIP Member
Just done a Jtag on a xenon (yes theres still a few out there) when pressing create xell reloaded, it creates it as xenon.bin, so when you come to write the image it comes up with a message along the lines of error needs .ecc file.
No biggie i just manually put the xenon.bin in the source file then wrote the nand, just thought you would like to know.
No biggie i just manually put the xenon.bin in the source file then wrote the nand, just thought you would like to know.
jsinger47
Troll Eating Dogs
Write xell reloaded should be what you were looking for. Are you sure you had "jtag" selected?
In the case of a spelling error, I blame Tapatalk.
Yes when you press write xell reloaded it came up with the message requires .eec, the file created is xenon.bin, hence i manually loaded that into the source file and then pressed write nand.
I had the jtag selected as the flash coolrunner tab was grey out.
heres the extract from the log.
Reading Nand to C:\J-Runner v02 Beta (283) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Nand Initialization Finished
Reading Nand
Done!
in 3:28 min:sec
Comparing...
Nands are the same
XeLL file created Successfully xenon.bin
You need an .ecc image
XeLL file created Successfully xenon.bin
You need an .ecc image
Initializing xenon.bin..
Header is wrong..
Nand Initialization Finished
Version: 01
Flash Config: 0x01198010
Writing Nand
xenon.bin
Done!
in 0:18 min:sec
Last edited:
stefanounick
VIP Member
Something else, not really a bug but...
When you are working with a Slim on 15572+ and DGX tab loads up, it puts everything in RGH2 "mode', but in JR Trinity is still classified as RGH. So before you can flash your CR and sometimes create an image you have to go back and select RGH again.
Maybe have three levels, RGH, RGH2 Phat, RGH2 Slim?
When you are working with a Slim on 15572+ and DGX tab loads up, it puts everything in RGH2 "mode', but in JR Trinity is still classified as RGH. So before you can flash your CR and sometimes create an image you have to go back and select RGH again.
Maybe have three levels, RGH, RGH2 Phat, RGH2 Slim?
- Mar 1, 2010
- 3,346
- 128
Thanks for going out of your way to point that out for me Oggy, what would I do without you.
Netkar
VIP Member
- Apr 27, 2005
- 389
- 33
suggest to add in rater the configuration (dip,cap,cpu rst etc) for remember the configuration
also a "screen" button is liked. If the screen can go in the same forlder of id console will be amazing
also a "screen" button is liked. If the screen can go in the same forlder of id console will be amazing
- Mar 1, 2010
- 3,346
- 128
Probably impress us all with your knowledge of components and exploits.
nofeloniesyet
VIP Member
Last edited:
- Status