FuZiioN1337 wrote Recently Just came across this text Document,

LINK: [ Register or Signin to view external links. ] a s t e b i n .com/QKc7SX4e (DELETE THE SPACES!)

What do you guys Think of It? Please POST your Opinions Down Below! Legit?

Thanks everyone!

That is exactly right! Please tell us more.....

Baisically my thought after reading that is get an xbox that is not jtagged and go on the lastest dash then dump the nand extract the xam.xex and compare the files. Changing the values of the jtag xam to match a retail nand

SiniSt3rCirCuS wrote Baisically my thought after reading that is get an xbox that is not jtagged and go on the lastest dash then dump the nand extract the xam.xex and compae re the files. Changing the values of the jtag xam to match a retail nand

i will save you the time, and tell you that they will be identical. Freeboot doesn't mess with is lol....if you try to edit the xam, you get a nice E-79 message, hence the reason for kXAM.patch

Ignore this post, not worth my time explaining and the user below explained stuff well.

Everyone always misses the point on this argument.

You don't replace a file with a retail copy. That would be stupid, as stated above.

The idea is to look as legit as possible. MS can't scan EVERY single bit and byte you have on every startup, especially from some remote server. So, if your NAND, and other files can match the rough checks (partition alignment sorta stuff, basic easy to read signs. Doubt / not sure if these are what's checked, just what I would look for)

The next part is simple enough to talk about. MS can't calculate Checksums and read your actual NAND contents (and if they can read certain parts, it can't be quick but your console can. You XBOX360 console is going to calculate checksums, than send them to MS. Bad checksums, hashes, etc. = ban. Hex-edit in some override code to send MS a proper retail checksum or hash or whatever they use and bam. You're 1 for 1. Do this for every check, and you have a dashboard online. Game launching, etc. is a similar process.

This is by no means a perfectly accurate or detailed tutorial, but this is a conceptual writing. Everyone argues about the methods used when its obvious. Not many other methods (or any at all) make sense, and are just some kid with no computer knowledge say "HERPA DERP PUT A DEVKIT AND A RETAIL AND A JTAG AND MY PENIS TOGETHER TO GET JTAGZZZ ONLINE"

So guess what, if you start reverse engineering the NAND, executable, and boot processes (the latter of which you can find plenty of documentation on), find out what needs to be spoofed, set up a custom flash to match the partition alignments (I actually think block offsets would describe this better, since the NAND isn't really setup as partitions, even thought the concept of the filesystem fitting how it should matches.) you can get online.

Gunstar wrote Everyone always misses the point on this argument.

You don't replace a file with a retail copy. That would be stupid, as stated above.

The idea is to look as legit as possible. MS can't scan EVERY single bit and byte you have on every startup, especially from some remote server. So, if your NAND, and other files can match the rough checks (partition alignment sorta stuff, basic easy to read signs. Doubt / not sure if these are what's checked, just what I would look for)

The next part is simple enough to talk about. MS can't calculate Checksums and read your actual NAND contents (and if they can read certain parts, it can't be quick but your console can. You XBOX360 console is going to calculate checksums, than send them to MS. Bad checksums, hashes, etc. = ban. Hex-edit in some override code to send MS a proper retail checksum or hash or whatever they use and bam. You're 1 for 1. Do this for every check, and you have a dashboard online. Game launching, etc. is a similar process.

This is by no means a perfectly accurate or detailed tutorial, but this is a conceptual writing. Everyone argues about the methods used when its obvious. Not many other methods (or any at all) make sense, and are just some kid with no computer knowledge say "HERPA DERP PUT A DEVKIT AND A RETAIL AND A JTAG AND MY **** TOGETHER TO GET JTAGZZZ ONLINE"

So guess what, if you start reverse engineering the NAND, executable, and boot processes (the latter of which you can find plenty of documentation on), find out what needs to be spoofed, set up a custom flash to match the partition alignments (I actually think block offsets would describe this better, since the NAND isn't really setup as partitions, even thought the concept of the filesystem fitting how it should matches.) you can get online.

someones had there weetabix

nice man that could make sense but will it work

Gunstar wrote Everyone always misses the point on this argument.

You don't replace a file with a retail copy. That would be stupid, as stated above.

The idea is to look as legit as possible. MS can't scan EVERY single bit and byte you have on every startup, especially from some remote server. So, if your NAND, and other files can match the rough checks (partition alignment sorta stuff, basic easy to read signs. Doubt / not sure if these are what's checked, just what I would look for)

The next part is simple enough to talk about. MS can't calculate Checksums and read your actual NAND contents (and if they can read certain parts, it can't be quick but your console can. You XBOX360 console is going to calculate checksums, than send them to MS. Bad checksums, hashes, etc. = ban. Hex-edit in some override code to send MS a proper retail checksum or hash or whatever they use and bam. You're 1 for 1. Do this for every check, and you have a dashboard online. Game launching, etc. is a similar process.

This is by no means a perfectly accurate or detailed tutorial, but this is a conceptual writing. Everyone argues about the methods used when its obvious. Not many other methods (or any at all) make sense, and are just some kid with no computer knowledge say "HERPA DERP PUT A DEVKIT AND A RETAIL AND A JTAG AND MY **** TOGETHER TO GET JTAGZZZ ONLINE"

So guess what, if you start reverse engineering the NAND, executable, and boot processes (the latter of which you can find plenty of documentation on), find out what needs to be spoofed, set up a custom flash to match the partition alignments (I actually think block offsets would describe this better, since the NAND isn't really setup as partitions, even thought the concept of the filesystem fitting how it should matches.) you can get online.

This is getting closer like I said in my post the method is "SIMPLE"

FuZiioN1337 wrote Recently Just came across this text Document,

LINK: [ Register or Signin to view external links. ] a s t e b i n .com/QKc7SX4e (DELETE THE SPACES!)

What do you guys Think of It? Please POST your Opinions Down Below! Legit?

Thanks everyone!

everyone already knows that security checks have to be patched. the problem is that no one has the knowledge to do it (non techies i mean). it takes allot of studing the dashboard code in idapro. then you have to change code to provide correct replies to server checks. this is not easy and would take allot of kvs until you get it right. so quit thinking about it and just enjoy playing xbox. leave the online stuff to the pros and just pay to get into a lobby.