Print

[Kieranl]

Im trying to dump my nand from the 512mb jasper nand, NandPro states "512MB NAND Detected!" and but my flashconfig is 00aa3020. It dumps fine with no errors but hten cant be opened in Degraded v1.1b

Two questions
1) Is my flashconfig ok
2)Is it normal for a jasper dump not to open with degraded or firmware tool?

[Poopchute]

Im pretty sure that you cant do this hack with the JAsper model 360's yet.  It's supposed to happen any day or possibly even next month...

[niai]

you dont need the jtag to dump the nand i have herd that u cant dump the jasper nand with nandpro

you may want to try an infectus if u have one

[Kieranl]

QUOTE(niai @ Oct 7 2009, 10:52 PM)

you dont need the jtag to dump the nand i have herd that u cant dump the jasper nand with nandpro

you may want to try an infectus if u have one

im pretty sure it does work because nandpro gives me the msg "512mb nand detected" which hints to me that it has been programmed to accept this, it still only dumps up to block 3FF, and every dump i have made so far has been identical with a "copyright m$ 2004-2009 blah blah" i tried changing the copyright to 2007 and 2005 but it didnt do anything for degraded... there must be someone else out there who has dumped a 512mb jasper before

[Poopchute]

So you guys are saying that its possible to do the JTAG hack or whatever its called on a Jasper now?

[Kieranl]

QUOTE(Poopchute @ Oct 8 2009, 04:17 AM)

So you guys are saying that its possible to do the JTAG hack or whatever its called on a Jasper now?

No. It has always been possible to read the NAND on a jasper console, but there hasnt been a xell compiled specifically for the jasper like ther has for xenon/falcon/opus/zephyr consoles. My question relates purely to dumping the nand

This post has been edited by Kieranl: Oct 8 2009, 03:45 PM

[Poopchute]

So then what are you going to do with it?  Just wondering...

[Kieranl]

QUOTE(Poopchute @ Oct 8 2009, 08:27 PM)

So then what are you going to do with it?  Just wondering...

just create a backup if my NAND in anticipation of the Jasper release, also I wanted to be able to open it in degraded and firmware tool

[acerman]

What command are you using to dump?  NandPro lpt: -r16 nand.bin   or  NandPro lpt: -r512 nand.bin  I cant get my flash to detect>

[cocker80]

Did the 7 wire ltp hack and dumped my 256mb jasper,  just waiting for the xell nand now   As Kieranl found out it dumps fine but does not open up in 360_Flash_Tool DevKit or Degraded v1.1b. For anyone who is interested it took just under 8 hours to dump the full 256mb nand, so I would expect it would take 16  hours to dump the 512mb version.

QUOTE

"D:\NandPro20>nandpro lpt: -r16 rawkv1.bin 1 1
NandPro v2.0a by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000001
Ending   Block:0x000001
Press any key to begin reading nand
0001

D:\NandPro20>
D:\NandPro20>nandpro lpt: -r16 rawkv2.bin 1 1
NandPro v2.0a by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000001
Ending   Block:0x000001
Press any key to begin reading nand
0001

D:\NandPro20>

D:\NandPro20>NandPro lpt: -r16 nand-hdmi2.bin
NandPro v2.0a by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000000
Ending   Block:0x0003FF
Press any key to begin reading nand
03FF

D:\NandPro20>

D:\NandPro20>NandPro lpt: -r256 nand-256-hdmi1.bin
NandPro v2.0a by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000000
Ending   Block:0x003FFF
Press any key to begin reading nand
Error: 250 reading block 10A0
Error: 210 reading block 10A1
Error: 210 reading block 10A2
Error: 210 reading block 10A3
Error: 210 reading block 10A4
Error: 210 reading block 10A5
Error: 210 reading block 10A6
Error: 210 reading block 10A7
3FFF

D:\NandPro20>

D:\NandPro20>NandPro lpt: -r256 nand-256-hdmi2.bin
NandPro v2.0a by Tiros

Testing LPT device address:0378
Using LPT device at address:0378
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000000
Ending   Block:0x003FFF
Press any key to begin reading nand
Error: 250 reading block 10A0
Error: 210 reading block 10A1
Error: 210 reading block 10A2
Error: 210 reading block 10A3
Error: 210 reading block 10A4
Error: 210 reading block 10A5
Error: 210 reading block 10A6
Error: 210 reading block 10A7
3FFF

D:\NandPro20>"

[cocker80]

Just been comparing the jasper -r16 with a dump from a Xenon board, I open both up in a hex editor and searched for vk.xex. The Xenon dump has it but not the jasper dump.
 I then opened the jasper -r256 dump and again searched for vk.xex this time it found it, so I can only presume you will have to dump the full 256mb/512mb nands.

This post has been edited by cocker80: Oct 21 2009, 12:19 AM

[sunnyzhi]

where ‘s j1f1 on jasper?  i don't know how to find it. i use 7 wired method.

[Chemodile]

Now that more people are dumping the 512mb Jaspers can anyone shed some light on this? I get FlashConfig:00AA3020 no matter what LPT mode I use and the free60 wiki says it should be FlashConfig:01198010.

I've rechecked and resoldered everything, significantly shortened my cable, and moved the diode from the d-sub connector directly onto the board. Nothing gets me a FlashConfig value other than 00AA3020.

It seems to read ok, but given how long it takes to fully dump a 512mb NAND I'd like to make sure I'm not wasting my time.

Here's the log from my first attempt:

QUOTE

Testing LPT device address:0378
Using LPT device at address:0378
Flashconfig:00AA3020
512MB Nand Detected
Starting Block:0x000000
Ending Block:0x007FFF
Press any key to begin reading nand
Error: 250 reading block 1300
Error: 250 reading block 1308
Error: 310 reading block 1309
Error: 210 reading block 130A
Error: 310 reading block 130B
Error: 310 reading block 130C
Error: 210 reading block 130D
Error: 310 reading block 130E
Error: 210 reading block 130F
Error: 250 reading block 1AE8
Error: 250 reading block 3308

I stopped it at 35E4 after seeing all the errors. (Is it normal to have that many bad blocks on a larger nand? It seems to me if a 16mb nand having 1-2 bad blocks is acceptable then a 512mb could have quite a few more.)

Since then I've resoldered everything, shortened the cable length, moved my diode from the LPT connector to board, and switched to NandPro 2.0b which adds the message "Configured for Large Block Nand." Hopefully less errors this time around, but in the meantime can someone confirm/deny whether FlashConfig:00AA3020 can produce an acceptable dump?

[Boke]

Here is the log from my 512mb jasper.

QUOTE

Testing LPT device address:0378
FlashConfig:00AA3020
512MB Nand Detected
Using LPT device at address:0378
Starting Block:0x000000
Ending   Block:0x007FFF
Configured for Large Block Nand
Error: 250 reading block 2B70
Error: 250 reading block 2B78
Error: 210 reading block 2B79
Error: 210 reading block 2B7A
Error: 210 reading block 2B7B
Error: 210 reading block 2B7C
Error: 210 reading block 2B7D
Error: 210 reading block 2B7E
Error: 210 reading block 2B7F
Error: 250 reading block 4B78
Error: 250 reading block 6B78

I dumped 512mb twice. Both matched.
Then I did four 2mb dumps. All matched.
I flashed jasper_6723_hack_for_256mb_512mb.bin. Got my CPU key and then flashed back one of the 2mb dumps.

Everything worked fine and the 360 functions just as it always did.

[Ranger72]

It took about 18 hours to dump my Jasper 512 nand.

I did get about 8 read errors and they was at the same location for each of my 2 dumps so I figure this may be normal. Both hash checks are identical so pretty sure I got all the dump.

Now it is a waiting game I guess.