ANSWERED Jasper 512MB E71 after update to 14699 dash

Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
So this was a mis-type:

360 Flash Dump Tool:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

So set noremap back to false as you original dump (which you should be using to build this) is ok.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
So this was a mis-type:

360 Flash Dump Tool:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016A found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]

So set noremap back to false as you original dump (which you should be using to build this) is ok.
Click to expand...
I already tried this. Juszt to be sure, I cleared out the old nand it made and the nanddump.bin, copied over the original nand given me to nanddump.bin, made sure noremap was false, and reran multi tool and tried to rawflash the resulting nandflash.bin. Same result. I can load FSB, but otherwise loading with no USB or HDD gives an E71.

---------- Post added at 15:13 ---------- Previous post was at 15:13 ----------

and yes, this should have been as follows for the original NAND:
360 Flash Dump Tool:

Note: Bad Block ID 0x0150 [Offset: 0x02B50000]
Note: Bad Block ID 0x016B [Offset: 0x02ECB000]

-> Block ID 0x016B found @ 0x1FE [Offset: 0x041BE000]
-> Block ID 0x0150 found @ 0x1FF [Offset: 0x041DF000]
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
try this:

nandpro nandflash.bin: -r64 150.bin 1ff 1
nandpro nandflash.bin: -r64 16B.bin 1fe 1

nandpro nandflash.bin: -w64 150.bin 150 1
nandpro nandflash.bin: -w64 16B.bin 16B 1

You're basically copying them back. You don't need a nand-x for this.

Flash this to your console using rawflash v4 and let me know if you get any write errors.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Martin C said:
try this:

nandpro nandflash.bin: -r64 150.bin 1ff 1
nandpro nandflash.bin: -r64 16B.bin 1fe 1

nandpro nandflash.bin: -w64 150.bin 150 1
nandpro nandflash.bin: -w64 16B.bin 16B 1

You're basically copying them back. You don't need a nand-x for this.

Flash this to your console using rawflash v4 and let me know if you get any write errors.
Click to expand...
So I run nandpro like this on the nandflash.bin I just created in Multi Tool, right? Not the original?
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Error 250 is an empty block, which makes no sense if you wrote back what had been remapped.

16B is a curveball. Not sure what's happening there either. Open 150.bin and 16A.bin in a hex editor and see what's in there.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
150.bin and 16B.bin are basically empty data, hex FF for the whole file.

---------- Post added at 17:11 ---------- Previous post was at 17:09 ----------

I used nandpro to rip 16A as well, and its the same, empty data/FF all the way.

---------- Post added at 17:19 ---------- Previous post was at 17:11 ----------

So, the nandpro commands you had me use were to dump 0x1FE and 0x1FF for the remaps of 0x16B and 0x150, right? And its empty data. I tried this on the original nand, and 0x1FE-0x1FF is showing data there. Is this clobbering data, thinking its empty when its doing a remap?
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
okay, looking at the original nand, the remapped 0x150 at 0x1ff is empty data, all FFs. The original 0x150 in that file is almost all empty Data/FFs, but a bit of data here and there. 0x16B and 0x16B remapped at 0x1fe contain full data, but each is different.

---------- Post added at 17:37 ---------- Previous post was at 17:33 ----------

so I checked the rewritten flash to be clear. 0x150, 0x16A, 0x16B, and the remaps at 0x1FF and 0x1FE are all filled with empty data/FFs all the way (confirmed checksums for these rips are the same), but the original nand differs as for the last post.

---------- Post added at 17:47 ---------- Previous post was at 17:37 ----------

I've reverted to juse using xebuild now. Rebuilt using noremap= true, and ripped the blocks again. Still the same, empty data, same checksum as before.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
So, I'm at a loss of what to do about this. If I have multi tool install dashlaunch, I can at least use fsd for now, but I have no way to run the original dash. I suppose when the next dashboard version comes out, I can try again and hope it works, since if something was broken during the dashboard install, I'm not able to try and install it again. Any other thoughts on what to do?
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I don't think there's much you can do without a proper USB writer. It's plausable that the issue would be resolved if you were to directly write without any software trying to be clever and remapping. You could also test the original NAND like this too.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
So, if I were to do this, would I just need a nandx? Any extra cables or devices? It was glitched with the xecuter coolrunner.

---------- Post added at 18:55 ---------- Previous post was at 18:51 ----------

And a NANDX to coolrunenr cable, I take it.
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Yes, I have. I've seen the 3D sticker that the Coolrunner has on it to confirm, if that's what you're asking. So the nandx has the proper cables I need just to do work on the nand then, right?
 
M

MadCabbit

Full Member
Jan 18, 2012
32
0
Toledo, Ohio. I couldn't find anyone before to do this, so that's why I shipped it off to someone in state. I might pick up a soldering iron and try to carefully do this myself. I should be able to solder the nandx qsbs on without removing the existing coolrunner connections, right?
 
You must log in or register to reply here.