Latest Windows Mobile Builds [SYS|XIP.bin]

Search This thread

AndrewSh

Senior Member
Jan 17, 2006
2,081
846
Minsk
forum.asusmobile.ru
c_shekhar, about minor updates - it's Windows. How often do you get Windows Update notifications on your computer? Almost every day? Why do you think that Mobile Windows differs from other Windows?
Why "they" are releasing? Normally their aim - not to make you happy with new rom but to debug OS. Guys are just fixing some mistakes in the system.... And guys are not "leaking" anything to you or to me.....
 

akash_bidhuna

Senior Member
Jul 28, 2008
66
4
Lucknow
will this build work on htc elfin

i cooked rom by using this build 29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT
and it is stuck at smart mobility

any idea
 

akash_bidhuna

Senior Member
Jul 28, 2008
66
4
Lucknow
problem in startin elfin after flashing

i cooked a rom using official rom of htc elfin i.e wm6.1 and 29019_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT without removing any pakages from it

but after flashing by using this rom it stuck at smart mobility

i am using ipl 3.07 and spl 3.1 cmon hardspl

this is first time i am cooking.So i hav no idea about it.
 

malatest

Senior Member
Sep 26, 2008
107
11
Rivas Vaciamadrid
ppgprov missed in 29019?

First of all, thanks for all.
Is possible that build 29019 doesn´t need ppgprov package? Or is missed and I have to replace with one of another version? Thanks
 

AndrewSh

Senior Member
Jan 17, 2006
2,081
846
Minsk
forum.asusmobile.ru
First of all, thanks for all.
Is possible that build 29019 doesn´t need ppgprov package? Or is missed and I have to replace with one of another version? Thanks

Normally ppgprov is a piece of registry, which configures Push Proxy Gateway for SMS... Actually - you have your SIM card with predefined settings to configure it.
It's absolutely static thing so you can use any ppgprov package from any build.
 
  • Like
Reactions: malatest

akash_bidhuna

Senior Member
Jul 28, 2008
66
4
Lucknow
drivers instalation problem

by using wince.nls file from other build i am able install the windows.

But there is a problem at the time of installation screem alingnment option does not appears, and nor the customization option ,because of that not a single application is installed in my phone which i defined while cooking and also there is singnal and touch screen is not working properly


any idea what is happening?
 

Farmer Ted

Senior Member
Nov 30, 2008
2,373
90
Make sure you're sending custom.lnk to the startup folder with your initflashfiles.dat.

You should probably ask this stuff in the cooking for beginners thread.
 

pupakota

Senior Member
Sep 29, 2009
854
102
any idea what is happening?

check oem for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Welcome reg key, maybe it is set for ffffffff, then you won't get calibration on first boot(what's not a problem for device with startmenu hardkey and dpad, as it is possible to get into screen options, but it may be serious prob for buttonless devices without predefined screen alignment).
it may be a part of solution, i'd recommend check initflashfiles.dat for links to startup processes, too.

or you cut too much.
 
Last edited:

mureta

Senior Member
Aug 14, 2009
63
0
29017 and 29018

I am repeating my question again since I got no response or the way my question is very complex, does not find anything about it, if they can at least tell me where can I read about this I doubt I will be more than grateful and not wanting to interfere with topic.

I thank all.

My steps:

I leave only the dpi96/resh240x400 ... everything related to the Omnia, the retreat langs SIM_TKit 0409, SYS, I put my langs 0416 (Brazil) and also removed the msxipkernel (hd.dll and osaxst0.dll).

My question:

What am I doing wrong, I can not make it work on my Omnia these builds 29017 and 29018?

Loads the boot but no screen appears welcomehead to continue, it might be?

Any help will be of great size.

Tks so much.

mureta.
 

Farmer Ted

Senior Member
Nov 30, 2008
2,373
90
where will i get these files in dumped base rom or in new build
please give me the path .

The easiest and fastest thing to do is just search your kitchen directory.

Loads the boot but no screen appears welcomehead to continue, it might be?

Any help will be of great size.

Tks so much.

mureta.

It sounds like you may be leaving out wince.nls as well, but really, you could be doing any of hundreds of things wrong, and it's next to impossible for anyone else to figure it out, unless it's one of the obvious things. I'd recommend either putting wince.nls in your oemxipkernel or in your oem and leaving it there. Personally, I keep mine in the kernel.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    29022 – AKU 5312 Windows CE 5.2 Build 6215 (Apr 17 2011 15:49:35)
    WVGA 0409 only.
    Not the "dumped custom". Original stuff.

    And please, Leo or Ted or someone else with mod rights here - clean all the **** in the topic. At least since your deleted post, Leo and up to my current post.
    22
    15
    WM upgrade path.

    Since we're on the subject of new builds and how WEH fits into it, I thought I'd elaborate a bit on the future of our aging OS.


    attachment.php



    Windows Mobile 6 is in the end of its life. It reached the beginning of its end of life cycle in Q3 last year. In that time frame, Microsoft began deploying WP7. WP7 is not the successor to WM6 or WEH. The line of upgrades will follow a different path.

    As we all know, Windows Mobile is currently transitioning into Windows Embedded Handheld. Essentially, they are the same thing with a different name. Both use the CE5/6 core. Windows Phone 7 uses the CE 6 Revision 3 core in version 1. These systems are incompatible as we've been seeing. This breaks the upgrade chain for Windows Mobile. However, as I mentioned, WP7 is not the successor to WM6.

    As WEH picks up steam in its course this year, it will eventually transition into another iteration of itself. In the second half of this year, WEH is supposedly going to begin using Windows Embedded Compact 7 (WEC7) as its core. This provided us with an alternative upgrade path from the dead end of WP7.

    Windows Embedded Compact 7 began shipping at the end of last year to be used in slates and other consumer handheld devices. OEMs were encourages to add their own custom UIs. I don't have much information on WEC7 at the moment since it really hasn't hit any markets or news sources that I'm aware of.

    Keeping that in mind, it is also of note that WP7 is set to begin using WEC7 instead of CE6 as its core in the next major release of the platform. I don't know if this will be in any way compatible with other WM6/WEH devices, but I would say it's unlikely.

    It seems more likely that Microsoft is planning to separate their enterprise devices from their mass-market devices.


    attachment.php



    So to recap, Windows Mobile is set to be re-branded as Windows Embedded Handheld. Both using the CE5/6 core initially. Windows Embedded Handheld will eventually be updated to use the Windows Embedded Compact 7 core in late 2011. The platform will still be known as Windows Embedded Handheld at that point. This platform is supposedly aimed at enterprise level consumers.

    Windows Phone 7 currently uses the CE6 R2 core. It is scheduled to be updated to the Windows Embedded Compact 7 core later this year as well. It will also retain its name as Windows Phone 7. This platform is supposedly aimed at the mass-market consumers.

    Hopefully this clears up the upgrade path thing for most people. Stop worrying about Windows Mobile. The name is changing. It's not a big deal. It isn't a dead platform. (At least not yet, anyway. ;))
    12
    29018_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT
    Windows CE: 5.2 Build 6212 (Mar 13 2011. 15:48:25)

    Thanx to BoomerCE (DFT) for sharing, thanx to rewwps (asusmobile.ru) for reuploading
    12
    21690_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409_FROM_DFT
    Windows CE: 5.2 Build 3600 (Mar 29 2011. 15:43:01)

    Thnx to Boomer for sharing and to rewwps for re-uploading