Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
paulcharles1 said:
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
Click to expand...
Click to collapse
well, I'll just try to give you some suggestions as I don't know much about MDA Compact III ,it does not fall in the category of wizard,it's a Magician device and I'm a wizard k-jam user. anyhow as a general of upgrading is to have your battery fully charged or atleast must have more than 70% charge.cuz during flashing in RUU upgrade mode,it does not charge,so if while during flash something goes wrong or it takes more time to flash,it shud have enough power to go through the whole process.if it does not have enough power to complete the process,it fails to flash properely and thus have a bad flash creating problems.so same has happened with u, you have a bad flash
well in wizards we have certain methods to revive the device or recharge the battery,i have no idea about your device,but can only suggest get the battery charge,secondly your usb connectivity problem is also due to the bad flash,cuz as there is no OS info on the device,it wont be able to establish the connection,which windows are you using,try to upgrade with winxp sp2 and active synchronize ver 4.5
as i have no idea about Magician upgrading method so wont comment further,but advise you to look in the below thread,it might be helpful,cuz its about Magician MDA Compact III
As your posting in the wring forum you might not get much help here,ok
http://forum.xda-developers.com/forumdisplay.php?f=276
good luck
thanks
thanks for the reply. Got it working - used 2.0 to unlock it, and 2.1 for the actual rom upgrade...
Related
I've searched through the forums and can't find reference to anyone having problems upgrading due to their PC.
I've upgraded ROMs many times before but the most recent venture on my MDA Pro to WM6 (hemi 1.1) has been unsuccessful.
Basically starting 'ROMUpgradeUt' brings up, 'Device Software Update Utility' then clicking next starts the sofware search for the device but then it shuts down with no error message!
I've noticed other ROMs to give me the same problem now (eg Helmi AKU 3.5).
Tried:removing SD card, removing SIM, 'device upgrade mode'(light, power+reset), unchecking usb connection, hard reset, computer restart (XP),
ActiveSync 4.5 5059 working fine, country id error upgrade, tried another MDA Pro same problem.
I've run out of ideas guys.
PS last time i tried to upgrade to WM6 i got stuck on boot screen and had to use the mtty tool to reboot.
I think you should try an other mashine.
SOLVED !
Universal didn't like the different USB port at the back of the computer i was using. I had connected an external hard drive to 'its' port.
This things more touchy than my wife!
AbuGWM5 said:
This things more touchy than my wife!
Click to expand...
Click to collapse
ROFL It's sometimes scary how much I compare my PC to my ex lol...
HELP!! Im trying to replace my current german language orbit rom with B&B4...activesync was working and my screen went blank like it was supposed to...but I instantly lost activesync when it did...I can not go any farther. What do I do??
I have replied in the other forum, please don't post in more than one forum.
sorry.
I figured it out. Just procede through the USPL setup even though it says make sure activesync is connected. (activesync is dissconnected when screen goes blank but will still update correctly) thanks again guys
of course when your device resets itself activesync connection is lost. even usb connection is lost for a short time (you can hear the ding-dong and dong-ding sound). activesync needs a usb connection and software running both on pc and pocket pc. so when your device starts into bootloader you cant have an activesync connection. but to flash some stuff all you need is a working usb connection.
I can understand that but
I see what your saying...but when your flashing anything be it a PSP, P3300 or anything else where there is a possibility of bricking it, your going to try not to deviate from the instructions...so when the screen goes black and you have to check the box which says you've complied with the above steps and a connected activesync connection is one them...time to hit the forums and get a few things cleared up.
I've searched but can't find the answer to this one - sorry if I've missed it somewhere. I have an unmolested T-Mobile UK MDA Vario 2 and I'm trying to install the official TM UK WM6 upgrade ROM.
On my desktop PC (which is properly paired to the phone through ActiveSync to sync with Outlook etc) running the exe results in a grey box with red text saying "Checking files on your PC" forever unless I unplug the phone. Then it will eventually launch the wizard. If I plug the phone in again and wait until it's synced and "Connected", the wizard will go all the way through to checking the existing version and starting the upgrade. However, when the upgrade starts the progress bar stays at 0% and the phone turns off!! Eventually it times out with a 260 error, and no changes have been made to the phone. The PC is running XP, but the only fixes I've seen for the 260 error are if you're running Vista?
I've also tried on my XP laptop - this isn't paired, so the connection through Activesync is just as Guest. The update still does the strange thing with the "Checking files on your PC" box if the phone's plugged in, but unlike the desktop PC the RUU won't talk to the phone at all - connection error before it can even verify the existing ROM version.
Can anyone help? I've been waiting for months to get WM6!
Cheers,
Tim
Phone just turns off?
OK, so now I've done a hard reset on the phone, paired it up to my XP laptop and told it not to sync anything. Now I get to the same stage as I do on the desktop - i.e. the phone switches itself off when the upgrade begins (at 0%), then the RUU times out with an error 260!
One odd thing I noticed is that if I plug the phone in with "Advanced network functionality" enabled (which it is by default) the PC tries to connect it as a new 10mb network card!? However, the RUU does the same thing whether this is enabled or not.
Getting desparate for help now - I've tried 2 different machines and even cleared the phone completely, what more can I do?
Cheers,
Tim
Try flashing from an sdcard. There are quite a post on it here, if you do a quick search you should be able to find the information and hopefully get your device upgraded.
It might be worth installig spl V7 from here before hand just in case anything goes wrong.
http://forum.xda-developers.com/showthread.php?t=296722
Working!
Thanks for the reply. Finally got it flashed using the instructions from here:
http://forums.cingular.com/cng/boar...thread.id=42389&view=by_date_ascending&page=1
Basically, you have to:
- Connect using Activesync and let it finish syncing.
- Start RUU.
- Activesync will close - ignore it and carry on.
- Eventually the phone will go into debug mode.
- Continue through the wizard - it won't be able to identify the existing rom version but this seems to be normal.
- Let it finish!
I was fiddling when Activesync closed - strangely, by disconnecting, restarting AS and reconnecting the wizard carried on and even identified the existing rom properly! It seems that it needs AS to connect to the phone initially, then it closes AS but keeps the USB connection open for the update.
Hope that helps anyone else with the same problem.
Cheers,
Tim
Help please
i have a t-mobile uk mda compact 3 phone nd im on t-mobile uk tariff, i have downloaded the official t-mobile uk windows mobile 6 rom.
when i atcive sync and go to flash the new rom i get the utility program up, the phone turns different colours ie red, green blue with black strips, the bar then shows on the pda on the pc screen it gets to 3% and bang invaild error 260 and the phone then resets
ive tried it on xp as im on vista same thinf happens, ive tried uspl, no joy can someone tell me how to get thos rom flashed to the phone in vista a easy step by step procedure to follow cause so far ive lost 8 hours since sunday to tonight
please help.............
SD card removed?
remove your SD card
USB board
you may have been not so carefully with the USB connection contact of the phone, or you ahve charged the phone at car while you were starting the car engine..some guys repaired this in service, or it passes by itself.
at me i tried different days and different softs ... and i did i, i got the same error.
fun0815 said:
remove your SD card
Click to expand...
Click to collapse
Hi i have removed SD Card, tried it without, with also with and without sim card still no joy i need step by step help on this
pskint said:
you may have been not so carefully with the USB connection contact of the phone, or you ahve charged the phone at car while you were starting the car engine..some guys repaired this in service, or it passes by itself.
at me i tried different days and different softs ... and i did i, i got the same error.
Click to expand...
Click to collapse
The phone usb connector is fine, i dont charged the phone in a car as i dont own a car
so what is ther soultion there is nothing wrong with the phone or the connector as it connects up via usb and uses active sync also installing other software and transferring pictures, music to and from it also work fine!
i can see both the phones memory and sc card in my computer.
its just this bloody rom file and error 206 that i am still needing someones expert advise and step by step help on
Please Please Please Please Heeellpp Aargggh Part 2
CAN someone please help me out and to whoever has managed to upgrade using vista!!!!!!
please help
After searching this forum, this came up:
http://forum.xda-developers.com/showthread.php?t=312052
Title: USPL - 100% Working in vista
step 7 says:
7. After switching the drivers plug your artemis again and install USPL, there should be no more problems with connection lost (errors 260, 270)
Suggest you read that thread, hopefully it solves your problem.
Hi, I have a huge problem.
I tried to update the software for my O2 exec (first time)
The first two steps succeed, but the CO stopped than 69%, I turned off the o2, I tried another version, but the process stop than 10% of stops, it does not do anything ... What can I do? Somebody help, please!!!!
Thank you in advance
Welcome to forums
Have a deep read here on upgrading ROM section
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Good luck,
MTTY can not open the USB port...
Please help me
Are you using Vista or XP on your PC? If XP, look for switching USB off in Activesync; if Vista, search on Win Mobile Device centre connections and untick "Allow USB connections". (or maybe it's the other way round!!!) Switch everything back on after you finish flashing.
I have XP. I bring my pda for my friend. The connection via USB was successfull, we made the proccess in MTTY, but the program told that can not read the fat (or something like this...)
Is there still hope?
Thanks for help, the problem is resolved. My Uni is working!
Have almost same problem.. but now,...
all upgrade always end in 30%
and now I can't see USB on MTTY (try on win7 and XP)
thanks in advance
I use mtty1.42.exe
type :
task 28 55aa, set 14 10, set 14 9, set 14 20
update can be run.. but always stop in 12% now
try with other rom.. still stuck and give me error 112
I've charge the batt still error
Hyem
Same problems .....Same solutions.
Read Wiki
Read stickies...For those stuck in bootloader..mamaich method
Thread started by hdubli...
Read this thread...it has almost eeeeevery possible scenario we encounter and it's really a good ROM....it's only 12 pages
http://forum.xda-developers.com/showthread.php?t=468776
Remove all cards and try again in bootloader with AS USB unticked.