New XeBuild and devkit unbricking?

http://www.youtube.com/watch?v=gxY9yodN4CY - internal option

 

Has this been tested? I have a xenon that was given to me so not sure if its a pnet ban or its just a bad flash but either way its useless otherwise so happy to give it a go.

I tried to find a donor nand but not working out and your link no longer works... :concern:

 

I understand your frustration with people wanting hand outs but I have two Dev kits and lots of time on my hands and I would like to ask nicely if you could share some of your knowledge.

From what I understand....

If they are bad flash/corrupt I can simply take a donor nand, rebuild it using a 0000000..... CPU key and that should be enough to boot to a recovery iso?
I am wondering if the DVD drive type and key needs to match the nand but doubt it?
I am 90% sure one of them was a 0022. People have said that they are bricked because the efuses were blown but you have said that does not matter so I am guessing some other form of efuse was blown. When you say we will need hardware are we talking about RGHing it? Maybe create a nand as above then create an ECC using that nand.

Trouble is the timings will be based on the retail units and there retail nands so perhaps also a custom jed file?

I have no problem transplanting chips and so on.

If you could perhaps give me something to start with since I have two boards you can have one of them for helping me out and if there is a fix I will do all the work on both and post one to you that way its not a hand out.

Lastly, Please.....

 

Just been searching about some more and you got stiffed so I doubt you will be in the mood to help anyone out thanks anyways.

 

Just had a look at the the infamous X*K.d*c... so apart from the addition of some small bits of hardware what realy makes the devkit is the rom within the CPU programed/generated on first boot. So for pnet banned units I cannot just grab a xenon retail and swap.

 

And where did you hear this?

For your above questions, put them to the test... If the console was bricked with a fake recovery then the method of fixing it will be different than if it was pnet bricked. The latter requires hardware, the former does not.

 

Someone tits were leaking/selling your HvxDump, guess it was not realy you that got stiffed but the people that bought it..

Anyways, ill just have to wait patiently for someone to offer up a donor nand so I can give that a whirl. Thanks for your responce.

 

Read what the console is POST'ing, it'll offer some insight as to what's wrong with the 0022(most likely pnet bricked) and how you may go about fixing it. Free60 has info on post codes.

-Doom

 

I know my chances are really slim but does anybody have a donor test kit nand for zephyr? I have one but it is very old.

 

Thanks Doom, checked one and its giving me two red lights and secondary error code 0011! Looking here it seems to think the CPU is overheating which is odd since I just booted it. Perhaps a re-flow is in order first?

 

If the cpu's heatsink isn't on properly it can say its overheat right away as a failsafe.

 

Dumped and ran through Degraded...

CB 1940 LDV 0
CD 8453
CE 1888
CF(0) 13599 LDV 14
CF(1) 12611 LDV 13

CB 1940 LDV 0
CD 8453
CE 1888
CF(0) 12611 LDV 7
CF(1) 12625 LDV 8

 

Looks like they might have been fake dumps are retail ye?

 

..........