[Trinity] Not booting retail neither glitch on CR4

[tavishor]

Hi,

I have a problem with a Trinity console that I tried to glitch with CR4. Could you please help me with some hints?
Initially I installed with Demon, reading Nand and trying to glitch it, without success. Now the console is not booting retail. I removed the Demon and also CR4 and I re-soldered all the pins for CR4 and using J-R Programmer V2 instead on Demon. I loaded the saved Nand and written back as retail but console is not booting.. ROL on red after 5 seconds. I tried to glitch it once again, without success.
Logs looking like this:

Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Retail Selected
Version: 10
Flash Config: 0x00023010
Writing Nand
nanddump1.bin
Done!
in 3:36 min:sec

Checking Files
Finished Checking Files
Checking Console..
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9231
Trinity
Glitch2 Selected
CR4 Selected
Version: 10
Flash Config: 0x00023010
Writing Nand
TRINITY_CR4.ecc
Done!
in 0:18 min:sec


Version: 10
Press Escape to exit
Waiting for POST to change
Post 03
Post 04
Post 05
Post 06
Post 07
Post 08
Post 09
Post 0A
Post 0B
Post 0C
Post 0D
Post 0E
Post 03
Post 04
Post 05
Post 06
Post 07
Post 08
Post 0A
Post 0B
Post 0C
Post 0D
Post 0E
Post 03
Post 04
Post 05
Post 06
Post 07
Post 08
Post 09
Post 0A
Post 0B
Post 0C
Post 0D
Post 0E




anc continuing cycling .

Thanks in advance!

 

[BrockThunderjam]

Why did you try to glitch it if you got RROD on retail, obviously something is messed up.

Post pics of the board please, especially any area you've soldered to.

 

[tavishor]

Here are the pictures:

CR4XL:


NandX QSB:


Former Demon Pins:

 

[BrockThunderjam]

Few things. Looks like where the CE pad gets soldered to the demon is lifted? Can you tell if its damaged (I dont think it would cause the console to not boot)? There is too much solder on the bottom of the board where the demon wires solder to J2C3.

So am I right in assuming you currently have the CR4 installed with the CR4 ecc written? What switch settings are you using for the CR4? I dont see that in the pictures.

BTW - nice job on taking pics.

 

[Antalpromille]

What secondary error code do you get?

 

[tavishor]

@BrockThunderjam: Could you please help me with some indication in the pictures in order to locate what you told me to check? The only suspicion from my side is related to NandX QSB lower left point from the group of fitth pins (lower one from the 3 pin row) that when I removed the QSB and re-soldered, the solder was melting very hard.. I suspect a massive ground or something because I cannot explain why the melting was so slow..
Yes, I have installed CR4 with ecc written (both on "normal"way and by generating from JRunner folder (Trinity_CR4.ecc), but no difference. The dip switch now in with 4 on.. but I tried multiple combinations with no much difference .
I forgot the picture also the ground wire but it is ok.
@Antalpromille: How could I found it? Since I didn't observed any error code.
Please find bellow also the picture from JRunner when I tried to load the saved Nand from retail image.



Thanks for effort!

 

[BrockThunderjam]

@BrockThunderjam: Could you please help me with some indication in the pictures in order to locate what you told me to check? The only suspicion from my side is related to NandX QSB lower left point from the group of fitth pins (lower one from the 3 pin row) that when I removed the QSB and re-soldered, the solder was melting very hard.. I suspect a massive ground or something because I cannot explain why the melting was so slow..

That pad is ground, which explains the slow melt.

As for what to check, I think you should remove some of the solder from the J2C3 pads where you have big solder blobs on top. If you dont know what I'm talking about look up the demon install pictures and look where the wires solder to.

To get secondary error code hold down the sync button and press eject four times. You will get four sequences of light flashes. 4 = 0, 3 = 3, 2= 2, 1= 1

 

[tavishor]

Ok, super, thanks for hints. I'll try it tomorrow evening, not being in the country today. Yes, I'll clean also that points once again .

 

[tavishor]

I cleaned up that points. Also I tried to find secondary error code. Before pressing the sync button, only the center led is light (on glitch mode). After pressing the sync button, all 4 circular leds are flashing on circle pattern. After pressing eject button, unfortunately I cannot figure out what is the sequence of light flashing since it seems that is similar. How can I determine better which led is not flashing? It should be completely off?
I tried to boot also on retail mode and central led is red after 5 second,but the 4 circular leds are off. When I tried to found out secondary error code the result was 0100 (all 4 leds flashing in the same time, 1 led flash only, 4 leds flashing in the same time, 4 leds flashing in the same time.

 

[MTWallet]

I cleaned up that points. Also I tried to find secondary error code. Before pressing the sync button, only the center led is light. After pressing the sync button, all 4 circular leds are flashing on circle pattern. After pressing eject button, unfortunately I can figure out what is the sequence of light flashing since it seems that is similar. How can I determine better which led is not flashing? I should be off completely? Thanks!

That means that the first and second numbers are "0", keep pushing the eject button for the third and fourth numbers. Then press it one more time and the ring lights should turn off and just the center light will be on again.

Each press of the eject button is a different number like what BrockThunderjam said above, all four leds flashing is a "0", three leds flashing is a "3", two a "2" and one a "1".

 

[Antalpromille]

Secondary error code 0100 means that you probably need a XCGPU reflow or reball.

 

[h1n1viruz]

maybe the blue wire. next to the xclamp, it looks like it was pinched and could be making contact and maybe grounding out.
just a thought.

 

[tavishor]

It might be possible to be an issue with xclamp? It is any possibility to fix it?

 

[tavishor]

And I'm not sure if the secondary error code is right, since on glitch boot is not appear and in retail boot, only the central led is red, not appearing 3 circular flashing leds. It is making sense?

 

[MTWallet]

And I'm not sure if the secondary error code is right, since on glitch boot is not appear and in retail boot, only the central led is red, not appearing 3 circular flashing leds. It is making sense?

So just making sure you are saying that when you try to boot it with a retail NAND image, you get a red center led, but no outer ring lights. And when you load a glitch NAND image it tries to boot but never glitches, and the center led does not come on red.

When installing my DemoN, I had installed an old image from a phat to it just to make sure it would read and write, and when the trinity tried to boot to that image I got a red error light. And I think some of the ring, maybe all was flashing?

Are you sure you are using the retail image you originally read from the NAND?

Does this part of the log mean you are trying to build a retail image and writing that to the NAND?

[SIZE=1][COLOR=#333333]Initializing nanddump1.bin..[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Trinity[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Glitch2 Selected[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Nand Initialization Finished[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Retail Selected[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Version: 10[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Flash Config: 0x00023010[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Writing Nand[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]nanddump1.bin[/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]Done![/COLOR][/SIZE]
[SIZE=1][COLOR=#333333]in 3:36 min:sec[/COLOR][/SIZE]

If you are trying to load your original image, I think you just put nanddump1.bin into the "Load Source" box and then click "Write Nand". You don't have to use the XeBuild portion to put back the original image.

 

[tavishor]

Yes, exactly as you translated . I'm trying to boot the saved retail NAND images (first saved when I previous installed Demon) and I got a center red led (after 4 - 5 seconds) and no outer ring lights. When I tried to glitch, yes, it never glitches and the center leg is blinking green, no outer ring lights and the POST output is continue looping as I posted above. Initially I suspected a problem with Demon and I uninstall it and used instead the J-R Programmer V2, but same result .
Yes, I tried the write the originally saved image (the one saved from Nand).
Yes, I done also the direct load source and write Nand... same result .... I initially suspected that is something wrong with the Nand saved image, but I don't know how to check that.

 

[tavishor]

And yes, coming back to secondary error code, on retail boot, only the central led is red (and no other outer ring led are on). When I press sync+eject (4 times), the following sequence is light, with green lights on outer rings (not red!): all 4 outer ring simultaneous, 1 outer ring (top left), 4 outer rings simultaneous, 4 outer rings simultaneous.
On glitch mode, there is no clear pattern for me to figure out since center led is green, and when I press sync +eject (4 times), the outer rings lights on circular pattern almost all the time.

 

[MTWallet]

Could a solder bridge across the two pads at C3B10 at the tip of the QSB up by R1 cause this? I remember reading a thread about not booting after messing up R3B15 which is the resistor right next to that pad.

 

[tavishor]

Well.. I suspected also this point, being difficult to solder. As far as I seen, the solder point is linked to the resistor? Right? It is a better option to clean up that connection and soldering up directly to the resistor? Or should I use the alternative point FT3N2?

 

[MTWallet]

Well.. I suspected also this point, being difficult to solder. As far as I seen, the solder point is linked to the resistor? Right? It is a better option to clean up that connection and soldering up directly to the resistor? Or should I use the alternative point FT3N2?

The right pad connects to adjacent resistor, but if the pads bridged under the qsb, I don't know what effect that would have, if any. If you want to check the resistor value, I believe it should be 33Ohm.

Don't know about the alt point, and this could all be a wild goose chase, I just remember in my prep for my install I read a thread on here somewhere about that resistor getting messed up and causing a problem.

Here is the thread: http://team-xecuter.com/forums/showthread.php?87478-Possibly-damanged-Trinity-while-trying-to-RGH