Related
I've currently followed the instructions for the 1.31 with Arabic and different radio file because that's exactly same original hardware as my UK O2 XDA IIs.
But I've ran the BaUpgradeUt.exe and it confirmed the version changes, but now it doesn't seem to be doing much.
Phone has gone dark and simply says:
USB
v2.06
And the Upgrade program says: Checking the information on the device please wait.
And a warning not to disconnect it.
Erm this is my first flashing so just a little worried I've toasted my new device :-( I can appreciate it takes a while to transfer 30Mb odd over USB, but it hasn't done anything for almost 10 minutes now :-(
Help please? :-(
Thanks!
And I think I've solved my own problem. Everything you need really is in this forum... somewhere
For everyone else who stumbles over this looking for same thing. I simply took battery out for 30 mins (to flatten backup I assume) and then hard reset it (comes up with serial v2.06 at point you unplug from cradle) and then restarted PC and re-ran update program and SEEMS to be going okay at the moment!
Hi,
I have the O2 XDA IIs just like you too but still with the original ROM. You can get a copy of the original ROM from O2 now off their myxda uk site if there are any problems.
Have you got a step by step guide of how you upgraded to 1.31?
Cheers
Hi,
Take a look at the Wiki site. It has all the info on there. I'm now running a 1.31 main ROM (was originally 1.12), a 1.06.02 radio (originally 1.02 I think) and an extended ROM that is hacked up from Orange's (the network I'm actually on!) as well as my own choice of programs etc. Wiki has all the info! It rocks! Thanks to the guys (and gals?) who write it!
http://t-mobile.iris-global.com/files/BA_TMUK_14200_112_11300_Ship.exe
Seems to have appeared as the FINAL offical release from t-mobile for uk users.
I've not tried it yet but the number does seem to suggest it is a slightly lower version than the Dutch one
EDIT MDAIIIUser
Added to wiki
no surprises
build of 2003se identical to Dutch rom previously released:
version 4.21.1088 (build 15159.2.6.4)
Extended rom just hasth changed regional settings (english UK default)
Added to wiki
Still a lot of echo.
Can't pair my Motorola HS820, BA sees the HS820, but error on connecting.
Anyone a fix for the echo and for the BT problem?
Use 1.40 before, was less a problem compaired to 1.42
Please help.
Regards,
Max
Report Back - T-Mobile Rom.. One week or so on..
Hi All,
Wanted to feedback my impressions of the new 1.42 T-Mobile UK Spec Rom..
Well, it's been interesting.. I now have (or have had) most of the faults that everyone else is experiencing.. I never used to get them at all with the i-mate 1.40 Rom or the NL 1.42 T-Mobile Rom.. I have listed the bugs below..
1 - One Hard-reset when inserted into GPS Car holder
2 - Several occasions where I've "lost" the Storage Card (when serching for it on the device AND through Active Sync)
3 - Interesting situation where I've started TomTom5 and I've suddenly had to go through the set-up process again only to be told that there's no maps (Can only attribute this to an occasion where the Storage Card is not seen by the PPC - See above).. Solved by remove Programs, soft-reset then re-install off SD Card.. (quite annoying as I was lost at the time!)
4 - Occasional failure for BT Headset being recognised on an in-coming call (I use the Logi-Tech Pro).. Solved by Soft-reset..
5 - Sometimes, after soft-reset, get a low performance from the Device.. ie, after soft-reset and switching to phone where it takes a few seconds to "build" the phone screen..
Strange but as I mentioned above, I don't recall getting these bugs on the 1.42 NL Rom or the i-mate 1.40 Rom.. I might try a hard re-set on Monday then re-install my tomTom, etc to see if it carries on.. If it does, I MIGHT switch back to the either :shock:
That's it really.. I have had the early T-Mobile 1.06, the i-mate 1.40, T-Mobile NL 1.42 and T-Mobile GB 1.42 and finally the WM5 Roms and from what I've seen, I place them in this order of preference..
1 - i-Mate 1.40
2 - T-Mobile NL 1.42
3 - T-Mobile GB 1.42
4 - WM5
5 - T-Mobile GB 1.06
Hi,
Updated to the dutch ROM, is better then this UK ROM.
Version number is also newer.
Regards,
Max
dazed and confused
sorry if I'm being simple but ....
I though this was the last offical rom
http://www.iris-global.com/t_mobile_download/download_manager_mda_com.html
MA_TMUK_11300_128_11200_SHIP.exe
Rather than
http://t-mobile.iris-global.com/files/BA_TMUK_14200_112_11300_Ship.exe
How did you maanage to find the link?
What is the diference between the builds - How can I find a change log?
What is the BA / MA?
:?:
See here:
http://forum.xda-developers.com/viewtopic.php?t=31360
No difference in UK and NL Rom..?
[email protected] said:
Hi,
Updated to the dutch ROM, is better then this UK ROM.
Version number is also newer.
Regards,
Max
Click to expand...
Click to collapse
Hi Max,
The Rom is exactly the same and the only difference is the changes in the extROM that makes it either UK or NL Spec (ie, MMS settings, etc)
Hi Starfish - Perhaps you need to look at this for the answers to your other questions:
http://wiki.xda-developers.com/index.php?pagename=BlueAngel_For_Beginners
Oh, and BA is "Blue Angel" and MA is the "Magician" HTC Names for the devices..
Sorry I did'nt read close enough Magican vs Blue angel
starfish_001 said:
Sorry I did'nt read close enough Magican vs Blue angel
Click to expand...
Click to collapse
That's ok.. We all have to start somewhere.. 8)
Now, I'm not too sure how far advanced you are in Upgrading, etc but before you do, please remember the following that I put on another post on here..
MrPhilly said:
General Tips to you (and others)..
If you do want to update or upgrade then make sure you read everything through first.. Make sure you're happy in doing it.. Perhaps use the search function to read through others comments.. I would also recommend reading others comments about trying to downgrade from WM5 to WM2003SE to see what others have encountered
You will not believe the amount of people who end up posting questions when they've not followed the instructions from Wiki that I've pasted for you here..
Finally, if you are stuck, use the search command and describe your problem in the Keywords section, select Blue Angel from the Category and read through the posts relating to it before posting questions..
Hope this helps..?
Cheers!
Click to expand...
Click to collapse
How can I upgrade to a stable rom
I have tried the TMobile NL and UK version both give the Country ID eror with the extra numbers 17-17-38-38-38
How can I safely upgrade to the 1.42 version (I have read the Getting Started With The Blue Angel) .
Is that the way to go?
"I get the password error on the xda3nbftool for the nbf segment"
I would like to get rid of all the phonesound failure and systemhangs with TomTom5.10
My Qtek9090
PH20B 0 B
WWE E
DANGA001
1.40.00 0 0
1.40.556
1.13.00 13.00
Upgraded to this from the last O2 update (my BA is an O2 Xda IIs), and while for the most part it works fine, now if the device turns the screen off for power-save while out and about, the GPRS connection drops. I know the hardware is capable of keeping the GPRS connection alive in such a situation because, well, it didn't drop it under the previous two O2 ROMs I ran.
Anyone else had this problem, or know a fix? Hopefully it's something simple that I've overlooked...
I'm getting better Bluetooth support with this (whether through actual improvements in the stack or through sheer dumb luck), so I'd prefer not to downgrade if I can avoid it.
Upgrade for NON OEM/Carrier Blue Angel
I have an unlocked OEM i-mate PDA2K. Because of this I am unable to install the T-Mobile upgrade to 1.42.
Is there a way to get around this?
I tried using the MaUpgradeUt_noID.exe, but I was unsuccessful.
Any ideas on how to upgrade a non-T-mobile branded blue angel?
Thanks
problems upgrading a non-t-mobile branded PD2K
BELOW IS THE SCREENSHOT OF THE ERROR
Did you make sure you had the MAUpdate file in the same directory as the actual upgrade had been uncompressed into? Since it's missing the RUU.DLL file that is part of that package.
Basically, get the files out of the real upgrade, then copy the MAUpdate into that directory, then run it instead.
I can not unzip or unpackaged the shipped OS
When I double click on the file, it runs the file, when you right-click and select extract, it gives you an error.
How do you unpackage the ship package?
Me, I used WinZip, I think it was.
Can not unrar or unzip setup files from exe package
the instructions states:
Unrar or unzip all files in exe or rar into a new folder. I get an error when I do that.
I also noticed that the instructions states:
First Method (Quick/Easy) (TYPE II), but there is another method Second Method (Slower/Harder) (TYPE I)
I am going to give that a try
O2 XDA IIs
Hi from Greece,
A friend bring me to Greece from Singapore one O2 XDA IIs but it has a old versions:
rom 1.31.00 wwe
rom date: 12/13/04
radio v:1.02.00
protocol version: 1337.32
ExtROM version: 1.31.920 wwe
sorry but I'm newbie here, can you tell me what (and where can i find) I must download in order to update to the latest versions.
I allready download the latest version from O2.UK for O2-XDA IIS but I do not want to lock my device to any network and that's the reason who asked you and I do not install this I allready download.
I allready see http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades but I don t now what I must download.
thk u
Hello everyone!
Yesterday I got T-mobile MDA Vario from T-mobile Ben NL. Actually I really need to switch from original pre-installed all Dutch into English. I tried already to download and to install some upgrades but non of them worked, instead responding with the following error: Invalid Vendor ID (Error 294).
Does it mean that my MDA is locked somehow and can not be upgraded without some unlocker or there is some other reason for that error? Actually this is my first MDA, so there might be some unclearness for me..
Thank you very much in advance for your possible thoughts.
Kind regards,
Michael
Ok, I have followed the thread: http://forum.xda-developers.com/viewtopic.php?t=33796&highlight=lockiwiz and the problem is solved. Now I use UK version of ROM.
I've been trying for a couple of hours now, but it doesn't work here. I'm switching from English to Dutch. Tried Lokiwiz, Awizard and TyphoonNBFTool now. First two: no effect. The latter: file read error after I start the update process. Any clues?
[writing from work in a hurry, so excuse me for not having all my details in front of me]
I'm a long-time avid user/flasher of the Wizard who recently bought an old BA on eBay for my wife. First thing I did was download the xplode WM5 ROM and flash the sucker. Very nice and now up-to-date.
Call volumes sucked, so I checked her Radio version, and it was 1.02 or something ridiculously old. I tried to flash the newer 1.15 Radio Rom using the bootloader app that came with it (MAUUpdate something). I got a country code error, so I added the special line to the config file to cheat.
Now it starts the process and never gets past 0% on radio flash. Just hangs. And then some strange 114 error when it finally dies.
I've tried with the newest MaUpgradeUt_noID files I could find. I even tried the 1.13 Radio ROM with no change.
I even re-flashed to WM2003 and tried to flash just the Radio from there. Kept getting "wrong device" message or connection error or something. I tried multiple times in a row (one post suggested the first time will error but second time will work).
I did SIM unlock just in case (Cingular on Cingular so shouldn't have been a problem).
Any suggestions out there? I think I've tried everything!
And yes, I've read all posts and wiki's. (Usually I read only Wizard, but have extended my reading to cover the BA).
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
xummy111 said:
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
Click to expand...
Click to collapse
yes, I did. mentioned that above.
I get either country code error (or after correcting that per the wiki advice, I get long period of hang followed by an odd error 113. I think.
does device origin matter? my BA is from ebay and the getdeviceinfo.cab leaves me a blank result except model number and a few random numbers...
I take it that when everyone else flashed to WM5, they followed the simple Wiki instructions and everything went fine? I think I got some odd-ball sub-model that is resistant to Radio flash.
Downgrade Your BA to the WM2003SE, then unlock it with xda3_all_unlock-v1.6_138.exe tool (You can find it in the BA forum here with description how to use it) then try to flash the Radio ROM You want....And then You might upgrade to WM 5.x again if only You wish.
I've tried one of the other sim unlock apps already (successfully) without solving the problem (was tried on WM5). I'll try the order of downgrade, unlock, then upgrade and see if it works.
Thanks for the suggestion.
Jeremy how did it go? are you able to upgrade to the latest radio rom? I also have the same problem as you do. Do you mind telling me the steps if you somehow able to upgrade to latest rom?
this worked for me. after you flash to a new rom (like xplode's), do not take out the BA yet. flash to the new 1.15 radio rom. then you can do the no/yes/yes routine.
Available at least in www.myqtek.se and www.myqtek.fi.
Changes: Updated client for streaming media. New radio version.
Although I cannot get upgrade to start properly, always gives me error 262 at 0%.
Thanks for the update! I've downloaded and will flash the new software in the morning (I want to charge the battery a bit first).
I hope radio is more stable with this software - I've been to Denmark and the UK this week and in both countries call were broken and the phone lost connection with the mobile network (No service and Searching). Same problem that I've had before, even though I have tried changing the sim card. If it wasn't for these problems it would be a great smartphone, but now I find it to be a very crappy phone. Let's see if that changes now!
what's the AKU of the new ROM?
Finally got the update to work, had to do it according to these instructions: http://forum.xda-developers.com/showpost.php?p=1050547&postcount=6.
OS version is now: 5.1.465 (Build 15673.3.3.1), BUT radio is 1.29.00.10 and not 1.38.00.10 as it says on the ROM package. Can someone confirm this? As I had the 1.32 IU Test version installed previously and although I went first back to 1.30 I didn't check what the Radio version was so I don't know if 1.29 radio is something that was left from the 1.32 version or if 1.34 just has the same radio as 1.32.
1.32 was pretty promising version and I hope this one will be even better. I've had no major issues with these newer versions, although just a few days ago the phone ate the battery from 100% to about 15% in two hours when I was in a movie theater and the phone was not supposed to be doing anything!
I too have problems upgrading - I get error 262 at the beginning of the flashing. When I restart the MTeoR it starts WM as usual, so it seems it hasn't started flashing yet. This happens on two different computers. Any suggestions, please?
Note: I am able to flash 1.30.251.1 with any of the above computers. Only the new 1.34 is a problem. Could the install program be faulty? If so, it is pretty bad considering it is an official release.
New Rom
Hi,
Can you put it on rapidshare of megaupload ???
cor
http://rapidshare.com/files/22706498/852727-mteor_upgrade_2.zip.html
New Rom
Thanks for putting it on rapidshare.
I found the problem about the 262 error.
Just use a older update program with the new
rom file and everything is OK.
What language include new rom?
I didn't know how to do that , but after having checked a number of threads etc this is what I did:
1. Extracted the files in the exe file RUU_BREE100_1.34.251.1_1.38.00.10_HTCEUR_SHIP using WinRAR.
2. Did the same with RUU_BREE100_1.30.251.1_1.16.00.10_HTCEUR_Ship
3. Removed the nbh file from the 1.30 directory and replaced it with the file from the 1.34 directory.
4. Ran ROMUpgradeUt.exe
It all worked, and I have now upgraded the Rom. Thanks!
jpalo: radio is 1.38.00.10, just as the file name says.
My radio didn't update first time either.
I found I had to use the 1.30 installer and it would only update the second attempt when it was already in the bootloader.
I then used the 1.34 updater and it then updated the radio.
Well I just updated mine and Yippeeee!!!!! Finally I have the EDGE "E" at the top. 'Bout freakin' time. My radio does still say 1.29 but I have noticed that before the update my phone was only on 2 bars, now it's steady on 4. Browsing seems to be much quicker now as well. Time to start reloading and testing.
Try updating with the 1.34 .exe and .nbh once you have managed to get to 1.34 the first time (ie just run the updater direct as you should normally)
My OS is 5.1.465 (Build 15673.3.3.1)
Radio Version is 1.38.00.10
So I guess that would make it AKU 3.3.1
No problems with it so far and have unlocked it to import the Vodafone settings as I would before, now to restart my mission to actually be able to load the UK Vodafone wap sites.
Dl also, and will try it out.
Electronic Punk said:
Try updating with the 1.34 .exe and .nbh once you have managed to get to 1.34 the first time (ie just run the updater direct as you should normally)
My OS is 5.1.465 (Build 15673.3.3.1)
Radio Version is 1.38.00.10
So I guess that would make it AKU 3.3.1
No problems with it so far and have unlocked it to import the Vodafone settings as I would before, now to restart my mission to actually be able to load the UK Vodafone wap sites.
Click to expand...
Click to collapse
Do you mean you "application" unlocked it? When I tried the old tired and true way of running SDA Unlock tool it tells me it can't be unlocked. I also can't make any registry edits, it won't save my changes and gives an error. What did you use to unlock it? Thx.
I ran the registry editor (same as before), made three registry changes.
Rebooted, ran the unlocker (which is now allowed)
Rebooted again and ran the unlock tool and said my phone was unlocked.
The steps I followed are here:
http://www.modaco.com/Mteor-application-unlock-solution-t244205.html
staffann said:
...I've been to Denmark and the UK this week and in both countries call were broken and the phone lost connection with the mobile network (No service and Searching). Same problem that I've had before, even though I have tried changing the sim card. ...
Click to expand...
Click to collapse
I had the same problems with my phone really bad. Finally got fed up and sent it for repair.
Got it back about 10 days ago, and haven't had any problem since. I'll wait another week or so before I really give it a clean bill of health.
The fix was quite simple... They replaced the mainboard... So it seems like there really was a hardware problem.
Royan
Royan said:
I had the same problems with my phone really bad. Finally got fed up and sent it for repair.
Got it back about 10 days ago, and haven't had any problem since. I'll wait another week or so before I really give it a clean bill of health.
The fix was quite simple... They replaced the mainboard... So it seems like there really was a hardware problem.
Royan
Click to expand...
Click to collapse
Sent in one last week, same problem, it cuts calls and cant find network and so on.
Royan and BarateaU: please keep me posted!
I'll try to let you know as well if the ROM upgrade solved my problems.
Looks like the 1.34 update has been removed from www.myqtek.fi and www.myqtek.se (although it is still available via some URL tweaking).
Running the ROM update again now succeeded without any 262 errors and radio was also updated to 1.38. Thanks for help.