Green Light just keeps blinking and won't glitch

aden34

Full Member
Sep 17, 2014
44
8
i installed jrp qsb, got the nand, created a .ecc and flashed to console. i got into xell after about 7-8 glitches, then went ahead and made a new nand with xebuild in jrunner. it would not boot no longer how long i left it there. haven't done anything to change it. messed with the dip switches, even tried a few caps. when i added the caps, it just wouldn't glitch at all

my console is a trinity, also i reflashed to stock nand, then went ahead and created an .ecc again to try and boot into xell, but it is still just not booting at all

maybe some recommendations on certain dip settings that have worked for you?




Console Type: Trinity
Programmer Used: JRP v2.0
NAND Size: 16
Dashboard version: 2.0.17349
CB Version: 9188
Console just keeps trying to glitch. never does. green light keeps flashing. already got into xell first try with no issues. just a 7-8 boot glitch time.
Was the console working before you started: Yes
Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Yes


















the error codes in the beginning were resolved with fixing some solder points. nand reads and writes fine now

Wednesday, May 27, 2015 1:52:34 PM

J-Runner v0.3 Beta (7) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Downloaded *xeBuild/lhelper.xex
Downloaded *xeBuild/xeBuild.exe
Finished Checking Files
Glitch2 Selected
Initializing nanddump1.bin..
Trinity
Nand Initialization Finished
CR4 Selected
Creating Directory C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild\17349\bin
Downloaded *xeBuild/17349/bin/addon.idx
Downloaded *xeBuild/17349/bin/nofcrt.bin
Downloaded *xeBuild/17349/bin/nohdd.bin
Downloaded *xeBuild/17349/bin/nohdmiwait.bin
Downloaded *xeBuild/17349/bin/nointmu.bin
Downloaded *xeBuild/17349/bin/nolan.bin
Downloaded *xeBuild/17349/bin/noSShdd.bin
Downloaded *xeBuild/17349/bin/nowifi.bin
Downloaded *xeBuild/17349/bin/patches_falcon.bin
Downloaded *xeBuild/17349/bin/patches_fat.bin
Downloaded *xeBuild/17349/bin/patches_g2corona.bin
Downloaded *xeBuild/17349/bin/patches_g2corona_WB.bin
Downloaded *xeBuild/17349/bin/patches_g2corona_WB4G.bin
Downloaded *xeBuild/17349/bin/patches_g2falcon.bin
Downloaded *xeBuild/17349/bin/patches_g2jasper.bin
Downloaded *xeBuild/17349/bin/patches_g2mcorona.bin
Downloaded *xeBuild/17349/bin/patches_g2mcorona_WB.bin
Downloaded *xeBuild/17349/bin/patches_g2mcorona_WB4G.bin
Downloaded *xeBuild/17349/bin/patches_g2mtrinity.bin
Downloaded *xeBuild/17349/bin/patches_g2trinity.bin
Downloaded *xeBuild/17349/bin/patches_g2zephyr.bin
Downloaded *xeBuild/17349/bin/patches_jasper.bin
Downloaded *xeBuild/17349/bin/patches_trinity.bin
Downloaded *xeBuild/17349/bin/patches_xenon.bin
Downloaded *xeBuild/17349/bin/patches_zephyr.bin
Downloaded *xeBuild/17349/su20076000_00000000
Downloaded *xeBuild/17349/readme.txt
Downloaded *xeBuild/17349/_glitch.ini
Downloaded *xeBuild/17349/_glitch2.ini
Downloaded *xeBuild/17349/_glitch2m.ini
Downloaded *xeBuild/17349/_jtag.ini
Downloaded *xeBuild/17349/_retail.ini
Creating Directory C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild\common
Downloaded *xeBuild/common/cb_1921.bin
Downloaded *xeBuild/common/cb_1940.bin
Downloaded *xeBuild/common/cb_4558.bin
Downloaded *xeBuild/common/cb_4578.bin
Downloaded *xeBuild/common/cb_4579.bin
Downloaded *xeBuild/common/cb_5770.bin
Downloaded *xeBuild/common/cb_5771.bin
Downloaded *xeBuild/common/cb_6723.bin
Downloaded *xeBuild/common/cb_6750.bin
Downloaded *xeBuild/common/cba_13121.bin
Downloaded *xeBuild/common/cba_13181.bin
Downloaded *xeBuild/common/cba_13182.bin
Downloaded *xeBuild/common/cba_1928.bin
Downloaded *xeBuild/common/cba_1942.bin
Downloaded *xeBuild/common/cba_4562.bin
Downloaded *xeBuild/common/cba_4569.bin
Downloaded *xeBuild/common/cba_4574.bin
Downloaded *xeBuild/common/cba_4577.bin
Downloaded *xeBuild/common/cba_5772.bin
Downloaded *xeBuild/common/cba_5774.bin
Downloaded *xeBuild/common/cba_6752.bin
Downloaded *xeBuild/common/cba_6754.bin
Downloaded *xeBuild/common/cba_7378.bin
Downloaded *xeBuild/common/cba_9188.bin
Downloaded *xeBuild/common/cba_9188_mfg.bin
Downloaded *xeBuild/common/cba_9231.bin
Downloaded *xeBuild/common/cbb_13121.bin
Downloaded *xeBuild/common/cbb_13181.bin
Downloaded *xeBuild/common/cbb_13182.bin
Downloaded *xeBuild/common/cbb_1928.bin
Downloaded *xeBuild/common/cbb_1942.bin
Downloaded *xeBuild/common/cbb_4562.bin
Downloaded *xeBuild/common/cbb_4569.bin
Downloaded *xeBuild/common/cbb_4574.bin
Downloaded *xeBuild/common/cbb_4577.bin
Downloaded *xeBuild/common/cbb_5772.bin
Downloaded *xeBuild/common/cbb_5774.bin
Downloaded *xeBuild/common/cbb_6752.bin
Downloaded *xeBuild/common/cbb_6754.bin
Downloaded *xeBuild/common/cbb_7378.bin
Downloaded *xeBuild/common/cbb_9188.bin
Downloaded *xeBuild/common/cbb_9231.bin
Downloaded *xeBuild/common/cd_12905.bin
Downloaded *xeBuild/common/cd_13181.bin
Downloaded *xeBuild/common/cd_13182.bin
Downloaded *xeBuild/common/cd_1921.bin
Downloaded *xeBuild/common/cd_1928.bin
Downloaded *xeBuild/common/cd_1942.bin
Downloaded *xeBuild/common/cd_4558.bin
Downloaded *xeBuild/common/cd_4562.bin
Downloaded *xeBuild/common/cd_4569.bin
Downloaded *xeBuild/common/cd_4574.bin
Downloaded *xeBuild/common/cd_5770.bin
Downloaded *xeBuild/common/cd_5774.bin
Downloaded *xeBuild/common/cd_6723.bin
Downloaded *xeBuild/common/cd_6754.bin
Downloaded *xeBuild/common/cd_7378.bin
Downloaded *xeBuild/common/cd_8453.bin
Downloaded *xeBuild/common/cd_9231.bin
Downloaded *xeBuild/common/cd_9452.bin
Downloaded *xeBuild/common/ce_1888.bin
Downloaded *xeBuild/common/cf_4532.bin
Downloaded *xeBuild/common/cg_4532.bin
Downloaded *xeBuild/common/xenonclatin.xtt
Downloaded *xeBuild/common/xenonjklatin.xtt
Downloaded *xeBuild/common/ximedic.xex
Finished Checking Files


===================================================
Wednesday, May 27, 2015 1:57:13 PM


J-Runner v0.3 Beta (7) Started




It's advised to run in administrator mode on Windows 8


Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Comparing...
Nands are the same
CR4 Selected
Wrong cpukey
Initializing nanddump3.bin..
Trinity
Nand Initialization Finished
Comparing...
Nands are the same
Initializing nanddump3.bin..
CpuKey is Correct
Added Key to Database
Trinity
Nand Initialization Finished
Load Files Initiliazation Finished
17349
Started Creation of the 17349 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17349.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 452696305105
ConsoleId : 033080581514
MoboSerial: 725655A119720505
Mfg Date : 12/13/2010
CPU Key : 0F4F-----------------------------------------
1BL Key : DD88----------------------------------------
DVD Key : 4D0-----------------------------------------
CF LDV : 13
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
Checking Console..
Version: 10
Flash Config: 0x00000400
Error: 201 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000400
CB Version: 0


===================================================
Wednesday, May 27, 2015 2:26:36 PM


J-Runner v0.3 Beta (7) Started




It's advised to run in administrator mode on Windows 8


Checking Files
Finished Checking Files
Downloaded *xeBuild/17349/_glitch.ini
Downloaded *xeBuild/17349/_glitch2.ini
Downloaded *xeBuild/17349/_glitch2m.ini
Downloaded *xeBuild/17349/_jtag.ini
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x00000400
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000400
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00000400
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000400
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00000400
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000400
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00000800
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000800
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00000800
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000800
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00000800
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000800
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00000800
Error: 001 reading block 0
Error: 001 reading block 1
Error: 001 reading block 2
Error: 001 reading block 3
00000800
CB Version: 0
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 0
Error: 201 reading block 1
Error: 201 reading block 2
Error: 201 reading block 3
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 0
Error: 201 reading block 1
Error: 201 reading block 2
Error: 201 reading block 3
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Initializing nanddump3.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Version: 10
Flash Config: 0x00023010
Writing Nand
nanddump3.bin
Error: 203 writing block 0
Error: 203 writing block 1
Error: 203 writing block 2
Error: 201 writing block 3
Error: 203 writing block 4
Error: 201 writing block 5
Error: 203 writing block 6
Error: 203 writing block 7
Error: 203 writing block 8
Error: 202 writing block 9
Error: 201 writing block A
Error: 203 writing block B
Error: 201 writing block C
Error: 203 writing block D
Error: 203 writing block E
Error: 203 writing block F
Error: 201 writing block 10
Error: 201 writing block 11
Error: 203 writing block 12
Error: 203 writing block 13
Checking Console..
Can not continue
Error: 203 writing block 14
Error: 203 writing block 15
Error: 203 writing block 16
Error: 203 writing block 17
Error: 201 writing block 19
Error: 201 writing block 1A
Error: 201 writing block 1B
Error: 203 writing block 1C
Error: 203 writing block 1D
Error: 203 writing block 1E
Error: 203 writing block 1F
Error: 203 writing block 20
Error: 203 writing block 21
Error: 203 writing block 22
Error: 203 writing block 23




Wednesday, May 27, 2015 2:31:20 PM

J-Runner v0.3 Beta (7) Started






Checking Files
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 0
Error: 201 reading block 1
Error: 201 reading block 2
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 1
Error: 201 reading block 2
Error: 201 reading block 3
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 0
Error: 201 reading block 1
Error: 201 reading block 2
Error: 201 reading block 3
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 0
Error: 201 reading block 1
Error: 201 reading block 2
Error: 201 reading block 3
00023010
Trinity, Jasper 16MB
CB Version: 9060
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Initializing nanddump3.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Load Files Initiliazation Finished
17349
Started Creation of the 17349 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17349.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 452696305105
ConsoleId : 033080581514
MoboSerial: 725655A119720505
Mfg Date : 12/13/2010
CPU Key : 0F4------------------------------------------
1BL Key : DD8------------------------------------------
DVD Key : 4D0------------------------------------------
CF LDV : 13
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
Version: 10
Flash Config: 0x00023010
Writing Nand
updflash.bin
Done!
in 3:53 min:sec


CR4 Selected
Load Files Initiliazation Finished
17349
Started Creation of the 17349 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17349.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 452696305105
ConsoleId : 033080581514
MoboSerial: 725655A119720505
Mfg Date : 12/13/2010
CPU Key : 0F4F-----------------------------------------
1BL Key : DD8------------------------------------------
DVD Key : 4D07----------------------------------------
CF LDV : 13
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
Initializing nanddump4.bin..
Trinity
Nand Initialization Finished
Load Files Initiliazation Finished
17349
Started Creation of the 17349 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17349.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 452696305105
ConsoleId : 033080581514
MoboSerial: 725655A119720505
Mfg Date : 12/13/2010
CPU Key : 0F4------------------------------------------
1BL Key : DD-------------------------------------------
DVD Key : 4D0-----------------------------------------
CF LDV : 13
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105
Image is Ready
Initializing updflash.bin..
Trinity
Nand Initialization Finished
Initializing nanddump4.bin..
Trinity
Nand Initialization Finished
CR4 de-Selected
CR4 Selected
Load Files Initiliazation Finished
17349
Started Creation of the 17349 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.15.709
---------------------------------------------------------------
base path changed to C:\Users\Aden\Desktop\J-Runner v3 (8) Core Pack\xeBuild
---- { Image Build Mode } ----
building glitch2 image


done! fsroot found ok!
---------------------------------------------------------------
C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105\updflash.bin image built, info:
---------------------------------------------------------------
Kernel : 2.0.17349.0
Console : Trinity
NAND size : 16MiB
Build : Glitch (v2)
Xell : power on console with console eject button
Serial : 452696305105
ConsoleId : 033080581514
MoboSerial: 725655A119720505
Mfg Date : 12/13/2010
CPU Key : 0F4F4---------------------------------------
1BL Key : DD8-----------------------------------------
DVD Key : 4D0----------------------------------------
CF LDV : 13
KV type : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to C:\Users\Aden\Desktop\J-Runner v3 (5) Core Pack\452696305105
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:53 min:sec


Initializing nanddump3.bin..
Trinity
Nand Initialization Finished
ECC created
You need an .bin image
Version: 10
Flash Config: 0x00023010
Writing Nand
image_00000000.ecc
Done!
in 0:19 min:sec
 
Last edited:

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension
Can you show us the POST logs?

Try using dip 4 with 10 ohms postbit

Is it me or I don't see the "nands are the same" statement from the jrunner logs?
 
Last edited:

aden34

Full Member
Sep 17, 2014
44
8
Can you show us the POST logs?

Try using dip 4 with 10 ohms postbit

i dont have any post logs in my jrunner folder. also that dip set still wont work. just keeps blinking


this log isnt the full log. its from when the issues started to happen. ill post the previous logs as well. but the nands are the same
 
Last edited:

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension
i dont have any post logs in my jrunner folder. also that dip set still wont work. just keeps blinking


this log isnt the full log. its from when the issues started to happen. ill post the previous logs as well. but the nands are the same
Your OP says you have Jr-prog v2 which can be used for POST monitoring. The feature is called RATER. Here is how to use it.

Solder a wire from the K point on the CR4 to the K point on the QSB:
CR4_TRINITY_1.jpg

Then connect the POST monitoring cable from the Jr-prog to the CR4 (The chip shown is the R-JTAG chip. Still plugs into the same place with the CR4)
8.jpg
Then open J-runner and click CR Pro Rater
dtr.png
 
Last edited:

aden34

Full Member
Sep 17, 2014
44
8
i get device not found in cr pro rater?

edit: nevermind, thought it was plugged in to my computer lol

Code:
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Post 0C - .......... 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Shutdown
 
Last edited:

aden34

Full Member
Sep 17, 2014
44
8
this looks bridged, also your postout and cpu rst wires are to long cut them to fit straight to the points and try dips again with postbit 10 ohms, trinity dips are 3-4 on
its not bridged. just a little something there that was wiped off.

ill cut the wires now and give it another go
 

aden34

Full Member
Sep 17, 2014
44
8

i shortened the wires as much as i could without risking lifting the post out or cpu rst

console booted into xell after about 7-8 boots. turned it off then tried turning it on fully, but does the same thing. tried going back to xell and doing the samething as far as just constantly trying to glitch.

changed the dip switches to 3,4 as well as nothing like it said in that link, still no change


console boots to dashboard!! after 4 boots

kept the dip switch to 3

any other ideas to hopefully get instant boot?


edit: just did 3 only and it went into xell after about 3-4 boots. will try turning the console on fully now
 
Last edited:

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension
The guide says it will explain about dips and Jumpers further in the guide but never does.....
"POSTBIT JUMPERS (P1):

These fine tune the resistor on Postbit. The jumper should be set to 0 Ohms by default. In a very few minor instances a 10Ohm or 100Ohm resistor was required to shape a perfect wave (we're talking 5 out of maybe 100 motherboards - so we added the option for those cases)

"

"
The CR4 XL Board comes with wires and tuning caps 10pf, 22pf, 30pf, 47pf, 68pf, 82pf, 100pf (the caps aren't always necessary but included for those who like to do a monster fine tune). I personally like to use the double shielded pro cables that Xecuter makes because it gives a perfect grounded line so you are guaranteed a clean wave. For less than a couple of bucks it's a no brainer - and i'm sure there are some bundle kits you can buy where it's probably thrown in as a freebie anyway. "


 
  • Like
Reactions: aden34

briggs01

VIP Member
Feb 17, 2013
1,324
0
you have dips 2 and 8 on , try 3 and 4 , default jumper

I have noticed aswell as others on here have had good results with just dip 4 on
 
Last edited:

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension
Offhand any idea where the K solder point is on the motherboard where the QSB connects to?
The K point on the mobo is right above the 5v line
 
  • Like
Reactions: pulse40