RGH Nand dump errors

[satans1978]

Hello all;

I've been trying to dump a trinity nand after the dae.bin update and i'm getting the following errors, does it have anything to do with the new update or should they be fine ??? i've read that 2 or 3 errors are ok as long as the dumps are identical as far as i can tell they are all the same.
my question is .... is it ok to proceed ? or should i re-do my soldering ? and re-dump ?


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\xxx>cd Desktop/nandpro2

C:\Users\xxx\Desktop\nandpro2>NandPro usb: -r16 flashdmpS.bin
NandPro v2.0e by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: flashdmpS.bin
Reading
Error: 250 reading block 225
Error: 250 reading block 329
03FF

C:\Users\joey\Desktop\nandpro2>NandPro usb: -r16 flashdmpS2.bin
NandPro v2.0e by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: flashdmpS2.bin
Reading
Error: 250 reading block 225
Error: 250 reading block 329
03FF

C:\Users\xxx\Desktop\nandpro2>NandPro usb: -r16 flashdmpS3.bin
NandPro v2.0e by Tiros

Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: flashdmpS3.bin
Reading
Error: 250 reading block 225
Error: 250 reading block 329
03FF

 

[Martin C]

All you need to do is open the dump in 360 Flash Dump Tool. Check to make sure these bad blocks are being remapped.

However bear in mind that error 250 is empty block- Nandpro could be reporting a perfectly good block (but empty) being bad, which means you won't see it remapped.

Why is nobody able to Google 'xbox bad blocks'? You can take the time to make a post but not search for it?

 

[satans1978]

hey guys i've been reading more and more and i got one more question, ok here we go. i tried dumping my nand for the 100th time and still blocks 0225 and 329 are bad. so i dumped again with Nand flasher 360 for windows 1.2... this one also reports same two blocks as bad... but i also get this message at the beginning

Error: Unknown or incompatible JTAG | CB: 9188 | NAND: 16 MB

any and all input would be appreciated.

 

[satans1978]

All you need to do is open the dump in 360 Flash Dump Tool. Check to make sure these bad blocks are being remapped.

However bear in mind that error 250 is empty block- Nandpro could be reporting a perfectly good block (but empty) being bad, which means you won't see it remapped.

Why is nobody able to Google 'xbox bad blocks'? You can take the time to make a post but not search for it?

ok. i'm sorry but i got one more i hope you all can bear with me. i checked the dumps in 360 Flash Dump Tool and here is what it says in the Bad Blocks Tab.

Note: Bad Block ID 0x0225 [Offset: 0x008D8A00]
Note: Bad Block ID 0x0329 [Offset: 0x00D09200]

--> Block ID 0x0329 found @ 0x3FE [Offset: 0x01077C00]
--> Block ID 0x0225 found @ 0x3FF [Offset: 0x0107BE00]

=== Analyzed successfully =========================

I assume the above analysis means that the bad blocks were moved to the end of the nand (0x3FF)

 

[MightyShots]

The nand is very complicated and can take awhile to understand, try nand healer maybe? Mine says 0 bad blocks but 0x23e ecc error, so gave me more info, maybe you could try it and see if it helps?


Sent from my iPhone 4 using Tapatalk

 

[satans1978]

did you mean "this nand" or nand in general ?...

 

[MightyShots]

Me? I mean all nands lol still quite new with nands, years experiance with firmware, nands not my strongest point


Sent from my iPhone 4 using Tapatalk

 

[Martin C]

ok. i'm sorry but i got one more i hope you all can bear with me. i checked the dumps in 360 Flash Dump Tool and here is what it says in the Bad Blocks Tab.

Note: Bad Block ID 0x0225 [Offset: 0x008D8A00]
Note: Bad Block ID 0x0329 [Offset: 0x00D09200]

--> Block ID 0x0329 found @ 0x3FE [Offset: 0x01077C00]
--> Block ID 0x0225 found @ 0x3FF [Offset: 0x0107BE00]

=== Analyzed successfully =========================

I assume the above analysis means that the bad blocks were moved to the end of the nand (0x3FF)

In other words, your NAND dump is fine.

Don't worry about these. Build your NAND as per normal. If you use multi_builder 0.3 it'll handle them for you.

 

[satans1978]

thanx for taking the time to help out...

 

[satans1978]

ok. sorry but i'm stuck again... wow this is harder than i thought. ok can anyone list the process for which you get your cpu key for RGH on slim mobo ??? it's confusing there is SO many tuts posts and none of them are very specific as to getting the cpu key....

what i'm talking about in particular is the Jtag Tool s/w. if you start with the RGH part of it, you have options to
1.program board
2.dump nand
3.compare two nand dumps.
4.create .ecc
5.write .ecc to nand (and what now ?... i wrote the .ecc and nothing)
Question 1. how does one proceed from this point.

Question 2. which one should be used on slim/trinity 16mb nands ? xell, xellous, xellous-reloaded, or xell-gggggg ??

 

[homelyn]

ok. sorry but i'm stuck again... wow this is harder than i thought. ok can anyone list the process for which you get your cpu key for RGH on slim mobo ??? it's confusing there is SO many tuts posts and none of them are very specific as to getting the cpu key....

what i'm talking about in particular is the Jtag Tool s/w. if you start with the RGH part of it, you have options to
1.program board
2.dump nand
3.compare two nand dumps.
4.create .ecc
5.write .ecc to nand (and what now ?... i wrote the .ecc and nothing)
Question 1. how does one proceed from this point.

Question 2. which one should be used on slim/trinity 16mb nands ? xell, xellous, xellous-reloaded, or xell-gggggg ??

Now start your xbox and copy your cpu key from the screen.

 

[Martin C]

Once again, the dangers of not actually understanding what you're trying to accomplish.

READ.

 

[satans1978]

Once again, the dangers of not actually understanding what you're trying to accomplish.

READ.

i did a few jtags on fats, but this slim process is a bit different and confusing to me... (not the process but the jtag tool, does anyone know of a better tool).... also i wrote the .ecc file and wasn't getting anything on my screen...could it be that i was using HDMI ( i read you have to use video port).... or maybe it was made incorrectly


here is the output when i created the .ecc for my nand does it look right to you guys ??

* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 9188) at 00008000
Found 2BL (build 9188) at 00009ac0
Found 4BL (build 9452) at 000112c0
Found 5BL (build 1888) at 000161e0
* found decrypted CD
* found XeLL binary, must be linked to 1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9188
CB_B: 9188
CD (image): 9452
CD (decrypted): 8453
* decrypting...
* checking if all files decrypted properly... ok
* checking required versions... ok
* this image will be valid *only* for: trinity (slim)
* patching SMC...
CRC32: f9c96639
patchset "Trinity, version 3.1" matches, 1 patch(es)
* patching CB_B...
patchset for 9188 found, 3 patch(es)
* constructing new image...
* base size: 70000
* No separate recovery Xell available!
* Flash Layout:
0x00000000..0x000001ff (0x00000200 bytes) Header
0x00000200..0x00000fff (0x00000e00 bytes) Padding
0x00001000..0x00003fff (0x00003000 bytes) SMC
0x00004000..0x00007fff (0x00004000 bytes) Keyvault
0x00008000..0x00009abf (0x00001ac0 bytes) CB_A 9188
0x00009ac0..0x000112bf (0x00007800 bytes) CB_B 9188
0x000112c0..0x000172bf (0x00006000 bytes) CD 8453
0x000172c0..0x000bffff (0x000a8d40 bytes) Padding
0x000c0000..0x000fffff (0x00040000 bytes) Xell (backup)
0x00100000..0x0013ffff (0x00040000 bytes) Xell (main)
* Encoding ECC, please wait ...
------------- Written to image_00000000.ecc
Press any key to continue . . .

 

[Martin C]

ecc looks ok - how did you program the coolrunner? Are you seeing the green light on it flash periodically?

 

[crash_elite]

EDIT** Never mind, you dont need to write xell, ... i forgot about the ecc file..

 

[satans1978]

ecc looks ok - how did you program the coolrunner? Are you seeing the green light on it flash periodically?

as far as the coolrunner i only see a red power light... (the other light doesn't blink)...and i programmed the coolrunner with trinity1.1.jed in iMPaCT over ltp port... but now when i take the motherboard back to pc, it fails to detect the nand whether it's over usb or ltp ports... i don't know.

i also checked my nand with nand healer, and it states that my CB is not hackable (this doesn't apply to the RGH) right ?

 

[Martin C]

Why run your NAND through NAND healer?

No need whatsoever. Don't complicate an simple process.

Common sense, remember.

 

[satans1978]

ok you're right with the nand healer check but anyhow, i'm still only getting one light on coolrunner, do you think it's a programming problem or connection problem ?

p.s. thanx for all your help.

 

[diaboliq20]

one light - i.e. no green is either down to bad solerding or the CPU_RST placement/length imo

 

[Martin C]

I would definitely check over all your wiring and make sure everything's in the right place. Pics of what you've soldered including wire positions would also help.