Topic: Hardware Ban Hammer Protect (Read 573 times)

odyvan · « **on:** November 10, 2009, 10:53:00 AM »

All you need:
1. hands
2. soldering iron or something else for disable pin on NAND

Teory: Dashboard storing in 16Mb NAND HY27US08281A (google specs.)

NAND have hardware write-protect option (http://yfrog.com/bee3f5a2a10507j).
After disable 19-pin (http://yfrog.com/iy422c319da174j), Microsoft can't write info in dashboard, only read.
So, If your console is locked, it will not affect its functionality (HDD Creeping for example).

Sorry for my poor english.

No_Name · « **Reply #1 on:** November 10, 2009, 11:02:00 AM »

You will still be banned regardless.

Also you will not be able to update like this.

k0mpresd · « **Reply #2 on:** November 10, 2009, 11:23:00 AM »

no_name is correct. they ban the keyvault of the console. not by writing files to nand.

Grim187 · « **Reply #3 on:** November 10, 2009, 12:23:00 PM »

it might prevent the banning of game installs tho.

lollercakes · « **Reply #4 on:** November 10, 2009, 12:37:00 PM »

QUOTE(k0mpresd @ Nov 10 2009, 08:23 PM)

no_name is correct. they ban the keyvault of the console. not by writing files to nand.

Not sure I understand this. Could you explain, or link me to an article (or tell me what to google) that explains this?

I know so far that there's some 'console revoke list' that will cause your 360 to become unable to connect to live (either at the server side or the console side), and that by updating your dash using an update that has a CRL that contains your console's ID, you will (by writing to the NAND), end up banning your console via offline means.

However, if this never happens then surely your console should still be able to sign data being written to the hard drive?

So wouldn't write-protecting your NAND chip essentially deny MS the ability to flash the NAND, in turn disabling the HDD install functionality?

*edit* This and, where does game update data get stored - on the NAND or on your hard drive? I somehow doubt you're going to fit all the update data for some games onto the NAND in pre-256mb consoles - so if they can't deny you install functionality, could you not potentially also retrieve updates for games via live?

This post has been edited by lollercakes: Nov 10 2009, 08:38 PM

No_Name · « **Reply #5 on:** November 10, 2009, 01:04:00 PM »

You might be able to preserve the current functionality but your never going to be able to update again, or even connect to live as your console is blacklisted and the connection will be rejected.

I know what you want to do but its a very complicated way to do something that you can do by never plugging that console in to a network connection again.

lollercakes · « **Reply #6 on:** November 10, 2009, 01:17:00 PM »

Well, that's one reason I would think of to do this - the ability to connect to a network with a DHCP router running an internet connection that you don't want your console connecting to live through.

I mean, ultimately, when you want to go and update a game, if you haven't been banned off Live yet, you're either going to still not get banned, get banned and lose live connectivity or get banned, lose live connectivity AND your hard drive install feature.

I'd rather be able to take my console online for now and still try to update games (I haven't as of yet been banned off Live) than be afraid of taking it online incase they throw the console-side ban at me removing HDD installation capabilities.

g-sas · « **Reply #7 on:** November 10, 2009, 01:39:00 PM »

There is one problem with that. There are games that force you to update. If they can no longer do this you will not be able to play them. So in about half a year you will not be able to play any new game.

lollercakes · « **Reply #8 on:** November 10, 2009, 01:48:00 PM »

Based on that CRL, yes.

Hopefully by then someone will have figured out a way to spoof the version the dash reports back to the game so that the game thinks it's already been updated? I'm thinking that this would not require you to extract you CPU key, and would thus not require you to have a pre-8xxx dash version?

That is to say, unless there's something in the dash update that would be required for the game to work.

*edit* As an added note, those updates are offline, and thus contain a static CLR in them. Someone could potentially extract and decrypt the CLR, and users could use the non-hacking methods to check their console ID, and then decide whether or not they can risk applying the patch to their console?

I mean, ultimately you will, as you said, eventually be unable to play any new games, but only until you're unable to install the patches and they become a prerequisite to being able to install.

At this point you would have to accept your console is essentially 'frozen in time' and can only play games up until X date, and get yourself a new, as of yet unlisted and thus unbanned console, instead.

This post has been edited by lollercakes: Nov 10 2009, 09:53 PM

metalguitarist112 · « **Reply #9 on:** November 10, 2009, 02:04:00 PM »

Wouldn't there be a way to make the nand only be able to write certain things? For example allow it to right game updates, etc. but not allow it to accept the HDD install ban.

We would probably need to find exactly what is causing the HDD ban though.

lollercakes · « **Reply #10 on:** November 10, 2009, 02:11:00 PM »

I don't think you could do that without having to have the chip in an intermediary slot that scans the data being sent/received to the NAND chip.

And I'm not sure putting one of those on is viable, since the data being written/read to and from the NAND chip is encrypted...

It would be great if that could be done, though...

Radament · « **Reply #11 on:** November 10, 2009, 02:44:00 PM »

Would be nice with cygnos v2, the ultimate offline security.

Mike1250 · « **Reply #12 on:** November 11, 2009, 02:38:00 AM »

I gave it a try, as my Xenon is still unbanned as of 11/11/09, so I just grounded the pin. If I can find a switch small enough I'll put it near the front behind the faceplate. Getting banned sucks, but not being able to fill my hard drive with games is just lame Microshaft.

picture

This post has been edited by Mike1250: Nov 11 2009, 10:38 AM

odyvan · « **Reply #13 on:** November 11, 2009, 06:38:00 AM »

I'm so glad.
Also you can use external switch for 19-pin.
(IMG:http://img35.imageshack.us/img35/3224/screenshot20091111at163.png)
The switch has three positions: ground 19pin/+3.3 volts/default connection.

lollercakes · « **Reply #14 on:** November 11, 2009, 07:24:00 AM »

I'm confused...

Why would you ground the pin or feed it +3.3v, and how do these differ from the 'default' connection?

I'm not electronically minded, so as far as I would know, if the pin has no connection to the PCB that means the NAND becomes write protected, whereas if it is connected, which closes a circuit of some kind, it is not write protected?

Personally I can afford to wait on trying this myself, and would rather someone that I'm confident knows what they're doing does this and posts their results. That is not to say I don't trust the two of you that have apparently done this already, but right now, I think no_name and k0mpresd have more credibility regarding these things. :/

*edit* namecheck

This post has been edited by lollercakes: Nov 11 2009, 03:25 PM

Author Topic: Hardware Ban Hammer Protect (Read 573 times)