(ask) what happen if I upgrade wm 5.0? - MDA III, XDA III, PDA2k, 9090 General

What happen if my BA was upgrade to wm 5.0 but I forget to push Hard reset n next configuration? I upgrade with Helmi AKU 3.2 v13.2 paging16mb Ramdisk32mb. I only upgrade & no push any key after upgrade.

I don't understand why you wouldn't push the reset buttons (or why you chose the 16/32 as opposed to the 32/16), but resetting your unit after a flash allows the changed settings to take effect fully. I don't know that you will have an undesirable outcome to not resetting, but it's your choice.

balakhan said:
I don't understand why you wouldn't push the reset buttons (or why you chose the 16/32 as opposed to the 32/16), but resetting your unit after a flash allows the changed settings to take effect fully. I don't know that you will have an undesirable outcome to not resetting, but it's your choice.
Click to expand...
Click to collapse
since My BA has upgrade, I think is fine ( from now ). I didn't find a serious problem. What the fully effect if I hard reset my device n push the key?

Related

The O2 GUI

If i delete this software from the add/remove programs will it clear the O2 software off and just leave me with the windows interface?
Secondly is it wise and can I get the software back if need be? Will I still have the phone software if I delete the O2 stuff?
The best way to do it is to do a hard reset and install the corporate version , which doesnt install the silly O2 stuff.
To do that poke the reset hole with the stylus and press the Power button at the same time (WARNING you will loose all programs/settings)
Then when it is installing it will ask either personal use or corporate ... Choose "Corporate User" when asked for the password put "0506" as the password.
backup your phone with Activesync first incase you want to return to the way it was before.

CLEAN O2 XDA IIs Reset (Skip ALL crap o2 software install)

I was reading through some previous threads on how to get rid of the dreaded O2 Active software that installs upon a Hard Reset.
One of the options people gave was to do a hard reset and select the infamous "Corporate Mode". Unfortunately I did not have this corporate mode option with my version of the ROM (1.31 WWE).
What I did notice, however, was after the Hard Reset, all this crap O2 software installs itself with a convenient little "warning" message stating it will do so.
In order to skip the O2 software install, just do a quick soft reset right before the software begins to install itself, and score, a fresh CLEAN O2 free install!
PS: I was also having problems getting T-Mobile GPRS to work on this device. But after a nice clean install with no O2 crud, GPRS worked fine.
All good - one major problem...
No MMS Settings - not even the MMS Options in menu!
Someone suggested on another forum to copy the .cab from ext ROM first, I cannot do this with File Explorer.
On a Palm I would use Filez - any similar prog for PPC?
Alternatively - how did you overcome this yourself if you have another way?
The hard reset once re-booted should start to load the OS at the end of this you are presented with a screen (for around 30 Sec) it is at this stage you select Corporate mode and enter the 0506 key - if you leave the device unattended then it will time out and load all the active rubish that wrecks the phone - mike
All sorted thanks.
Did the Corporate start so clean machine. Still got some crap.
So, instead soft reset just after hard reset before ANYTHING installed. Then installed all the .cab files that did not have O2 in the name from ext ROM. The MMS details I wrote down prior to Hard reset this time.
Sorted! Yay!
After the hard reset and corp install - what remained on the unit that you didn't want? - just interested - Mike

WM5 on BA - Why Upgrade?

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

4 color bands at boot

Hi,
I have a problem with my QTek 9090.
when i want to hard reset it, (power, record, camera and reset) it just displayed the 4 colored bands and stuck here.
how can i restore the normal booting sequence ?
thx.
this is normal, no problem. OS is kichen, no orginal. My Qtek work perfect WM6. Thanks Helmi!
so what should i do because it is block on this stupid 4 colored bands screen...
hard and soft reset do not help.
are you sure you have chosen No/Yes/Yes to clean the registy hive and format the storage at hard reset?
have you pressed the Mail Button to execute the instruction?
being stuck at the 4color screen is a common glitch in wm6 upgrading but nothing serious, that's because even though you flashed the ROM, your storage still has the files of your OLD Os (ex. WM2003).
you have to format the storage to have a fresh and working OS.
the problem is that i did not get any message on screen to which i can answer yes or no :-(
i effectively read some article in this forum about such step, but my Qtek 9090 did not propose me something like that !
:-(
i tried the steps you posted in http://forum.xda-developers.com/showpost.php?p=1603200&postcount=8
but the menu is never displayed :-(
oh... ok.
try pressing Camera + Record... before you stick the Soft Reset.
hold them until you see the menu.
if that doesnt work. then maybe one of the required button is failing.
good luck!
unfortunatelly, it does not work :-(
this is making me crazy...
try searching for MMTY hard reset. that's probably the thing that you need.
i did not find anything about MMTY and hard reset...
:-(
any additional help would be very appreciated
You would find you get a better response if you explain what rom it was that you were installing when this happened,was the rom for your device and did it complete fully?
scousemartin is right... we need details.
about MTTY ok...
here's a link about MTTY on Hermes Bootloader... some of its commands are general and can be used on BA with care.
look for something specific to your problem
i.e. Task 28 to format your DOC.

Password bug or something windows mobile 6.5

I've got very bad problem. I've set password on Windows Mobile 6.5 in my MDA III. And someday it happened... I couldn't turn on the phone mode so I've used soft reset option in xcpuscalar mounted on device. At start it asked me for the password. I'm 100% sure I've typed the correct password (even compared with password I wrote in my notes) and it says that's "The password you typed is incorrect".
I tried several times and nothing. I tried even to hard reset (Power button + reset button), but it seems it does only soft reset (so I don't know how to hard reset it at all). I've tried to discharge backup battery, even took it of. Nothing helps. Please help me with this.
I want to hard reset, but I don't know how? The procedure has changed since WM 6.5? Or help me with solving problem otherwise.
Sorry for my bad english.
the password bug is long since known. that's why it is generally better not to set one on a cooked rom. as far as i know there is no way to reset the password, so i would advise you to hard reset.
that is indeed done differently in wm6.5 than in wm2003
you have to press power +reset and then immediately press camera+record.
a menu should appear.
using the camera and record buttons you set the menu entries from "NO", "NO", "YES" to "YES", "YES", "NO" and press the mail button to confirm, after a little while the device restarts and is hard resetted.
Have the same problem, company policy is enforcing password security....
No chance to cheat that bug? Or any rom without that secured evaluation mode available ?
Thanks and best regards,
Muskote
WM 6.5 lock issue
I have the same issue on my HTC Vogue phone, I haven't hard reset it because I can still answer calls, and I would like to synchronize 1 last time before I hard reset and have to reinstall all my apps. Anybody have a way of bypassing this feature? An NV item to change maybe? I can mtty when I boot into bootloader screen and "rtask c" to get into diag mode and access CDMA section of phone, anything I can do from there? The lock on CDMA is not the same of the WM 6.5
muskote75 said:
Have the same problem, company policy is enforcing password security....
Click to expand...
Click to collapse
They enforce password security but let you flash the device with a ROM of obscure to unknown origin?
Dirk
spades you nailed it again, exactly what i was thinking, plus there is still nothing new to say, that i didn't write in my other posts, and also, this is the blueangel section, not the vogue's we are 99% dealing with gsm devices here, nearly no cdma.
sorry can't help you.
Same problem here...
I'm facing the same problem...
My phone is HTC Himalaya (XDA II) with WM6.5
I cant enter my phone. it keep asking password altough i entered the correct password.
And it doesnt confirm anything, like ur password is wrong.
the button is pressed but nothing happends.
My contact and my task are synced with exchange server, but i hav plenty important SMS in that phone...
Is anything i can do except hard reset the device?
Btw, i still can receive any call.
Last nite this phone is OKAY, the problem appeared in the morning.
Micro**ft let me down again.
Anyone please help me!!!
as probably you are aware of the fact that this is not the himalaya section (which doesn't matter as this is a general wm problem), and since you posted in an older thread (which i assume, you read before) the only thing i can tell you is,
there are no new known ways around that problem but to hard reset or re-flash. i understand that people want to protect their phones, the password just does not work (yet)!
but to get to your real problem, i have never set a password and do not know if you can still sync the device w/o entering the password, but there is a neat little program called -=Windows Mobile SMS Sync 1.3=-. try that to back up your sms, but i don't know, whether you'd be able to restore them to the device. -=spb backup=- or -=DotFred's pim backup=- are programs for the ppc that are also able to back up and also restore sms, but you probably can't run programs, when you can't get past the password screen.
i hope any of this works for you, and i hope you learned your lesson, not to set a password in a cooked rom

Categories

Resources