RGH RGH NAND will not boot anymore?

[iomega311]

So about a month ago I installed a Rev B Coolrunner, Post_Out QSB, Xecuter PCB 1.1, and a DemoN. Pulled my keys using a DGX.

The Coolrunner is a rev B, and I removed the capacitor used by the phats.

Everything in the install went perfect.
This is a Trinity 250gb console on latest dash, both stock and RGH nands.

When I was done with it all, both the stock NAND and the RGH NAND would boot great. I installed FSD3 on the RGH and have been using it just fine.

I put all my RGH stuff on an external HDD and on an internal MU inside to save games and profiles to. (It doesnt show up in stock, only in RGH)

I was getting random red dot errors when booting stock. Would boot still, but with a red dot error. I checked a post by Bl4k4y and discovered that this happens for random consoles. Is not REALLY a red dot error in the general sense.

It was getting annoying though, trying to boot stock and getting a red dot issue every so often.
I read that the fix seems to be to change the coolrunner away from being on the "Slim" setting over to being on the "Phat" setting.
Has been known to mess up boot times, but that can be adjusted by changing wire lengths, etc.

I opened up my console today and litterally all that I did was lift up my DVD drive, reach under to the switch, and moved from slim to phat. Thats it. I didnt even unplug the DVD drive. I laid it back down and then plugged in my system both to power and HDMI.

I then started it up and the debug light started to flash and the fans reset, just like all should.... except after about 5 minutes, no glitch?

So, I switched it back to slim and then tried to reboot. Doing everything that normally happens... except, no glitch.

I then took out the rest of the screws and pulled the motherboard out of the metal cage.
I then moved the post_out to a new wire length on the QSB, tried booting... etc.

I have not yet been able to get my console to glitch yet? Ever since I moved that switch on the Coolrunner, it has not booted in to RGH at all.

I literally left it attempting to glitch for over 2 hours! This was after I returned the post_out back to where it was before I started messing it with it, and left the switch back on slim, where it was before.

Stock NAND boots just fine. No issues at all. But RGH will not boot.

I hooked up my DemoN to J-runner and I was able to read the NAND from both stock and the the DemoN.

At this point, I don't even care about the red dot issue, at least I could boot my RGH nand. Now I just have a stock Xbox.

Any suggestions as to what may have happened or how I can fix this?

Below are my JR logs from when I installed the DemoN last month as well as pictures that I took today after I put it all back together the way it was working before I played with the CR settings.



J-Runner v0.2 Beta (284) Started

Merry Christmas from Team JR!
Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Nands are the same
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:02 min:sec

XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:02 min:sec

Reading Nand to C:\Users\J-Runner v02 (278) Core Pack\output\nanddump1.bin
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Reading Nand
Done!
in 0:20 min:sec

Reading Nand to C:\Users\J-Runner v02 (278) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Header is wrong..
Nand Initialization Finished
Done!
in 0:20 min:sec

Comparing...
Nands are the same
Comparing...
Nands are the same
Initializing nanddump2.bin..
Nand Initialization Finished
Comparing...
0x0000
0x0001
0x0002
0x0003
0x0004
0x0005
0x0006
0x0007
0x0008
0x0009
0x000A
0x000B
0x000C
0x000D
0x000E
0x000F
0x0010
0x0011
0x0012
0x0013
0x0014
0x0015
0x0016
0x0017
0x0018
0x0019
0x001A
0x001B
0x001C
0x001D
0x001E
0x001F
0x0020
0x0021
0x0022
0x0023
0x0024
0x0025
0x0026
0x0027
0x0028
0x0029
0x002A
0x002B
0x002C
0x002D
0x002E
0x002F
0x0030
0x0031
0x0032
0x0033
0x0034
0x0035
0x0036
0x0037
0x0038
0x0039
0x003A
0x003B
0x003C
0x003D
0x003E
0x003F
0x0040
0x0041
0x0042
0x0043
0x0044
0x0045
0x0046
0x0047
0x0048
0x0049
0x004A
0x004B
0x004C
0x004D
0x004E
0x004F
0x0119
0x022D
0x03A3
0x03A4
0x03A5
0x03A9
0x03AA
0x03DE
Initializing nanddump2.bin..
Nand Initialization Finished
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:28 min:sec

Initializing nanddump2.bin..
Nand Initialization Finished
Reading Nand to C:\Users\J-Runner v02 (278) Core Pack\output\nanddump1.bin
XBOX360
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Reading Nand
Done!
in 0:20 min:sec

Initializing nanddump1.bin..
Nand Initialization Finished
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Nands are the same
Comparing...
Nands are the same

===================================================
Saturday, December 29, 2012 6:17:16 AM

J-Runner v0.2 Beta (284) Started


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

Merry Christmas from Team JR!
Checking Files
Finished Checking Files
sending xsvf to demon...
Done
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Nands are the same
Programming Coolrunner
C:\Users\J-Runner v02 (278) Core Pack\common\xsvf\trinity_en.xsvf
sending xsvf to demon...
Done
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Nand Initialization Finished
* unpacking flash image, ....
Spare Data found, will remove.
Removed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9231
CB_B: 9231
CD (image): 9231
CD (decrypted): 9452
* checking required versions...
ok
* patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3
* Replacing CD...

* XOR HACK NEEDED FOR CB 9231
File C:\Users\J-Runner v02 (278) Core Pack\common\CB\CB_B.9231.bin not found!
Failed to open CB_B.9231.bin
Programming Coolrunner
C:\Users\J-Runner v02 (278) Core Pack\common\xsvf\trinity_en.xsvf
sending xsvf to demon...
Done
* unpacking flash image, ....
Spare Data found, will remove.
Removed
* f TimeOut
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Users\J-Runner v02 (278) Core Pack\115704304605\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 115704304605
ConsoleId : 030390599187
MoboSerial: 725625A125330465
Mfg Date : 11/11/2010
CPU Key : xxxxxxxxxxxxxxxxxxxxx
1BL Key : xxxxxxxxxxxxxxxxxxxx
DVD Key : xxxxxxx
CF LDV : 7
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\J-Runner v02 (278) Core Pack\115704304605
Image is Ready
Current: DemoN
Switching to XBOX
Success
Current: XBOX
Switching to DemoN
Success

===================================================
Saturday, December 29, 2012 6:42:32 AM

J-Runner v0.2 Beta (284) Started



===================================================
Saturday, December 29, 2012 6:43:52 AM

J-Runner v0.2 Beta (284) Started


Merry Christmas from Team JR!
Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Nand Initialization Finished
Comparing...
Nands are the same
Load Files Initiliazation Finished
16202
Started Creation of the 16202 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.06.555
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
C:\Users\J-Runner v02 (278) Core Pack\115704304605\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : 115704304605
ConsoleId : 030390599187
MoboSerial: 725625A125330465
Mfg Date : 11/11/2010
CPU Key : xxxxxxxxxxxxxx
1BL Key : xxxxxxxxxxxxxx
DVD Key : xxxxxxxxxxxxxxxxx
CF LDV : 7
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to C:\Users\J-Runner v02 (278) Core Pack\115704304605
Image is Ready
DEMON
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:28 min:sec


Sorry for the overload on pictures, I just want to make sure everything that I have soldered is here to see how to fix this.

The white wire is running to an LED on my ROL board to an LED to indicate glitch attempts.

This shows where I had to solder to the pin where the rev B doesnt have a CR_EN point.

 

[TilVl]

I would ditch the. Shielded cable. Use the blue wire.

Sent from my SGH-T999 using Tapatalk 2

 

[iomega311]

I would ditch the. Shielded cable. Use the blue wire.

Sent from my SGH-T999 using Tapatalk 2

K, i've ditched the sheilded cable and have replaced it with a short piece of wire and so far have tried half of the points on the QSB and thus far no glitch... i'll keep going though. I'm giving them all plenty of time to glitch.

 

[XEX DriZzy]

Not that this is your problem, but those links I first sent you had the post qsb installed too. Have you thought about ditching that qsb and just using wired connection? However, removing that qsb incorrectly could result in a lifted pad or trace. It is just a suggestion.... but I would not do it if you don't have much soldering skills. Maybe try cleaning up that coolrunner soldering too. If you can try to get your points to look like this: http://gyazo.com/9fb294baf434d674be42eac0e9b2f1b5

 

[WNYConsoles]

The ground wire on your coax is too long, shorter the better. I have noticed longer ground cause odd glitch pulses and delays.

I myself usually start with XClamp wiring then if that is not up to par or there are issues I will move to coax ungrounded with POST_QSB, then coax grounded if absolutely necessary.

Grounded COAX will also fix DemoN retail red dot bug too.

 

[iomega311]

Ok, no matter what wire length I tried... nothing was working.
I have a spare rev B CR. I removed the one that I had installed and put the new CR on, then flashed it, wrote the xsvf file for the DemoN, used my stock NAND and built a new image then flashed it over. Am using just a regular wire for post_out, but am still using the QSB as I don't want to desolder that and risk lifting a pad... I do have flux and a soldering braid, but I just don't want to risk it.

It is now booting within 1 to 2 cycles.

But now I am back to the red dot issue.
grrr.
If I switch to Phat on the CR, then no red dot.
If I switch to Slim, then I am back to red dot about 80% of the time.

On the Phat setting, it will not glitch.
I'm about to call it quits and just deal with the red dot.
It seems like on the slim setting that when booting stock the fans brefly reset at the very moment that the power is given, then they quit. That's what is causing this red dot... I think another member pointed that out already.

 

[gavin_darkglide]

Just looking at the pictures i noticed that your coolrunner has a white switch, and if i read correctly this is one of the indicators that that is a clone coolrunner..... i could be mistaken, but you might want to look into this, the clones are not supposed to be as good.

 

[LoneWolf913]

Just looking at the pictures i noticed that your coolrunner has a white switch, and if i read correctly this is one of the indicators that that is a clone coolrunner..... i could be mistaken, but you might want to look into this, the clones are not supposed to be as good.

Whoever started this 'white switch is a clone' crap needs to be chewed out. Not going off on you or anything, just putting it out there, I have received GENUINE TX Coolrunners from XConsoles and VGCRepairs, with white Nor-Prg switches, and (recently, at least) serials that validate just fine on the serial checker. So no, a white switch does not mean it's a clone. They may have been referring to a white 'Phat-Slim' switch, to the best of my knowledge all TX CRs use black for that switch, at least I've never in my career seen a white 'Phat-Slim' switch except on a clone.

 

[socalbill]

Whoever started this 'white switch is a clone' crap needs to be chewed out. Not going off on you or anything, just putting it out there, I have received GENUINE TX Coolrunners from XConsoles and VGCRepairs, with white Nor-Prg switches, and (recently, at least) serials that validate just fine on the serial checker. So no, a white switch does not mean it's a clone. They may have been referring to a white 'Phat-Slim' switch, to the best of my knowledge all TX CRs use black for that switch, at least I've never in my career seen a white 'Phat-Slim' switch except on a clone.

I have bought over 150 Coolrunners from xconsoles, and only the first coolrunners had white switches on Nor-Prg. Rev B and Rev C had black Nor-Prg switches on every single one that I have bought. I bought a batch today, and I will see if that trend continues when I receive them on Saturday.


Edit: Glad you got it working OP! And as a follow up to my post...20 Rev C Coolrunners delivered from Xconsoles yesterday, 20 black switches. http://i1083.photobucket.com/albums/j398/socalbilljtag/IMG_0864_zps3c97d4ab.jpg

 

[iomega311]

I currently have 2 Coolrunner rev B's... both were purchased from Modchipcentral. And both have white switches. Granted, I bought these over a year ago... I am pretty sure that Modchipcentral is selling legitimate TX Coolrunners.

Anyway...

I tried 3 different wire types tonight and now have it booting within one to two cycles and best of all NO RED DOT anymore!!!

I tried the standard blue wire wrapped tightly across the x-clamp's opposite corners, then just soldered directly to the post_out point and bypassed the QSB (still left the QSB attached) and got it booting within 3-5 cycles, every now and again within 2 cycles.

Also tried removing the coax cable and replaced it with a short wire that soldered from the CR to the post_out QSB. Using the shortest 2 lengths, I had it booting within 2-6 cycles...

Then I took WNYConsoles advice with the coax and shortened the ground. I then attached it to the 2nd shortest point and am now glitching within 1 to 2 cycles consistently. Either it was the new CR plus the shortened ground, reflashing the NAND to the DemoN, or a combo of them all... but either way, no red dot anymore. Am using the slim setting on the CR, and am glitching very fast now.

Thank you for all of your advice, tips, etc... It took most of the day and away from my homework time, but who wants to study Linux when there are Xbox's to toy with?

Thanks again!