Database Develop

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!

Upgrading help needed.

Hi Gurus,
Tried upgrading using different methods to O2 XDA IIs Asia Eng rom, however all methods seem to fail. Have already read the readme file.
a) Using Activesync and MaUpgradeUt__NoId.exe with the new rom.
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Activesync 4.5 somehow connects at first, detects the rom versions, and closes without warning, leaving the xda2s disconnected giving connection errors.
b) Using manual method,
Using editfix.exe & getdevicedata.exe
Somehow gets warning errors about invalid passwords and wrong header file.
Is it a type 2 rom ?
c) Done hardreset and Going direct into bootloader (V.2.08) and using usb cable without activesync. The word serial does not change to usb, hence there is no connection through usb to the xda in bootloader mode.
Any ideas ? SD Card interface is not working. My guess is that the drivers for usb and sdio is not working. Any input ? I know that the usb cable and interface is working as i can browse the windows folder using activesync.

Updates
Managed to solve the issue with the bootloader mode detecting usb.
I'm trying to download from WM2005 to WM2003 (O2 Official WWE 1.42 release - Asian version.)
Followed the steps exactly in this link :
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Copied the official nk.nbf rom to the downgrade folder as instructed. When i ran MaUpgradeut_noid.exe, the screen stuck at the checking of info of device. does not seem to be able to flash in bootloader.
I'm using v2.08 of the bootloader (and usb is being displayed.)
Am i doing anything wrong ? Is there an alternate method ? This doesn't seem to work for me.

please help
i've got a ppc660kit and i did the processing and when it was done and i reset it show some colored screen and at the bottom it says no gsm and d 5. somthing.
please help
thanks

just a guess
mtnbikefreak said:
Managed to solve the issue with the bootloader mode detecting usb.
I'm trying to download from WM2005 to WM2003 (O2 Official WWE 1.42 release - Asian version.)
Followed the steps exactly in this link :
http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5
Copied the official nk.nbf rom to the downgrade folder as instructed. When i ran MaUpgradeut_noid.exe, the screen stuck at the checking of info of device. does not seem to be able to flash in bootloader.
I'm using v2.08 of the bootloader (and usb is being displayed.)
Am i doing anything wrong ? Is there an alternate method ? This doesn't seem to work for me.
Click to expand...
Click to collapse
just a guess, are you trying to flash your device from a widows vista pc, because connection errors especially happen there, because windows downloads new drivers while flashing, disconnecting your device, normally the manuals here are detailed step by step and seem to work for every compatible device, so there is probably the vista thing, a broken cradle or cable which is rather unlikely, or a general software issue with your pc
i forgot to ask, why are you using a Maupgrade, isn't he general upgrade file for blueangel compatible devices the Baupgrade?

nevermind
no i got it. i uploaded the 2.0.3 on my phone it fix the phone. but still shows the 4 color screen, that doesn't matter it still works
thanks anyways guys

D810 w/WM6 upgrading fail, error 260

I've spent whole day reading through the froum and the trinityguides.info site but can't find any proposed solution to work for my situation.
Device info:
ROM version: 3.00.707.17 (WM6)
ROM Date: 6/29/07
Radio version: 1.46.00.11
I've tried using all 3 versions of hard-spl but they all end up with the same result. With active sync linked and ready, ran the "romupdateutility.exe" at the end the PDA prompts if I want to run the "enterbootloader.exe", the moment I press yes the active sync connection would drop and eventually the program timed out with error "260" while PDA stuck in the tri color screen displaying the following:
TRIN100
SPL-1.07.ds
I've found some similar problems in the forum but those users are using vista however I am running XP sp3 in this case. I've tried all other solutions in the FAQ areas but none of them works.
My unit came with the WM6 already but I just want to upgrade the radio and get some cooked ROM to get faster performance. What am I missing here?
Any help is appreciated.

Once it drops to the tri-colour screen and is in bootloader, run the RUU again. Should be all that you need.

I've tried running it over and over but on the bottom it just kept on saying "serial" when it suppose to say USB.
Anyways, problem solved and it turned out to be the cable. For some reason the cable is good for anything, except keeping the phone connected/recognized while in bootloader mode.
I think this should be listed as one of the FAQ in the trinityguide. This might be a rare problem but it surely took me a lot time to figure out.

on Vista
Hi,
I have similar problem but I'm using Vista (Business). Is there any workaround ?
Regards,
Daneal

Hi
I have the same problem
spl 1.20 Olipro display serial instead of usb
I tryed several usb cables and still the same
when trying to update the rom it refuse to connect the ppc and end displayng the 260 error no connection
My system is vista and the first time I upgrade everything was fine, I followed all tutorials and no problem at all.
Do you think that could be this new 6.1 Mobile device center I recent install the cause?
best regards
Inabox

The problem isn't the WMC as such more the fact its Vista. Find an XP PC and do it from there.

Hi there, I had the same problem just now and cured it(in Vista). Just upgrade the htc driver in device manager again with "wceusbsh.inf" previous file, then should be ok. It seem to be Vista replaced the driver during it switched to Tri color menu.....

please help downgrade wizard g3 wm6.1 tnt romto wm5

i have searched for a long time and cant find any answers i have a tmobile mda ive tried running the tmobile rom and it didnt work gave me an error any advice please help me i wan wm5 again

Download Official T_mobile wm5 Rom from this link,bet the phone in Bootloaders (RGB screen) and flash to recover back to its default status,then read carefully this guide fron the below mentioned link and do the unlocking and upgrading.
T_Mobile Rom:-
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
Unlocking Guide :-
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies

thats the prob when i do iit it takes me to the rgb screen and the comp says error any info for that

Exactly what error it displays,it must with an error No. and some explanation about it,can you recall it correctly.Does it display Communication error ?

pmed error 260 communication

Ok,I hope you are doing all this on a WinXP machine,if its a vista,it won't work,WinXP is recommended.Now,before start to flash,close/disable any Anti virus and firewall running on the pc,and also try to close as many applications running on the desktop or background through Task manager,don't surf the net during flash or do any Office work.
Close/disable Activesync,coz its not needed while flashing,end the process 'WCESCOMM.EXE' in the Task Manager,delete any Partnership with Activesync.
To check the connectivity problem,get the phone into Bootloaders (RGB) and hook up the phone with pc via usb cable and watch small usb appear at the bottom of the Bootloader screen,if its there,its establishing connectivity,than its good to go and run the flash,but if its not there,then its a connection problem.It may be the usb cable or mini usb port of the phone is faulty,check this out and do the needful.
Many communications errors are also due to dead or discharged battery,it doesn't have enough juice to complete the flash,hence,results in comm error,always start to flash with a fully charged battery.

le problem was the laptop i used a different one and its almost done i got another ? if i changed the radio am i gonna have to get the original tmobile radio too or does it change with the downgrade

Original ROMS
lorijuan1024 said:
le problem was the laptop i used a different one and its almost done i got another ? if i changed the radio am i gonna have to get the original tmobile radio too or does it change with the downgrade
Click to expand...
Click to collapse
The Original ROMS got his Radio ROM included. in fact... Stck ROMS got...
IPL and SPL
Extended ROM
Operative System
Radio Version

Can this be done if I have Vista?
I know someone mentioned installing a rom won't work with Vista, but I was hoping maybe it was just a personal preference. I have two pcs that both run Vista and Linux. My problem is, the wm6 rom (faria crossbow) doesn't work by default and I have a cracked screen so when I try to set it up I can do every step except setting the proxy port #s because when I highlight one there's no way to tap on it, and pressing or holding the select button (the button in the middle of the 4 way joypad) doesn't allow you to edit the values or pop up a context menu. I was hoping to get my $5.99 internet or at least my email and mms working but I got layed off and the holidays are coming so I prob won't have the extra (I know its not much, but I have no job) $30 to buy a new screen until sometime in the new year.

Why not downgrade to the Button ROM, and then upgrade to WM5 afterward?
Chuck

Hard SPL via MicroSD card

Hello all,
I'm having big problems syncing my phone to pc...is the above possible via MicroSD card...I know flashing a rom is but can I hard SPL it in the same way
Thanks in advance

I don't believe it is possible unfortunately.
What issues are you having? Have you tried updating (or even downgrading them depending on what you currently have) the usb drivers?

The probleme that most of us flashing new cooked ROMs & my device get stucked several times. Likely it is connected via USB, Otherwise I can not do any thing.
Also due to several ROM flash times the USB connection in HD (or other devices) might broken.
This why we need a way to install USPL or HSPL via SD card.
Can some one help?
Regards

What I don't understand is how can a usb port become 'broken' due to flashing several custom build roms?
I too having a problem with the usb port on my blackstone. It can only be charged but not synchronized with pc anymore. I had HTC pick up my phone to have the mainboard replaced. Luckily the phone was still under warranty, so it won't cost me much.
Can someone explain?

i had similar probs ...
went to regedit , local maschine, software, microsoft,
windows ce services and changed to (1) the key : hasusbdevice
after this no problems anymore
it seems that a program installation changes this number from 1 to 0.
i have win 7 32

kersey said:
Hello all,
I'm having big problems syncing my phone to pc...is the above possible via MicroSD card...I know flashing a rom is but can I hard SPL it in the same way
Thanks in advance
Click to expand...
Click to collapse
This is not possible infortunately. However you do not need your device sync'ed with your pc to run HSPL. You only need to put device into bootloader and then connect it to pc. Bottom of bootloader should change from 'serial' to 'usb'. If not, you will need to update usb drivers. All this info can be found on this thread, no need for another
Thread closed