JTAG Lost Everything (NAND, CPU Key, and maybe wrong NAND inside)

[sthetix]

Hello, i have a customer who has a JTAG Jasper but he lost everything (no original NAND, no CPU key)and maybe he flashed a wrong NAND and his console get an RROD now.
I flash jasper_hack_aud_clamp.bin to boot xell, but I get error 0022 after +- 30 second. I tested C5D5 i get 1.8 ohm. Is there a way to fix it?

thx

 

[MANUMAN]

Yea find the originand and cpu key that will fix the 0022 error

 

[Martin C]

Yea find the originand and cpu key that will fix the 0022 error

Nope, it won't. This is bad information. XeLL should boot on any JTAG console (or E79 if the wiring is an issue). The OP is getting a 0022 after about 5 resets, which means the bootloader is failing.

OP - please post pics of all soldering/wiring.

 

[sthetix]

Here's the pic Martin..

 

[Martin C]

If U6T1 was bridged before you got it, it may eliminate CB LDV changing. However it may have been done after the fact.

Get a CR3-Pro/R-JTAG and wire up for full post. try to boot with this in place.

 

[sthetix]

ok Martin, suppose the console has been updated to CB 6750/6751 (RGH1), can i still wire R-JTAG to see some information within RATER?
I will try installing an R-JTAG then.
thx

 

[Martin C]

ok Martin, suppose the console has been updated to CB 6750/6751 (RGH1), can i still wire R-JTAG to see some information within RATER?
I will try installing an R-JTAG then.
thx

Unless you know more than you've said, if U6T1 bridge is/was in place there's no reason why the CB would have changed.

POST output will help determine why it's not booting.

 

[sthetix]

ok i will try to R-jtag then.. Some more info : This console is 3 years old dead since 2010 (he kept this console in his garage for 3 years). if it is updated then the CB should be 6750/6751. but since the u6t1 is intact, then CB is not the problem (i am guessing).

If it is not a CB problem, then it maybe bad / dead GPU? or bad/dead hana or southbridge? anyway thanks for the tips Martin, i will post some more info later on.

 

[Martin C]

0022 after 27 secs may be CPU related. POST monitor will provide more information.