DGX Trinity not glitching with DGX

nickwood

Junior Member
Jun 11, 2011
15
0
Belgrade
Hi all,

I have funny problem with one Trinity 15574, trying to extract key with DGX.

I dumped NAND, got one error on Bad Block ID @ 0x0111 [Offset: 0x466200]

Below is JRunner log, when loading those nands.

Trouble which Trinity gives me goes like this>

When flashed with DGX ecc, there is no green light on DGX blinking, and Xbox fan makes repetitive clicking sound.

When flashed with below dumped nand, after 2 seconds on, Xbox shows red light. Also, when flashing dumped stock nand back, it always has Error: 202 writing block 111

Can someone somehow at least fix proper stock nand from this I have, or eventually tell me what to do with troublesome Trinity and DGX combination?

Nand dump> https://www.dropbox.com/s/uayod774iwi2df1/nanddump1.bin

Thanks

Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Bad Block ID @ 0x0111 [Offset: 0x466200]
Bad Block ID 0111 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0111 [Offset: 0x466200]
Bad Blocks Remapped
Bad Block ID @ 0x0111 [Offset: 0x466200]
Bad Block ID 0111 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0111 [Offset: 0x466200]
Bad Blocks Remapped
Nands are the same
Version: 03
Flash Config: 0x00023010
Writing Nand
nanddump1.bin
Error: 202 writing block 111
Done!
in 1:59 min:sec

Version: 03
Flash Config: 0x00023010
Writing Nand
TRINITY_DGX.ecc
Done!
in 0:09 min:sec

Edit>
To add, DGX is ok, not malfunctioning, it dumped key from 7 more consoles after this issue with trinity.
 
Last edited:

nickwood

Junior Member
Jun 11, 2011
15
0
Belgrade
No, with retail nand (with those errors always showing), and with removed DGX, Xbox does not boot, after two seconds shows red light.
 

nickwood

Junior Member
Jun 11, 2011
15
0
Belgrade
I don't have install, I removed everything.

What I understood is that when I dumped original nand, soldering was probably sh*tty and bad block @111 is causing all this mess.

Can this be mended somehow?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I don't have install, I removed everything.

What I understood is that when I dumped original nand, soldering was probably sh*tty and bad block @111 is causing all this mess.

Can this be mended somehow?
Did you bother to read up on 360 NAND bad blocks before posting?
 

nickwood

Junior Member
Jun 11, 2011
15
0
Belgrade
To be honest, I did not. Main reason for that is remapping of Bad blocks that Jrunner does. But I get something is not so automatic as it should be, so I get error writing dumped nand back.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Read the log again. J-Runner hasn't remapped anything.

While you're in reading mode, I suggest reading up on bad blocks on the free60.org site. This will answer all your questions.
 

nickwood

Junior Member
Jun 11, 2011
15
0
Belgrade
Ok, being noobish, maybe.

Per this log below, it says that bad blocks are remapped. What am I doing wrong, and better question, can I fix my nand somehow? :)

Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Bad Block ID @ 0x0111 [Offset: 0x466200]
Bad Block ID 0111 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0111 [Offset: 0x466200]
Bad Blocks Remapped
Bad Block ID @ 0x0111 [Offset: 0x466200]
Bad Block ID 0111 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0111 [Offset: 0x466200]
Bad Blocks Remapped
Nands are the same