Develop Bugs

Complete idiots guide needed, please!

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?

O2 Orbit German to english

Hello friends,
I am not new but this is my first thread.
I have just bought a sim-free O2 Orbit from germany and it is working fine.
How can I turn the OS language into english? and I also get a failure connection to the internet since I arrived home in australia. it is 0x8007278.
Please the experts any advice is appreciated. thanks for sharing the science.

I was in the exact situation as you, this is how you change your ROM to English.
Get this program called USPL, it was created by a member of this bard called Bepe. Look on the first post for the program AND the instructions...read them.
http://forum.xda-developers.com/showthread.php?t=311403
What this program does is it unlocks the phones carrier lock so that it will take a ROM that is not OEM.
Once you have this, look for the ROM you want to run, I can personally recommend Bepes WM6 or WM6 Black and Blue v3.
Bepes rom...
http://forum.xda-developers.com/showthread.php?t=309702
PDA Viet WM6 ROM (super freaking cool, way better than I thought it would be)
http://forum.xda-developers.com/showthread.php?t=314568
Once you have these two things, put them all on the desktop for easy access, then run the USPL according to the instructions. You MUST have Active Sync installed, running and sync'd with your phone (plus its a great idea t have all your contacts backed up with Outlook). Once the USPL program has completed its process and the phone has restarted, you can then load any ROM you want. Simply plug in your phone via USB to your computer, then run the Rom Upgrade Utility that installs on your desktop when you download the ROM. It will show a progress bar, once you make it past 3 or 4 percent you know you are in the clear and the ROM will load right.
I cannot stress enough the importance of running USPL, if you dont you run an almost guaranteed risk of turning your phone into a cool looking paper weight.
If you follow these instructions, read a little in the Upgrading and the WM6 sections of this board, you will have an English phone in your hands by the time you go to bed tonight. Good luck and feel free to PM me if you need and help.

Oh and PS - For the data, once you have changed you ROM to English, you need to either find the settings or the CAB file for your data connection. Most of the time these can be found on your service provenders site, if not, run a search of this bard, almost anything you need - world wide - is on here somewhere.

THANK YOU Itschcase. your responce was brilliantly quick.
I was trying since yesterday. read most of the eplanatory threads. tried not to bother you again. but I am stuck at the USPL. after fist step the screen goes black or grey and the activeSync disconnects and it remains like that. if I continue the process nothing happened if I soft reset then continue I get error 270 "image file corrupted" and the pda reboots automatically and goes back to its state. tried 10 times. reinstalled my xp after formatting the computer. tried on my other computer vista . still no change.
any ideas please

error [260] message every time

Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)

Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2

I am assuming you mean flash with the new ROM, sammy's in my case?

yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)

No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.

the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.

What operating system en activesync are you using?

On the PC I am using XP and Activesync 4.5

Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.

deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.

BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.

Vista
Using Vista? if so which version?

Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard

It works
Now to discover the joys of WM6 after only having WM5 for two weeks....

/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone

sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?

This seems to be on any rom bar the Dopod roms
and it says 260 connection error

Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.

I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps

htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help

O2 Cosmo (Excalibur) ROM Update - How the Hell ?

Hello Experts,
i have read a lot of the Threads here, but i can't find a good information
about my O2 Cosmo. My Dash is Simlook free and SuperCID enabeld.
I found this instructions:
Tools you need:
===============
- HexWorkshop from http://www.bpsoft.com/downloads/-
the ROM of your choice
- Winzip or Winrar
- a valid UNL file for YOUR phone
Preparation:
============
a) install HexWorkshop and Winzip or Winrar on your pc
b) in explorer on pc, RIGHT click on the ROM of your choice and use: "Extract files to folder ..." from conext menu Now it will unpack all the files
c) in the new folder you will have ONE file like "HRUU_signed.NBH" (*.NBH) RIGHT click on the .NBH file and use: "Hex Edit with Hex Workshop" from context menu
d) You'll see on the 5th row EXCA20000 ==> !!! make it EXCA***** (5 stars) and save the file
e) Now RIGHT click on ROMUpdateUtility.exe and use: "Hex Edit with Hex Workshop" from conext menu
Search for word "BsaD5SeoA" (without quotes, case sensitive)
You'll find it around address 0x3FC6C ==> !!! replace "BsaD5SeoA" with "IMEICHECK" (without quotes) and save the file
ROM-Update:
===========
1) take SIM card and SD card OUT of the phone
2) Connect the phone running windows ce to the pc (normal way).
3) Completely Unlock your phone using our unlocker <== REALLY IMPORTANT
4) After phone is unlocked run unlocker (again) BUT when the unlocker ask for UNL file, remove the USB cable from the phone THEN press "Cancel" on the unlocker select file window (unlocker will close on PC). NOTE: The screen on the device will not show something usefull when in this mode. Most probably it is complete WHITE. !!THIS IS NORMAL!! Don't touch phone, let it like it is!
5) After you closed the unlocker, attach usb cable again (phone has still white screen)
6) start (the modified) ROMUpdateUtility.exe
7) when update finished and device started you will get a message: "Data Crashed, contact service provider" (!NO PANIC!) ==> Simply fix this problem by running the unlocker again and this time select the key file normal way (full unlock process again). In case you have problems please indicate the step letter/number which is not clear/not working for you. If you REALLY do it STEP by STEP exact like described you will have no problem.
Click to expand...
Click to collapse
When i edit the .NBH file, i get a "ERROR 270" message!
When i dont edit the .NBH file, i get a "Invalid Ventor - Error Message"
I try to install this ROM:
"RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.90_Ship.exe"
So my Dash is a German Device, and i want a German ROM, if it is possible!?
OK, i try to go manually in the Bootloader modus, disable ActiveSync for
USB Transfer...and run the RUU Rom...but it allways break down the flash
process at 4% !
...mmh...have i forget any info, that you can help me...i dont know?
Ah Yes...i read in the Thread:
"How to flash a new ROM to your Wizard... a little tutorial!"
Here the link to:http://forum.xda-developers.com/showthread.php?t=298613
But i can see anything on the starting screen, if my dash ist a G3 or G4,
on my start screen ist "ABSOLUTLY - NO - Information" about it!
In the "System Information" i found a RIL Nr. 2.0002 ...
So i think my dash is a IPL/SPL G3...but i dont know it really!
I dont know what i can do anymore, to update my device to WM6.0 or 6.1
Plz, if anyone know what i can do, to fix my problem, plz then tell it to me,
thank you very much, and forgive me about my bad english!

Ok, i test many times this tool "Excalibur USPL- CID BYPASS" ...and yesterday
it works suddenly...i dont know "why" it works, i have done the same, like
every time i try it, but yesterday my dash move to the needed "WHITE
Screen"! And so i able to run the Rom Update, and it works fine!
Ah yes, my Phone tell me i'm in "SuperCID" Mode...so "WHY" i must use
this "CID Bypass Tool" ....crazy??? Or is my Phone a Liar...?
I have now installed this Rom, it Works a bit faster i mean:
RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.90_Ship.exe
But it is the same Rom Vers, like my old O2-Cosmo Rom, WM5.0 (1) with
Future Pack. But i have now the HTC Splash Screen!
So i want now to install this Rom (with WM6.1) :
"NoThrills_WM61_GER_V3.exe"
This is a "Kaiser" Rom... "Warum eigentlich Kaiser, hat der Beckenbauer damit
was zu tun...*g*
But when i try to run again the "Excalibur USPL- CID BYPASS" tool, my
dash show me only the "Linux Monkey" (Pinguin) Screen and hang up the
Phone, so that i must remove the battery....
The "White Screen" (that is the Screnn you must have to flash your Rom),
will dont come anymore....i dont know how...??? I start this batch file,
"Uspl.bat" ... and follow the instructions....mmh....allways i get the Linux
Monkey Screen...and not the white screen, "WHY" ?
Anybody a hint, how i can move into the "White Screen" Modus?
And a Question, is this Kaiser Rom compatible to my HTC S620 ?
Please belive me, i read a lot here...but i cant figure out this..., this Forum
here is a bit confusing, on many Threads you can read other informations!
Plz anyone, tell me (who know it) how i move exactly in the White Boot Screen?
Thank you!

If I understand you right you flashed a rom from the HTC Kaiser on your Dash. That's Windows Mobile 6.1 Professional for Touch Screen Devices. You need a rom from this thread for your Dash, not the Kaiser thread. Those ROM's are specifically for that phone. I doubt they'd even work on other Touch Screen phones because of it has the radio (I believe Radio is like Drivers in Windows, I may be wrong.) for that phone. As to fix your problem. I have no clue. Maybe you can get lucky and reflash it with an Official Dash ROM for your phone, but better getting advice on that from one of the more experienced people here. I'm a bit of a newby when it comes to this phone stuff. Good luck...

drkfngthdragnlrd said:
If I understand you right you flashed a rom from the HTC Kaiser on your Dash. That's Windows Mobile 6.1 Professional for Touch Screen Devices. You need a rom from this thread for your Dash, not the Kaiser thread. Those ROM's are specifically for that phone. I doubt they'd even work on other Touch Screen phones because of it has the radio (I believe Radio is like Drivers in Windows, I may be wrong.) for that phone. As to fix your problem. I have no clue. Maybe you can get lucky and reflash it with an Official Dash ROM for your phone, but better getting advice on that from one of the more experienced people here. I'm a bit of a newby when it comes to this phone stuff. Good luck...
Click to expand...
Click to collapse
Thank you!
But "NO" i don't flash my HTC S620 wit a Kaiser Rom..."What a Luck" ...i try
to do it...and now im Happy that this have not work for me!
I actually install this Rom:
RUU_Excalibur_HTC_GER_1.11.407.2_4.1.13.28_02.63.9 0_Ship.exe
I have now understand, what is a Kaiser ROM, it is the Device Name, oh
Man...i'm so a dummy....haha...
But i have a success, i change my O2 Rom to a HTC Rom
The Question now is, how i move in the "WHITE BOOT SCREEN" ?
That i'm able to Update my Rom to a WM6.1, if posible, a German 6.1 Rom.
Is here a German WM6.1 Rom?
Is a WWE a Multilingual Rom, is in such ROMs German Language included?
And how i can remove the CID forever, so that im able to update a ROM
without a CID Bypass Bootloader?
Any ideas?
The thing is, ...this CID Bypass Bootloader work "ONCE" and now that
Bootloader dont work anymore...i dont know why...i get only the Linux
Pinguin Screen...and this is a "Hang up Screen" so that i must remove
the Battery, for a new start.
But i get nevermore the "White Boot Screen" ...how is this posible?
I do the same, like before i do...mmh...???

If I understand what's been said. You need to re-run the CID-Bypass anytime you reflash you phone. As for a German ROM. I am not sure. Ypu'd need to look around through the furom. You could try the "Seach" feature and see what you come up with.

drkfngthdragnlrd said:
If I understand what's been said. You need to re-run the CID-Bypass anytime you reflash you phone. As for a German ROM. I am not sure. Ypu'd need to look around through the furom. You could try the "Seach" feature and see what you come up with.
Click to expand...
Click to collapse
Thank you,
but i try to run the "CID Bypass" but the "CID Bypass" run every time
into the "Linux Pinguin Screen" ...(i think it is programed in Linux?)
But the same "CID Bypass Bootloader" - work - for me "once" !
But now, not ! I dont know why?
With this CID Bypass Bootloader, i flash my Q2 Rom into a HTC Rom !
But that was only possible, as my dash move with this "CID Bypass Bootloader"
INTO a "White Boot Screen"...!
But "HOW" this was possible...i dont know...now this CID Bypass Bootl.,
wont work anymore....
You know what i mean?
The same tool (CID Bypass) wont work anymore, it work one time only.
When i now try to run this CID Bypass, i get a "Linux Pinguin Screen" in
Black. So there is a little Linux Pinguin "Preloader" ...and then the Phone
have a SOD..."Stand of Death" you Guys call that so, i think so!?
To search here, is very strange for me....i get results of all Forums here!
That was the reason why i want to try the Kaiser Rom, while i search
here in the Excalibur Forum...so i had think so, that was wrong, you know!?
Sorry, my english is not good enough to tell exactly my expirience!
But Thank you for Advice!

Hum, does it still look like windows mobile? If so they may have just changed the load screen. Either way when you run the bypass program, there' one step that'll show a screen on the phone when in windows mobile itself and you must press the center soft button to "continue" and then it'll enter the white screen mode. Sometimes I forget this step and bounce through the steps missing that. If you can't get into windows mobile, try reflashing with your phones official ROM first. They don't require the white screen. There's also a way to enter the bootloader screen by holding down a button, I forget which, while you press power to turn the phone on.

drkfngthdragnlrd said:
Hum, does it still look like windows mobile? If so they may have just changed the load screen. Either way when you run the bypass program, there' one step that'll show a screen on the phone when in windows mobile itself and you must press the center soft button to "continue" and then it'll enter the white screen mode. Sometimes I forget this step and bounce through the steps missing that. If you can't get into windows mobile, try reflashing with your phones official ROM first. They don't require the white screen. There's also a way to enter the bootloader screen by holding down a button, I forget which, while you press power to turn the phone on.
Click to expand...
Click to collapse
...no no, this ROM runs great! I have no Problem with this Rom!
But i have found a Solution "Yeah" !
For all who want to flash a O2 Cosmo!
Try this Link: Click
Thanks to the Uploader, found it by searching!
The last in line: "Unlock_phone_files.zip" !
Follow the steps in the text document!
Work fine for me!
But when you want to flash, and you get a connection ERROR, remove
the USB cabel, and put it back on your Dash, and run then only the
"ROMUpdateUtility.exe" again and it will work.
(Your srceen are allways WHITE!!!)
I had flash for 10min the "RUU_Excalibur_SPL-1.11_UpgradeOnly.exe"
You must extract the exe file, and copy the *.nbh file to folder 3!
After you run the "Auto.bat" and the Connection Error, click finish,
remove the USB cabel, put it back on the dash and run again and only
the "ROMUpdateUtility.exe" !
All work fine!
Thank you Developers!

WM 6.5 for T-Mobile MDA III

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.