ZEPHYR Error 0022 after R-Jtag install

M

MopedMan

Full Member
Apr 29, 2014
31
0
Hey guys,

Posted here before regarding a Falcon, but got annoyed at it and threw it out a window!

So got my hands on a Zephyr and tried again at chipping it.

This time around I used a Flux past, and soldering seemed to have gone better this time. After I intalled the QSB's i tried to power on the console to see if everything worked, and it booted up fine.

I will note that while I was installing the QSB near the HANA chip, I accidentally knocked off the resistor beside the point where the board is soldered. I just bridged it and it worked fine.

I then proceeded the read, create Xell and wrote Xell, but when it came to reading the CPU key, I get error 0022. I have tried both using HDMI and AV cables to project the screen.

The green debug light on the CR4 comes on under certain conditions.

I have since worte the stock NAND back onto the board, but no the console only produces 0022.




What other information can I provide you guys to get this thing rolling again?
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
MopedMan said:
Hey guys,

Posted here before regarding a Falcon, but got annoyed at it and threw it out a window!

So got my hands on a Zephyr and tried again at chipping it.

This time around I used a Flux past, and soldering seemed to have gone better this time. After I intalled the QSB's i tried to power on the console to see if everything worked, and it booted up fine.

I will note that while I was installing the QSB near the HANA chip, I accidentally knocked off the resistor beside the point where the board is soldered. I just bridged it and it worked fine.

I then proceeded the read, create Xell and wrote Xell, but when it came to reading the CPU key, I get error 0022. I have tried both using HDMI and AV cables to project the screen.

The green debug light on the CR4 comes on under certain conditions.

I have since worte the stock NAND back onto the board, but no the console only produces 0022.




What other information can I provide you guys to get this thing rolling again?
Click to expand...
as stated you need to fill out the template , the reason is because you could have bridged solder etc or anything , you should start by removing all that you have soldered then try to boot it , if it still gives error there is a problem on the board , again thats why you need to put pics up because you may have caused the problem
 
M

MopedMan

Full Member
Apr 29, 2014
31
0
I'll have to sort out some proper pictures, only have a camera phone with me at the moment. I'm assuming that the soldering is fine, and I booted the Xbox after I have installed everything, but before I even read the NAND and it was working fine.
 
M

MopedMan

Full Member
Apr 29, 2014
31
0
  • Console Type: Zephyr
  • Programmer Used: JRP v2.0
  • NAND Size: -Unknown-
  • Dashboard version: NXE (Exact dash unknown)
  • CB Version: 4570
  • Screenshot of NAND details from J-Runner:
  • J-Runner log
  • ===================================================
    14 December 2014 09:58:30

    J-Runner v0.3 Beta (6) Started



    Checking Files
    Finished Checking Files
    RGH Selected
    Jtag Selected
    Aud_Clamp Selected
    R-Jtag Selected
    Version: 10
    Flash Config: 0x01198010
    01198010
    Xenon, Zephyr, Opus, Falcon
    CB Version: 4570
    Zephyr
    Reading Nand to C:\Users\C660-28R\Desktop\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\output\nanddump1.bin
    Reading Nand
    Done!
    in 3:26 min:sec

    Reading Nand to C:\Users\C660-28R\Desktop\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\output\nanddump2.bin
    Initializing nanddump1.bin..
    Header is wrong..
    Zephyr
    Nand Initialization Finished
    Reading Nand
    Done!
  • updflash.bin log (if applicable)
  • Image of the CR4 XL
  • Images of close-up soldering to motherboard
  • Detailed Description of the Problem
  • Console is no giving Error 0022. Worked perfectly before, after soldering QSB to board check to see if it still worked and it did. (Knocked off resistor near HANA chip, but bridged points and it booted fine). Read NAND, no issues, all NAND's the same and no bad blocks. Turned on console after writing Xell to get CPU key, and was faced with 0022. Wrote stock NAND back to board, and no boot at all. Either 0022 will show, or green power l.e.d will show and will not go further.
  • Green debug light was flashing every 4-5 seconds, for 1 second at a time, but not anymore.
  • Was the console working before you started: Y
  • Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: N
  • How long is the light on for each time
 
M

MopedMan

Full Member
Apr 29, 2014
31
0
Youll have to wait for that, as my camera can't focus on it.7

Slight update, wrote Xell onto the board again. No RROD when trying to retrieve CPU key. Tried different resistor settings on both the CR4, and a AUD_CLAMP and to no avail. Just have a green power light.
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
just noticed in you log it say header is wrong , not sure but that usualy eans there is something wrong with your nand or its the wrong one , wait for a pro to confirm that
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
MopedMan said:
No, I wasn't aware I should do that. I'm in work now, so a response to that won't be until later.

- - - Updated - - -

Again, I wasn't aware I was to do that, as I didn't see an option?
Click to expand...
sorry my mistake you dont need to with r-jtag only rgh
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
when you get home write your original nand , desolder red wire , then try to boots your board is ok
 
M

MopedMan

Full Member
Apr 29, 2014
31
0
I noticed that too, but this is my first install so thought nothing of it once it said the NANDS were identical, and there were no bad blocks.
 
Taijigamer2

Taijigamer2

VIP Member
Jun 8, 2013
1,292
0
England
briggs01 said:
sorry my mistake you dont need to with r-jtag only rgh
Click to expand...
He will need to desolder 5v wire (red) and turn off Jtag qsb to boot retail. Otherwise the chip will keep resetting the Cpu to try and glitch, the only chips u could leave powered were the old coolrunners because u could set it to PROG. To the Op, u may find it hard to solder the unsoldered point on your jtag qsb as u have soldered it to far left, occluding the DB1F1 point.

Your problem is still glitch related as the jtag qsb doesn't kick in until after a successful glitch. Then u would get E79 error or freeze at logo.

Please post pics of Blue and White wire points, also pics of Stby_clk point/resistor. Have u got a post log of your boot attempt. A damaged Stby_clk can give this error, u may have also damaged the GPU by not repairing Stby_clk properly. A post log of your boot sequence will help show this.
 
  • Like
Reactions: briggs01
You must log in or register to reply here.