WM 6.5 Kitchen QVGA and VGA Developer Edition

[Adrynalyne]

212xx were MS non OEM specific builds, pretty sure.
216xx is HTC, if memory serves.

[da_reeseboy]

Originally Posted by Adrynalyne

212xx were MS non OEM specific builds, pretty sure.
216xx is HTC, if memory serves.

Thanks...updated orginal post.

Anyone else? I'd like to be able to fill in all the blanks if possible...

Originally Posted by da_reeseboy

Does anyone know what the branch-offs are for or who is doing each of them? As in -

212xx were MS non-OEM builds... (thanks Adrynalyne)
215xx were Samsung builds... (thanks blazingwolf)
216xx were HTC builds... (thanks Adrynalyne)
217xx were ???
218xx ???
219xx ???

Who is behind these builds?

[joojoobee666]

Originally Posted by da_reeseboy

Thanks...updated orginal post.

Anyone else? I'd like to be able to fill in all the blanks if possible...

Well, according to Da_G, 217xxx was Crossbow COM1 and 218xx was Crossbow COM2. Also, apparently neither 217xx or 218xx are from OEM builds. They are developement builds, but from where? I dunno. 219xx was branched off from the 217xx tree but I do not know what the tree name is.

[da_reeseboy]

Originally Posted by joojoobee666

Well, according to Da_G, 217xxx was Crossbow COM1 and 218xx was Crossbow COM2. Also, apparently neither 217xx or 218xx are from OEM builds. They are developement builds, but from where? I dunno. 219xx was branched off from the 217xx tree but I do not know what the tree name is.

Sorry... I'm sure this is a stupid question, but what is crossbow? Is that a company?

[lennie]

Originally Posted by joojoobee666

What did you use as the donor XIP? If you used the files from say Da_G's kitchen it won't work since XIPport is looking for the text files that correspond to each module (not the imageinfo.txt inside the module). That's one reason. Another is that there or overlaps with o32_realaddr of the modules (the first section of the XIP map.txt). XIPport does not like overlaps here.

I dumped the xip myself: I extracted the OS.nb from the rom, I've read that the athena doesn't have any extra data in the os.nb so I renamed it os.nb.payload, I ran the ImgfsFromNb and got the offeset which in the shipped from is at 0x00660000. I didn't know where the xip started in the file so I used Hex Editor Neo to find the beginning of the second xip at the address "FE 03 00 EA 00 00 00 00 00 00 00 00 00 00 00 00 00 00", which is at 0x00310000. then I used RomMaster to extract the xip.

I used xipport and dumped the xip, wright maps, make packages for the xip I just extracted all went fine. with the xip to be ported I used xipport to dump and make packages.......however, when I copy over the msxipkernel, msxipkernelltk and click undo xipport throughs an unhandled exception.......and crashes. this is where I'm stuck.....

[lennie]

Originally Posted by da_reeseboy

Sorry... I'm sure this is a stupid question, but what is crossbow? Is that a company?

crossbow was the code name for windows mobile 6:

http://www.bing.com/search?q=crossbo...bile&form=QBRE

[da_reeseboy]

Originally Posted by lennie

crossbow was the code name for windows mobile 6:

http://www.bing.com/search?q=crossbo...bile&form=QBRE

LOL yep... that was a stupid question by me then. So the fact that 217xx and 218xx are referred to as Crossbow only means its windows 6.x - No deep insight there. Should COM1/COM2 mean something to me?

[joojoobee666]

Originally Posted by lennie

I dumped the xip myself: I extracted the OS.nb from the rom, I've read that the athena doesn't have any extra data in the os.nb so I renamed it os.nb.payload, I ran the ImgfsFromNb and got the offeset which in the shipped from is at 0x00660000. I didn't know where the xip started in the file so I used Hex Editor Neo to find the beginning of the second xip at the address "FE 03 00 EA 00 00 00 00 00 00 00 00 00 00 00 00 00 00", which is at 0x00310000. then I used RomMaster to extract the xip.

I used xipport and dumped the xip, wright maps, make packages for the xip I just extracted all went fine. with the xip to be ported I used xipport to dump and make packages.......however, when I copy over the msxipkernel, msxipkernelltk and click undo xipport throughs an unhandled exception.......and crashes. this is where I'm stuck.....

Does that happen when you undo either dump WITHOUT making any changes?

[joojoobee666]

Originally Posted by da_reeseboy

LOL yep... that was a stupid question by me then. So the fact that 217xx and 218xx are referred to as Crossbow only means its windows 6.x - No deep insight there. Should COM1/COM2 mean something to me?

I believe those builds are internal Microsoft dev builds and those are continuations of the 212xx tree. But I could be wrong :P Where's Da_G, I'm sure he knows.

[chump]

anybody interested in a fix for the backlight going dim on lockscreen? this works for KAISER, try on other devices at your own risk!