Related
today i tried to switch my xda2 from t-mobile's 1.72.170GER final rom back to o2's 1.72.184GER final which has been provided recently. i run into that damn country code error 120 because my xda2 has got a t-mobile device id. please find my steps for solving that problem:
1. unpacked the 1.72.184GER package into a folder and replaced the original HimaupgradeUt.exe by the hacked one (which is supposed to ignore country codes).
-> result: same problem - country code error 120 : 1-3-1-1-1
2. then i deleted the HimaGetDeviceData.exe in the folder containing the rom-files. and i deleted any existing DeviceData.txt in the windows folder of my xda2. time to start again the hacked HimaupgradeUt.exe.
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom 1.72.01, radio 1.17.00, extrom 1.72.170 to rom 1.72.01, radio 1.17.00, extrom 1.72.184. i am happy so far but the next screen is again that damn county code error 120 message :-( meanwhile my device is stuck in bootloader 1.06 mode.
3. at this time i deleted the HimaClearJumpCode.exe (which is no longer needed for setting the xda2 in bootloader mode, it is already there) and started again the hacked HimaUpgradeUt.exe (the third time).
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom "blank", radio "blank", extrom "blank" to rom 1.72.01, radio 1.17.00, extrom 1.72.184. next screen tells me that the devices rom is getting erased now and the progress bar shows the current status. everything went through the update process fine.
and my device has been successfully transformed from a t-mobile mda2 which looks like an xda2 to a real o2 xda2 with current xda2-software
summary: i guess you can shorten the whole procedure by setting the xda2 into bootloader mode connecting to your pc by usb unpack only the three rom file images into a folder, copy the hacked HimaUpgradeUt.exe into that folder and start it. but i have no time and motivation for doing that since my device works now.
best regards
peter
where to download hacked HimaUpgradeUt.exe
Dear
where to download hacked HimaUpgradeUt.exe
beast regards
:lol: :lol: :lol:
Thank you very much
Thank you very much its work now
beast regards
o2 ruu
i have tryed upgrading my i-mate to the o2 finaleng ruu with the help of dcs i got it to work with the acked file but now i have megga probs, no camera no extrom and no caller id file so i can't open pictures or video as they are looking for 'albam' to view them, can you suggest a way to get them back???
i have tried the upgrade a fair few times and am getting to the end of a short fuze..... if i run the upgrade direct from o2 i get a model id error, in the device data file i noticed that it has::
usb30 cdl uk5
cdl 1.70.00wwe ph10
or something like that..... it's the uk5 bit that is new..
any ideas :?:
Well, this is pretty newbie advice to most of you, so you may think it doesn't warrant a write up, but I had to do some searching for info on how to upgrade my ROM so I thought it would be good to put it all in one thread.
1) Download the ROM you want from the FTP server....Details here http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
2) Download MaUpgradeUt_noID.exe to your Desktop from here http://forum.xda-developers.com/download.php?id=7644
3) Disconnect your device from the USB cable.
4) Hold the Power button + Light bulb button, and press the reset pin found at the back of the device (fiddly if you have large fingers).
You will notice that the screen of the device is dark but has “USB” and "v 1.0" written on it.
5) Connect back your device via the USB cable.
6) Run the download ROM upgrade application...When it prompts you to begin the upgrade process, just minimise the window or leave it alone (DON'T CLOSE THE PROGRAM).
7) Whilst it is running, use Windows to search for a file named RUU.dll
8 ) Right click file and choose ‘Open Containing Folder’
9) Select all files and copy them
10) Create a temporary storage location....C:\Upgrade....And Paste all copied files in here.
11) Copy the file MaUpgradeUt_noID.exe from the desktop into C:\Upgrade
12) Close the previously started upgrade application running in the background
13) Run MaUpgradeUt_noID.exe from it's C:\Upgrade location
The upgrade process should begin now…If it does not, run the MaUpgradeUt_noID.exe application again
Make sure you DO NOT DISCONNECT the cable.
The upgrade takes around 20 minutes to complete.
14: Disconnect the USB cable when told, then push the reset pin. Ignore the advice to do a hard reset by holding down the soft keys while you do this, just push the reset pin by itself. Your Universal will load the new ROM image and you're all done.
Thanks.
Thanks!
There is only one thing, step 4, it is not USB but Serial.
Mento said:
Thanks!
There is only one thing, step 4, it is not USB but Serial.
Click to expand...
Click to collapse
It will go to USB when upgrading.
It doesn't seem to work with last Qtek 9000 ROM...
Help!
OK, I made my own instructions. Follow this instruction of mine:
The file is extracted in your computer. Once you run the shipped.exe file, you need to go to:
My Computer
Your Drive (mine is Drive C)
Show the contents of this drive
Documents and Settings
Choose your folder name
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
Now go to TEMP folder
Now you will notice a bunch of folders will show up, tons of them to be exact. What you need to do now is click on the shipped.exe file again and "LOOK" for the folder being created because that folder is what you want to copy. If you did not see it created, you have to manually open each folder and look for the files I listed below.
Assuming you found the folder, you will have these following files inside that folder:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
If the file MaUpgradeUt_noID is not there. You need to get hold of a copy of this file as you need this.
There you have it, REMEMBER, you need to have the MaUpgradeUt_noID file plus all the rest of the file if you want to upgrade to the ENTIRE I-Mate ROM, QTEK, O2, or whatever ROM you want.
If you only want to upgrade to the radio version then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf" alone and click on the "MaUpgradeUt_noID" file to initiate the Radio installation. Basically those 3 files control what you want to update on your device.
Hope my instructions were clear enough for you. Hope this helps.
cannot locate files after running exe
Hi All, I have ran the ROM update exe and the message saying extracting file XXX etc appears OK then the program closes. When I search for the files, for instance *.nbf they dont exist anywhere on the computer - does the exe autodelete the temp directory and have I missed a stage ? Any help gratefully accepted
Re: cannot locate files after running exe
SteveInUK said:
Hi All, I have ran the ROM update exe and the message saying extracting file XXX etc appears OK then the program closes. When I search for the files, for instance *.nbf they dont exist anywhere on the computer - does the exe autodelete the temp directory and have I missed a stage ? Any help gratefully accepted
Click to expand...
Click to collapse
Did you follow the instructions above on how to show hidden files and folders? After double clicking the .exe file and running it, leave it open then look for the NEWLY created folder in the TEMP folder as instructed. You need to look for it the hard way by opening each folder one by one and check for the files to see if you got the right one.
someone advised me for some extra step, someone please advise is it coorect steps:
"Then you need to make a small change to one of the text files. Look in the directory for
RUU.conf
Open it in notepad and add this line
[CHECKCEID_TYPE]=1
then save it
That’s about it….."
thx for reply christian,
yes i tried searching every folder the manual way but still no joy, I have just copied the rom exe onto my other computer and it worked OK on there and updated my exec without any further problems
Hi All, Linked to the update of the exec software , i noticed the audio playback on tom tom navigator and media files is very jerky to the point you can hardly make out what is being said. has anyone else had the same problem and have you found a solution to fix the problem ?
many thanks
Steve
Bricked QTek 9000
I got a Qtek on ebay and it was working when I tried to upgrade it failed with a "115" Radio Error.
Tried the method on this thread and it completes the upgrade but when I reset, I does not change from "USB v1.0" can anyone help!!!!
Hi
I'd like to take the risk for updating my Dopod 900 for new versions of ROM & radio, but I've got couple of questions.
1. I've got Dopod 900. I do understand, that it's absolutely the same with Qtek9000, but to be sure: may I use ROM update for Qtek?
2. My ROM (1.13.69) & radio (1.04.02) as of 10/12/05 are ancient What version of ROM & radio consider to be stable as of now? I saw in signatures that people using ROM 1.30.77 and radio 1.09.00. Are they OK?
3. I got on FTP and was a bit confused: as far as I understood the latest ROM is 1.30.100 (UNI_QTEK_130100_190_10900_ESN_Ship.exe), but it's for ESN (Spanish???) localization. So in order to get WWE I should use UNI_ORUK_13090_174_10300_WWE_Ship.exe and that update radio separately from 1.03.00 up to 1.09.00 or just UNI_QTEK_13077_176_10900_WWE_Ship.exe? What would u advice me?
4. What is the benefit for updating from 1.13.69 and 1.04.02? Will it works faster & more stable?
Thx in advance & take care
Hi
I tried this and get a 120 (incorrect country ID) error.
Strange, my V1640 from Vodafone is spanish and i want to upgrade to UNI_QTEK_130100_190_10900_ESN_Ship.exe
so it should be ok.
Am i wrong? Is there a way to get rid of that message?
Hi I have a Xda Exec
ROM: 1.13.82 WWE
Rom date 11/30/05
Radio 1.04.02
Protocol 42.37.P8
Ext Rom 1.13.188WWE
And when i do this:
4) Hold the Power button + Light bulb button, and press the reset pin found at the back of the device (fiddly if you have large fingers).
The devide says me:
Boot options:
Enable KITL
Clean registry hive
Format storage
I soupouse that it isn´t the boot loader for go on with the proces... what happens?
I want to upgrade to UNI_QTEK_13077_176_10900_WWE_Ship.exe for use my heasphones motorola stereo... (AD2P..)
Can any body help me?
Thanks a lot
Please!!!
Edit post number 1 and add as the last step:
14: Disconnect the USB cable when told, then push the reset pin. Ignore the advice to do a hard reset by holding down the soft keys while you do this, just push the reset pin by itself. Your Universal will load the new ROM image and you're all done.
It seems that a lot of people are having trouble after a ROM upgrade by following the instructions on the upgrade program which tell them to hard reset.
Many thanks! PU10 by German T-Mobile upgraded to WWE
I have a T mobile mda pro, any recommendations as to what the best rom is.
Im torn between the new orange rom which is supposed to be good and the jasjar one?
Anyone?
Latest jasjar ROM
Hi,
Can I follow these instructions with my UK jasjar?
Where can I find the latest Rom?
Cheers
Anyone can point me out to the adequate ROM?
thanks
astpaul said:
Hi
I tried this and get a 120 (incorrect country ID) error.
Strange, my V1640 from Vodafone is spanish and i want to upgrade to UNI_QTEK_130100_190_10900_ESN_Ship.exe
so it should be ok.
Am i wrong? Is there a way to get rid of that message?
Click to expand...
Click to collapse
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
stunno said:
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
Click to expand...
Click to collapse
having asked the same question myself here goes.
Download USPL and follow the instructions. they are very clear.
Download
extract
connect phone with minimum 50% battery
soft reset and once started up fully run the app by clicking on Rom Update utility
follow the process through once finished your device will restart.
once restarted you then can flash the rom of your choice
I used Black and Blue again ran the update utility and bingo.
dont forget that all data on your device will be lost so make sure you have back up of contacts etc in outlook on pc.
Finaly make sure you have Activesync 4.5
enjoy
AS STATED ALTHOUGH THIS WORKS YOU ALL DO IT AT YOUR OWN RISK
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
joey jojo said:
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
Click to expand...
Click to collapse
i have o2 uk orbit and all is well
pof said:
I created update package for this ROM in NBH format, so no risk of bricking when flashing it, just unzip & run RomUpgradeUtility.exe
Download here:
ARTE_WWE_WM6.zip
NOTE: Before flashing you need to have Artemis USPL on your device.
Click to expand...
Click to collapse
Taken from Bepe's thread about the modified o2 German update. Basically you need to use the Artemis USPL program and then use the first link to install which I did successfully on a CID locked phone.
Thanks guys, but, unfortunately, the uspl thing does not work on my pc
Along with a few others I get the 'black screen' on my mdac3 then activesync disconnects and the rom loader throws up an error
Luckily my mdac3 survives through a soft reset
I think the idiots guide is not quite there yet
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
crushuk said:
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
Click to expand...
Click to collapse
Confused... is it really necessary to take all these steps? I thought that the only thing required is to run Pof's tool USPL, and after that run Romupdateutility.exe from the package in .nbh format (the link is just a few messages above yours). Please correct me when I'm wrong.
step by step guide
stunno said:
Any volunteers?
Click to expand...
Click to collapse
OK, I volunteered... This is a detailed list of steps how I installed a new ROM on my MDA Compact III (CID locked, at least I think so). It worked without any errors or problems. I used PDAVIET Black&Blue v2.0. It was my first flash on my Artemis, so I more than understand your need for step-by-step guide
1. download the file Artemis_USPL.zip
2. unpack into the folder c:\USPL
3. download the file ARTEMIS_Black_Blue_v2.zip
4. unpack into the folder c:\ROM
5. soft reset your phone and have it charged over 50% (I have it fully charged)
6. wait until the system starts on your Artemis
7. turn on flight mode (probably not necessary, but I wanted to minimize any risks)
8. connect your Artemis to PC with a USB cable
9. wait until ActiveSync icon in your tray (lower right corner of your windows desktop) turns from gray to green. If you connect your Artemis for the first time to PC, you do not need to set up synchronization, just click "cancel" on the first screen of "Synchronization Setup Wizard"
10. while ActiveSync icon is green, run c:\USPL\start_uspl.exe
11. a DOS screen will pop up with the text "Initializing: 0.." in the bottom indicating probably seconds from the start (it stopped around 70 in my case after about 1.5 min)
12. DOS screen disappears and PDA Phone ROM update utility pops up
13. at the same time, your Artemis turns blank (orange/green LED turns off as well)
14. tick the check box next to " I understand..." and then click Next
15. tick the check box next to " I completed..." and then click Next
16. a box saying "Verifying information on your PDA..." pops up
17. on the next screen click Update button
18. next screen says "Upgrade to ... image version 9.99" - click Next
19. Next screen says "You are now ready to update..." - click Next, a window with a blue progress bar appears with a text "Updating ROM image..", it quickly runs to 100%
20. next screen says "Congratulations! ..." - click Finish
21. your phone turns on and boots into your old system, however it should be CID unlocked now
22. your Active Sync should reestablish and icon turns green again
23. do not touch anything (phone or USB cable) and run C:\ROM\ROMUpdateUtility.exe (make sure activesync icon is green)
24. PDA Phone ROM Update utility window appears, tick the check box next to " I understand..." and then click Next
25. tick the check box next to " I completed..." and then click Next
26. a box saying "Verifying information on your PDA..." pops up
27. on next screen click Update button (says "Current information...")
28. next screen says "Upgrade to ... image version BnB2.0" - click Next
29. Next screen says "You are now ready to update..." - click Next
30. a window with a blue progress bar appears with a text "Updating ROM image..", your Artemis will have light gray screen with blue progress bar showing the progress of flashing - do not touch anything and wait (it took 2-3 minutes on my 3 years old PC)
31. next screen says "Congratulations! ..." - click Finish
32. your Artemis turns on and starts booting, you can disconnect it from PC now
33. the boot screen remains the same (T-Mobile in my case), so do not panic!! it is normal
34. wait until calibrate the screen appears, calibrate, choose time zone and you are ready to use your new OS
35. let me know if this manual was clear enough, whether it helped you and please suggest potential changes for improvement
Take care,
Dzim
i've just succesfully flashed my dutch CID-LOCKED MDA Compact 3 with this method, so i'd say it's reasonably fool-proof
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Cheers Dzim!
Your instructions worked perfectly.
One very happy complete idiot here!
Furbious said:
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Click to expand...
Click to collapse
There is a TMobile rom on here somewhere already, I just cant find it at the moment
My Compact 3 it’s death now. After pres voice commander button MDA start only to the boot loader. Can’t run complete system.
Pleas tell me. How can I write the new rom with WM5 or WM6 ?
OOPS! Working well apart from the "cant save word documents" bug!!
Just an update - to use the v1 or v2 black and blue, even though it is unlocked, you still need to use the supercid util.
Otherwise you get the rom update getting to 3% before crashing out to say the rom is corrupted.
I've now converted 2 other tmobile compact mda IIIs successfully, wm6 is much quicker
Yes, with my Compact was exactly as You say. Now is death. What I can do now to repair it.
big thanks to Dzim, used the idiots guide and now on wm6 =D
cheers!
PS: first post
Hi! Nemesis, try to connect your HTC to your pc in bootloader mode.
Lauch start_uspl.exe in USPL folder. Follow instruction on post N°9 by DZIM.
After USPL your HTC should reboot (maybe in bootloader mode only).
Launch the ROMUpdateUtility.exe in Black&Blue ROM v2 and follow instruction.
Thanks gguyaz
Pleas tell me.
Could I doing this upgrade with Windows Vista on my PC?
I've read good reviews on chrismrulz's bootlaoder programe and I'm trying to use it to update my iPAQ 4700 from 2003 to WM6. However I am obviously doing something wrong as I just cannot get it to work!
Please can anyone offer any advice?
I hope I am following the exact instructions as mentioned here at http://forum.xda-developers.com/showthread.php?t=325727
and here is what is happening:
Step 1.
Make new folder in root directory.
No Problem c:\Bootloader set up.
Step 2.
Download WM6 ROM and bootloader into file.
Done as directed from links in instructions directly into new folder.
Checked and c:\Bootloader now has 2 files in it Bootloader.exe and WM6_4700_0_7_0_RELEASE4.rar
Step 3.
Put hx4700 in bootloader mode and place in sync cradle.
I assume I have done this correctly. Screen goes blank and you can just make out the HP logo it says USB when in cradle and shows version 1.01
Step 4.
Open bootloader and select image.
Ok I go to folder and double click on Bootloader.exe
I get a security warning about the software and ignor by pressing run.
2 things now happen simutaniously. Bootloader.exe expands and creates c:\Bootloader\Bootloader and fills it with more files and directories and....
I get a box asking me to select a file to flash ROM to my device. I change the directory back to C:\Bootloader and select WM6_4700_0_7_0_RELEASE4.rar and press open.
I get a message telling me to please wait the file is being extracted and inviting me to press ok. Before I can press ok the box is replaced with a winRAR Diagonistic Message saying c:\Bootloader\WM6_4700_0_7_0_RELEASE4.rar no files to extract.
I close this dialog box and get another message telling me to wait whilst it edits files. Then this in turn is replaced by a message saying Error reading file c:\Bootloader\Bootloader\temp_nbf\ I click on OK to acknowledge.
And that’s it nothing else happens.
I've obviously read the instructions wrong or something can anyone help point me in the right direction? Or offer any alternatives?
I'm using Active Sync 3.7.1
Thanks
Phil
Open the rar file (with WinRar), and read the instructions that are in the Readme.txt file... And update your Activesync to version 4.5, which is needed for WM6.
Excellent,
Thank you Ridolfo, so much easier than what I was trying to do. I now have WM6 working and am very pleased with it.
One problem i now have is Activesync 4.5 will not work with my Outlook 2002 I dont suppose anyone knows a workaround or do I have to buy a copy of Outlook 2007?
Phil3099 said:
Excellent,
Thank you Ridolfo, so much easier than what I was trying to do. I now have WM6 working and am very pleased with it.
One problem i now have is Activesync 4.5 will not work with my Outlook 2002 I dont suppose anyone knows a workaround or do I have to buy a copy of Outlook 2007?
Click to expand...
Click to collapse
Very strange indeed, my AS works fine with OL2002... Did you use the MS Office Update to get the latest servicepacks for OL ?
Dirk
Outlook 2002 now ok. I was havinag a bad day yesterday. Now if I can just find a way of viewing java enabled web pages I will be happy
Phil3099 said:
Outlook 2002 now ok. I was havinag a bad day yesterday. Now if I can just find a way of viewing java enabled web pages I will be happy
Click to expand...
Click to collapse
Try these .....
First install JBed, then Opera
Cheers
Dirk
Hi Dirlan,
Thank you for the files. I was already experimenting with Opera so I deleted it from my iPAQ loaded Cloudyfa_EsmertecJbed.cab and then reinstalled Opera.
Unfortunately I get an error message from Jbed saying "the file jbed cannot be opened. Either it is not signed or one of its components cannot be found.
Any ideas?
Phil
After extracting using WinRAR
Trying to upgrade from 2003 to WM6 ...
After extracting WM6_4700_0_7_0_RELEASE4.rar using WinRAR I am trying to follow the instructions in the readme.txt (as Bootloader didn't work for me as in the first post in this thread):
From readme.txt
To begin with if you want to flash your device using cradle,you have to:
1.In processes (CTRL+ALT+DEL) you must kill Wcesscom.exe
2.Then Enter in Bootloader (Contacts+iTask+Reset)
3.Put your device on usb cradle.
4.Run mtty11a.exe
5.In "Port" choose \\.\WCEUSBSH001 and click OK
6.Write command: lnb OS_WM6.nb0
7.Wait
8.Enjoy yourself
As I'm not all that familiar with this can someone explain in step-by-step what's involved with the mtty11a.exe application, and Step 6?
Currently my hx4700 is what I think in bootloader mode (Screen is dim an I can barely make out "USB" the hp logo and the current version "v1.01"). I previously tried the original WM5 upgrade and it just dies on me at 0.1%.
Hi tk2000
As I posted the original post I know exactly what you are going through. However once I went through the instructions you are currently trying to use every thing went smoothly. You have extracted the .rar file and are unsure of the mtty11a.exe file.
Assuming you have you have killed Wcesscom.exe on your pc as in step 1,
and the device in in its cradle in bootloader mode (as you described very faint HP logo, USB and version 1.01 displayed).
Then double click on the mtty11a.exe as in step 4. This then brings up an application and you will see a dropdown menu next to port, simply select the option \\.\WCEUSBSH001 and click ok.
6.Write command: lnb OS_WM6.nb0 now this stage I was a little unsure of myself I simply typed "lnb OS_WM6.nb0" in from the keyboard and pressed enter and it started to load. This takes a few minutes but afterwards you should have WM6 on your device.
I had to do a couple of hardware restarts and it took a few minutes in its cradle but it all works fine for me.
Phil3099 said:
Hi Dirlan,
Thank you for the files. I was already experimenting with Opera so I deleted it from my iPAQ loaded Cloudyfa_EsmertecJbed.cab and then reinstalled Opera.
Unfortunately I get an error message from Jbed saying "the file jbed cannot be opened. Either it is not signed or one of its components cannot be found.
Any ideas?
Phil
Click to expand...
Click to collapse
Hi Phil,
There should be an 'opera-unsigned*.cab' somewhere here on the forum. I didn't try it because Opera works fine for me.
Sorry
Dirk
Phil3099, I a followed the instructions exactly but I don't see a status bar on the pda. mtty showes the progress with lines of + but the 4700 stays on the hp logo screen with USB on top.
Hello,
if got the T-Mobile MDA III with WM6.0.
Now i want to update my ROM with WM 6.5, bit i only become the following error:
Your image has corrupted. please check your update utility.
Can anyone help me???
i hope you can help me.
thx
markus
try to re-download the rom and make sure you run a USPL first if it's your first upgrade. Search the forum if you need help
it dosn´t works
i´ve tried 5 different roms but no one works.
its the second upgrade on the fon.
Try a new update of SPL, files here= http://forum.xda-developers.com/showthread.php?t=311403
Download "ArtemisUSPL.zip"
1. Unzip
2. Connect your phone to computer, make sure activesync is enabled (green icon)
3. Run start_uspl.exe on your computer and wait until process finishes
4. The phone reboot.
When boot is done, you are CID unlock forever normally so you can flash all rom you want.
Then, You can flash now your rom, just run RUU from your rom folder and normally it's good.
If it always don't work, give us all the number show in your 1st screen when the phone boot (IPL, SPL ...)
yes, tell us what numbers you get on your screen
also what error are you getting
and what OS are you on....vista? XP ? Did you get an activesync connection before you tried flashing?
also try putting phone into bootloader mode first and then flashing, sometimes helps. (hold down RECORD/NOTES button when you reset)
once you've got an error number ( eg error 260 ) you can try searching the forum for that error number and see how everyone else has coped with it.