Database Users

How To: Revert to Windows Mobile 2003

Whats needed:
TyphoonNBFTools: http://w1.whatcounter.com/dlcount.p...yphoonNBFTools_0.3_SPL1010064_SPVServices.zip
Any Official Rom (I used I-Mate SP3 WWE).
A Typhoon running Windows Mobile 5.0.
Reverting Back:
Run TyphoonNBFTools and Open the SPL1010064.nbf. Right click on SPL in the bottom part of the screen and choose Emergency Flash. If this is the first time you have used the program you will get a prompt on your phone to run the runtimes. Choose yes. Click OK to flash the new bootloader to your phone. Next disable Activesync by turning off USB connections. Turn off your phone. While holding down the Camera button insert the USB cable, the phone should run the bootloader and you will be presented with the tri-color screen. It should say USB in the bottom corner. Now run Mtty and choose USB connection. Hit enter in the blank white space. You should now see Cmd>. Type "info 2" without the quotes. You should see some information about your phone. Next type "format BINFS" agains without the quotes. This one is case sensitive. You should see format complete or something along those lines. Now close Mtty and re-enable USB connections. Run the exe from the update you downloaded and follow the instructions. Your phone should now boot back up to WM2003.
For those stuck in bootloader mode you will need to run mtty and reflash the wm5.bin to the phone then follow the steps above.

Leiden said:
Whats needed:
TyphoonNBFTools: http://w1.whatcounter.com/dlcount.p...yphoonNBFTools_0.3_SPL1010064_SPVServices.zip
Any Official Rom (I used I-Mate SP3 WWE).
A Typhoon running Windows Mobile 5.0.
Reverting Back:
Run TyphoonNBFTools and Open the SPL1010064.nbf. Right click on SPL in the bottom part of the screen and choose Emergency Flash. If this is the first time you have used the program you will get a prompt on your phone to run the runtimes. Choose yes. Click OK to flash the new bootloader to your phone. Next disable Activesync by turning off USB connections. Turn off your phone. While holding down the Camera button insert the USB cable, the phone should run the bootloader and you will be presented with the tri-color screen. It should say USB in the bottom corner. Now run Mtty and choose USB connection. Hit enter in the blank white space. You should now see Cmd>. Type "info 2" without the quotes. You should see some information about your phone. Next type "format BINFS" agains without the quotes. This one is case sensitive. You should see format complete or something along those lines. Now close Mtty and re-enable USB connections. Run the exe from the update you downloaded and follow the instructions. Your phone should now boot back up to WM2003.
For those stuck in bootloader mode you will need to run mtty and reflash the wm5.bin to the phone then follow the steps above.
Click to expand...
Click to collapse
Man! Can't thank you enough for this. I took my phone to the service centre, willing to pay for the repair, and they could not do it. Every thing works fine now. Very good manual, clear instructions and correct info!
THANKS!

Hi
I Am Trying To Follow The Procedure Mentioned. But When I Right Click On Spl I Am Not Getting 'emergency Flash' Active.
Can U Please Assist Me Regarding This

You need TyphoonNBFTools.dll installed on your phone. Try running TyphoonNBFTools and selecting Tools->Immediate Flash Tools->Test Immediate Flash. It should automatically install the required stuff for you. Check you phone when you run the program. You should get a prompt to installed a program from unknown publisher. Make sure to choose yes.

Stuck in bootloader
Just trying to do this following my question here.
I though it was going well but I have a major problem now! I managed to do the emergency flash, but every time I boot I just get the tricolour bootloader screen (IPL 1.00, SPL 1.01.0064) and can't get any further. Any ideas please? I have tried using mtty to load wm5.bin but get the error "MTTYDownloadImageNot allow operation!"
I have also tried re-doing the "format BINFS" and doing the above again but still no joy.
Any ideas would be much appreciated!

maybe u need to make a "goldcard"
my feeler (o2 xphoneII) lives again after flash with goldcard.

I can't find a way to create one for Typhoon, can you point me in the right direction?

I try flash Amadeus = Qtek 8100 with UpdateTool from Qtek 8310.
Update process stopped at 74% , and UpdateProgramm closed.
Now my Qtek 8100 not Powered ON , and can't enter in boot mode (tricolor screen) with "Camera" button hold + USB cable conneting.
PC don't see any USB devices when I connected my Qtek 8100 to USB port.
I think I erased Boot loader in my Qtek 8100 (but not sure).
Is any method for repair ?
WBR !

er1cc said:
I try flash Amadeus = Qtek 8100 with UpdateTool from Qtek 8310.
Update process stopped at 74% , and UpdateProgramm closed.
Now my Qtek 8100 not Powered ON , and can't enter in boot mode (tricolor screen) with "Camera" button hold + USB cable conneting.
PC don't see any USB devices when I connected my Qtek 8100 to USB port.
I think I erased Boot loader in my Qtek 8100 (but not sure).
Is any method for repair ?
WBR !
Click to expand...
Click to collapse
UR Phone is fried!
this happens to almost 1 out of 20 users.....that while downgrading/upgrading to another bootloader, ur phone becomes dead....

DomConway said:
Just trying to do this following my question here.
I though it was going well but I have a major problem now! I managed to do the emergency flash, but every time I boot I just get the tricolour bootloader screen (IPL 1.00, SPL 1.01.0064) and can't get any further. Any ideas please? I have tried using mtty to load wm5.bin but get the error "MTTYDownloadImageNot allow operation!"
I have also tried re-doing the "format BINFS" and doing the above again but still no joy.
Any ideas would be much appreciated!
Click to expand...
Click to collapse
get the tricolour bootloader type in mtty info 2 the type format BINFS then upgrade using rom upgrade

DomConway said:
Just trying to do this following my question here.
I though it was going well but I have a major problem now! I managed to do the emergency flash, but every time I boot I just get the tricolour bootloader screen (IPL 1.00, SPL 1.01.0064) and can't get any further. Any ideas please? I have tried using mtty to load wm5.bin but get the error "MTTYDownloadImageNot allow operation!"
I have also tried re-doing the "format BINFS" and doing the above again but still no joy.
Any ideas would be much appreciated!
Click to expand...
Click to collapse
i also got that problem but i reinstalled the patched RUU again and my phone now boot but i have not been able to go back to the 2003 as i insalled WM5 but still cant format the BINFS

If already have patcher the bootloader with the guide to upgrade to wm 6.0 can I ignore to do it again? I mean flash bootloader again ?

PLEASE PLEASE PLEASE!!! don t let my Universal be DEAD!!!!!!*** HELP ME PLZ!!!

Guys,
I ve just downloaded this http://rapidshare.com/files/21256078..._DUT_11500.rar romversion in the understanding that it was for the HTC 9000 PDA. There was a file called MaUpgradeUt_noID.exe which I let 'upgrade' my 9000. However, I think something very VERY big went wrong! A reset by pushing the 2 buttons and reset button on the back gives me the option 0 to reset but all I can see after that is a black screen which says USB at the top and at the bottom v1.00
What happened and is this the end of my PDA? Sync won t work anymore now since my PDA can t be detected by windows because I can t get in the PDA!!!
Is there something I can do??!!!
PLEASE HELP ME OUT!!!!
Edit/Delete Message

sounds like you're just in bootloader mode
I think you are in what's called bootloader mode. Read the wiki to check - the screen you are describing sounds normal to me you plug you device into the comp via usb (with sync over usb disabled in active sync) then install a new rom.
You really shouldn't have tried to flash your rom without reading some instructions first but I think that your device should be fine.
If you have already upgraded your rom just do a hard reset and select the option to reset.

Will this thread help?
http://forum.xda-developers.com/showthread.php?t=310056

I'm sorry, this is the thread I ment to link:
http://forum.xda-developers.com/showthread.php?t=310054

strangely enough I found out that I DID use a good version picked from this http://forum.xda-developers.com/showthread.php?t=298020 post. In this thread mwang gives a link to here http://buzzdev.net/index.php?option=com_phorum&Itemid=125&phorum_query=read,40,30486,30486#msg-30486 where I picked the dutch version. I than double clicked the MaUpgradeUt_noID.exe file and the software for upgrading started. When he was at 100% he said the the ROM update was completed and that I had to do a reset. So, I than pushed the three buttons (2x the - button and the reset button at the back of the 9000) but all I than see is the bootloader menu with USB and V1.00...........
Sorry for putting it in three sub forum, my fault, but the device is from my work so I don t want it to be screwed up!!!

sanderh said:
Sorry for putting it in three sub forum, my fault, but the device is from my work so I don t want it to be screwed up!!!
Click to expand...
Click to collapse
Rather late now, but if it's owned by your company for work, should you really be di**ing with it?

Solution to probl: Stuck in Bootloader
The one way of fixing your problems....you're officialy stuck in bootloader,
Here's the way to fix it:
1. Stop Activesync USB connection on your machine under connection settings.
2. Uni : Reboot Bootloader then Connect USB ( If your phone isn't in bootloader already..)
3. PC : Run mtty1.42.exe ( Download from XDA's ftp site or search the forums, I'm sure you'll find it.)
4. Choose USB in "Port" (Reconnect if can't find/reconglize USB and try remove sim and sd card)
5.1 Press Enter
5.2 USB> (This will show up)
6. Type: Set 14 0
7. Press Enter
8. Run your rom update again and it should flash this time.

did it start??
did it start?? ?

Hi. first post.
Have an o2 exec. Different brand same deice and none of the other methods worked but finally got it working. Using mtty1.42.exe it would not see usb connection and therefore could not go down that route.
I booted into the bootloader mode that says serial at the top and v1.00 at the bottom.
Connected to the pc and cant remember if i stopped wcescomm.exe or not but you can try both ways.
Then started Midget_1990_v1_0_PU10_WWE.exe rom and followed the instructions and voila.
Hope this helps someone.

"Using mtty1.42.exe it would not see usb connection"
You need to disable the usb connection of active sync under connection settings and then only mtty will pick up a usb connection..

[FIXED]cannot install NAND roms anymore[FIXED]

Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I got this when I first installed the standard DFT ROM, i found that by remving the accept USB connections in activesync resolved it and I was able to install. I then tried to install a different ROM and failed, I tried another and the same. I was initally getting RAPITOOL errors, dll not found. Reinstalled activesync and I am not getting those errors anymore but ROM still wont install. With error above.
Reinstalled Mag ok so bootloader installs still ok, anyone any ideas?
FECK, my NAND Android build has gone as well...

What helped for me:
- If USB is connected: right click on USB -> safely remove MAGLDR USB device
- remove MAGLDR USB driver from PC
- restart pc
- connect phone again via USB and let driver install
Should work fine again now. Guess something can go wrong in the USB driver sometimes.

mag does not show up as a device to remove, i will reboot and try again.

I think activesync reinstall resolved it as it worked after a rebooted, didnt reboot prior to that, thanks for your help anyway.

I spoke to soon, well managed to flash another ROM, didnt like it so flashed again, got half way through and then came up with error again, tried again, back to square one. Anyone ideas what is causing this?

rebooted, still the same, reinstalled activesync and rebooted, all ok again. Why is activesync required, cany anything else be used, anyone any idea what is happening here?

you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)

t3g said:
you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)
Click to expand...
Click to collapse
Hi, thanks for info but I am passed that point. I have already installed mag and tested my first ROM, I am having this problem when trying to flash new ROMS. I have now go another ROM on by reinstalling activesync and rebooting again, I am hoping someone is aware of this issue and let me know how to resolve it as I dont want to have to go through this rigmarole everytime I want to flash - as I am still at the stage of settling on a ROM and are trying all the current set.

In a much happier place right now. don't have to stress over winmo 6.5 anymore. Thank you all for your help. Lovin' Android on my HD2. So fast.

Try this http://forum.xda-developers.com/showthread.php?t=918698

And this might be helpful, too

deckoff said:
And this might be helpful, too
Click to expand...
Click to collapse
cheers but problem now solved after using android_install.exe rather than daf.exe

[Q] Problem mit flashing magldr versions

Hello...
I have a SD-bootable Android on a Dutty Windows ROM 6.5 with a working radio and HSPL 2.08. All perfectly working.
Now i want to go NAND and want to install MAGLDR. I start it as administrator, then i can select update and my phone goes straight from windows to bootloader. But after that i get the message that my workstation can't connect to my phone (althought boot loader says "USB"). I tried it directly from boot loader too and that too doesn't work (from there i can't even get the Update selection).
Could there be an issue with the Dutty ROM or has anyone else an explanation for this kind of behavior?! And is there anything i can do... maybe erase the whole ROM (HOW???) or anything?
Regards
Elmar

Is the error message by any chance "USB init failed"?

What version of Windows are you running? Also, do you have a firewall or antivirus application running? I have seen them interfere before and you could try temporarily disabling / deactivating them.

I have an antivirus (AVG), but it is only on Android, which i am not accessing when updating. As i said i tried from windows (6.5) and the update took me to the boot loader but then the windows application is trying to connect and then gets no connect and this error message appears :
"Error (260)
Check the following :
1. PDA Phone is connected via USB
2. USB cable is connected to the workstation"
And it is connected, which you can the on the fact, that the update is running my phone into the bootloader, but then i get stuck on 0% and after that the error message appears.

What you want to do is try disabling the allow usb option in active sync. Do this after you install magldr but before you try to flash the rom. This seems to fix the problem.
Sent from my Wimax infested cm6.1.2 SuperSonic

Hello again...
I am so sorry to have bothered you with my nonsense.
From the workstation i tried (which i strangely flashed all other ROM's before and had no problems) there had been missing the driver for the boot loader which pretty simple explains my problems here (Do'h).
Tried it from a workstation with internet connection and eureka, the driver installed and i could install magldr afterwards.
Thx for all your support and sorry for my homer-like thinking for not checking that before.
P.S. Any of you any recommandations for a good NAND ROM. I think i am going to try MDJ's CyanogenMod7. Or has anyone tried various and come to another good ROM?
Regards
Elmar

[Q] Can't run RUU, always stuck at 0%

Hi,
i am having lots of trouble with my HD2. I just got it so im kinda new to this new stuff. I previously came from the HTC Desire.
My problem is that i can't run any RUU. Even the original one. Or the magdrl one.
It is always stuck at 0%.
Steps i have taken: I established activesync unfortunately it does not sync properly because it asks me to log in in my phone and i cant seem to do it. though i still go to the bootloader and have USB at the bottom.
I have installed HSPL4 with 2.08.0000. It was succesful. I tried different USB ports on my computer.
Its only the RUU problem where i am stuck at 0% and after awhile it fails and gives me error 276.
Please help me...
Thanks
Vevek

I also had this problem seldomly.
Possible reasons are:
- battery charge level
- virus scanner on PC
- firewall on PC
- non removed SD
- other devices connected to USB (printer, scanner, ...), disconnect which you don't need.
- USB 3.0 ports on PC
- ...
- Have you tried to reboot your PC?
- Which OS are you running on PC?
- If Window 7 try to install Windows Mobile Device Center again
- Have you already tried LeoAdvacedRUU?

shockem said:
I have installed HSPL4 with 2.08.0000. It was succesful.
Thanks
Vevek
Click to expand...
Click to collapse
2. 08.0000 is stock, so won't allow flashing. Run hspl4 again and choose "2.08.hspl" .