BB Jasper Error 0022??

[morinzo]

TX Product(s) used: JrProg v2, CR4
Console Type: Jasper
NAND size: 512mb
Dashboard version: 2.0.16547
CB version: 6754
Was the console working before you started: Yes

Description of problem:
Anyone have any thoughts on why this would be giving error 0022 and the cpu still getting hot as hell on stock nand & chip removed? It was working before I installed the CR4, I read the nand before we knew the CR4 was going to get delayed so my friend told me he was going to take it home and put it in the closet till the chip came because his son was grounded anyway.
Tonight he called me after he got back home and said his son might have got it out while he was at work and we didn't know it. So this is my noob fault for not reading the nand to be sure someone didn't update it from 16547 which is where it was when I made the dumps. I have the 2 matching full dumps & 2 matching 64mb dumps.

I have been searching 0022 here on the forums and I saw where martin said the time it takes to error could help solve the issue, It takes about 28.5sec to error.

I have taken the pll_bypass resistor off and it was 10k, I also took the stby_clk resistor off and measured it to 33ohm.

I have tried to take the best pics that I could so you guys can see everything needed, The pics were taken after I removed and tested the resistors. I'm sorry about all the pics, I just want to try to get one of everything that had been soldered.

Images of close-up soldering to motherboard:

 

[ablegepu]

If it was updated and then you flashed back the original from before then can't you just create the ecc with the one you have then boot to xell and check the fuses in xell to get the ldv right.

 

[morinzo]

If it was updated and then you flashed back the original from before then can't you just create the ecc with the one you have then boot to xell and check the fuses in xell to get the ldv right.

honestly, i'm not sure. I've never had this happen before & I'm hoping it's just something simple like that since the cpu is getting hot.

 

[ablegepu]

Yeah you are having an ldv issue I believe. from the time you got the console back until you got 0022 what have u done?

 

[morinzo]

wrote the 16547 nand that I had And tried to install CR4 & it was acting funny so i flashed back to stock and removed the +5 and discovered the issue.

I know that i should have read the nand again but he promised it had been in a closet and no one had touched it, so this one is my fault & no excuses for not taking the 3min to read the nand again other than being a dumb ass. lol

 

[Antalpromille]

Does it boot xell and/or xebuild image? These two should boot as long as the hardware are ok since they ignore LDV mismatches.

 

[ablegepu]

Exactly. There should be no problem of you just create ecc with the nand you have saved and write it to the console then boot cell and you will have everything you need to create a new retail or xebuild image

 

[morinzo]

Does it boot xell and/or xebuild image? These two should boot as long as the hardware are ok since they ignore LDV mismatches.

With the CR4 installed the dbg led flashes 5 times then it errors to 0022 just like stock..

What error would it give me if the bb nand was corrupt??

 

[BL4K3Y]

I could be wrong, but if you see RROD 0022 after about 28 seconds, the CPU might be toast.

Have you tried writing XeLL to the console's NAND to see if it boots with the CR4 installed?

 

[morinzo]

I could be wrong, but if you see RROD 0022 after about 28 seconds, the CPU might be toast.

Have you tried writing XeLL to the console's NAND to see if it boots with the CR4 installed?

yes I have and xell gives 0022 after 5 glitches, I thought as log as the cpu was getting hot that it was fine..

 

[ablegepu]

The CPU could still be hot and have certain problems I think. I don't really know what to say. What if he just wrote back stock nand and up'd the ldv by 1. That wouldn't work either because it is the 16547 image. Um what if he tried using donor files to build a nand could it be undone afterwards?

 

[gavin_darkglide]

The CPU could still be hot and have certain problems I think. I don't really know what to say. What if he just wrote back stock nand and up'd the ldv by 1. That wouldn't work either because it is the 16547 image. Um what if he tried using donor files to build a nand could it be undone afterwards?

That would work, as long as he got the write ldv, as the CB is still the same. The cb hasnt changed in an update since 15574, so if you have the cpu key, you could build a stock 15574 with the current ldv, and it would boot. not that there would be any reason to do that.

 

[morinzo]

Still trying to figure this one out, is there a way to test the cpu??

Or what should I try next??

 

[nofeloniesyet]

Still trying to figure this one out, is there a way to test the cpu??

Or what should I try next??

if the rrod is round 28 seconds before throwing,its dead cpu.also the fact that it wont even boot xell is a great indicator you have a hardware fault.