ANSWERED No CPU_PLL Error 0022 Need some Advice

G

gamehawk55

VIP Member
Mar 21, 2006
202
33
Canada
www.chaotic-consoles.com
Ok so heres the story.

This is a Jasper 512 that a buddy of mine had been trying to glitch for the last few months and could never get it to glitch so he gave it to me to work on it in my free time to see if I could get it to glitch.

After a few days of trying and no success and trying to much I ended up lifting the CPU_PLL point on the bottom of the board and one of the pads of the resistor beside it. When that happened I tried booting the console to stock retail nand and got 0022. I managed to desolder the resistor, placed a new pad that i got from a rrod xenon I had and replaced the resistor.

Everything seems to be in place properly but I'm still getting the 0022 error on it when i try to boot. I have taken the coolrunner and all wires right out as I'm just trying to get it booting stock again before I wire anything else back in to try again.

Do I need to run a wire from the resistor to the CPU_PLL point on the top of the board in order to repair it and get it booting again or is there something else I can try?. The pics show the original CPU_PLL pad missing and the new pad and CPU_PLL resistor I have put in place.

If someone can lead me in the right direction to get this one booting again I would greatly appreciate it:biggrin:
 
Statecowboy

Statecowboy

BANNED
Feb 23, 2005
713
0
Midwest USA
gamehawk55 said:
Do I need to run a wire from the resistor to the CPU_PLL point on the top of the board in order to repair it and get it booting again or is there something else I can try?.
Click to expand...
Yes you do. I've run into this myself. You'll probably have to remove the x-clamp to access the trace you need to expose (using a fiberglass pen if you have).
 
  • Like
Reactions: gamehawk55
G

gamehawk55

VIP Member
Mar 21, 2006
202
33
Canada
www.chaotic-consoles.com
Statecowboy said:
Yes you do. I've run into this myself. You'll probably have to remove the x-clamp to access the trace you need to expose (using a fiberglass pen if you have).
Click to expand...
Well I completed the circuit between the resistor and the top side CPU_PLL point and the error code changed to 1033 which is just a dashboard error. And I forgot that last time I wrote the nand my graphics driver screwed up right before the end of the nand write so I had to kill it. Writing the original nand back again now (all 512MB of it :facepalm:). Things are looking good:biggrin:

---------- Post added at 20:15 ---------- Previous post was at 20:13 ----------

Best part of it all was that I had already created the alternate point before when I was trying to make it glitch so I just had to solder it:biggrin:. Don't know why I didnt think of that before:facepalm:. Guess I thought that even with the one pad ripped it would still boot. Guess not.
 
G

gamehawk55

VIP Member
Mar 21, 2006
202
33
Canada
www.chaotic-consoles.com
Statecowboy said:
Hopefully you have the original nand. Did you try to boot xell with your CR?
Click to expand...
Oh yeah I had two matching copies of the original nand it was flashing back as I was typing. Xbox is booting back to stock now perfectly. Never could get it to glitch. It's one of those finnicky 512MB 6751CB Jaspers. Thats how I ripped the pad in the first place was continuously re-soldering and desoldering connections to try and make them better to see if it would eventually glitch and it never did.

CR would always glitch like 5-6 times and then just quit. This xbox has been worked on by me and my buddy for the last 6 months and both of us have RGH'ed alot of xboxs already, but this one just WILL not glitch.

Maybe when RGH 2.0 comes it might work (Here's Hoping:p).

But thanks for the tip about re-creating the CPU_PLL with the top side point. Dont know why I never thought of doing that before:facepalm:. But oh well everything is working perfect on stock 12625 now:D. Dont owe my buddy a case of beer anymore lol.
 
You must log in or register to reply here.