Database Develop

Wrong device upgrade, none of Wm5 is working

Hello! I talked to xplode about this and he had no clue what could it be...
soul_train said:
...When I run Device Software Update Utility I go to next. It finishes with updating info I go to next. And then it says "This ROM update does not design for your device, please get a proper ROM upgrade and thry again...
Click to expand...
Click to collapse
-------------​
xplode said:
Strange, works fine here, try to repeat the procedure afterall you upgrade with noid, it is not likely to get error like this
Click to expand...
Click to collapse
Don't know where is the problem. I have Helmis 1.4 3.5AKU... I have thryed both new WM-s and On both I get the same problem. So if anyone knows help would be appreciated. Thanks!
Soul Train

I got the same error message. I tried to change operater, but that didn't do the trick, so I'm still on the case
Edit: I'm normaly using Windows Vista, but I still have my XP installation, so I tried to boot in XP an run the upgrade from there. This worked fine, so mayby it's a problem with Vista althroug it should work. So my best advice is to try reboot you system, i know it's not alot of people who runs dual boot systems as standart

hagsted said:
I got the same error message. I tried to change operater, but that didn't do the trick, so I'm still on the case
Click to expand...
Click to collapse
What WM do you have? Shoud I try to Revert back to Wm2003 and try like that?

I upgraded from Helmi's Aku 3.2 to Xplore's 3.5 R4. If you have the posibility, try to connect your BA to anothor PC and run the update from there, I think it's a problem caused by Windows on the specific pc.

Very new person, why am i having so much trouble?

When I run the wizard update for rom or radio or anything it says one of two things on my pc, 1. that there is a connection error and or 2. That the program needs to close because it says so. Im sure there is a simple fix to this issue but i just dont know it.
Thanks

I think I know why
After reading through the posts I discovered why I am having so much trouble. Reason being last week I upgraded to Vista, which would explain alot.
Anyone know a way arround this problem?

irishmatt12 said:
Anyone know a way arround this problem?
Click to expand...
Click to collapse
Downgrade to XP...
There are lots of issues with the rom updater and Vista. Unfortunately until a new version of the rom update utility comes out (or some other new method) its going to be an issue.

Not only RUU, WMDC itself sometimes get problems in Vista.
When I connect the Wizard to PC, sometimes WMDC does not show up, and the PPC is not present in My Computer, and you will see a yello exclamation in device manager!
The only thing I can do is to remove the device complete from device manager and let it detects again, then I can use it again for several times.

Unable to flash under vista x64

Hi, i've read the "How to" from this URL http://trinityguides.info/index.php?option=com_content&task=view&id=20&Itemid=66 but with no success.
Device Manager shows an error code 39.
I just don't understand, i followed everything without errors from the start.
what can i do now ? i want to reflash my radio rom from 1.50.08.11 to 1.46.30.11. My battery was draining slower with that one.
Thanks !

first of all, it helps if you post this under the thread for trinityguides...
you had your device in bootloader and connected before step 2?
are you vista 32 or 64?
it's quite strange cause most people had success with these steps. How have you flashed your ROM in the past?

same for me. the reason is that vista isnt able to install the drivers when the bootloader start.

vista 64bit only works with signed by ms driver be that videocard drivers or pda drivers
if you ask me 64bit is not yet for primetime
drivers are few and limited
support for many external things are non
funny to see how pc entuthieasts pay that much for
vista ultimate when the only thing they get is the 64bit option
and backup and some crypting options which if they ever use
they'll cry salty tears when they have to reinstall and cant
get access to their data anymore
ultimate dont mean it's faster or better
just that one gets the full ms bloatware packet

yeah... the guide shows how to load the unsigned drivers though...
are the two of you running 64 or 32bit vista?

his title "Unable to flash under vista x64"
the x64 would sugest that he's using the 64bit version

mmm... you are observant haha... can't believe i missed it

Same problem here, did what was written in the trinityguide (twice now), but to no avail. Code260 (no connection)
Vista64
-EDIT-
Fortunately my laptop runs on vista32bit, update works like a charm on that one...

hmmm... this is getting strange...
so you followed the 64bit instructions for unsigned driver that are in the popup window? (on trinityguides)

racerx_ said:
hmmm... this is getting strange...
so you followed the 64bit instructions for unsigned driver that are in the popup window? (on trinityguides)
Click to expand...
Click to collapse
Yep, every step, including the unsigned driver stuff (have used that for other programs too, it worked before). Did it twice, no error messages apart from the error260 while trying to update the device.
There must be people who do manage to get it to work, but not me (on the 64bit vista)

yeah, i'm really sorry to hear that. Most people have been successful. Every once in a while, someone reports that they have had trouble with it, but i don't have vista x64 to troubleshoot.
i remember reading in another forum about someone with the same error saying that some kind of optimization option he had selected for vista was the culprit. I think he ended up reinstalling vista with default options and was ok..
(i know that's not really the answer you're looking for, but just thought i'd throw it in there )

hey i was just thinking...
do you want to see if any of these other methods of disabling driver signing work for you, listed in this post

it works under vista x64
If you enable automatic update in vista x64, and you plug in your trinity, after a few minutes a update will appear from microsoft asking that there is a update for your trinity, install it and my phone works and was able to flash new roms on it with this update....i have windows vista ultimate x64 edition...

great tip... the_stranger or simkard, can you try this and verify if it works? i'm sure a lot of vista x64 users would be thankful to know

forgot somthing
if you have updated the drivers from microsoft, put your trinity in bootloader and then in "device management" select your trinity and select update drivers...if not your not able to flash.....

racerx_ said:
great tip... the_stranger or simkard, can you try this and verify if it works? i'm sure a lot of vista x64 users would be thankful to know
Click to expand...
Click to collapse
I've allready flashed under vista32bit and more importantly, installed all programs and contacts. However, when I update the ROM again, I will try this method and report back...

The_Stranger said:
Yep, every step, including the unsigned driver stuff (have used that for other programs too, it worked before). Did it twice, no error messages apart from the error260 while trying to update the device.
There must be people who do manage to get it to work, but not me (on the 64bit vista)
Click to expand...
Click to collapse
ive got vista 32 and i doesnt work 4 me. ive only gotten 1 rom 2 load 4 me. i need a new radio rom and it wont load.ive got the no gsm. wanna fix it bad.

Big Problem?

I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.

Drake008 said:
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Click to expand...
Click to collapse
I'm using a Vista PC.
After the Radio update to 1.15 the error described above is not to go away yet.
What to do, I'm nearly in tears.

Finally I got it back but with an old Romupdate from T-Online. Is there someone who got the QTC 9090 update (latest one)

That was fast..
im glad you solved your problem.
i think someone here has it.
just post what you need and make it as a title for others to read in the digest.

Im not a expert but is vista the problem??

Most likely.

Failed MDA II flash with vista notebook
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated

mda3newbie said:
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
Click to expand...
Click to collapse
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.

thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie

mda3newbie said:
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
Click to expand...
Click to collapse
In vista i dont know...sorry for my late reply too.... in XP u must kill ActiveSync process called wincecom.exe. in vista, maybe u have to kill the Windows Mobile Device Center....i dont know...
Dont forget, put the Qtek 9090 in Boot Loader Mode (Pressing Power Button + Record Button + Reset), maybe will appear USB and u can format the device.
If this does not work, try on Windows XP....Find a friend with Windows XP and ask him to use his PC only to do that.
Maybe somebody in forum have the Windows Vista and can help u....
Sorry my terrible english....

Sjogos said:
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
Click to expand...
Click to collapse
hi guys I tried the step by step process and when im enterin( Task 28 ) then pressed Enter -
Invalid command : Task28
For a help screen, use command ? or h
does any one know where the problem is??

Try this
Downlaod the XDA IIs .exe file and run it - no need to put into USB mode
http://www.o2online.ie/wps/wcm/conn...es+&+accessories/Xda+Range/Software+upgrades/
this should reset to factory default (o2)
it runs on vista too
I am not 100% sure it will work but worth a try

diesel_dog said:
Im not a expert but is vista the problem??
Click to expand...
Click to collapse
Yes, i know my reply is late but the problem ist 100% Vista! i Tryed 2 ours with vista...then i decided to format my pc and to install XP. At the first try it worked!

WOW do I need help !!!!!!!!!!!!!!!

I am running windows mobile device center on a Vista 64 bit laptop.
I have a t-mobile wing that I got second hand. The wing has OpenTouch V7.6 BP WWE.
Here is the problem,
I am trieing to flash the rom to the latest T-Mobile update. When the flash starts the activesync connection drops and it never gets to even 2% done.
I have also tried to flash to different Ver. of OpenTouch and same thing.
Is this a problem with the phone or yet another Vista Issue...........
ANYONE !!!!!!!!!!!

omg! we have the same problem dude i wanted to flash the latest t-mo wing rom but then activesny drops and never installation progress never reach 2%.... will sum1 pliz help? i think this is not a small issue here pliz some1 help

I flash from vista 64 all the time run flash as Administrator

i can flash HERALD.ASerg.Clean2.WM61E.WWE and also HERALD.ASerg.9.WM61E.WWE.6pp(which i am currently using) but i cant flash the t-mos really need help pliz

Solution for flashing from Vista 64bit and postin only once
I do have the solution for your issues (specially looking the amount of posts you have done since your incorporation to XDA-Dev's):
1) Go to the top of the page, near to your username
2) Look the third link in the brown menu bar, from the right (LogOut, QuickLinks, ...)
3) That's right: this one which says "Search". Click on it.
4) Write "Flashing from Vista" in the combo which appeared
5) Read the issues with Vista and specially with Vista 64 bit or even XP 64 bit
6) You'll have the solution, and you'll have found it by yourself. That's to be proud !
6b) In some cases, you'll find it's too hard to flash from Vista and you need XP or the use of SD card ;-p

thanks buddy but actually i am using xp32. so now?

is your phone Hard spl?

wingmanbill said:
I am running windows mobile device center on a Vista 64 bit laptop.
I have a t-mobile wing that I got second hand. The wing has OpenTouch V7.6 BP WWE.
Here is the problem,
I am trieing to flash the rom to the latest T-Mobile update. When the flash starts the activesync connection drops and it never gets to even 2% done.
I have also tried to flash to different Ver. of OpenTouch and same thing.
Is this a problem with the phone or yet another Vista Issue...........
ANYONE !!!!!!!!!!!
Click to expand...
Click to collapse
That's not Win XP 32bit...
On the other side, if you use Win XP 32 bit, did you hard-SPL ? Can you put all the data about your device ? (SPL, Radio, etc.) so that we can know what is happening ?

afn691 said:
That's not Win XP 32bit...
On the other side, if you use Win XP 32 bit, did you hard-SPL ? Can you put all the data about your device ? (SPL, Radio, etc.) so that we can know what is happening ?
Click to expand...
Click to collapse
I too had trouble flashing the default ROM on my Wing. The secret is actually to open up the official RUU application, then search your Temp folder for two NBH's, the RUU_signed.nbh, and the SPL.nbh. You need to then copy them into the RUU folder of Flash Center, run that as administrator, and make sure to flash without SD card. That's the way that I used to restore mine to stock from Hard-SPL.