xboxscene.org forums

Author Topic: Console Ban List Crl.bin  (Read 99 times)

signal-to-noise-ratio

  • Archived User
  • Full Member
  • *
  • Posts: 170
Console Ban List Crl.bin
« on: November 09, 2009, 07:51:00 AM »

QUOTE(effortless @ Nov 9 2009, 05:57 AM) View Post

Revocation is done through the use of Console Revocation Lists (CRLs).  If your console's ID is present in the revocation list, then your console has been revoked. There are two types of CRLs, static and dynamic.

A static list refers to a list that is saved onto the flash inside your Xbox360. This list is updated when system updates are performed on your console.  The Fall'08 update contains an encrypted version of this list in the file "$SystemUpdate\su20076000_00000000\data.bin".  When the list is installed onto your console another layer of encryption is added using your Xbox360's unique fusekey and the result is saved to a crl.bin file on the internal flash.

A dynamic list refers to a list that is sent to your console when you connect to Xbox Live. This way an updated revocation list can be employed without requiring a system update.

-the above has been put out before by Xorloser (You can read more about what it means for your console to be revoked here...  http://xorloser.com/?p=45 )

Recently Microsoft has been adding all of the flagged consoles to the list.  To recover you must overwrite or erase the crl.bin on the internal flash.. which would be possible if we were able to force install an older dash which included an older crl.bin or through jtag (but this is limited to systems without the recent update anyway and certain versions of hardware).

I thought I'd remind everyone of this so we can focus better at a solution.

A solution to eventually get back online would require a new console id or a way to spoof a different one.  To see your real console id visit http://xorloser.com/?p=45.

So... who can overwrite or alter the crl.bin first??

To verify all this, our console ID's will most likely be in the updated static list coming in the next big update this month (someone with jtag could dump it for us once their console is updated).. and to answer some people's questions, if your system has been flagged but not banned yet, a future game will probably incorporate the updated crl.bin and ban your system once you play it.


http://forums.xbox-s...o...529&st=540#

This seemed important enough to deserve its own topic.
Logged

Juvenal1228

  • Archived User
  • Sr. Member
  • *
  • Posts: 447
Console Ban List Crl.bin
« Reply #1 on: November 09, 2009, 08:08:00 AM »

as far as i know you can read/write anything on the nand chip with the jtag hack, whether or not you can make anything of it is another story

 

sounds like the file itself is encrypted inside the nand and the part of the nand it is in is encrypted by the CPU key, which can only be gotten by using the jtag hack and Xell.

 

so in theory if you had your CPU key already you could replace the file but chances are if you did that your dash would know and fail to load because the files hash wouldn't match.

Logged

CocoaPistolero

  • Archived User
  • Newbie
  • *
  • Posts: 47
Console Ban List Crl.bin
« Reply #2 on: November 09, 2009, 08:14:00 AM »

Wow, so they added every banned console to this list?  That list must be huge now, lol.

The last time I read this on this forums I thought it was some bunk theory he had made up.  I didn't honestly think MS would keep an active list of banned consoles that they deliver to every unbanned console.

So I'm guessing theoretically if I can spoof a console ID on game saves or my profile I can use that data on other unbanned Xbox 360s and, for example, update my gamerscore with games I've played on my banned console?

EDIT: Or wait, I think I'm misunderstanding.  I'm confused sad.gif
Logged

signal-to-noise-ratio

  • Archived User
  • Full Member
  • *
  • Posts: 170
Console Ban List Crl.bin
« Reply #3 on: November 09, 2009, 08:17:00 AM »

QUOTE(Juvenal1228 @ Nov 9 2009, 10:08 AM) View Post

as far as i know you can read/write anything on the nand chip with the jtag hack, whether or not you can make anything of it is another story

 

sounds like the file itself is encrypted inside the nand and the part of the nand it is in is encrypted by the CPU key, which can only be gotten by using the jtag hack and Xell.

 

so in theory if you had your CPU key already you could replace the file but chances are if you did that your dash would know and fail to load because the files hash wouldn't match.


Off topic
I was under impression latest update out now removes jtag functionality? Is this true?

On topic
I guess you change your console Id beforehand before applying updates on game disc. You would have to have another id to change it to. Say a rrod console that was never flagged I would think that might work?

Edit more info available here:

http://www.ps3news.c...ble-105809.html

partial quote

"Below you can find a list of all the currently revoked consoles at the time of the Fall'08 system update release. Read on to find out why and how an Xbox360 gets revoked and what effect it has.

http://xorloser.com/...2009/05/crl.txt
This is a list of the Console IDs of the 433 Xbox360 consoles that had been revoked when the Fall'08 update was released."
Logged

SliderX

  • Archived User
  • Newbie
  • *
  • Posts: 1
Console Ban List Crl.bin
« Reply #4 on: November 15, 2009, 02:38:00 PM »

QUOTE(mogwaimon @ Nov 10 2009, 01:34 AM) View Post

I've got a question about this as well...if theoretically I kept a console offline that may or may not have been flagged for a ban, and continued to use backups on it...assuming that new games would all be wave 4+, could I use that wave 4 patcher to make the game conform to wave 2 standards?

Does that patcher remove the updates, because I know new 'waves' just have a system patch in the video partition making the DVD firmware think the game is a bad rip, so I'm thinking that the patcher just takes the update out of the video partition, right?

On that note, do game updates contain the crl.bin?Would it be safe to put a patch for say Left 4 Dead 2 on my HDD so I could also continue to do system links with friends without my console ever knowing it was banned?



Also interested in the answer to this. Anyone know?
Logged

llamax

  • Archived User
  • Newbie
  • *
  • Posts: 1
Console Ban List Crl.bin
« Reply #5 on: November 15, 2009, 09:07:00 PM »

Please forgive me for being a noob.  But is it possible for us just to patch or inject an earlier crl.bin (pre-ban file) into the system update process?  So in theory, if Modern warfare 2 requires your console to be updated to play wave 4 games, could we update the console but at the same time rollback the crl.bin file to an earlier file?  Thanks for entertaining the idea.
Logged

hobosrock696

  • Archived User
  • Newbie
  • *
  • Posts: 16
Console Ban List Crl.bin
« Reply #6 on: November 17, 2009, 10:37:00 PM »

Anyone know if this is possible? (what the guy above me said...)
Logged

importune

  • Archived User
  • Newbie
  • *
  • Posts: 19
Console Ban List Crl.bin
« Reply #7 on: November 17, 2009, 11:30:00 PM »

At the moment none of these ideas are possible, give it time. People are trying. X.x


Logged

JOCKz

  • Archived User
  • Newbie
  • *
  • Posts: 23
Console Ban List Crl.bin
« Reply #8 on: November 18, 2009, 03:13:00 AM »

nice to see the ball rolling !!!
Logged

hobosrock696

  • Archived User
  • Newbie
  • *
  • Posts: 16
Console Ban List Crl.bin
« Reply #9 on: November 18, 2009, 03:36:00 PM »

How about patching a wave 3 video partition to wave 4 game and run it on a system that doesnt know wave 3 exists... Anyone think the system might somehow catch it and report it upon xbl connection?
Logged