Hacking Zune 3.01

[Netrix]

Originally Posted by Locke

That's the thing: a lot of people have a hard time turning simple English commands into doing something on a screen. There's a complete disconnect, and it makes it hard to follow even basic commands. If you've ever read Rinkworks' computer humor archive, there's more than enough proof.

I am sure there are people like that, since there are people who have a hard time speaking simple English, and some that seem to be incapable of coherent thought.

[BroiledVictory]

Originally Posted by Locke

Many people are afraid of touching the registry and system files, and almost as many rightfully should be.

Well, you shouldn't be playing with the registry unguided or not knowing the registry. I'm thinking about getting a book to teach me about the registry.

[Prodigy12]

Alrighty... I've kept on researching the way Zune software interacts with Zune hardware. It seems that all software that is allowed to add or modify files on the Zune device has a Microsoft certificate.

However the actual communication between the Zune and computer is done with several dlls located in the driver folder. Some of these dll files are signed, others are not. Most of them are triggered during transfer. But the only dll we are interested in is wdfCoInstaller as it is probably the one responsible for unlocking the Zune.

Besides this I have also found that Zune and XNA software access a registry value called "SyncInProgress" to determine whether or not it is safe to begin transfer.

Anyways, my question to all of you more advanced hackers is: Is there some way to hijack the communication dll that Microsoft software uses in order to free the WDF protocol?

My attempts so far have been futile since the dlls are encrypted well, and I lack hijacking skills. *Sigh*

If no one comes around to help me solve this conundrum I'll eventually give up, and regretfully downgrade my Zune.

Please help me before that happens!