Windows Mobile 6.5

[xz_OXO_xz]

http://imgarchive.info/200907/109699.jpg

PDA / Mobile | Windows Mobile 6.5 (wm 6.5) | 240MB

Windows Mobile is a compact operating system combined with a suite of basic applications for mobile devices based on the Microsoft Win32 API. Devices that run Windows Mobile include Pocket PCs, Smartphones, Portable Media Centers, and on-board computers for certain automobiles. It is designed to be somewhat similar to desktop versions of Windows, feature-wise and aesthetically. Additionally, third-party software development is available for Windows Mobile. Originally appearing as the Pocket PC 2000 operating system, Windows Mobile has been updated multiple times, with the current version being Windows Mobile 6.1 (Windows Mobile 6.5 is due for imminent release as at 14 July 2009).


http://imgarchive.info/200907/th_109700.jpg

Common features:
Windows Mobile for Pocket PC carries these standard features in most of its versions:
* Today Screen shows the current date, owner information, upcoming appointments, e-mail messages, and tasks.
* The taskbar shows the current time and the volume.
* Office Mobile a suite of Mobile versions of Microsoft Office applications
* Outlook Mobile comes with Windows Mobile.
* Internet Explorer Mobile is an Internet browser developed by Microsoft for Pocket PC and Handheld PC that comes loaded by default with Windows Mobile and Windows CE for Handheld PC.
* Windows Media Player for Windows Mobile.
* Client for PPTP VPNs.
* Internet Connection Sharing (ICS) which in mobile phones allows attached computers to share internet connections via USB and Bluetooth.

Hardware platforms:
Windows Mobile runs on multiple hardware platforms including Pocket PCs, smartphones, Portable Media Center, and automobiles. These hardware platforms did not always exist from the inception of Windows Mobile.

Pocket PC
The Pocket PC was the original intended platform for the Windows Mobile operating system. These devices consisted of both standalone Pocket PC devices without mobile phone capabilities, and those that included mobile phone capabilities. The most current name of Windows Mobile intended for use on Pocket PCs is officially "Windows Mobile 6 Professional" for devices with mobile phone capabilities and "Windows Mobile 6 Classic" for devices without mobile phone capabilities.

Smartphone
The Smartphone became the next hardware platform after the Pocket PC to run Windows Mobile, and debuted with the release of Pocket PC 2002. Although in the broad sense of the term "Smartphone", both Pocket PC phones and Microsoft branded Smartphones each fit into this category, it should be noted that Microsoft's use of the term "Smartphone" includes only more specific hardware devices that differ from Pocket PC phones. Such Smartphones were originally designed without touchscreens, intended to be operated more efficiently with only one hand, and typically had lower resolution displays than Pocket PCs. Microsoft's focus for the Smartphone platform was to create a device that functioned well as a phone and data device in a more integrated manner.[6] The current name of Windows Mobile intended for use on Smartphones is officially "Windows Mobile 6 Standard".

Portable Media Center
The Portable Media Center was a device that focused on integration with Microsoft's Windows Media Center and Windows Media Player to allow users to carry their media libraries with them on the go. The Portable Media Center was officially introduced in 2004, and ran a modified version of Windows Mobile. These devices became the predecessor to Microsoft's Zune, and after 2006 Microsoft discontinued the project in favor of the latter.

Automobiles
Microsoft Auto is the name for Microsoft's operating system that facilitates multiple functions in automobiles including communication, entertainment, information systems. Windows Mobile for use in automobiles is the latest platform for the operating system, and was introduced by Microsoft in February 2006 at the Geneva International Motor Show. Microsoft Auto comes in two different versions. The Basic version includes a Bluetooth connectivity and USB interface for music playback. The Standard version includes this also, but additionally it features a built-in GPS, GSM phone, and security features. The Microsoft Auto hardware specification includes a 300 MHz ARM processor, 32 MB of RAM, and a microphone.

Read more...
How to install?

Homepage
MS Windows Mobile
http://www.microsoft.com/windowsmobile/en-us/default.mspx

RapidShare:
Part 1
http://rapidshare.com/files/256497474/Wind.Mobile.v6.5_tonyka.softarchive.net.part1.rar
Part 2
http://rapidshare.com/files/256497452/Wind.Mobile.v6.5_tonyka.softarchive.net.part2.rar
Part 3
http://rapidshare.com/files/256494704/Wind.Mobile.v6.5_tonyka.softarchive.net.part3.rar

[adelco93]

so is this the official release?

[ace10134]

so is this the official release?

lol

Idk what or why this post is here.

[ivanmmj]

lol

Idk what or why this post is here.
Neither do I. lol
And no, there won't be any official Herald 6.5's. I can't wait until 6.5.1, though, so I can port it to the Herald.

[adelco93]

Sorry, just came back from a business trip, when i wrote that i'd been awake for more than 20 hours, what i meant was is this a newer build, so i can port it myself to my wing.

[ivanmmj]

Sorry, just came back from a business trip, when i wrote that i'd been awake for more than 20 hours, what i meant was is this a newer build, so i can port it myself to my wing.
What build is that?
Currently, I have 23001, 23004, 23007 and 21925.
21925 is from the MS's experimental branch. It's got a LOT of GUI changes, massive changes, but it's a little unusable at the moment.

[ace10134]

What build is that?
Currently, I have 23001, 23004, 23007 and 21925.
21925 is from the MS's experimental branch. It's got a LOT of GUI changes, massive changes, but it's a little unusable at the moment.

Like what GUI changes and such?? Anything interesting or revolutionary? Did they make WinMo more finger friendly? Sounds cool.

[adelco93]

What build is that?
Currently, I have 23001, 23004, 23007 and 21925.
21925 is from the MS's experimental branch. It's got a LOT of GUI changes, massive changes, but it's a little unusable at the moment.

oh, thank you for the info. I'm just going away for a while and i just want to get stuff done right now while i can, that includes trying to get up to date with my phone.

[ivanmmj]

Like what GUI changes and such?? Anything interesting or revolutionary? Did they make WinMo more finger friendly? Sounds cool.
More finger friendly, yes.

Here are some screenshots.
http://forum.ppcgeeks.com/showpost.php?p=1037817&postcount=6005

[ace10134]

More finger friendly, yes.

Here are some screenshots.
http://forum.ppcgeeks.com/showpost.php?p=1037817&postcount=6005

Ahh! It's ugly!!...

http://forum.xda-developers.com/attachment.php?attachmentid=206325&stc=1&d=1247941840http://forum.xda-developers.com/attachment.php?attachmentid=206326&stc=1&d=1247941840
http://forum.xda-developers.com/attachment.php?attachmentid=206327&stc=1&d=1247941840http://forum.xda-developers.com/attachment.php?attachmentid=206328&stc=1&d=1247941840

[WhatzinyourphonE]

thanks ivan for the info. Should we move discussion of 6.5 for the herald here? ivan tell me in at least one of those builds theyve fixed the typing predictive thing! and wow! MS is really making an effort to use no styless! I cant wait to put it on my phone! one thing they need to bring back is the transparent bars, top and bottom! please! microsoft!!!

[ace10134]

thanks ivan for the info. Should we move discussion of 6.5 for the herald here? ivan tell me in at least one of those builds theyve fixed the typing predictive thing! and wow! MS is really making an effort to use no styless! I cant wait to put it on my phone! one thing they need to bring is the transparent bars, top and bottom! please! microsoft!!!

They do have the transparent bars, it's just that Ivan's theme in JustHome disabled the transparency. If you put a new theme on it, then they can be transparent.

And yea, I say this thread is perfect for WM6.5 discussion, why the heck not?

[apreichner]

They do have the transparent bars, it's just that Ivan's theme in JustHome disabled the transparency. If you put a new theme on it, then they can be transparent.

And yea, I say this thread is perfect for WM6.5 discussion, why the heck not?

Transparent bars never actually existed in Windows Mobile 6.5 at all, at least not true transparency. Each of the bars is a theme image, what gives it transparency is changing the Opacity of one of the theme images in photoshop or something, but still this will not equal true transparency. This is why in the Programs menu, you still cannot see the programs when they are under a translucent (semi-transparent) bar.

[ivanmmj]

The ugliness will hopefully go away. That build family is just where they test everything to see whether it's a good idea or a bad idea.

[ivanmmj]

thanks ivan for the info. Should we move discussion of 6.5 for the herald here? ivan tell me in at least one of those builds theyve fixed the typing predictive thing! and wow! MS is really making an effort to use no styless! I cant wait to put it on my phone! one thing they need to bring back is the transparent bars, top and bottom! please! microsoft!!!
Yea, why not.
As far as the typing predictive thing, I'm not sure what MS changed that caused it.
And yes, they're moving towards capacitive screens. (Which is what we use for the Android phones and for the iPhone.)

[apreichner]

The ugliness will hopefully go away. That build family is just where they test everything to see whether it's a good idea or a bad idea.

So should we expect anymore 6.5 ROMs from you, or is the kitchen the last thing?

[ivanmmj]

I don't know. I don't want to get ahead of myself. I MIGHT be releasing a few "stock" ROMs and a few stripped ROMs based on the new SJK set I'm building, but after that, I might just start porting the kitchen to other devices only. (And I have to spend some time finding multi language packages.)

[apreichner]

I don't know. I don't want to get ahead of myself. I MIGHT be releasing a few "stock" ROMs and a few stripped ROMs based on the new SJK set I'm building, but after that, I might just start porting the kitchen to other devices only. (And I have to spend some time finding multi language packages.)

You can release the new 6.5 one if you want lol :)

[ivanmmj]

Yea, that would include 6.5 in a few different languages as well as 6.1 in a few languages.

Or just the WHOLE kitchen.

[fishwiz45]

hey ivanmmj, have you seen any references to or hints of the tellme software(voice recognition stuff) on any of the 6.5 builds yet? i'm really looking forward to this http://www.tellme.com/you

[ivanmmj]

hey ivanmmj, have you seen any references to or hints of the tellme software(voice recognition stuff) on any of the 6.5 builds yet? i'm really looking forward to this http://www.tellme.com/you
Not yet, but from the looks of it, it's not an official Microsoft product, so it might never be leaked with the MS builds. It looks like a program that just happens to be for 6.5

[WhatzinyourphonE]

Ivan, I know you stopped on the Justhome roms. But how about releasing the 21925 build? I just watched a video of it, i want to see how it is. and did you noticed the rounded edges on the screen? Check pocketnow.com to see it. Hopefully when MS is done, 6.5 will really stand out!

[ivanmmj]

The newest 21928 build is out, too. I haven't messed with it because there are a lot of UI issues with it. (Can't get to certain menu's.)
I am currently focused on getting SJK ready, but I can technically dump 21928 into it an hope for the best. I won't have any time to mess with this until next week, though.

[WhatzinyourphonE]

The newest 21928 build is out, too. I haven't messed with it because there are a lot of UI issues with it. (Can't get to certain menu's.)
I am currently focused on getting SJK ready, but I can technically dump 21928 into it an hope for the best. I won't have any time to mess with this until next week, though.

ok, no rush. wat do u need to know to cook a rom? wing users need more cooks and im up for it. Ive done everything but cook! and since ur busy and semi retired ill fill in for u!

[ace10134]

ok, no rush. wat do u need to know to cook a rom? wing users need more cooks and im up for it. Ive done everything but cook! and since ur busy and semi retired ill fill in for u!

Dude, you won't have to know, like, anything. Once Ivan releases his SuperJustKitchen, it'll be easy as ever. It's a "visual" kitchen, so you just select the options and go! I think after he releases that, everyone will just be making their own ROM's. It'll be fun once that's released.

[SSJ_Gomike]

Dude, you won't have to know, like, anything. Once Ivan releases his SuperJustKitchen, it'll be easy as ever. It's a "visual" kitchen, so you just select the options and go! I think after he releases that, everyone will just be making their own ROM's. It'll be fun once that's released.

Yeah, i'm pretty excited about it too....

[daniel_costa_rj]

here is the video with Windows Mobile Build 21925, many things change, it's nice. rsrs KNOW WE CAN BACK TO THE MENU AFTER USE SOMETHING OPTION OF SETTINGS EEEEEEEEEEEEEEEEEEEEEEEEEEEEE hjauahuhauHUAhhAHUauhAUHAuhuAHUHuhAUHUah
http://www.youtube.com/watch?v=LhiYQwCIVdI

[SSJ_Gomike]

here is the video with Windows Mobile Build 21925, many things change, it's nice. rsrs KNOW WE CAN BACK TO THE MENU AFTER USE SOMETHING OPTION OF SETTINGS EEEEEEEEEEEEEEEEEEEEEEEEEEEEE hjauahuhauHUAhhAHUauhAUHAuhuAHUHuhAUHUah
http://www.youtube.com/watch?v=LhiYQwCIVdI



Very impressive....i would like to be able to cook this build into a ROM using SuperKitchen soon as it's ready....

Thanks for the video!

[ivanmmj]

Very impressive....i would like to be able to cook this build into a ROM using SuperKitchen soon as it's ready....

Thanks for the video!
As I mentioned, that build is not ready for prime time. You can't access a lot of the menus because of the layout.

[ace10134]

Very impressive....i would like to be able to cook this build into a ROM using SuperKitchen soon as it's ready....

Thanks for the video!

I've been trying to cook that 21925 build into a ROM for a while. It's my first ROM, so I'm just trying to learn everything, and I've failed so far. But I wanna play around with that *new* build, so if I get it working, I'll let you guys try it too.

[ivanmmj]

I've been trying to cook that 21925 build into a ROM for a while. It's my first ROM, so I'm just trying to learn everything, and I've failed so far. But I wanna play around with that *new* build, so if I get it working, I'll let you guys try it too.
Well, there's a hybrid 21925/23008 going around, but I'm not sure what is taken from which version. (Someone put it together over at ppcgeeks, I believe.)

[DrE_braxx]

http://imgarchive.info/200907/109699.jpg

PDA / Mobile | Windows Mobile 6.5 (wm 6.5) | 240MB

Windows Mobile is a compact operating system combined with a suite of basic applications for mobile devices based on the Microsoft Win32 API. Devices that run Windows Mobile include Pocket PCs, Smartphones, Portable Media Centers, and on-board computers for certain automobiles. It is designed to be somewhat similar to desktop versions of Windows, feature-wise and aesthetically. Additionally, third-party software development is available for Windows Mobile. Originally appearing as the Pocket PC 2000 operating system, Windows Mobile has been updated multiple times, with the current version being Windows Mobile 6.1 (Windows Mobile 6.5 is due for imminent release as at 14 July 2009).


http://imgarchive.info/200907/th_109700.jpg

Common features:
Windows Mobile for Pocket PC carries these standard features in most of its versions:
* Today Screen shows the current date, owner information, upcoming appointments, e-mail messages, and tasks.
* The taskbar shows the current time and the volume.
* Office Mobile a suite of Mobile versions of Microsoft Office applications
* Outlook Mobile comes with Windows Mobile.
* Internet Explorer Mobile is an Internet browser developed by Microsoft for Pocket PC and Handheld PC that comes loaded by default with Windows Mobile and Windows CE for Handheld PC.
* Windows Media Player for Windows Mobile.
* Client for PPTP VPNs.
* Internet Connection Sharing (ICS) which in mobile phones allows attached computers to share internet connections via USB and Bluetooth.

Hardware platforms:
Windows Mobile runs on multiple hardware platforms including Pocket PCs, smartphones, Portable Media Center, and automobiles. These hardware platforms did not always exist from the inception of Windows Mobile.

Pocket PC
The Pocket PC was the original intended platform for the Windows Mobile operating system. These devices consisted of both standalone Pocket PC devices without mobile phone capabilities, and those that included mobile phone capabilities. The most current name of Windows Mobile intended for use on Pocket PCs is officially "Windows Mobile 6 Professional" for devices with mobile phone capabilities and "Windows Mobile 6 Classic" for devices without mobile phone capabilities.

Smartphone
The Smartphone became the next hardware platform after the Pocket PC to run Windows Mobile, and debuted with the release of Pocket PC 2002. Although in the broad sense of the term "Smartphone", both Pocket PC phones and Microsoft branded Smartphones each fit into this category, it should be noted that Microsoft's use of the term "Smartphone" includes only more specific hardware devices that differ from Pocket PC phones. Such Smartphones were originally designed without touchscreens, intended to be operated more efficiently with only one hand, and typically had lower resolution displays than Pocket PCs. Microsoft's focus for the Smartphone platform was to create a device that functioned well as a phone and data device in a more integrated manner.[6] The current name of Windows Mobile intended for use on Smartphones is officially "Windows Mobile 6 Standard".

Portable Media Center
The Portable Media Center was a device that focused on integration with Microsoft's Windows Media Center and Windows Media Player to allow users to carry their media libraries with them on the go. The Portable Media Center was officially introduced in 2004, and ran a modified version of Windows Mobile. These devices became the predecessor to Microsoft's Zune, and after 2006 Microsoft discontinued the project in favor of the latter.

Automobiles
Microsoft Auto is the name for Microsoft's operating system that facilitates multiple functions in automobiles including communication, entertainment, information systems. Windows Mobile for use in automobiles is the latest platform for the operating system, and was introduced by Microsoft in February 2006 at the Geneva International Motor Show. Microsoft Auto comes in two different versions. The Basic version includes a Bluetooth connectivity and USB interface for music playback. The Standard version includes this also, but additionally it features a built-in GPS, GSM phone, and security features. The Microsoft Auto hardware specification includes a 300 MHz ARM processor, 32 MB of RAM, and a microphone.

Read more...
How to install?

Homepage
MS Windows Mobile
http://www.microsoft.com/windowsmobile/en-us/default.mspx

RapidShare:
Part 1
http://rapidshare.com/files/256497474/Wind.Mobile.v6.5_tonyka.softarchive.net.part1.rar
Part 2
http://rapidshare.com/files/256497452/Wind.Mobile.v6.5_tonyka.softarchive.net.part2.rar
Part 3
http://rapidshare.com/files/256494704/Wind.Mobile.v6.5_tonyka.softarchive.net.part3.rar

sooo... do you have to download each part individually, or do you just pick one, download, and install, i need some sort of explanation why do they have to make it difficult for people who know nothing :(...

[ace10134]

Well, there's a hybrid 21925/23008 going around, but I'm not sure what is taken from which version. (Someone put it together over at ppcgeeks, I believe.)

Sounds like they cut the work out for me, then. I might look into that, if I can ever figure out how to cook a freakin ROM, first.

Ivan, how do you cook in a .CAB file??? I got the cab file extracted into the proper setup for using in a ROM (using some tool). Now, where do I place the folder? Do I have to re-name the folder too, or will any name work? And do I have to create a .TXT file or anything for it, or JUST place the folder in the OEM folder? I need some full, quality instructions. I'm gonna ask the ToadLife guy too. I searched my heart out, cooked my heart out, flashed my heart out, and couldn't get it to work. Plz help!!! Thanks, Ivan.


sooo... do you have to download each part individually, or do you just pick one, download, and install, i need some sort of explanation why do they have to make it difficult for people who know nothing :(...

Idk. You need the SYS folder and the XIP.bin file. Not sure what that download has. I'm new to cooking too, but if I ever figure this shit out, I'll write up some good instructions and help you out.

[ivanmmj]

Sounds like they cut the work out for me, then. I might look into that, if I can ever figure out how to cook a freakin ROM, first.

Ivan, how do you cook in a .CAB file??? I got the cab file extracted into the proper setup for using in a ROM (using some tool). Now, where do I place the folder? Do I have to re-name the folder too, or will any name work? And do I have to create a .TXT file or anything for it, or JUST place the folder in the OEM folder? I need some full, quality instructions. I'm gonna ask the ToadLife guy too. I searched my heart out, cooked my heart out, flashed my heart out, and couldn't get it to work. Plz help!!! Thanks, Ivan.




Idk. You need the SYS folder and the XIP.bin file. Not sure what that download has. I'm new to cooking too, but if I ever figure this shit out, I'll write up some good instructions and help you out.
In the case of the older OEM folders, it's as simple as converting the CAB to an OEM converter using any of the readily available cab converters then inserting the folder (whatever name it may be without spaces) into the OEM folder. Nothing else needed. The converters usually take care of the rest.
And I don't know what that link is. I've never bothered with it.

[apreichner]

Sounds like they cut the work out for me, then. I might look into that, if I can ever figure out how to cook a freakin ROM, first.

Ivan, how do you cook in a .CAB file??? I got the cab file extracted into the proper setup for using in a ROM (using some tool). Now, where do I place the folder? Do I have to re-name the folder too, or will any name work? And do I have to create a .TXT file or anything for it, or JUST place the folder in the OEM folder? I need some full, quality instructions. I'm gonna ask the ToadLife guy too. I searched my heart out, cooked my heart out, flashed my heart out, and couldn't get it to work. Plz help!!! Thanks, Ivan.

Idk. You need the SYS folder and the XIP.bin file. Not sure what that download has. I'm new to cooking too, but if I ever figure this shit out, I'll write up some good instructions and help you out.

You would need to convert the cab into its OEM parts, you can search "CAB to OEM", but it would probably be easier to search for an Application already in OEM format. And I'm pretty sure you just place the application oem folder inside the OEM folder in the kitchen's Working_folder.

EDIT: Oops didn't realize Ivan was posting here to lol, sorry for the double post.

[ace10134]

In the case of the older OEM folders, it's as simple as converting the CAB to an OEM converter using any of the readily available cab converters then inserting the folder (whatever name it may be without spaces) into the OEM folder. Nothing else needed. The converters usually take care of the rest.
And I don't know what that link is. I've never bothered with it.

Ok. I already made the .CAB file into an OEM file, if I already didn't mention that.

So, what will make the difference is removing the spaces from the folder's name??? The folder's current name is.."Pointui Home v 1_51a". If I remove the spaces, then it'll work, eh? So simple..I'll try it out. thanks for that, Ivan.

And Arpreincher, or whatever the heck you are. You didn't help me at all, buddy. I already tried that. I didn't know about having the spaces in the folder though. So just shut it, and write your guide to the Wing already.

[ace10134]

How to cook a .CAB file into a ROM

Here's how to take a .CAB file, convert it to the OEM format, and then cook your new ROM with it.


Download Package Creator v 2.7.zip (http://thewingster.com/Documents/Package%20Creator%20v%202.7.zip)
Extract it to a location of your choice
Open the extracted folder, Package Creator v2.7
You should see this in the folder...
http://forum.xda-developers.com/attachment.php?attachmentid=209015&stc=1&d=1248585060
You can go ahead and remove the Pointui Home v 1.51a.CAB file. It is not necessary. But it is also not necessary to remove that file, since you can have mulitple .CAB files in that folder. Do what you want with it.
Take the .CAB file that you want to be cooked in your ROM, copy it, and paste it into the Package Creator v2.7 folder.
Now your Package Creator v 2.7 folder should be similar to the screenshot shown in step 4, but you should have the .CAB file that you just pasted into it there.
In the same folder (Package Creator v2.7), run the Package Creator v2.7.exe file.
You should see this screen...
http://forum.xda-developers.com/attachment.php?attachmentid=209016&stc=1&d=1248585060
Click the Open Cab file button. A new window will then pop up. Navigate to the location of your Package Creator v2.7 folder (if it's not already there), and then double click your desired .CAB file.
Wait for one second, and then a window will pop up, saying Done. Click OK.
Now go back to your Package Creator v2.7 folder, and observe that a new folder was created there. Whatever the name of it is, it is now your .OEM app folder.
You now need to remove the spaces from that folder's name. Click on the folder once (so that it's highlighted), and then click on it a second time (so that you can re-name it). You can change the name of the folder to whatever you like, but make sure that there are NO spaces left in the folder's name!!
Open your kitchen folder up.
Navigate to your OEM folder within your kitchen.
Take the folder that you created and re-named (in steps 12 and 13) and drag it into your OEM folder. Just place it in the root of your OEM folder.
Cook your ROM like normal now. Your new .CAB program will be automatically installed! If you have more questions, just ask, and I'll clarify it more.

[ace10134]

So yea, I figured it out (how to cook the cab) as you saw above. Thanks Ivan!!

But Ivan, how can you control which programs get started when you boot up the phone? I'd like PointUI to be loaded automatically when you boot the phone, you know? Just direct me to the file name of the file that I need to edit, that should be all I need to get going. Thanks again!

[ace10134]

I discovered how to make a program that I cooked in automatically boot.

Now, I wanna figure out how to create a .CAB file that simply places a shortcut for a program into a folder. Do you know how to do that, Ivan??

I have an ultimate goal, as to why I want to create that. Since when PointUI automatically boots up, when you first flash the ROM, PointUI interferes with the screen calibration, which makes the phone basically unusable. If I create a .CAB file that does what I said in paragraph 2, then I can make that CAB file install in the ExtROM while the ROM is setting up on the device after flashing. Therefore, the screen will already be calibrated, but then on the next boot-up, the shortcut to run PointUI will be in the start up folder, which will make PointUI run on all future boot-ups. So is there any other way I could achieve that? Making a program auto-start up after the initial screen calibration is done? I don't want to install PointUI using ExtROM, because ExtROM doesn't give the benefits that cooked-in programs do, right?

Thanks for the help. If you can just tell me how to create a CAB file that places a shortcut, that'd be awesome. I've been searching through threads for hours now, and had no luck :( Thanks!!

[ivanmmj]

I discovered how to make a program that I cooked in automatically boot.

Now, I wanna figure out how to create a .CAB file that simply places a shortcut for a program into a folder. Do you know how to do that, Ivan??

I have an ultimate goal, as to why I want to create that. Since when PointUI automatically boots up, when you first flash the ROM, PointUI interferes with the screen calibration, which makes the phone basically unusable. If I create a .CAB file that does what I said in paragraph 2, then I can make that CAB file install in the ExtROM while the ROM is setting up on the device after flashing. Therefore, the screen will already be calibrated, but then on the next boot-up, the shortcut to run PointUI will be in the start up folder, which will make PointUI run on all future boot-ups. So is there any other way I could achieve that? Making a program auto-start up after the initial screen calibration is done? I don't want to install PointUI using ExtROM, because ExtROM doesn't give the benefits that cooked-in programs do, right?

Thanks for the help. If you can just tell me how to create a CAB file that places a shortcut, that'd be awesome. I've been searching through threads for hours now, and had no luck :( Thanks!!
I suppose the easiest way would be to make the shortcut installing part of the configuration that is done at the beginning (the config.txt file.)

[ace10134]

I suppose the easiest way would be to make the shortcut installing part of the configuration that is done at the beginning (the config.txt file.)

Ok, I'll look at that then. I'll tell you if it works.

[ace10134]

Oh yea, so in the Config.txt file, how would I put in a create shortcut command?

Nvm, got it working!! See below. I wrote up another total dummies guide on how to create the shortcut.

(I know I'm using this thread as a sort of "how to cook" thread, but this thread really has no importance right now, as someone already said before!)

[ace10134]

How to Create a Shortcut using the Extended ROM

It's fairly simple...and useful, if you want to make a program automatically boot up after your ROM customizes the phone.


Download WinImage, Dutty's, and HTC Tools.zip (http://thewingster.com/Documents/WinImage,%20Dutty's,%20and%20HTC%20Tools.zip)
Unzip it to the location of your choice. Open the WinImage, Dutty's, & HTC Tools folder. You should find three files in there, winimage, duttys tool nbhtool, and Htc Rom Tool, as you can see below...
http://forum.xda-developers.com/attachment.php?attachmentid=209143&stc=1&d=1248631468
Run winimage from within that folder. Click OK to the Trial Registration screen (you have a 30 day trial, and the days only count when you use the program).
Now you should see this screen...
http://forum.xda-developers.com/attachment.php?attachmentid=209144&stc=1&d=1248631468
On that screen, go to File -> Open, and then navigate to your kitchen's folders. Now navigate to your kitchen's Build folder. Locate a file that has "ExtROM" in it's filename and make sure that the extention is a .NB file. (For users of Holly's Kitchen, the file is called WingDev_ExtROM.nb) Double click on the file, and then you should see something like this...
http://forum.xda-developers.com/attachment.php?attachmentid=209145&stc=1&d=1248631468
Double click on the __TFAT_HIDDEN_ROOT_DIR__ folder. Now you should see something like this...
http://forum.xda-developers.com/attachment.php?attachmentid=209146&stc=1&d=1248631468
Drag and drop the Config.txt file from that window to your Desktop (or any other location of your choice)
Now open your Config.txt file from your Desktop (or wherever you placed it). You should see something similar to this in the notepad window...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Now, to create the shortcut, first you must have a pre-existing shortcut .lnk file. If you're trying to automatically start a program upon boot that you cooked in, then you will most likely find the location of the .lnk file by navigating to the OEM\ folder within your kitchen. Find your program's folder, open it, and then open the initflashfiles.txt file within there. Try to find a string of code that looks similar to this...
Directory("\Windows"):-Directory("Start Menu")
Directory("\Windows\Start Menu"):-File("Pointui Home.lnk","\Windows\Pointui Home.lnk")
Once you find a code that looks similar to that, write down the final directory (for me, it would be \Windows\Start Menu) for later use in step 13. Also write down the link's file name (Pointui Home.lnk) for step 14, too.
Go back to the other notepad window (Config.txt). Remember that the notepad window should have something like this in it still...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Just before the LOCK:Disabled line, create an empty line, as such...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml

LOCK:Disabled
RST: Reset
Now fill that line in with CPY1:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:
LOCK:Disabled
RST: Reset
Remember back in step 9 where you wrote down a folder path? Well put that folder path right after the CPY1: command, as such...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu
LOCK:Disabled
RST: Reset
From step 9, you also wrote down the file name of the shortcut (the second thing you wrote down). First place a "\" after step 13, and then copy/paste in your file name, like so...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
LOCK:Disabled
RST: Reset
Then press enter after that line to create another empty line, and fill that one in with CPY2:
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:
LOCK:Disabled
RST: Reset
Now you can decide where you want to place the shortcut. CPY1: was used to find the inital location of the file (you can move any file you'd like), and CPY2: is used to place the file where you'd like. If you want your program to automatically boot, then you would add \Windows\StartUp after the CPY2: prompt, like below...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:\Windows\StartUp
LOCK:Disabled
RST: Reset
Now, in the line right above where you are currently at in the Notepad window, on CPY1: line, copy the last part of that line (for me, I would copy \Pointui Home.lnk) Then paste that on the end of the CPY2: line. Your code should look like this...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
CPY1:\Windows\Start Menu\Pointui Home.lnk
CPY2:\Windows\StartUp\Pointui Home.lnk
LOCK:Disabled
RST: Reset
Save and close that notepad (Config.txt) window. You are now done editing it!
Return to the WinImage program (you should have left it running this whole time).
In WinImage, select your Config.txt file, and press Del on your keyboard.
Now in a File Explorer, navigate to your Config.txt file that you just edited (I told you to place it on your Desktop). Drag and drop that Config.txt file into the WinImage program. It will ask you, "Do you want to inject 1 files occupying xxxxx bytes?" Click Yes.
In WinImage, right click the Config.txt file that you just placed there. Click File properties. Then check the Read-only box and click OK.
Go to File -> Save. Once it saves, (it saves quickly, so you probably don't even notice it saving), close the WinImage window.
Now cook your ROM like usual. The shortcut will be automatically placed! If you have any more questions, or need more clarification, just ask!

[ace10134]

So, Ivan, How do you cook in a theme file? (.tsk)

I can't figure it out :(

[ivanmmj]

So, Ivan, How do you cook in a theme file? (.tsk)

I can't figure it out :(
Yes. Easiest way is to call the cusTSK command from the config.txt.
Use something like:
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk

That will configure your ROM to use that TSK during the set up procedure.

[ace10134]

Yes. Easiest way is to call the cusTSK command from the config.txt.
Use something like:
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk

That will configure your ROM to use that TSK during the set up procedure.

Ahh, I see how that works now. I saw that posted somewhere else before, but didn't understand what they were talking about. I think I got it now. Thanks a lot Ivan!! (I'm writing up a huge How To guide, as I go, so future people will have it easy) (Oh, and thanks for the quick reply. I hate waiting!)

[ace10134]

How to Cook a Theme into your ROM


Start with your .tsk file (That's the theme file). Rename it so that it has no spaces.
Open up your kitchen's folder. Locate the SYS folder. Then locate this folder, "Base_Lang_0409_DPI_96_RESH_240_RESV_320". That is where all the theme files are stored.
You should already have some themes in that folder. Take your .tsk theme file (from step 1) and place it in the folder from step 2. Remember, you can't have spaces in the name of the .tsk file.
Now... Download WinImage, Dutty's, and HTC Tools.zip (http://thewingster.com/Documents/WinImage,%20Dutty's,%20and%20HTC%20Tools.zip)
Unzip it to the location of your choice. Open the WinImage, Dutty's, & HTC Tools folder. You should find three files in there, winimage, duttys tool nbhtool, and Htc Rom Tool, as you can see below...
http://forum.xda-developers.com/attachment.php?attachmentid=209143&stc=1&d=1248631468
Run winimage from within that folder. Click OK to the Trial Registration screen (you have a 30 day trial, and the days only count when you use the program).
Now you should see this screen...
http://forum.xda-developers.com/attachment.php?attachmentid=209144&stc=1&d=1248631468
On that screen, go to File -> Open, and then navigate to your kitchen's folders. Now navigate to your kitchen's Build folder. Locate a file that has "ExtROM" in it's filename and make sure that the extention is a .NB file. (For users of Holly's Kitchen, the file is called WingDev_ExtROM.nb) Double click on the file, and then you should see something like this...
http://forum.xda-developers.com/attachment.php?attachmentid=209145&stc=1&d=1248631468
Double click on the __TFAT_HIDDEN_ROOT_DIR__ folder. Now you should see something like this...
http://forum.xda-developers.com/attachment.php?attachmentid=209146&stc=1&d=1248631468
Drag and drop the Config.txt file from that window to your Desktop (or any other location of your choice)
Now open your Config.txt file from your Desktop (or wherever you placed it). You should see something similar to this in the notepad window...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
LOCK:Disabled
RST: Reset
Just before the "LOCK:Disabled" line, create a new line, and write in, "EXEC: \Windows\cusTSK.exe", like below...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
EXEC: \Windows\cusTSK.exe
LOCK:Disabled
Then, press space and write in "\Windows\". Now, write in the name of your theme's file, and remember to include the .tsk extention. It should look like this, with "PointUI_Theme" being replaced by your theme's file name...
LOCK:Enabled
XML: \Extended_ROM\WingDev_Config.xml
EXEC: \Windows\cusTSK.exe \Windows\PointUI_Theme.tsk
LOCK:Disabled
Save and close that notepad (Config.txt) window. You are now done editing it!
Return to the WinImage program (you should have left it running this whole time).
In WinImage, select your Config.txt file, and press Del on your keyboard.
Now in a File Explorer, navigate to your Config.txt file that you just edited (I told you to place it on your Desktop). Drag and drop that Config.txt file into the WinImage program. It will ask you, "Do you want to inject 1 files occupying xxxxx bytes?" Click Yes.
In WinImage, right click the Config.txt file that you just placed there. Click File properties. Then check the Read-only box and click OK.
Go to File -> Save. Once it saves, (it saves quickly, so you probably don't even notice it saving), close the WinImage window.
Now cook your ROM like usual. The theme will be applied just after the ROM flashes, while the Setup is running! If you have any more questions, or need more clarification, just ask!

[ace10134]

So, Ivan, how do you do registry edits and cook them in? I haven't found anything on how to do that yet.

Nvm, I think I found some instructions that are good. I'll be posting back if I get it working or not.

[ivanmmj]

So, Ivan, how do you do registry edits and cook them in? I haven't found anything on how to do that yet.

Nvm, I think I found some instructions that are good. I'll be posting back if I get it working or not.
I use reg files since I use the visual kitchen, but I used to just do selective dumps of what I needed (using my phone to test and set the settings) then I would save the registry keys in the RGU files.

To search for keys that you want to nix or modify, it's a secret. ;) I've taught one person how I do it. I will write up something if need be (if you can't figure it out.)
The big thing that I've learned while cooking is that you HAVE to develop SOME things yourself because while you do all the researching, you'll uncover a LOOOOOT of cool things that you wouldn't have known you wanted.

When I learned how to cook, there weren't any walkthroughs. It was just a read the VERY little and make up the rest. That's where you learn the most. ^_^ With all the information put together, we can make it easier for anyone to get started. But the experts will be those who venture into the unknown. ;)

[ace10134]

I use reg files since I use the visual kitchen, but I used to just do selective dumps of what I needed (using my phone to test and set the settings) then I would save the registry keys in the RGU files.

To search for keys that you want to nix or modify, it's a secret. ;) I've taught one person how I do it. I will write up something if need be (if you can't figure it out.)
The big thing that I've learned while cooking is that you HAVE to develop SOME things yourself because while you do all the researching, you'll uncover a LOOOOOT of cool things that you wouldn't have known you wanted.

When I learned how to cook, there weren't any walkthroughs. It was just a read the VERY little and make up the rest. That's where you learn the most. ^_^ With all the information put together, we can make it easier for anyone to get started. But the experts will be those who venture into the unknown. ;)


Hehe. Well I "venture" into these unknown files a lot. I don't enjoy reading that much, so if it's at all possible, I try to figure it out myself. Then I check online to see if I can find a tutorial. Then, if those 2 fail, I ask you.

And searching for the registry keys to edit sounds cool. I might hit u up about that later.

[ace10134]

Check the adobeflash and browseringie folders. Some of those modules require a native 6.5 nk.exe with the two memory slots. You'll have to convert those modules to files.

So, Ivan, I got some of WM6.5 to boot. I've been porting the SYS folders, one by one. I've identified that the Base_Lang_0409 and the OS folders are the one's that cause it to not boot.

I can just leave those folders out of the port, and use the old ones, but if I use the old OS folder, will that have any effect on the ROM???

[ivanmmj]

You should really use a newer base_land_0409 (find another one to replace it, if you have to.) It's strange that that's what fixing the issue. Did you check the modules that I mentioned?

[ace10134]

You should really use a newer base_land_0409 (find another one to replace it, if you have to.) It's strange that that's what fixing the issue. Did you check the modules that I mentioned?

I haven't tried replacing those modules, since the phone booted fine with them as-is. But I guess I'll try those and see if they make any difference in combination with the new Base_Lang_0409

[ace10134]

I haven't tried replacing those modules, since the phone booted fine with them as-is. But I guess I'll try those and see if they make any difference in combination with the new Base_Lang_0409

Well, actually, Holly's kitchen doesn't have a nk.exe folder/file anywhere. Neither does the 23016 SYS folder. Weird.

[ace10134]

Well, actually, Holly's kitchen doesn't have a nk.exe folder/file anywhere. Neither does the 23016 SYS folder. Weird.

The nk.exe folder is actually located in the XIP folder. I haven't ported the XIP yet, since I could never get anything to work, I've been working on the SYS only.

But I guess I'll replace the nk.exe folder with a new 6.5 build one. I'll see if that makes a difference!

[ivanmmj]

Well, actually, Holly's kitchen doesn't have a nk.exe folder/file anywhere. Neither does the 23016 SYS folder. Weird.
Do NOT replace the nk.exe.
It's device specific.


You have to port the XIP for the SYS to work properly. It's both or nothing. But the XIP has to be ported properly.

[ace10134]

Do NOT replace the nk.exe.
It's device specific.


You have to port the XIP for the SYS to work properly. It's both or nothing. But the XIP has to be ported properly.

Ok, well, I did port everything previously, and it didn't work. That's why I was just working on the SYS individually, to see what was breaking it.

[ivanmmj]

Ok, well, I did port everything previously, and it didn't work. That's why I was just working on the SYS individually, to see what was breaking it.
How are you porting everything in general? Maybe I can help you with it all.

[DrE_braxx]

oh wow.........................

[ace10134]

How are you porting everything in general? Maybe I can help you with it all.

Yea, you CAN help me!!!

So, this is what I've done so far...


Started with Holly's Kitchen
Replaced SYS folders one-by-one, identified that Base_Lang_0409 and OS folders cause the phone to not boot
Then I tried porting the XIP folder, since you said it's all or nothing. Not sure how to exactly port the XIP though.
For the XIP, I have the 23016 XIP folder from another kitchen (QVGA). Would I just use that XIP folder? Are there some folders that must stay in the XIP?


I hope you can help me somehow. If you need more info, just ask me, and I'll try to tell you.

[ace10134]

This is the kitchen that I got the 23016 files from (http://www.sendspace.com/file/6kwauc)

So maybe if you look into those files, then you can see what I'd have to do, instead of just navigating blindly.

Think you can help me?

[ivanmmj]

Yea, you CAN help me!!!

So, this is what I've done so far...


Started with Holly's Kitchen
Replaced SYS folders one-by-one, identified that Base_Lang_0409 and OS folders cause the phone to not boot
Then I tried porting the XIP folder, since you said it's all or nothing. Not sure how to exactly port the XIP though.
For the XIP, I have the 23016 XIP folder from another kitchen (QVGA). Would I just use that XIP folder? Are there some folders that must stay in the XIP?


I hope you can help me somehow. If you need more info, just ask me, and I'll try to tell you.
Depending on how your XIP is set up from that other kitchen: Does it have a MSXIPKernel folder?
If not, we can get around that.
Don't replace SYS folders, just dump out the old ones and use the new ones only. There might be DSM's that change names and that will cause a problem. Did you convert those modules to files that I mentioned?

[ace10134]

Depending on how your XIP is set up from that other kitchen: Does it have a MSXIPKernel folder?
If not, we can get around that.
Don't replace SYS folders, just dump out the old ones and use the new ones only. There might be DSM's that change names and that will cause a problem. Did you convert those modules to files that I mentioned?

The 23016 kitchen doesn't have a MSXIPKernal folder. Neither does Holly's kitchen.

When replacing SYS folders, I delete the entire SYS folders and then copy in the other new folders. I don't just tell it to "replace", since I don't trust what it's doing, so that's all good.

And I couldn't find those "nk.exe" folders or whatever you told me to convert from modules to files. So I'm not sure about that. You can download the kitchen that I linked to in the last post and look around, see if you can find those.

[ivanmmj]

The 23016 kitchen doesn't have a MSXIPKernal folder. Neither does Holly's kitchen.

When replacing SYS folders, I delete the entire SYS folders and then copy in the other new folders. I don't just tell it to "replace", since I don't trust what it's doing, so that's all good.

And I couldn't find those "nk.exe" folders or whatever you told me to convert from modules to files. So I'm not sure about that. You can download the kitchen that I linked to in the last post and look around, see if you can find those.
1. I should say, keep your original ROM's VM folder in the SYS but everything else throw away and replace.

Don't touch the nk.exe. Look around for platformrebuilder. It comes with a tool that will let you use the DSM's in the XIP to organize the XIP files. Use that and the copy all the files/modules in the MSXIPKernel into your XIP, leaving all the other older files there.
The files that I want you to convert are all the files in the adobeflash folder and the browsingie folder.

[ace10134]

1. I should say, keep your original ROM's VM folder in the SYS but everything else throw away and replace.

I always do that, Ivan. That's straight from your guide. Also, there's no need to keep shell32 and shellres, since my SYS folder is the same resolution? And I don't need to keep the WinCLES folder either? Just keep VM? Ok.

Don't touch the nk.exe. Look around for platformrebuilder. It comes with a tool that will let you use the DSM's in the XIP to organize the XIP files. Use that and the copy all the files/modules in the MSXIPKernel into your XIP, leaving all the other older files there.
The files that I want you to convert are all the files in the adobeflash folder and the browsingie folder.

I'll find PlatformRebuilder. And I'll look at those files->modules.

[ivanmmj]

I always do that, Ivan. That's straight from your guide. Also, there's no need to keep shell32 and shellres, since my SYS folder is the same resolution? And I don't need to keep the WinCLES folder either? Just keep VM? Ok.



I'll find PlatformRebuilder. And I'll look at those files->modules.
Correct. My guide is a little on the older side. Don't keep the older shell stuff or it will cause problems with the newer builds. Especially the 6.5 builds.
Same with the Wincles folder. JUST the VM.
And remember, modules to files. Check to see if there are even any modules on it right now. They might have already been converted by someone.

[ace10134]

Correct. My guide is a little on the older side. Don't keep the older shell stuff or it will cause problems with the newer builds. Especially the 6.5 builds.
Same with the Wincles folder. JUST the VM.
And remember, modules to files. Check to see if there are even any modules on it right now. They might have already been converted by someone.

What do modules look like, anyways?? I haven't looked up those, yet. Looking at the Platformbuilder thing right now.

And here's what the AdobeFlash and broswingie folders look like: (There's no AdobeFlash_0409, seems like it's all in one folder) (sry about small resolution, fixing it...)

http://forum.xda-developers.com/attachment.php?attachmentid=211601&stc=1&d=1249233410
http://forum.xda-developers.com/attachment.php?attachmentid=211602&stc=1&d=1249233410

[ivanmmj]

What do modules look like, anyways?? I haven't looked up those, yet. Looking at the Platformbuilder thing right now.

And here's what the AdobeFlash and broswingie folders look like: (There's no AdobeFlash_0409, seems like it's all in one folder) (sry about small resolution, fixing it...)

http://forum.xda-developers.com/attachment.php?attachmentid=211601&stc=1&d=1249233410
http://forum.xda-developers.com/attachment.php?attachmentid=211602&stc=1&d=1249233410
Those folders within the packages that have file names are modules. (Also, the 0409 folders are just the language files for wwe (English).)

[ace10134]

Those folders within the packages that have file names are modules. (Also, the 0409 folders are just the language files for wwe (English).)

So then those DO need to be changed? I'll look into it tonight. Hopefully I'll get 6.5 working today, that'd be cool.

[ivanmmj]

So then those DO need to be changed? I'll look into it tonight. Hopefully I'll get 6.5 working today, that'd be cool.
Yes. They need to be converted into files. If not, they'll throw off random errors that will cause the ROM not to boot for seemingly random reasons. (My SuperJustKitchen also has the feature to turn modules directly into files and viceversa. (Built-in feature of ervius's visual kitchen which is the base to my kitchen.)

[ace10134]

Yes. They need to be converted into files. If not, they'll throw off random errors that will cause the ROM not to boot for seemingly random reasons. (My SuperJustKitchen also has the feature to turn modules directly into files and viceversa. (Built-in feature of ervius's visual kitchen which is the base to my kitchen.)

K cool. Yea I tried making a kitchen off of Ervius's, but just got too tired. I'll tell you when I start working on 6.5 tonight.

[ace10134]

Ivan, one more question...

When you're porting the XIP, do you also need to use the "xip.bin" or "out.bin" or whatever you call it? I know that it's used to dump the XIP, but do you still need it after that? Or just leave the old one and it won't make a difference?

And I think I'm about to try 6.5 again, once I get home.

[bigdee]

is this rdy for use ? where is downlod link ?looking good keep up good work

[ivanmmj]

Ivan, one more question...

When you're porting the XIP, do you also need to use the "xip.bin" or "out.bin" or whatever you call it? I know that it's used to dump the XIP, but do you still need it after that? Or just leave the old one and it won't make a difference?

And I think I'm about to try 6.5 again, once I get home.
You don't need the new one. Some kitchens keep a copy of the original one in the ROM folder, but it's not really needed, either.

[ace10134]

is this rdy for use ? where is downlod link ?

NO.

It's NOT a ROM. It's for discussion. I'm making a 6.5 ROM as we speak.

IVAN!!!!!!!!!!!!!
Thank you soooo much dude, I got 6.5 working!!! Made my own ROM!! Ivan, I'm gonna donate to you soon. that PackageBuilder worked, got it working in about 30 minutes, easiest thing I've ever done! I should probably dontate to Bepe, too, for the awesome tool. But we'll see. I know you, Ivan, so I wanna donate to you. And you're the one that inspired me, youre the one that stuck with the Wings, you're the one that's the boss.

Ok. I'm just so freakin happy I cooked 6.5!!!!!!!!!!!!!!1 Ok. I think I'm done. Thanks again Ivan, I'll donate some time this week or so. If I donated now, I'd end up giving you $100. I'm just in the moment right now.

Ok. now done. Thanks again Ivan. I'm gonna optimize this 6.5 babby.

[ace10134]

So, Ivan, you probably know why ExtROM freezes in WM6.5, right?

Right after you flash your phone, calibrate the screen, the initial setup tries to run, and then it freezes the phone. Soft reseting makes it work.

I know it's a problem with the ExtROM, because when you remove Config.txt, it all works fine.

Did you ever find a fix for it, Ivan? Or did you just do what I did?

[ace10134]

And THIS (http://forum.xda-developers.com/showpost.php?p=4215191&postcount=10) is how I got Windows Mobile 6.5 ported.

The PackageBuilder worked perfectly Ivan, I didn't even have to do the modules to files thing.

The guide took longer to write up than it did to originally figure out!

[ivanmmj]

haha. Awesome to hear that it worked! ^_^
As far as it freezing, mine doesn't freeze so it must be something that your ExtROM or your local config.txt file is calling. Show me what's in your config.txt.

[ace10134]

haha. Awesome to hear that it worked! ^_^
As far as it freezing, mine doesn't freeze so it must be something that your ExtROM or your local config.txt file is calling. Show me what's in your config.txt.

Well it's basically an empty Config.txt I think it goes something like this...

LOCK:Disabled
XML:/ExtROM/Wing.Dev.01.xml
RST:Reset
LOCK:Enabled


I know thats not formatted right, wrote it from mmy phone. But thats the only thing it has in it, the XML..

[ivanmmj]

Strange.... it might be having a hard time accessing your ExtROM.
What's in that Wing.Dev.01.xml? If it's your file, just move it to the ROM and call it from /Windows/Wing.Dev.01.xml instead and see what happens. (I never use the ExtROM (since everything is already cooked in my ROMs, so I've never noticed whether it freezes 6.5 or not.)

[ace10134]

Strange.... it might be having a hard time accessing your ExtROM.
What's in that Wing.Dev.01.xml? If it's your file, just move it to the ROM and call it from /Windows/Wing.Dev.01.xml instead and see what happens. (I never use the ExtROM (since everything is already cooked in my ROMs, so I've never noticed whether it freezes 6.5 or not.)

Well it's actually called WingDev_Config.xml, and it looks like this...

<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\OEM" translation="filesystem" >
<parm name="ExtROMVersion" datatype="string" value="WingDev.01" translation="filesystem" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

So what does that do, then? You have any ideas on what to do about it?

[ivanmmj]

Well it's actually called WingDev_Config.xml, and it looks like this...

<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\OEM" translation="filesystem" >
<parm name="ExtROMVersion" datatype="string" value="WingDev.01" translation="filesystem" />
</characteristic>
</characteristic>
</wap-provisioningdoc>So what does that do, then? You have any ideas on what to do about it?
It just sets the ExtROMVersion in the registry. Not needed. (But strange... that means that you have a Dev ExtROM from Tmobile...)