Related
What you need
A stable radio rom, and id recommend that you skip using the
extended rom for now since there might be programs that is incompatible
with Windows Mobile 2005. So, get a blank extended rom for installing.
Id recommend using the new radio rom from WM2003SE that seems
to be the most stable so far.
To install this, you also need nk.nbf, Patch1.exe to patch nk.nbf to work
with your XDA II (whateverbrand). And you need the update utility.
Summary of files:
Actice Sync 4.0 beta.exe
HimaUpgradeUt.exe
nk.nbf
patch1.exe
"empty" extended rom. ms_nbf
1. Installing Activesync 4 Beta.
- Install ActiveSync 4. Make shure that you can sync with your XDA II
just like it is, with the current Windows Mobile.
- If you run into problems, remove ActiveSync and reinstall.
- If it still wont work, try removing the device driver in windows control
panel - system - device manager. Look for the driver on the error messege.
(have not tested this, but should work if you have driver problems)
2. Going to boot mode.
- Put your XDA II in boot mode, by pressing the direction key left while
holding the off button and then pressing reset button with your stylus.
- It should go black, displaying only a version Nr. Like V 1.03 or V 1.06.
3. Patching nk.nbf.
- Run the Patch1.exe to fix the nk.nbf for your XDA II.
- Now run the WM2005 update program (HimaUpgradeUt.exe) and follow
onscreen instructions. If it complains about Country ID, download
the tool ER2003Edit.
Link: http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Make shure you do as it says on the info page on this, so that you wont
change anything you shouldnt change!
When in boot mode, the thing to edit should normally be the brand name.
So set it to the brand on your XDA II.
4. Finishing up!
-When it is done, just reset your device and you all set.
5. About WM2005 bugs and stops.
- The new operating system handles memory differently, so you cant
install the programs in the default directory because of low memory install
it to the Storage Card (SD), in Active Sync 4.0 you can not chose this, but
you will be prompted on the device after install of a program.
- Some programs that have _not_ been rewritten into WM2003SE does
not work, and will likely to crash on WM2005.
That is mainly directed to programs that have heavy multimedia demands,
or rewrites the screen graphics.
- Be aware that bad SD card may slow down the system
extremely! But if that is the problem, i promise you will notice!
Skinning programs is to forget directly, i have not found a single program
that works.
- Pocketbreeze have problems updating on the Today screen, i do not
know if that is because of the new database system or if it is a new today
screen code. Also, contactbreeze does not work at all, seems like the
database for handling contacts is all new.
Good news!
Bluetooth works perfecly, and syncing is flawless, its faster and seems
more stable. (i will write more good things later, have to go eat now)
In all the excitement of the hacked ROM coming out - I need to ask one question. Why should I upgrade my BA to the WM5 ROM? What benefits does it offer over the existing WM2003SE ROMS?
I'm tempted like everyone else just to bung it on and update it every day for the next few weeks until it's working properly - I'm also tempted to wait for the official O2 1.4 ROM that works properly.
I must admit that I'm going to wait before upgrading to WM5. I see no compelling reason to upgrade other than "beacuse I can". I wouldn't necessarily wait for the official O2 1.40 ROMs though, you might be waiting forever. I use the imate 1.40 ROMs with no problems.
Having said that, I hope to get hold of a "spare" Blue Angel this week & might experiment with WM5 on it
The existing 1.4 ROMs are annoying for me because I have problems with GPRS and disconnections and a few other niggles that are hard to live with - whereas tghe O2 ROMs have these niggles fixed - hence the wait for the O2 1.4 ROM.
I was thinking of tinkering with the WM5 ROM, but not for a little while until a few things are sorted out, just to see what the interface was like but if it's too much hassle.....
I've got my heart set on an O2 Exec which looks like it might be out soon.
I use it and apart from lack of camera function and a longer boot up time, I MUCH prefer it over 2003SE. First it has a revamped design and it makes 2k3se looks boring.
OK, there are some stability issues but what can you expect for a leaked rom?
If you don't vitally depend on your BA i'd give it a try, and if you don't like it, get activesync 4 and flash back.
Now, seeing how we came accross WM5, is there reason to believe we will be getting the FINAL version of the WM5 firmware for the BA??
In other words, is Mamaich's patched WM5 version the best we're going to get??
What do y'all think?
man(darkblak) is askins simple...if someone knows what benefits gets with wm5...if someone had experience should tell us...im interested in that to... will be blueangel with wm5 faster or slower how will be in performances and itc...
10x in advance
WM5 on SX66 (Blue Angel)
I updated my SX66 to WM5 before the ROM was patched (by Mamaich)... and then spent the next few days working on the issues of performance/sound.
With sound disabled (prior to patch), the device was undoubtedly faster. I made registry changes to increase cache size, disable animations, etc. but I had made those changes in 2003SE as well... and WM5 still outperformed it by a significant margin.
As for the areas not dealing with speed/performance, the new OS requires some getting used to. Hardware buttons that are unassignable (old Windows and OK buttons are softkeys now) and a few other issues (such as GPRS on only when activated by Internet Explorer and Bluetooth shutdown on power off) were a little unnerving, but nothing that would make the OS unusable.
What makes WM5 indispensable is PERSISTENT STORAGE. This is the Holy Grail for all Windows Mobile devices prior to this OS. When your battery dies and your backup battery dies, you must re-load all of your aftermarket software and PIM info. Software such as Sprite Backup made this process easy... but what if you're mid-flight to another country without a laptop and your PDA crashes? This is not an issue with WM5. All after-market software and PIM data is stored to ROM (software install location is optional)... which means that it is stored in non-volatile memory. It is not lost during power/system failure. What this means in terms of device security is that the person that finds your PDA on your desk at work cannot simply "hard reset" it to remove all of your info and use it themselves... Your password/PIM data and software will still be secure/in place and only downgrading the device to 2003 and repartitioning the ROM will clear it.
At the moment, I have no issues with WM5 on my SX66. Editing the camera keys in the registry solved the issues with sound and there are plenty of patches available to reconfigure the hardware buttons, etc. But I'm learning to like the OS as shipped...
I've been using Windows Mobile for more than three years and this iteration is undoubtedly worth the upgrade. If you have the time and patience to read through these forums, make an installation checklist and then follow it to do the upgrade.
My checklist would read:
-Download patched WM2005 ROM
-Download MaUpgradeUT_NoID.exe
-Download all patch CABS
-Download DOC tool (Disk On Chip partition tool)
-Run DOC tool (if successful, the ROM size is now ~63MB in control panel)
-Copy and rename the HTCRUU.dll and HTCRUU.conf files to RUU.dll and RUU.conf
-Run MaUpgradeUT_NoID.exe (if the first try is unsuccessful, put device into bootloader mode. Rec/Media/Power/Reset all at once)
-After upgrade check functionality BEFORE applying any patches, there are as many differences between just SX66's as there are between all of the Blue Angel devices... some patches may NOT be required.
-Apply patch CAB's
-Apply registry edits suggested in the forums for performance improvement
I hope this enlightens those waiting to see the efficacy of this ROM upgrade. I have had a good experience with WM5, in spite of the initial problems. I'm happy with its performance and will not downgrade to 2003SE unless I screw up WM5 bad enough to make it necessary to re-partition the ROM... then I'll go right back to WM5.
Cheers all...
MRwheeler2: Where is the edited rom on the FTP site? I cannot find it where it says it was, BA/test or something like that. Where can I get it from
Also, I have noticed that using the standard rom I cannot change bootup images. It is constantly the stupid colour thing (how about that for a name!) and it's more like a TV test screen.
Download locations for patched ROM
Sorry for the delay... I was out.
You can download the patched ROM from: ftp://xda-developers.com/Uploads/Blueangel/WM5Pack/
There currentyly isn't a fix for the boot screen... I'm looking right now at the MSDN site for CE5.0 and searching their registry settings for Bluetooth and boot screen. Nothing yet... I'll post a new thread if I figure it out.
Hope this helps...
any reason that I'm getting permission denied errors?
I'm logged in but can't do it withe IE or FF, and firewall on or off.
One says permission denied, the other says can't find.
Download locations for patched ROM... continued.
Looks as if it was moved... Try the BlueAngel/BA_WM5/Shipped_Extracted_Updates folder and look for WM5_pack_v1.rar
That should do it...
Good luck.
Still says 530 permission denied. I tried looking in some of the higher level folders and still no joy.
Download locations for patched ROM... continued.
A 530 error is an incorrect login... Go to the "File" pull-down in Internet Explorer and click on "Log In" then when prompted, enter xda for both user name and password.
The default setting for Internet Explorer is to log in anonymously... most non-public FTP sites require some type of non-anonymous log in to ensure that the user has been referred from a site and not someone searching FTP servers.
Once you've logged in, you should be able to see a list of folders/files. You can use the "Folders" button if you would like to see a directory tree in the left panel.
Post a reply if you're successful (or if you're not)...
Later,
Mick...
10x mwheeler2 i will hawe that what u write in my mind...but 530 error i hawe still in ftp ... hope that will solve soon...
Download locations for patched ROM... continued.
For those still looking for the patched ROM...
try this:
ftp://xda:[email protected]/BlueAngel/BA_WM5/Shipped_Extracted_Updates/WM5_pack_V1.rar
The above link is on the wiki page for the upgrade:
http://wiki.xda-developers.com/index.php?pagename=BA_5.1.1700_build_14343_Upgrade
There is a walkthrough on the site and some helpful information...
Later,
mick...
Well - after reading all the stories about persistent storage and speed I was about to go ahead with the install until I found out that my main application TomTom 5 would not install - a quick search later found a workaround - seems like everyone is pulling together on this.
So I'm now running WM5 on my O2 XDA IIs and it's not too bad - it's no worse that O2's existing "beta/official" ROM (1.31) and there is very little reason not to go for the upgrade as it's easy to install - just a little hairy with the funny screens at the start.
I can't say that the I have noticed much difference with the speed issues once all my baggage is loaded on the machine. I'll keep checking the reg fixes etc from time to time.
The interface is much the same as the old interface apart from a few nice touches - but as someone said earlier the ability to re-map certain keys is a pain - until you become used to the context sensitive buttons.
All in all - probably worth the upgrade - you just have to get used to the new ways that some things work.
Where can I download the files to update my SX66 to WM5
I did try to search the fourm but can someone please send me the web link to where I can down load the files to upgrade my Cingular/Siemens SX66 to WM5?
Thank you and I have donate to BA***
mwheeler2 said:
I updated my SX66 to WM5 before the ROM was patched (by Mamaich)... and then spent the next few days working on the issues of performance/sound.
With sound disabled (prior to patch), the device was undoubtedly faster. I made registry changes to increase cache size, disable animations, etc. but I had made those changes in 2003SE as well... and WM5 still outperformed it by a significant margin.
As for the areas not dealing with speed/performance, the new OS requires some getting used to. Hardware buttons that are unassignable (old Windows and OK buttons are softkeys now) and a few other issues (such as GPRS on only when activated by Internet Explorer and Bluetooth shutdown on power off) were a little unnerving, but nothing that would make the OS unusable.
What makes WM5 indispensable is PERSISTENT STORAGE. This is the Holy Grail for all Windows Mobile devices prior to this OS. When your battery dies and your backup battery dies, you must re-load all of your aftermarket software and PIM info. Software such as Sprite Backup made this process easy... but what if you're mid-flight to another country without a laptop and your PDA crashes? This is not an issue with WM5. All after-market software and PIM data is stored to ROM (software install location is optional)... which means that it is stored in non-volatile memory. It is not lost during power/system failure. What this means in terms of device security is that the person that finds your PDA on your desk at work cannot simply "hard reset" it to remove all of your info and use it themselves... Your password/PIM data and software will still be secure/in place and only downgrading the device to 2003 and repartitioning the ROM will clear it.
At the moment, I have no issues with WM5 on my SX66. Editing the camera keys in the registry solved the issues with sound and there are plenty of patches available to reconfigure the hardware buttons, etc. But I'm learning to like the OS as shipped...
I've been using Windows Mobile for more than three years and this iteration is undoubtedly worth the upgrade. If you have the time and patience to read through these forums, make an installation checklist and then follow it to do the upgrade.
My checklist would read:
-Download patched WM2005 ROM
-Download MaUpgradeUT_NoID.exe
-Download all patch CABS
-Download DOC tool (Disk On Chip partition tool)
-Run DOC tool (if successful, the ROM size is now ~63MB in control panel)
-Copy and rename the HTCRUU.dll and HTCRUU.conf files to RUU.dll and RUU.conf
-Run MaUpgradeUT_NoID.exe (if the first try is unsuccessful, put device into bootloader mode. Rec/Media/Power/Reset all at once)
-After upgrade check functionality BEFORE applying any patches, there are as many differences between just SX66's as there are between all of the Blue Angel devices... some patches may NOT be required.
-Apply patch CAB's
-Apply registry edits suggested in the forums for performance improvement
I hope this enlightens those waiting to see the efficacy of this ROM upgrade. I have had a good experience with WM5, in spite of the initial problems. I'm happy with its performance and will not downgrade to 2003SE unless I screw up WM5 bad enough to make it necessary to re-partition the ROM... then I'll go right back to WM5.
Cheers all...
Click to expand...
Click to collapse
Hi
Does anyone know how to setup IGuidance to work with WM5? I dont know how to work the BT ports at all. In 2003se, i could use the "scan" for bt data and it'd find the itrek gps unit but now it results in "no gps found". alternatively, what other gps software will work other than tomtom? I dont have tomtom =(
I've got version 2.1 and it seems to work with WM5. I add the gps to the bluetooth and then I create an incoming and outgoing port. I set my gps to port 6. In IGuidance it won't detect the gps but if you manually choose port 6 it will work just fine.
Andy
iGuidance 2.1.3 locks up my Wizard after several minutes. Grrr...
I am having all sorts of trouble with my PDA2K (WM5) and iGuidance. Although I think it has more to do with my bluetooth than anything. When I first started trying to get it to work it gave me coordinates that I was in Africa... Anyway, I think I am going to go back to 2003SE.
I'm having a different problem with iGuidance v2.1.3 on WM5. It installs and runs just fine. I use BT over COM6 and it seems fine. The problem I have is that the coordinates are off. The strange thing is that when I run GPSInfo (a separate app) it shows the correct coordinates - iGudiance thinks they are different and thinks I'm in a different location ( a few miles away).
I gave up on it and decided to go back to 2003SE (iGuidace v2.1 that worked perfectly fine on that configuration a long time ago). I followed teh steps to format/clean hive and did the down grade but am having a different problem. I've seen other people running into similar issues but I've not been able to get around it
"BTTrayCE - bluetooth can no longer be used because the license has expired" - I have tried a number of things using different BT stacks, 2003SE builds, reset (soft+hard) etc. Same problem!!! Argh - I'm stuck. I really miss my GPS!
Hi krille,
I also had similar problems with my SX66 and iGuidance and finally decided to go back to win 2003 because it worked fine with it. In WM5 my BT GPS receiver was never able to make a connection with iGuidance. But now I am having a different problem. I cannot downgrade even though I followed all the instructions correctly posted on the BA_Downgrade page. The upgrade program ( MaUpgradeUt_noID.exe ) does not seem to identify the rom versions and though it gives me a successfully upgraded message nothing had happened. I cannot downgrade now and stuck with WM5. Did any of you experience this when downgrading and can offer me any help.
DEK.
I've been upgrading/downgrading with differnt ROMs without any problems
Make sure to disable activesync on the pc and copy the nbf files as described in http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5. Sometimes the verion info update to/from doesn't show between WM5/2003SE...
What happens when you click Update to continue?
BaUpgradeUt.exe worked
Thanks for your reply. I followed all the steps as described in the link you have sent but MaUpgradeUt_noID.exe did not upgrade (downgrade to 2003SE) though I got a message saying it did. Then I tried the file BaUpgradeUt.exe in PH20B folder and it did work. My device data file says my SX66 is in fact PH20B1 though. I do not know why MaUpgradeUt_noID.exe cannot update my ROM. Anyway I am happy now with my WM2003SE and iGuidance and BT all work faster with ROM update to 1.40. Now I am planing to customize my ExtROM to have all my personal settings and programs so that I want feel bad not having WM2005. Thanks for your willingness to help.
DEK.
HI,
I am trying to run this GPS application called GPS DIS 'GPS Driver Information Service and works with all PDAs running Pocket PC 2002 or higher
GPS DIS was developed for PocketPC 2002. With PocketPC 2003 you will have to install the appropriate VB runtime files.
I have loaded the VB Runtime files onto my P3600i as well as the GPS DIS. The install completes fully, and when i launch the application, i see the spinning microsoft icon indicating its loading then it disappears then returns then disappears again. (It does not lock up)
Then nothing actually loads.
Can someone help, possibly try to load this and let me know if they get a different response.
Does anyone know if VB runtime is included in WM6? If not, which is the best one to install into WM6?
thanks
polite bump,
surely some experts can shed some light on this.
bump bump.
I am also looking to find a vb runtime module for wm6.
pls, any one have any ideas how to achieve this.
As far as I Know there isn't anyone VB Runtime for WM6. Microsoft doesn't support it anymore. I also needed it...
PS: found a way to install it: Install in main memory or internal storage, not in SD. See: http://www.cebeans.com/runtime/runtime.htm
Hi Bicalho,
Can you tell me if GPS application called GPS DIS 'GPS Driver Information Service will run with your method?
Thanks!
GLO said:
HI,
I am trying to run this GPS application called GPS DIS 'GPS Driver Information Service and works with all PDAs running Pocket PC 2002 or higher
GPS DIS was developed for PocketPC 2002. With PocketPC 2003 you will have to install the appropriate VB runtime files.
I have loaded the VB Runtime files onto my P3600i as well as the GPS DIS. The install completes fully, and when i launch the application, i see the spinning microsoft icon indicating its loading then it disappears then returns then disappears again. (It does not lock up)
Then nothing actually loads.
Can someone help, possibly try to load this and let me know if they get a different response.
Click to expand...
Click to collapse
Download it from here http://msdn.microsoft.com/mobility/windowsmobile/downloads/evb_eula.aspx and install in Device memory...it should work.
I tried this again with some hope, but again, both apps GPSDIS and VBruntime install successfully and when launching GPSDIS i get the ' you have X times remaining for this trial' then that disappears and the spinning beach ball returns for a couple of seconds then dissapears and nothing.
The search continues...
any new ideas please
uber noob here
just got my htc hermes 100, wanting to update to WM6 (from 5) follow all the steps in page 1, did two things
save the RUUwrapper an that NBH file to my pc, while my phone is sync tried running the file and got error msg (the application failed to initialize properly (0xc0000135)
one last thing i did was copied both files in my phone and run it, got this msg this time (thid spplication (ruuwraper.exe)requires newwr version of ms.net etc)i'm lost, i know this is the 1st step i need to do to make it a WM6 ryt?
Hi...read mrvanx's guide before flashing:
http://forum.xda-developers.com/showthread.php?t=299462
You must to put hardspl on FIRST! U need to install NETCF on your PC. Do not put the ruu or rom files on your PPC and run them. Take Care
lordaxel said:
uber noob here
just got my htc hermes 100, wanting to update to WM6 (from 5) follow all the steps in page 1, did two things
save the RUUwrapper an that NBH file to my pc, while my phone is sync tried running the file and got error msg (the application failed to initialize properly (0xc0000135)
one last thing i did was copied both files in my phone and run it, got this msg this time (thid spplication (ruuwraper.exe)requires newwr version of ms.net etc)i'm lost, i know this is the 1st step i need to do to make it a WM6 ryt?
Click to expand...
Click to collapse
You forgotten one step. Please read the wiki on upgrading
i've just installed NETCF on my pc,copied the RUU_signed.nbh and RUUWrapper on a folder on my desktop (PC) and run the RUUWrapper file while my phone is sync to my PC and get this error ( the appilication failed to initialize properly (0xc0000135) .click on OK to terminate the application)
im not sure what to do next, this is the 1st step and i keep on getting errors, em i doing something wrong? please help!!!
lordaxel said:
i've just installed NETCF on my pc,copied the RUU_signed.nbh and RUUWrapper on a folder on my desktop (PC) and run the RUUWrapper file while my phone is sync to my PC and get this error ( the appilication failed to initialize properly (0xc0000135) .click on OK to terminate the application)
im not sure what to do next, this is the 1st step and i keep on getting errors, em i doing something wrong? please help!!!
Click to expand...
Click to collapse
Let mrvanx hold your hand READ!!
http://www.mrvanx.org/thg/ <------ cLIck hErE
OK I'll happily admit to being a NOOB as well but I have had exactly the same issue and I don't think (and I read the guides many times!) that the answer is there. So it is not helping simply endlessly pointing to the guides (helpful though they are).
The point seems to be that you need the Microsoft 2.0 .NET framework installed on your PC (i.e. the computer not the phone) rather than the NETCF mentioned above.
I think (assuming that I am right!) it would be great to add this clearly to the guide ("Make sure sure your computer has Microsoft .NET 2.0 Installed") preferably with a link to the Microsoft download site for .NET as well.
eliseman said:
OK I'll happily admit to being a NOOB as well but I have had exactly the same issue and I don't think (and I read the guides many times!) that the answer is there. So it is not helping simply endlessly pointing to the guides (helpful though they are).
The point seems to be that you need the Microsoft 2.0 .NET framework installed on your PC (i.e. the computer not the phone) rather than the NETCF mentioned above.
I think (assuming that I am right!) it would be great to add this clearly to the guide ("Make sure sure your computer has Microsoft .NET 2.0 Installed") preferably with a link to the Microsoft download site for .NET as well.
Click to expand...
Click to collapse
I once was a noob too, this is three months ago, and I had spent days on reading up before I did my first flash. The wiki is there just for that! hmm, also with .net framework, you'll be surprise how many software these days that will run WITHOUT them installed.
Hi . I had same problem with my 3 PCs. I downloaded latest version of .NET framework from microsoft site & reinstalled it & WOW.. it started..
zocster said:
I once was a noob too, this is three months ago, and I had spent days on reading up before I did my first flash. The wiki is there just for that! hmm, also with .net framework, you'll be surprise how many software these days that will run WITHOUT them installed.
Click to expand...
Click to collapse
.Net Framwork is required ONLY by software that is written directly for it and does NOT include the required DLLs in the app itself...which is most. C# is one language that you MUST have the framwork installed most of the time. Very few people want to include the DLLs because people SHOULD have the .Net Framework installed anywas.
This thread was very useful by the way. I'd come across this problem today and it's helped me to solve it. I'm sure any noobs (like myself) will find this thread useful in future.
Just wanted to add one thing, RUUWrapper was crashing on me as well.....
You cannot run this from a network drive! Has to be ran from a local drive, or it crashes...heh (I have a main file server setup over gigabit)
If you've read up then you have Hard SPL installed. That means you can bypass the computer for the flashing. You can use the sd card method. I believe its safer and doesn't have those niggly little sync errors and there's less chance of the phone crashing/being reset or powered off. Recommended if you flash the radio rom where a simple problem results in a permanent brick.
Cheers...