Hello all,

First off, I apologize for my ever so off topic thread. Messenger Plus! was the only place that I could ever find when searching for information about UIB, and seems to be the only group of people who would have any pointers for my problem.

Here's the sitch: When attempting to modify a file (specifically for my Windows-based phone) with UIX information in it (XML, basically), a challenge arose. All the UIX files were present in the resource extractor and extracted easily as binary files. However, upon opening these files, I discovered their contents to be in an encoded manner I have never seen before. The only similarity between the files is the presence of the letters "UIB", which lead me here.

Naturally, I tried the MPTools.exe file to decode them, but to no avail-no error, no written files, which I suppose indicates the format is not the same as the Windows Live messenger UIB encoding.
Another interesting find was that each file referenced a DataTable.uib file, which, after opening, was very large and also encoded, but I suspect may be some sort of a "key" to the other files. That, or it's just very, very large reference.

Anyway, here's a link to the files I have uploaded. I do not believe this to be "warez" as these files were extracted from a file publicly available off of the Microsoft website. If this violates any rules, however, feel free to remove it:
http://www.megaupload.com/?d=XLKD7BYB

Basically, I need the "Notifications" file decoded one way or another, and if any pointers could be given, I would be so very, very grateful. Thanks

UIB encoding... hmmm....

The only people I know who have experience in it (that is: the 'MS Windows format') are Patchou and somebody else who I forgot the name of, and I even think TheBlasphemer (oldie from here too, though he is not active anymore). But Patchou doesn't develop Messenger Plus! anymore. Nevertheless, maybe, if he reads this, he can give you some pointers etc.

Messenger Plus! is currently developped by Yuna. And I dunno if they will give you some pointers or not (you know: 'trade secrets' sort of ). But who knows......

quote:

---

Originally posted by CookieRevised
UIB encoding... hmmm....

The only people I know who have experience in it (that is: the 'MS Windows format') are Patchou and somebody else who I forgot the name of, and I even think TheBlasphemer (oldie from here too, though he is not active anymore). But Patchou doesn't develop Messenger Plus! anymore. Nevertheless, maybe, if he reads this, he can give you some pointers etc.

Messenger Plus! is currently developped by Yuna. And I dunno if they will give you some pointers or not (you know: 'trade secrets' sort of ). But who knows......

---

I got word that that other person I'm talking about (who helped Patchou too) is TheSteve. He's another programming-über-wizard who eats bytes for breakfast.

He is also a member here and also on the Mess.be forums. He is still active, but he doesn't always read (random) threads. So, best is to contact him directly.

I did a search on the forums for UIB related stuff and here are some interesting posts about it:
ryxdp's reply to How to re-encode an UIB file?
TheBlasphemer's reply to A little fairie told me this...
(indeed confirms that it were TheBlasphemer and TheSteve working with Patchou to implement UIB encoding/decoding in Plus!)

And (blog post from TheBlasphemer):
http://fw.hardijzer.nl/?p=10

And this might be of huge interest for you (post from TheSteve on the old MSNFanatic forums):
http://forums.fanatic.net.nz/index.php?showtopic=...08499&#entry108499
(though, the info might be out of date. But at least it's a start)
(thanks to pollolibredegrasa for digging this up)





PS: Your thread isn't [OT] though. Tech talk like this is right on topic in the 'Tech Talk' subforum

I remember TB and TheSteve were working on theme-related stuff at the time but I'm afraid I never worked with them directly on anything that was UIB related. The code that I wrote to decode/encode this data in Messenger Plus! is now the property of Yuna Software so it cannot be shared by me. As Cookie mentioned though, the other two guys are excellent reverse engineers and they may be able to help you.

That said, I'm intrigued by what you're trying to achieve. Can you give us more information on what you want to do on your Windows phone?

quote:

---

Originally posted by Patchou

That said, I'm intrigued by what you're trying to achieve. Can you give us more information on what you want to do on your Windows phone?

---

I'll talk to TheSteve and see if he's still doing that stuff. Although, he might be a big busy given the recent events...

This is just a theory, so I don't know if its possible or not.
If you edit and replace the resources inside messenger with those of winphone 7, will mptools still extract it?

quote:

---

Originally posted by MeEtc
This is just a theory, so I don't know if its possible or not.
If you edit and replace the resources inside messenger with those of winphone 7, will mptools still extract it?

---

Hello.

Disclaimer 1: The following comments are guesses are very likely to be wrong.

Disclaimer 2: The following information applies to the files attached to the first post and very possibly do not relate to the Windows Live Messenger UIB format. (I have not looked at the newest versions of messenger, however versions 0.4 and 0.5 of the messenger UIB format are quite different  )

Based on what I've seen so far with WLM's UIB files, putting the data tables in a seperate file make sense as the data tables are the biggest part of a UIB file. I didn't have much time to look at it, however here are the simple notes I have made for the files you posted:

code:

---

struct UIBHeader
{
    char szSignature[4];  //"UIB\x1a"?
    DWORD dwVersion;   //0x0000046e  version?
    DWORD dwOffset1;  // dt:0 bytes 0x00013c43
            // notify:3375 bytes 0x00000742
            // Perhaps this is stack machine code
    DWORD dwOffset2; // dt:0 bytes 0x00013c43
            // notify: 0 bytes 0x00001471
    DWORD dwOffset3; // dt:2 bytes {0,0} 0x00013c43
            // notify: 4922 bytes 0x00001471
    DWORD dwEOF; // 0x00013c45  EOF
                   // 0x000027ab EOF
    BYTE bDataTableType[2];  // 0xFF 0xFF  <file offset> for no include
           // 0x1F 0x80 <include string> for include
    union {
        DWORD dwOffsetDataTablePointers;
        char szDataTablePath[];  // 0x04, 0x00 terminated?
    }
}

struct DataTableStringEntry
{
    BYTE bStringLength;
    BYTE bUnknown; //0x80
    char szString[bStringLength];
}

---