Need Help Bad Blocks Jasper 16mb

[mnkay]

Hey guys,

I am new here and need some help on a Jasper RGH 1 16mb with bad blocks.

I did not check the Jasper at first to see if it was a big block or small block as you can see in teh log. Stopped the read and powered up console to verify it was a 16 mb and sure enough, no onboard so assumption was right.

I then proceeded to read and bad blocks came up. I stopped the read and checked wiring, solder points.

Still same. So I tried to read as a 64mb and still errors and bad blocks.

Pretty well tried everything, different Jrunner, different PC and still have bad blocks and ultmately prevents the Jasper from powering up at all.

I flash the updflash bin file and wont boot. Flash xell/ecc boots everytime instantly. Falsh to stock and boots perfectly.

I have done many Jtags/RGH and usally depend on Jrunner to rebuild but does not rebuild the blocks in this instance.

I am an electronics technician and have extensive knowledge and expertise in soldering/diagnostics but do not have much experince in the software/nand building department.

I will apreciate any help or someone who could possibly help rebuild a working nand/Updflash bin file that I can flash to my Jasper.

Here is the log... I have replaced the important info KV/CPU etc with zeros to protect some info.


J-Runner v0.2 Beta (284) Started

Checking Files
Finished Checking Files
Finished Checking Files
Finished Checking Files
Version: 01
Flash Config: 0x00AA3020
CB Version: 6751
Version: 01
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Done!
in 5:11 min:sec
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Win32Error
Win32Error:No more bytes!
Version: 01
Flash Config: 0x00000000
Can not Continue
Could not find a part of the path.
===================================================
Wednesday, February 20, 2013 3:30:17 PM
J-Runner v0.2 Beta (284) Started

WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Checking Files
Finished Checking Files
Finished Checking Files
Version: 00
Wrong Version.
Finished Checking Files
===================================================
Wednesday, February 20, 2013 3:32:31 PM
J-Runner v0.2 Beta (284) Started

WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button

Checking Files
Finished Checking Files
Finished Checking Files
Finished Checking Files
Version: 01
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Win32Error
Win32Error:No more bytes!
Version: 01
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Done!
in 3:28 min:sec
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Done!
in 3:28 min:sec
Comparing...
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Bad Block ID @ 0x0000 [Offset: 0x0]
Bad Block ID @ 0x0001 [Offset: 0x4200]
Bad Block ID @ 0x0002 [Offset: 0x8400]
Bad Block ID @ 0x0003 [Offset: 0xC600]
Bad Block ID @ 0x0004 [Offset: 0x10800]
Bad Block ID @ 0x0005 [Offset: 0x14A00]
Bad Block ID @ 0x0006 [Offset: 0x18C00]
Bad Block ID @ 0x0007 [Offset: 0x1CE00]
Bad Block ID @ 0x0008 [Offset: 0x21000]
Bad Block ID @ 0x0009 [Offset: 0x25200]
Bad Block ID @ 0x000A [Offset: 0x29400]
Bad Block ID @ 0x000B [Offset: 0x2D600]
Bad Block ID @ 0x000C [Offset: 0x31800]
Bad Block ID @ 0x000D [Offset: 0x35A00]
Bad Block ID @ 0x000E [Offset: 0x39C00]
Bad Block ID @ 0x000F [Offset: 0x3DE00]
Bad Block ID @ 0x0010 [Offset: 0x42000]
Bad Block ID @ 0x0011 [Offset: 0x46200]
Bad Block ID @ 0x0012 [Offset: 0x4A400]
Bad Block ID @ 0x0013 [Offset: 0x4E600]
Bad Block ID @ 0x0014 [Offset: 0x52800]
Bad Block ID @ 0x0015 [Offset: 0x56A00]
Bad Block ID @ 0x0016 [Offset: 0x5AC00]
Bad Block ID @ 0x0017 [Offset: 0x5EE00]
Bad Block ID @ 0x0018 [Offset: 0x63000]
Bad Block ID @ 0x0019 [Offset: 0x67200]
Bad Block ID @ 0x001A [Offset: 0x6B400]
Bad Block ID @ 0x001B [Offset: 0x6F600]
Bad Block ID @ 0x001C [Offset: 0x73800]
Bad Block ID @ 0x001D [Offset: 0x77A00]
Bad Block ID @ 0x001E [Offset: 0x7BC00]
Bad Block ID @ 0x001F [Offset: 0x7FE00]
Too Many Bad Blocks
Nands are the same
Too Many Bad Blocks
* unpacking flash image, ....
Spare Data found, will remove.
Removed
A donor version will be used with this CB
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 2.3
CB_A: 6750
CB_B: missing
CD (image): 8453
CD (decrypted): 8453
* this image will be valid *only* for: jasper (CB_6751)
* patching SMC...
Patching Jasper version 2.3 SMC at offset 0x12BA
* zero-pairing...
* constructing new image...
* encrypting CB...
* encrypting CD...
* base size: 70000
* No separate recovery Xell available!
* Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x11A3F (0x9A40 bytes) CB_A 6750
0x11A40..0x17A3F (0x6000 bytes) CD 8453
0x17A40..0xBFFFF (0xA85C0 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...Done!
------------- Written into output\image_00000000.ecc
Version: 01
Flash Config: 0x00AA3020
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec
Programming Coolrunner
C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\common\xsvf\jasper.xsvf
USB XSVF Player Initialized
Xilinx XC2C64A-VQ44 ......... [DETECTED]
Erase Succeeded
File: C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\common\xsvf\jasper.xsvf
Sending Out Packets .........
Success
Initializing nanddump1.bin..
Too Many Bad Blocks
CpuKey is Correct
Added Key to Database
Nand Initialization Finished
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image

**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
***** WARNING: nanddump.bin has a bad LBA at block 0x7f (raw offset 0x105f000), block LBA ignored

An unhandled exception 0xC0000005 has occured, exiting...

Failed
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image

**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
***** WARNING: nanddump.bin has a bad LBA at block 0x7f (raw offset 0x105f000), block LBA ignored

An unhandled exception 0xC0000005 has occured, exiting...

Failed
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image

**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
***** WARNING: nanddump.bin has a bad LBA at block 0x7f (raw offset 0x105f000), block LBA ignored

An unhandled exception 0xC0000005 has occured, exiting...

Failed
Initializing nanddump1.bin..
Too Many Bad Blocks
Nand Initialization Finished
Version: 01
Flash Config: 0x00AA3020
Writing Nand
nanddump1.bin
Error: 202 writing block 130
Done!
in 5:49 min:sec
Version: 01
Flash Config: 0x00AA3020
CB Version: 6751
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump1.bin
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Done!
in 5:11 min:sec
Reading Nand to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Too Many Bad Blocks
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Cancelled
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building retail image

**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
***** WARNING: nanddump.bin has a bad LBA at block 0x7f (raw offset 0x105f000), block LBA ignored

An unhandled exception 0xC0000005 has occured, exiting...

Failed
Value cannot be null.
Parameter name: start
Version: 01
Flash Config: 0x00AA3020
Reading Nand
Error: 250 reading block 130
Error: 210 reading block 131
Error: 210 reading block 132
Error: 210 reading block 133
Error: 210 reading block 134
Error: 210 reading block 135
Error: 210 reading block 136
Error: 210 reading block 137
Error: 250 reading block 8A0
Error: 210 reading block 8A1
Error: 210 reading block 8A2
Error: 210 reading block 8A3
Error: 210 reading block 8A4
Error: 210 reading block 8A5
Error: 210 reading block 8A6
Error: 210 reading block 8A7
Error: 250 reading block 8E0
Error: 210 reading block 8E1
Error: 210 reading block 8E2
Error: 210 reading block 8E3
Error: 210 reading block 8E4
Error: 210 reading block 8E5
Error: 210 reading block 8E6
Error: 210 reading block 8E7
Done!
in 20:42 min:sec
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building retail image

**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
---------------------------------------------------------------
C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\304876700205\updflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper
NAND size : 16MiB
Build : Retail
Serial : 304876000000
ConsoleId : 046540000000
MoboSerial: 705993120000000
Mfg Date : 01/05/2010
CPU Key : 8DA6F79ABC699EC00000000000000000
1BL Key : DD88AD0C9ED669E00000000000000000
DVD Key : B72F086AEBA559000000000000000000
CF LDV : 6
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\304876700205
Image is Ready
!You are creating an ecc image and you have selected retail!
* unpacking flash image, ....
Spare Data found, will remove.
Removed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 2.3
CB_A: 6754
CB_B: 6754
CD (image): 6754
CD (decrypted): 9452
* checking required versions...
ok
* patching SMC...
Patching Jasper version 2.3 SMC at offset 0x12BA
* Replacing CD...
* XOR HACK NEEDED FOR CB 6754
File C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\common\CB\CB_B.6754.bin not found!
Failed to open CB_B.6754.bin
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\304876700205\updflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 304876000000
ConsoleId : 046540000000
MoboSerial: 70599310000000000
Mfg Date : 01/05/2010
CPU Key : 8DA6F79ABC699EC00000000000000000
1BL Key : DD88AD0C9ED669E00000000000000000
DVD Key : B72F086AEBA559000000000000000000
CF LDV : 6
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Documents and Settings\me\Desktop\Jtag\J runner\J-Runner v02 Beta (283) Core Pack\304876700205
Image is Ready
Initializing updflash.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
Version: 01
Flash Config: 0x00AA3020
Writing Nand
updflash.bin
Error: 202 writing block 130
Done!
in 5:48 min:sec
Version: 01
Flash Config: 0x00AA3020
Writing Nand
image_00000000.ecc
Done!
in 0:28 min:sec
Version: 01
Flash Config: 0x00AA3020
Writing Nand
updflash.bin
Error: 202 writing block 130
Done!
in 5:48 min:sec

 

[stefanounick]

oh FFS
you have a 512MB!
and bad blocks are damn normal!

 

[mnkay]

When I flash the Upd flash bin it will not boot at all, no power nothing.

J runner did not choose what block the Jasper was, I had to and determined this by having no onboard MU. How can it be a 512 with no onboard memory?

Can it be rebuilt so the console will power on and boot like a normal RGH?

 

[un_xe]

hi

can you show us a picture from your solder points?

What kind of Nand Flasher did you use? Nand-X oder something else?

 

[mnkay]

I will take a pic in a few minutes.

Sorry about not better describing what tools I am using. Jrunner 1.2 programmer also used a JR runner. I am using a Cool runner Rev C.

 

[mnkay]

Here are some pics.

 

[un_xe]

Thanks for your pictures at first.

Have you two equal 16MB Nand.bin?

 

[Martin C]

OP - when J-Runner asked you to select either 256 or 512, why did you override it with 16?

You have ONE bad block. That's all.

 

[BraveH43]

When I flash the Upd flash bin it will not boot at all, no power nothing.

J runner did not choose what block the Jasper was, I had to and determined this by having no onboard MU. How can it be a 512 with no onboard memory?

Can it be rebuilt so the console will power on and boot like a normal RGH?

If stef said you have a 512 nand, I'd believe him.


sent using tippytalkytappa thingy

 

[Martin C]

J runner did not choose what block the Jasper was, I had t?

BS - J-Runner would have read your flashconfig as we can all see from your output. You thought "I can't see an MU so it's wrong".

Unless you know what you are doing (which you don't), NEVER override software defaults.

 

[Slayertex6]

People could avoid problems like this if they paid attention to the flash config in the first place.

 

[Martin C]

I'll condense your comment:

People could avoid problems like this if they RTFM

 

[mnkay]

How is one to learn if no mistakes are ever made?


So I will clarify...


JR programmer connect and click read nand.

J Runner prompts me to click which Jasper it is. J RUNNER does not choose it for me!!!

Choices are as follows. 16mb
256mb/512/

I choose 16mb

Bunch of bad blocks come up. Think it may be a big block and stop read and power up console to verify.

No MU so assume it is a 16mb. 2 full reads with bad blocks.

I assumend A J runner would fix them as it has before in the past for me.

Created ECC and booted Xell instantly.

Flashed back to stock and all is good.

Tried to create UPDflash bin and said wrong LBA. and could not create a valid UPDflashbin file.

Tried 64mb read and so on with tons of errors

... and that is why I am here.

I have the original dumps just need insight on what to do to have a working RGH.

 

[Martin C]

How is one to learn if no mistakes are ever made?

But you're not learning anything.

The 'mistakes' have been made already, which is why everything is well documented.

You're basically making the same mistakes everyone else did about 5 years ago.

Therefore your comment is null and void.

Find someone to send it to - job done.


"I choose 16mb

Bunch of bad blocks come up. Think it may be a big block and stop read and power up console to verify.

No MU so assume it is a 16mb. 2 full reads with bad blocks."

This is where you should have stopped.

Instead...

"I assumend A J runner would fix them as it has before in the past for me."

Assumption will always kick you in the nuts. You don't understand bad blocks and there are no messages in J-Runner to indicate it fixed anything.

so what do you do?

"Created ECC and booted Xell instantly.

Flashed back to stock and all is good.

Tried to create UPDflash bin and said wrong LBA. and could not create a valid UPDflashbin file."

Yeah, you carry on writing to something even when you don't have a valid dump.

Read my RGH Roadmap for noobies and tell me where it says to carry on if you have 20 or so lines of bad blocks?

So what's the point in stating 'how can I learn' if you're not going to read?

 

[mnkay]

OP - when J-Runner asked you to select either 256 or 512, why did you override it with 16?

You have ONE bad block. That's all.

J runner never did overide and detect the Jasper, it asked me what version it was and I had to choose.

What you see in the log is me having to choose what Jasper it is, not J runner deciding for me.

So J runner did not choose the version I had to. That is what stumped me from the beginning.

---------- Post added at 12:13 ---------- Previous post was at 12:08 ----------

Interested in rebuilding it for me?

I have no problem donating some cash through paypal if need be. I am a true believer you get what you pay for and here I am. Just need some help getting this rebuilt to working order, thats all.

Trust me, I am learning and paying for it.

 

[Martin C]

Ok - we might be able to get this back without needing donor NANDs.

1. Do you still have the original 16MB dump you took?

2. Did you write anything over 16MB in size to your NAND?

 

[mnkay]

Have the original dumps and can upload them for you. I did a bunch of dumps just have to go through them.

I will upload the dumps for you so you can take a peek.


Thanks Martin

 

[Martin C]

ok - zip them up as lots of filler data in the 64MB dumps.

 

[mnkay]

Do you want me to Post the link and make it public or send you the link via Email?

 

[Martin C]

email me the link with the CPU key:

xbox guru 23 @ gmail .com

(remove spaces)