XeDK Important information database

If you remove R6T3 or do the bridging method, you will still be able to use recoveries, as XDK's do not burn fuses when updating. The only time an XDK will ever burn fuses is if you malicious XEX executes syscall 22, or if M$ decides to brick your kit.

 

syscall 22 ?
It's not on the sdk documentation,what is that ?

 

syscall info can be found here: http://free60.org/Boot_Process

 

Probably best not to teach people about that, it only promotes malicious activity.

 

Thx inspuration.

 

I know what you mean, but this information is freely available on the internet anyways. If someone wanted to create a malicious xex, it wouldn't take much research.

It's up to the end user to be watchful in what they run on their consoles, and to take appropriate measures to prevent bricking, such as removing R6T3 and grounding the write protect leg of the nand.

 

More tutorials soon, just getting caught up with work. However my next tutorial will be how to properly convert a dev game to retail along with its addon's and tu without patching the xex which usually leads to incompatibility. I'm working with GOD files right now using the SDK which is getting quite tiresome.

 

this tuts works so well my xdk now resists pnet like well any thing and goes into a nice reboot look when ever you try to connect or access a live profile

 

I have never done the write protect mod that was posted, but I know for a fact that removing R6T3 does not cause this to happen. Does this happen for you lllsondowlll?

 

isn't there a file rewritten to the nand every time you connect to 'live'? you probably would have to disable the nand protect switch in the diagram for that to be able to write anything to it.

 

one of two things can be happening.

1. Pnet is trying to brick your kit but the resistors are removed so it only lands a reboot. (In theory)

2. You don't have your write protect on a switch which might explain why you didn't try to turn it off to test anything, you should be safe to turn it off to connect to pnet.

 

Yeah i didn't have my write protection on a switch just had it soldered straight to ground i unsolder it and now works perfect,

 

It should always be on a switch it is a bad idea otherwise you wont be able to run recoveries and such.

 

Updated

 

do dev kit .god make the game cleaner ?

 

What do you mean by "make it cleaner"?

 

It creates a higher chance of running a retail converted game on your devkit as I have discovered recently some game's have issues with the method they are booted from so god files are designed to emulate a game disc so it will usually knock out any incompatibility when ran from the HDD like fable 3 had.

 

Fable 3 has AP2.5 checks in the xex for the 12*** kernal.

 

I am aware, never the less these problems are solved by the method in the tutorial.