1st, I do not know where the SPi comes from, so I can't help you there. Also, yes 64MB is fine, technically you only need 2mb. *NOTE: However, in your case and having to using progskeet, you did good by getting the whole 64MB. If you only got the 2mb, you might of been screwed with progskeet.
First of All ,thank u very much Julets for helping me. I really appreciate that. I did some google and found that the SPI is inside the Flash, so I canīt just exchange the NAND with another one from an old mobo (and use the old mobo SPI - IF the SPI circuit was in the mobo). If the SPI is (probably) dead, I just need another way of reading/writing the dump, and progskeet will help me (I think so).
About the 64MB, I also believe that that size is ok for glitching. Besides the GliGli tutorial, I've read several times in foruns that 64MB dump is far from enough.
I will assume you already flashed your appropriate .jed/.xsvf to the glitcher and that you actually waited between 1-10 minutes for it to boot (BB Jaspers can take forever to boot, especially without the correct capacitor). If you did flash your .jed/.xsvf how did you do it? I was under the impression only nandpro30 was only capable of doing that.
For the 64MB dumps you have, well you could open that up in a hex editor, copy it, then paste it into any 512mb nand overwriting the data.
That's right. I flashed the Matrix Gltcher with appropriate .jed file and, in fact, I awaited 10min to console to boot - but the main issue was that after writing the ECC to the NAND, I try to turn the console on and didn't have any response from X360 (I know it because the PSU didnīt start - it stood in Stand by mode - just orange led, no green led) and the console didn't turn on (no green ring of light - it seemed the console was off all the time, like all cables were disconnected). I flashed my .jed file using Xilinx (following the GliGli tutorial) and checked it was ok (run Chain Process in Xilinx software). Even after I take the Glitcher off, the console refuses to turn on (no green ring of light, no PSU startup).
I'll try to follow your hint and try to copy/paste the 64MB-dump in a 512MB-dump I'll take using Progskeet. I think it will work.
General steps are for RGH....
1.Flash the coolrunner device.
2.Dump Nand and then flash generated .ecc
3.Get CPU key and then flash generated freeBoot or xell image.
Now in the case of a BB Jasper, you might have to wait a VERY long time. Before I applied the capacitor, it would take about 2-7 minutes to boot!
Again, I can't help your progskeet, so sorry on that. I know if you would let any program like progskeet write to the nand, after 64mb you could just terminate the process. It's dirty I know, but it works (I've CTRL+C out of nandpro plenty of times).
I followed the same steps you said, I just didn't get CPU Key (The tutorial didn't explain how to do it).
Don't worry about the Progskeet, I really appreciate your help and support, that's the real deal to me. You set aside some of your time just to help me, and I'm very thankful for that. I'll see what I can get from Progskeet foruns. If I didn't get a word from them, I'll try to use the tips you gave me.
You sure you have the correct .jed/.xsvf? Have you kept all the wires on the bottom of the mobo away from center (not that this matters much)?
When I received "ARM device not compatible..." when flashing the coolrunner, the wires to the coolrunner were incorrect, or it was not in programming mode. When I receive "ARM device not compatible..." when flashing SPi to the nand, I just unplug my maximus flasher and plug it back in.
Yeah, I've checked the .jed file and double checked the Matrix Glitcher, I think the issue is ECC-related. I'm not sure, but I believe the ECC generated is corrupted at some point and not allowing the boot process to start.
I don't know why I get that message ("ARM device not compatible"), some people say it's Flasher-related, others say it's software-related. I really don't know who's right or wrong, all I know I just got NandPro 2.0a working and since the tutorial asks for at least NandPro 2.0e, I got really insecure about the dumps I got.
And unfortunately, I don't have such good tools like Coolrunner and Maximus Flasher, just the Chinese ones (Matrix Glitcher and generical SPI Flasher).
As far as the status light on the PSU, does it change prior to boot anyways? I don't see how the orange status can indicate anything besides the xbox isn't powered on, which doesn't seem to help does it?
The orange status on the PSU is just to confirm that the issue is not related to lack of power into the NAND circuitry. I also refer to the orange status to show the console is not powering on when the Matrix Glitcher is soldered to the console, showing that the console is not powering on with or without the Glitcher. That why I believe, the NAND dump is corrupted and can't start the boot up.
thx one more time