Rumor: PartnerNet Bricking Kits?

bearkilla has a nand dump, I believe.

 

I think the proper thing to do is just ignore all the posts that want proof. That way we can all go on about our day.

 

Something familiar about that, but i cant quite put my finger on it....


on a side note
and are we positive theres absolutely no way to fix this?

 

Short of getting a new paired NAND and CPU...nope. =(

 

He does not.

 

I think its implied that are always risks the minute you acquire a kit illegally.

 

so i get my testchick on the way and played some arcade. Downloaded also.I noticed in one game graphicissues. Then i played another game. Also some little curious issues. And then i get some error and xdk rebootet. After that three reds.
I have several nanddumps. No luck with that.

 

see now that does sound like a proper rrod

we need error code model please

 

no error code

edit:

but i have dumps before, at bricking and after. Will ask some friend ,
if he can find something.

 

do you have you cpu key?

there must be an error code, i'm not talking about one displayed on screen

do you know how to get it with the eject and sync buttons?

 

Looks like we might be making some progress!

 

i have all, dumps,cpu key.
It was a zephyr 2007.

@ bear
ah k, let me now the trick with eject and sync

 

when your unit is off hold the sync button and while holding it push eject
than push it 4 more times to get the error code
4 lights = 0 3=3 2=2 1=1 so if it looks like 4424 its really 0020

 

also just do a quick compare with total commander on the before/after nand dump

 

Got today a Demo Kit (HDMI Prototype) (no black marked source!) , going not online with it... Done

My God... use your Kit offline... and you have no problems. (i know.. simple)

 

+1

 

ok, so the nanddump isn't helpful. Just some small differnence in the paringdata.
So i will test after work the sync+eject trick to get code.
But i think, there is no future solution to rescue broken kits.

 

wouldnt this be important - and a cause for 0022?

 

where is this pairing data you're talking about located?

 

will ask what location it is.

So, i can just get the code when it Rod.
Then i think i get 4422.

edit:
Unconfirmed: CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP