Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Razkar]

The HC.org team is proud to make today with the help of spainsellers.com the review of the lastest baby from Team Xecuter : The DGX 1.0s.

What is it for ?

This tool is a hardware solution to get the CPUkey of your xbox (only for slim consoles currently) regardless of the dashboard version. So with this, you will be able to glitch the xbox slim console with a dashboard 15572 (or higher, it also works on lower dashboard versions!).

This chip is preprogrammed and reusable, indeed once you get the key, you can remove it and perform a classic RGH with your favourite chip

Package content :
The DGX package include the following elements :

- a double sided adhesive tape
- Wires.
- The DGX chip.

Instuctions :

• Prepare the console :
  

Dumping the nand :
Use your favourite USB SPI to dump your console nand twice and be sure they match



Write the ECC :
- In Lastest J-runner and on the advanced tab click on Write DGX



Press yes to confirm you already have a nand dump of your console (of course if you don't already have one, make a correct dump...) and choose your motherboard revision (in my case it's a trinity).





Now check the image was properly written.

• Solder the DGX chip
  

Use the official diagram to solder the DGX.

For this test we used a Trinity and we get the result by using :
For POST_OUT : a thick 70cm cable to the regular POST OUT point.
For CPU_RST : a thin 5 cm wire to the alternative CPU_RST point (right pad of R4D4).
DIP : 1-8 OFF





If you succeded you should see XeLL appear and be able to grab the key directly or by the network


For Corona V1-V2 we recommand to use :
For POST_OUT the yellow cable given with the package
For CPU_RST : 12.5cm of the Blue cable
DIP : 1-7 OFF ; 8 ON (you can also try ALL set to ON position)
(PS : XeLL works on most corona motherboard using HDMI, but with some rare consoles XeLL will not output anything so you will have to use this alternative ECC).

For Corona V3-V4 we didn't succeed to glitch it yet
But we still recommend to use the TX Post Fix Adapter which is a very SAFE solution to get a POST OUT access. We DO NOT recommend to solder directly under the CPU.



Conclusion :

Positive :
- Only solution on the market for slim with a dashboard 15572+.
- Price : Around 30€ for the package with which you will be able to use on many consoles (you don't have to leave it in the console).

Caveat :

- The glitch success (specially on Trinity) can probably be improved (a method which will work on a console might not work on another ...). DGX wiring needs in most cases a lot of testing before you get it to glitch (boot).

Thanks :

Thanks to spainsellers.com for their sample.
Thanks to BlaCKat.

[Juggahax0r]

Nice I see the use of R4D4 rst point has caught on ... I first saw it in the official forums , worked nicely for me as well. I haven't done any Corona but the 2 Trinities were completely different , one didn't need any special tweaking and it booted in 2 min ... The second 1 I spent 5 days fighting with until someone released the 70CM POST wire fix, and that worked for me.
Thanks Raz

[Razkar]

The second 1 I spent 5 days fighting with until someone released the 70CM POST wire fix, and that worked for me.

Same for me ... endless hours of testing :/
But finally with the 70cm + r4d4 it worked fine on 3 trinity =)

[LordX]

Same for me ... endless hours of testing :/
But finally with the 70cm + r4d4 it worked fine on 3 trinity =)

So boot time is not good as they say, like 1-3 Glitches...
70cm on POSTout trick, it works after how many glitches ? stable ?
DGX can boot freeboot as coolrunner ? or only ECC ?

[Swizzy]

So boot time is not good as they say, like 1-3 Glitches...
70cm on POSTout trick, it works after how many glitches ? stable ?
DGX can boot freeboot as coolrunner ? or only ECC ?

The DGX chip isn't meant to be used as a permenant glitch chip, infact, it won't work with the methods currently done, the reason for this is because of the bootchain encryption, each bootloader is encrypted in the current methods just like they should be, however the DGX glitches when CB_A is trying to decrypt CB_B and once more to make it accept it even tho it's not valid therefor the DGX won't work for a permenant install, etheir way once you have your cpukey you can easily rebuild the bootchain to the older version which is glitchable using the old "normal" glitches