JTAG Cant get a good dump no matter what

[Krafter]

I just now had a chance to get back on this. I did what you suggested with a clean retail NAND I had already built that I know boots but I still have the same problem. Here is the log as requested.

===================================================
Wednesday, July 10, 2013 10:17:36 PM

J-Runner v0.2 Beta (289) Started



Filechecks disabled - No Filechecks carried out
Version: 03
Flash Config: 0x008A3020
Erasing Nand
Error: 202 erasing block 3D0
Error: 202 erasing block 3D0
Error: 202 erasing block D20
Error: 202 erasing block D20
Done!
in 0:25 min:sec

Initializing updflash.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Version: 03
Flash Config: 0x008A3020
Writing Nand
updflash.bin
Error: 202 writing block 3D0
Error: 202 writing block D20
Starting remapping process
Remapping Block 3D0 @ 1FF
Remapping Block D20 @ 1FE
Done!
in 7:31 min:sec

 

[BL4K3Y]

Apologies for posting in the wrong section. I could have sworn I posted this in the JTAG section and just realized I didn't. Feel free to move it.

I have moved this thread to the JTAG section for you.

Have you got the full log which includes image creation (updflash.bin)?

 

[Krafter]

Thanks for moving it lol.

I didn't have a log of the one I built to flash this last time but it's always the same as this one when I do.

===================================================
Wednesday, July 10, 2013 10:52:26 PM

J-Runner v0.2 Beta (289) Started



Filechecks disabled - No Filechecks carried out
Initializing retail.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Load Files Initiliazation Finished
Clean SMC detected
16203
Started Creation of the 16203 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.07.561
---------------------------------------------------------------
building jtag image
---------------------------------------------------------------
E:\xbox\J-Runner\002999690307\updflash.bin image built, info:
---------------------------------------------------------------
Console   : Jasper (big block)
NAND size : 64MiB (system only)
Build     : JTAG
Xell      : power on console with console eject button
Serial    : 002999690307
ConsoleId : 003383851821
MoboSerial: 8920961208559027
Mfg Date  : 01/12/2009
CPU Key   : 345CD0DD6F7BD17813CCC522A162A5E9
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : 4AD0C2C013C733CB230B5E339F6290D7
CF LDV    : 1
KV type   : type2 (hashed)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to E:\xbox\J-Runner\002999690307
Image is Ready

 

[BL4K3Y]

Was it your intention to build a JTAG image just now or did you mean to build a new retail image to test?

Am I correct in assuming that the retail image works, but any JTAG image you build and write refuses to boot?

I'm just trying to understand what stage you are at right now.

 

[Krafter]

Your are correct in your assumption. I can build a retail (7371) and it boots just fine. I was even able to flash back the original JTAG image (4532) and it boots with normal JTAG wiring. I have tried a 16203 image with both normal and AUD_CLAMP wiring. No matter what I do I get E79.

Edit: I should add that in each case, Xell boots. I only run into problems when I attempt to boot into the dash.


Tapatalk misspelled it. Knot me.

 

[Martin C]

Did it definitely erase up to 7FFF?

Also, just stick with AUD_CLAMP. If AUD_CLAMP xell boots then you know that option is fine to stick with.

Have you tried one of the older XBR images - they should be on xbins still. Just dump block 1 from your existing NAND for rawkv.bin and EF7-EF8 for rawconfig.bin. write these to the XBR image and see if it boots.

 

[briggs01]

I'll give it a try when I get home.

PS
Apologies for posting in the wrong section. I could have sworn I posted this in the JTAG section and just realized I didn't. Feel free to move it.


Tapatalk misspelled it. Knot me.

i hope you got an infraction for posting in the wrong thread mate cus i did lol

 

[Krafter]

i hope you got an infraction for posting in the wrong thread mate cus i did lol

Thanks. I'll try that right now..... Oh wait. Your reply was just sh*t and not intended as helpful. So right back at you. I hope you get an infraction for your reply. I did once for getting off topic and so should you.


Tapatalk misspelled it. Knot me.

 

[Martin C]

Don't hijack threads.

 

[SoulReaper223]

have you tried building any other dashboard other than 16203. dont know if that could be the issue.

 

[Krafter]

I finally got it to boot a 16203 JTAG image! I went with my gut and replaced the 256 NAND with a 512 NAND from a Wii and that done the trick. I think it had something to do with the read/write/erase errors in those two blocks. My guess is that they weren't able to be marked as bad and therefore the system continued to try to access them and found corrupt data (or wrong) .... but that's just a guess. In the end, all that matters is that it's working.

Thanks for your help Martin.