What's new

Solved Need help with trinity rgh given to me. No original nand nor key and Won't boot to anything. Bricked, I assume.

S

Sorb_Effectzz

Newbie
Messages
3
Reaction score
0
Hey guys, this is my first thread on this site. I was given a bricked(I believe its bricked) trinity rgh by a friend who just recently moved out. It was taken apart(everything is here, though. Not the hdd, however), and had the soldering for everything and the jr programmer "already set"(I'll explain in a bit). He even left me a jr programmer v2. When powered on, nothing shows up on the screen, only the solid green console led(with the dvd drive connected: blinking green led without it), and the coolrunner attempting to flash, with the green led turning on and off every few seconds or so, as it normally would when glitching. I have left it on for an hour or so, with no luck. The jr programmer nand cables are soldered on, but seem very messy. However, as bad as it seems, he explained it still read and wrote to the nand properly(which I was able to partially verify by using the '?' to find its nand type, as well as gently using force to test if they would come off. They didn't), and that he flashed a donor nand because he didn't have any original files(nand(dump)/ keys), before giving it to me because he bought it years ago and bricked it almost two weeks ago. He explained that xell won't even boot up now. No output, even with the av and different monitors/ tvs. He said he believed I could fix it, thus the reason it was given to me to keep. I have already an rgh jasper, which I have all files for, but this is a trinity. I have worked with rgh before, but this is different and new to me. Any help will be appreciated. I will post pictures/ videos after I get my phone charged. I want to fix it in order to give it to my cousin, and his brothers and parents, who live almost in poverty, with no entertainment, only a tv, with no cable nor wifi. They can't(don't either) go outside now because of the pandemic.

Thank you. Again. Any help to get this working will be deeply appreciated.

Pictures: I got the pictures. I had to use one of my friend's iPhone because they have good quality.

Link to my google drive folder with the pictures-
[Click here to view this link]

I assume the soldering is at fault here?
 
Last edited:
C

Classified Life

Enthusiast
Messages
43
Reaction score
2
If it won't boot Xell, that is the first thing you should work on fixing otherwise the system is ****ed. Try flashing it with a xell image. If you get it booting to Xell then you can build a nand for it.
 
C

Cryptic7s

Enthusiast
Messages
379
Reaction score
48
It's an RGH2 Trinity. By the sounds of your post your friend flashed the Donor nand, then didnt follow anymore of the topic to rebuild his nand. First thing I would do would be to tidy the wiring up on the JR Programmer v2 nand cables, then follow this guide:


xtracted Nand Files Download

UnHidden Content:
[SIZE=medium]XENON[/SIZE]
[SIZE=medium]ZEPHYR[/SIZE]
[SIZE=medium]OPUS/FALCON[/SIZE]
[SIZE=medium]JASPER SB[/SIZE]
[SIZE=medium]JASPER BB[/SIZE]
[SIZE=medium]TRINITY[/SIZE]
TRINITY No FCRT
[SIZE=medium]CORONA[/SIZE]
[SIZE=medium]CORONA 4gb[/SIZE]




  • [SIZE=medium]Next you need to solder/plug in your nand programmer wires onto the motherboard [/SIZE]
  • [SIZE=medium]Open J-Runner app an click on "show working folder" button located at the bottom right[/SIZE]




  • [SIZE=medium]Open the folder name "data" located inside /J-Runner/xeBuild/ folders[/SIZE]

  • [SIZE=medium]Open your extracted nand files folder and copy and paste KV.bin, SMC.bin, smc_config.bin and fcrt.bin(if required) to data folder. It should look like this.[/SIZE]

[SIZE=x-large][/SIZE]


  • In J-Runner, copy and paste this cpu key F37C0CD50B928F4E67614ACD548A4E49 in the cpu key section.

  • Choose dashboard version according your hack type (for JTAG choose 7371 - for phat rgh1 choose 14699 - for R-JTAG choose 15574 - for phat RGH2 choose 14719 - for slim choose anything above 14719)

  • Select your motherboard nand type.

  • Select retail as your image type.

  • In J-Runner under the Advanced tab click on Create an image without nanddump.bin





  • Then you will be ask to enter LDV just enter any number between 1 and 80 and click ok.






  • At this point the dummy image should be successfully created and automatically loaded in the "Load Source" section.

  • Now with your nand programmer properly connected to both you pc and motherboard click on "Write Nand".

  • Wait until J-Runner is finish writing the nand and select your "hack type" then click on "Create ECC" for rgh machine or "Create Xell-Reloaded" for JTAG/R-JTAG machine.

  • Now click on "Write ECC" or "Write Xell-Reloaded" depending on your hack type[SIZE=11pt].[/SIZE]








  • You are now ready to boot xell and recover your cpu key.

  • Disconnect the nand wires from the nand programmer and Power ON your console and wait for xell to boot.
  • .
  • Once xell as booted write down your cpu key, fuseset 02 and fuseset 07/08.






Understanding and calculating LDV's
  • Calculating CF/CG ldv is fairly simple. Just count the number of "F" in fuseset 07 to fuseset 11. So in the example above we have a cf/cg lock down value of 2.

  • Calculating CB LDV can be a little bit more trickier. You have to take the right-most "F" and calculate how many character it is from the left. In the example above the right-most "F" is 5 characters from the left so we have a cb lock down value of 5.

  • [SIZE=11pt]Understanding CB LDV; Quote from Martin C @ TX [/SIZE]

  • [SIZE=11pt]This value is NOT updated every dashboard version and is not directly reflected in any apps. However, the value can be translated to a CB/dashboard version. You cannot 'edit' your image to use a different CB for a retail NAND. It MUST match the entry as found in XeLL, otherwise it'll fail to boot.[/SIZE]

  • The example above is from a Jasper with a cb ldv cseq of 5, remember that this value can be translated to a dashboard version. So by looking at the chart below we can determine that dashboard 7371 would be the highest compatible version for this particular console.





[SIZE=x-large]Step 2; Building the fake OG nand image[/SIZE]


  • Now back in J-Runner, enter your cpu key in the cpu key section.

  • Select your dashboard according to your CB LDV cseq

  • Select Retail as Image type.

  • Select Motherboard nand type.

  • Click on the "Advanced" tab and on "create an image without nanddump.bin"






  • You will be ask for LDV, this is the cf/cg LDV so you enter what you have in fuseset 07/08 and click "OK".





  • You have now created a fake original nand image. Even though you won't be able to boot your console with this image it would still be a good idea to keep it somewhere safe.

  • With your new image loaded in the "Load Source" section and your cpu key in the "Cpu Key" section click on the "kv info" tab. You will notice that the info in there are obviously not from your console. So now would be a good time, for those who can, to extract your dvd drive key and patch the key vault with the appropriate dvd key.

  • Click on the "XB Settings" tab, click on "Advanced XeBuild Options", paste your dvd key in the "dvdkey" section, click "OK" then click the "Use Edited Options" check box.

  • For DG16D5S and DLN10N owners; the easiest and cheapest way to make your dvd drive functional would be to install a TX LTU 2 pcb.




Final Part; Building/writing the hacked image



  • Back in J-Runner, with your new fake original nand image loaded in the "Load Source" section and cpu key in the "Cpu Key" section select hack image type(Jtag - rgh - rgh2 - r-jtag), select your desired dashboard(should be the latest which is 17150 at the moment), select motherboard nand type. You can also edit dashlaunch and xeBuild options at this point.

  • Click on create xeBuild image. You will see 3 or 4 warning messages poping up which will ask you if you want to delete kv.bin, smc.bin, fcrt.bin and smc_config.bin. Click yes on all of them.



  • With your nand programmer properly connected to both your console and pc click on "Write Nand"

  • Disconnect nand wires, Boot your console and have fun.
Tut taken from XPG, follow that and you should get the console booting normally again, from there i'd swap the Rev C for an Ace v3 and do an S-RGH Install for those InstaBoot timings. Hope this helps bud!
 
Top Bottom