we need to know which jasper you have , we can then put the original nand back on and then dump only what we need .
jasper coolrunner not booting
- Thread starter windstorm
- Start date
well since xell just writes the first few blocks, i thought should try writing the 16mb nand right now, and there is no error at the starting
no ...there`s no point becase we need a 64mb image to complete the process . If it doesnt work from NXE dash , it aint going to work
we need to know exactley which jasper it is or the nand wont work. If he can dump 512 then i`m thinking it`s a 512
nandpro is the better way to do this . JTAG tool , for me , is useless if you dont know which console you have
we need to know exactley which jasper it is or the nand wont work. If he can dump 512 then i`m thinking it`s a 512
nandpro is the better way to do this . JTAG tool , for me , is useless if you dont know which console you have
Last edited:
xell booted fine
---------- Post added at 06:49 ---------- Previous post was at 06:48 ----------
whats the point of dumping when i have already written to the nand, i am currently writing the 512mb nand
---------- Post added at 06:49 ---------- Previous post was at 06:48 ----------
whats the point of dumping when i have already written to the nand, i am currently writing the 512mb nand
you NEED A 64MB IMAGE .....or it`s going to take a week to write. **apologies frustrated with yer..lol
it`s not the LDV sean he just doesnt know what console he has and has built the image with the wrong size nand . If he knew which one it was then it would be a HELL of a lot easier for him but he if just flashing and flashing ...lol
it`s not the LDV sean he just doesnt know what console he has and has built the image with the wrong size nand . If he knew which one it was then it would be a HELL of a lot easier for him but he if just flashing and flashing ...lol
Last edited:
seanr28
VIP Member
- Mar 7, 2004
- 1,203
- 0
i am trying to but it don't boot, i will wait and see when the 512mb is finish writing, it will take a long time, and in that time i will be going to school
---------- Post added at 06:59 ---------- Previous post was at 06:59 ----------
i will be back in about 2-3 hours
---------- Post added at 06:59 ---------- Previous post was at 06:59 ----------
i will be back in about 2-3 hours
seanr28
VIP Member
- Mar 7, 2004
- 1,203
- 0
Ok, but for futrue refernce use the command above, this is the nand area only, the rest is Memory Unit.
Once you have it back to stock use the read command in nandpro for just t he first 64mb
---------- Post added at 13:02 ---------- Previous post was at 13:01 ----------
Once you have it back to stock use the read command in nandpro for just t he first 64mb
---------- Post added at 13:02 ---------- Previous post was at 13:01 ----------
Yes i realilse that. Unfortunatley Jaspers are more of a pain if you dont know what you are doing with them, I had a similar only 2 weeks ago, but martin C managed to help me out and get it going again
yeah i only do jaspers now so have done loads of them now , jtag tool is crap for jasper big blocks i much prefer nandpro as you do
---------- Post added at 13:15 ---------- Previous post was at 13:05 ----------
OK . i`m going to leave this post for when you get back
When you have NXE dash back and working
Start nandpro and use this command
nandpro usb: -r64 nand.bin
that will be your image . do it twice but renamd nand.bin to nand_1.bin the second time
then type
fc /b nand.bin nand_1.bin
to compare the nand , you should get no differences found
then you are good .
you now have a good image .
use multi builder 0.5 to make the image using your key and nand
flash nand and you are good to go .
---------- Post added at 13:15 ---------- Previous post was at 13:05 ----------
OK . i`m going to leave this post for when you get back
When you have NXE dash back and working
Start nandpro and use this command
nandpro usb: -r64 nand.bin
that will be your image . do it twice but renamd nand.bin to nand_1.bin the second time
then type
fc /b nand.bin nand_1.bin
to compare the nand , you should get no differences found
then you are good .
you now have a good image .
use multi builder 0.5 to make the image using your key and nand
flash nand and you are good to go .
i got the original 512mb nand back on but its not booting, the coolrunner does its little flash thing every few seconds, also it give me rrod, error code 0002
---------- Post added at 08:59 ---------- Previous post was at 08:55 ----------
i tried booting again but with my dvd drive in this time, and the coolrunner went green fro like 4 seconds, and still getting rrod
---------- Post added at 08:59 ---------- Previous post was at 08:55 ----------
i tried booting again but with my dvd drive in this time, and the coolrunner went green fro like 4 seconds, and still getting rrod
I`d say at a guess that your "shorting" thing has messed something up on the board . 0002 is not good . It`s usually something to do with the network controller i think but in this case i would doubt that . I think you should have come here before you started as you were unsure about the type of console you have. That should have been your very first question here (or you could have turned it on and had a look to see how much memory you had !!!!) ...Maybe someone else has an idea , but for me it`s done for i think .
so can't i do something through xell, is the nand corrupted or would it be the video or something like that, could hdmi be a fix
well you can try and install xell but I personally dont think its going to boot. Give it a try and let me know. if xell boots then in theroy dash should .