CR4 XL - Jasper 16MB - Possibly Corrupted CR4?

GodsRTM

Noob Account
Apr 17, 2020
6
1
USA
Hello All, I completed my very first RGH a week ago and all was well until the chip stopped glitching after having the console powered off for 3 days of the week. (No debug LED activity).
So, as expected. I inspected the points, as well as the chip to be sure and all appeared to be fine. I had my console booting in 1-3 glitch attempts before this issue presented itself. Also yes I know the yellow wire has a lot exposed, but that is due to resoldering it to test not for permanent installation. I'd like to add that I do not get any RROD when attempting to boot, CPU gets warm as usual.

The chip was bought Brand New from ModChipCentral by me.

**To be fair, E pad did get lifted pretty easily on the CR4 but since there is a resistor trace visible I did solder to the resistor and all was working fine this way so that couldn't be the issue.**

Here are pictures of the basic wiring, it's a bit messy as I redid the wiring just to be sure but still no debug indicator or successful boot. I also attached J-Runner Log and Screenshot.
I'm very sorry for how large they are, I had my phone in 4K mode, at 10x zoom trying to get the best picture for you.





I did make an XeBuild image a couple of times because J-Runner kept switching back to J-TAG without me noticing but I finally got it right and flashed the correct image. (Console booted Xell within 2 glitches, 0-Ohms , Default dips)
Code:
===================================================
Monday, May 11, 2020 2:43:18 PM

J-Runner v0.7 Started


Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 6754
Jasper 16MB
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 6754
Jasper 16MB
Reading Nand to C:\Users\mmcco\Desktop\JRunner_V0.7\output\nanddump1.bin
Reading Nand
Error: 250 reading block 314
Done!
in 3:21 min:sec

Reading Nand to C:\Users\mmcco\Desktop\JRunner_V0.7\output\nanddump2.bin
Initializing nanddump1.bin..
Jasper 16MB
Jtag Selected
Nand Initialization Finished
Reading Nand
Error: 250 reading block 314
Done!
in 3:21 min:sec

Comparing...
Bad Block ID  0314 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0314 [Offset: 0xCB2800]
Bad Blocks Remapped
Bad Block ID  0314 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 0314 [Offset: 0xCB2800]
Bad Blocks Remapped
Nands are the same
Glitch2 Selected
CR4 Selected
Jasper 16MB Manually Selected
ECC created
Version: 10
Flash Config: 0x00023010
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec

Tip: Load the nand on source to have quicker results.
Scanning.........Connection TimeOut
.
No Xbox Detected
Finished
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Jasper 16MB
Jtag Selected
Nand Initialization Finished
Moving All files from output folder to C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005
Load Files Initiliazation Finished
Clean SMC detected
17559
Started Creation of the 17559 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.21.810
---------------------------------------------------------------
base path changed to C:\Users\mmcco\Documents\JRunner_V0.7\xeBuild
---- { Image Build Mode } ----
building jtag image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17559.0
Console   : Jasper
NAND size : 16MiB
Build     : JTAG
Xell      : power on console with console eject button
Serial    : 111553594005
ConsoleId : 024841321050
MoboSerial: 705643E203499405
Mfg Date  : 09/29/2009
CPU Key   : 070DD23FE877EE34A9028A467EFDAA80
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : C8727E418D6A79623E59439C59A88721
CF LDV    : 25
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005
Image is Ready
Initializing updflash.bin..
Jasper 16MB
Nand Initialization Finished
Glitch2 Selected
Load Files Initiliazation Finished
17559
Started Creation of the 17559 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.21.810
---------------------------------------------------------------
base path changed to C:\Users\mmcco\Documents\JRunner_V0.7\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17559.0
Console   : Jasper
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 111553594005
ConsoleId : 024841321050
MoboSerial: 705643E203499405
Mfg Date  : 09/29/2009
CPU Key   : 070DD23FE877EE34A9028A467EFDAA80
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : C8727E418D6A79623E59439C59A88721
CF LDV    : 25
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005
Image is Ready
Initializing updflash.bin..
Jasper 16MB
Nand Initialization Finished
Version: 10
Flash Config: 0x00000000
Can not Continue
Checking Console..
Version: 00
Wrong Version.
Can not continue
Checking Console..
Version: 00
Wrong Version.
Can not continue
CR4 de-Selected
CR4 Selected
Load Files Initiliazation Finished
17559
Started Creation of the 17559 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.21.810
---------------------------------------------------------------
base path changed to C:\Users\mmcco\Documents\JRunner_V0.7\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17559.0
Console   : Jasper
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 111553594005
ConsoleId : 024841321050
MoboSerial: 705643E203499405
Mfg Date  : 09/29/2009
CPU Key   : 070DD23FE877EE34A9028A467EFDAA80
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : C8727E418D6A79623E59439C59A88721
CF LDV    : 25
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005
Image is Ready
Initializing updflash.bin..
Jasper 16MB
Nand Initialization Finished
Version: 00
Wrong Version.
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Load Files Initiliazation Finished
17559
Started Creation of the 17559 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.21.810
---------------------------------------------------------------
base path changed to C:\Users\mmcco\Documents\JRunner_V0.7\xeBuild
---- { Image Build Mode } ----
building glitch2 image

done! fsroot found ok!
---------------------------------------------------------------
C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17559.0
Console   : Trinity
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : 111553594005
ConsoleId : 024841321050
MoboSerial: 705643E203499405
Mfg Date  : 09/29/2009
CPU Key   : 070DD23FE877EE34A9028A467EFDAA80
1BL Key   : DD88AD0C9ED669E7B56794FB68563EFA
DVD Key   : C8727E418D6A79623E59439C59A88721
CF LDV    : 25
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\mmcco\Desktop\JRunner_V0.7\111553594005
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Version: 10
Flash Config: 0x00023010
Writing Nand
updflash.bin
Done!
in 3:44 min:sec
 

GodsRTM

Noob Account
Apr 17, 2020
6
1
USA
where is ur E (green wire) going to? it should be going to this point
View attachment 16652
also why is jrunner trying to create a freeboot img for a trinity?
also dont forget to select cr4 on when creating nand for jasper. good luck.
J-Runner has it listed as Trinity, Jasper. I noticed it too but when I hit F2 it changed to Jasper. The image was fine, I booted fine and consistantly within the first 4 days of completing the RGH2.

As for the green wire, It's going to a point under the board which was listed as an alternative to that point you listed because that one on this board was mangled when I got it. (eBay :eyeroll: lol) But all was working using this method, I just tried to adjust the postbit jumper and got some quick flashes out of the debug indicator, I think the header for the jumper may be damaged?
 

GodsRTM

Noob Account
Apr 17, 2020
6
1
USA
try reflashing nand by xell n see if that does anything.
Same results when flashing again. No attempt to glitch at all.
I do have a support ticket with ModChipCentral opened and they are trying to help me out because they said it's very rare for a bad one to have slipped through. Which is understandable to me because any mass produced product can have a very minimal defect. I think the postbit jumper for changing between 0ohms, 10ohms, etc is damaged because of how I mentioned the debug indicator flickered when adjusted.


I now realized their return policy isn't in my favor, it was 15 days after delivery which I bought the chip in advance. So I'm 15 days past. I guess continuing their support isn't practical at this point.
 
Last edited:

Jrok96

Senior Member
Oct 12, 2015
119
18
highly unlikely its the chip. especially with the soldering issues you've mentioned. personally i would reflash stock nand / remove power from chip and see if it boots stock before proceeding.
 

GodsRTM

Noob Account
Apr 17, 2020
6
1
USA
highly unlikely its the chip. especially with the soldering issues you've mentioned. personally i would reflash stock nand / remove power from chip and see if it boots stock before proceeding.
Reflashing a stock nand isn't something I understand how to do properly (i guess), haven't seen any clear guides. Because if I do flash either my original nanddump1 or 2, it causes RROD 0022 as I've seen others mention on here when trying. If you know how to flash stock properly or know a guide I'd appreciate it.
I have a Jasper 16MB, I know it's not GPU/CPU related as the chips do heat up when powered on. I've gotten 0022 on Zephyrs with a bad flash.

I've seen people mention a guide by "Martin" but I've been unsuccessful in finding it.