Database Develop

Help! Custom Tmo 2.17 update gone VERY WRONG

I tried updating my Qtek 9100 from the firmware it came with (1.01 or something, I wish I'd written down the specific one, but it was the 9-22-05 release) to the custom ROM for Tmo 2.17 from here: http://forum.xda-developers.com/viewtopic.php?t=44631
My phone refuses to recognize on ActiveSync, it doesn't list a GSM version in the top left when it boots up, the phone app won't even load, and in the comm manager the ActiveSync icon is greyed out, and the phone icon is green. I clicked on the phone icon to turn it off, and when I tried to turn it back on, it wouldn't. Hard resetting does nothing. I can't revert back to old firmware because activesync won't detect my phone. Someone please help, what can I do to make my phone work again? I don't want a brick!

I've been on the phone with T Mobile USA all day trying to get support (their 2nd tier support is always nice enough to try and help, even though I didn't buy an MDA from them). No help. They bumped me up to tier 3 and the tech I spoke to said I'd need to bring it in to get a replacement.
This is bad news for me since I bought this phone in LA, and I won't be going back there until next week. Until then I'll have no cell phone (assuming that they'll replace it when I bring it in) unless someone here can help me.

DedEye said:
I've been on the phone with T Mobile USA all day trying to get support (their 2nd tier support is always nice enough to try and help, even though I didn't buy an MDA from them). No help. They bumped me up to tier 3 and the tech I spoke to said I'd need to bring it in to get a replacement.
This is bad news for me since I bought this phone in LA, and I won't be going back there until next week. Until then I'll have no cell phone (assuming that they'll replace it when I bring it in) unless someone here can help me.
Click to expand...
Click to collapse
Nah...I can't believe that it's time to give up and bring it back.
I think what you should do is locate a copy of the latest Qtek 9100 ROM (should be available here), get your device into "boot loader mode" -- which you can probably do even if it doesn't start up properly -- and try to load the Qtek ROM.
I don't have time to search the forum for the Qtek ROM, but you should be able to find it here, and also find instructions on getting your device into Boot Loader mode (with the red, green and blue bands displayed on the screen). Once you're there, and your device is plugged via USB cable into the pc, I'm guessing you'll have a decent shot at getting the Qtek ROM loader to work.
Suggestion: if you're having trouble finding individual posts that have what you're looking for using the forum's search tool, try google, targeted to this site. Each returned link will point to a single page. If, for example, you wanted to use google to search this site for info about the boot loader and ROM, you would go into google and type the following:
"boot loader" ROM site:xda-developers.com
...and hit enter. Google is great for finding specific pages in huge forum threads.
Hang in there. I believe you'll get this working again and won't have to return it.
EDITED: Did you CID unlock the Qtek before attempting to flash it? This is critical as I understand it...

Thanks Jon; I was climbing up the walls trying to find anything with the built in search. I'll use Google. The bootloader info is what I really needed to know, that should save me from having to replace the phone.
Edit: Yes, I did CID Unlock before attempting to flash it.

DedEye said:
Thanks Jon; I was climbing up the walls trying to find anything with the built in search. I'll use Google. The bootloader info is what I really needed to know, that should save me from having to replace the phone.
Edit: Yes, I did CID Unlock before attempting to flash it.
Click to expand...
Click to collapse
If you haven't found it yet, I think I just did. See this page from the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
Scroll down to the heading "Upgrading, bootloader" and see the following: "The bootloader can be entered by holding the "Camera" button while resetting". So it sounds like you can hold the camera button and simultaneously insert the tip of the stylus into the reset button recess. Aside from some gymnastics, that sure would be nice and easy!
I believe that, after this, you should be able to run the firmware loader again immediately from your pc as long as your cable is hooked up between the pc and the MDA. Worth doing a bit more reading on this, but I'm pretty sure you'll be able to resurrect the phone, especially since you did the CID unlock first. I doubt that there's any permanent damage - just something messed up in the last load.

That doesn't seem to have worked; now it keeps displaying the Tmobile splash screen with the OS, IPL, SPL, and blank space where GSM should be in the top left. It stays that way for a few seconds, then the screen goes black and it goes back to displaying it. Only way to make it stop is to take the battery out.
This situation may have gone from bad to worse.

DedEye said:
That doesn't seem to have worked; now it keeps displaying the Tmobile splash screen with the OS, IPL, SPL, and blank space where GSM should be in the top left. It stays that way for a few seconds, then the screen goes black and it goes back to displaying it. Only way to make it stop is to take the battery out.
This situation may have gone from bad to worse.
Click to expand...
Click to collapse
Some of the guys here are incredibly knowledgeable about this stuff. I would browse / search and see if you can ID a couple of likely candidates -- maybe the moderators themselves? Trying messaging them directly and asking for a recommendation or person to speak to. I still think it's worth pursuing some more before giving up.

I was about to say success; in reality its just progress. I've accessed the boot loader. I had to hold down the camera button while the device was off, then plug it into the USB port on my laptop. I have IPL 2.17 and SPL 1.01, no other data is listed. I need to figure out a way now to update the firmware; I tried installing a KJam firmware and it gave the error message "Error 294: Invalid vendor ID". Seems that I need a ROM from Qtek if I'm not mistaken. I'll track one down and will update as I get more info.

DedEye said:
That doesn't seem to have worked; now it keeps displaying the Tmobile splash screen with the OS, IPL, SPL, and blank space where GSM should be in the top left. It stays that way for a few seconds, then the screen goes black and it goes back to displaying it. Only way to make it stop is to take the battery out.
This situation may have gone from bad to worse.
Click to expand...
Click to collapse
Let's take this a step at a time. Let's get you back to stock ROM first of all.
Dowload this file:
ftp://xda:[email protected]/Wizard/Roms/Qtek/Qtek_9100_RUU_Prodigy_10107105_Qtek_WWE_ship.exe
1.Turn your device off
2.Hold the Camera button in and push the power button for 2 seconds
...you should get the 3 color bar screen
3.Plug your usb cable in to the phone
4.Execute the file you downloaded above and follow the prompts
...If everything is happy with the phone's bootloader, you should see a progress bar as the ROM us updated. Be patient..it may take up to 10 minutes to complete, at which time the phone will reboot.
Post back here with your progress and we'll help you along.

@summiter - thanks for stepping in - I had nothing new to offer. glad you're here to help him out. I will watch and learn...

I'm to step 3 so far, but I can't download that ROM version (gives me an error). I need to find that version and install that next and I should be in the clear - until the next time I try to update my firmware of course.

DedEye said:
I'm to step 3 so far, but I can't download that ROM version (gives me an error). I need to find that version and install that next and I should be in the clear - until the next time I try to update my firmware of course.
Click to expand...
Click to collapse
What kind of error? I just clicked the link that summiter provided for the download and it worked for me (except that I killed it half way through because I don't need the file!)

"Could not connect to FTP server, possibly because of too many users. Please try again later."
Prompts for a username and password, but I have neither (unless its my forum password. I'll try that and update you if it works,

DedEye said:
"Could not connect to FTP server, possibly because of too many users. Please try again later."
Prompts for a username and password, but I have neither (unless its my forum password. I'll try that and update you if it works,
Click to expand...
Click to collapse
It shouldn't prompt you since the username and password are embedded in the URL, but if it does, use this:
username: xda
password: xda

DedEye said:
"Could not connect to FTP server, possibly because of too many users. Please try again later."
Prompts for a username and password, but I have neither (unless its my forum password. I'll try that and update you if it works,
Click to expand...
Click to collapse
I just tried it again and it's fine. The user name is "xda" and the password is "xda". That's in the link that summiter provided: the beginning of the link shows the password, then the user name and the file URL. Once you start navigating the FTP site, though, the username and password disappear from the URL displayed in the browser address bar.
Try clicking summiter's link again. Alternatively, you can:
Try the FTP link to the whole wizard download dir:
ftp://xda:[email protected]/Wizard
Notice just above - you're seeing "password:username" followed by the "@" and then the file URL...
Click on Roms
Click on Qtek
Click on the link for the 10107105 ROM -- looks like it's the 7th file down in this subdirectory.

Is there anywhere else I could download it from? Its not even bringing up the prompt to put in the user name and password now, just says too many users downloading. I'll keep trying.

DedEye said:
Is there anywhere else I could download it from? Its not even bringing up the prompt to put in the user name and password now, just says too many users downloading. I'll keep trying.
Click to expand...
Click to collapse
I think you have some seriously bad karma. haha =)
I hate to suggest this, but, reboot your PC. Or try another browser..do you have Firefox? (every self respecting geek should)

DedEye said:
Is there anywhere else I could download it from? Its not even bringing up the prompt to put in the user name and password now, just says too many users downloading. I'll keep trying.
Click to expand...
Click to collapse
Doesn't make sense. I just tried it a few more times and get right in - no problem or hesitation at all.
Is there any chance your browser has cached the error page and keeps giving that to you without even trying the reconnect? I'd try making sure you kill your browser completely -- check task manager and make sure your browser is completely gone -- then open it up, clear your cache and try again.

@Jon:
I tried taking the filename out of the URL before you suggested it with the same results; it keeps telling me that too many users are connected to the ftp.

I also tried using a different browser because I thought that might have been the problem. Neither Firefox or Opera will load it; Firefox gives me error code 530.
**EDIT**
Success with IE! I'll download it and give it a shot now.

ROM upgrade issues...

So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
-----------
Originally posted under xda-developers > Wizard (Oops? )

Please help me! My phone has commited suicide!

You all probably have heard the things that have happened to others, this might be different.
I got my Audiovox XV6600 (verizon) from a friend. His father used it extensively so there were some blemishs and such on it, and the battery life is horrible.
That was about 4 months ago and a week after I got it, I flashed it to the lates firmware.
Before I continue, I would like to state that I am computer lieterate, so through anything at me. I have owned a few regular cell phones that I have modded with firmware and such (not personally modded but flashed). Same goes for regular PDAs. (But I will warn you that I am a horrible speller )
Yesterday, I went to use my phone, and a common error happened that requires a soft reset. When I hit talk on w/e number I am calling, it just says "Dialing" for like 3 minutes, even if I turn off the phone, it will complete the call later if it has too, no way of cancelling in unless I reset or wait.
So I reset it.
That is when wierd **** happened.
Normally, the screen will blank, Windows Mobile will pop up and about 10 seconds later the back light will pop on. Well it the light took about 1 minute to start and I noticed at lower right hand part of the screen it says
"p DM FAIL"
"r DM FAIL"
"2.07.00 WWE"
After it FINALLY boot, I noticed I that it said the phone was off and there was NO WAY of turning it back on.
My hunch is that somehow the radio ROM got corrupted or this phone finally bit the dust. Probably both. BUT I WILL NOT ACCEPT DEFEAT UNTILL ALL OF MY OPTIONS HAVE BEEN EXSAULSTED!
I have searched google, searched this forum, searched the wiki and nothing fixes this thing.
The first option = Reflash
Answer= I have tryed that multiple ways and I am typing this right now since I think I have tried everything.
Option A,
I got the latest ROMS from verisons site. When I flash I get the country ID error, so I tried it with the _noid updater. First time, got the id error again, second time, continued with the update BUT, NO PROGRESS happens on the radio update and that is the first update!
Option b =?
option f = THROUG THE F***ing THING AT THE GROUND! (but this is my ONLY phone and it will be months before i even get a **** phone!)
Here is what is listed in my Device information of the phone. Remember I can use the PDA side of this phone, but that is all. NO phone, NO inet, and it makes sense too, it is like I don't have the drivers for the radio.
ROM version:2.07.00 WWE
ROM Date: 02/07/06
Radio version: DM FAIL
Protocol version: DM FAIL
PRL version: N/A
ExtROM version: 2.07.00 WWE
Hardware Version: 0041
ESN: N/A
Browser Version: MSIE 6.0
(Info from GetDeviceData.exe)
PH20A2 ( and yes that is all that is in the txt file)
HELP!
EDIT: Wow, UTStarcom can suck my *....*
Meexplains what happend)
Tech: Your phone is "pooched"(wtf is that) Let me transfer you to *click* HELL no I am NOT going to send my freaking phone some where so you can restore my perment save and sell my contacts for money!

Starhero said:
You all probably have heard the things that have happened to others, this might be different.
Click to expand...
Click to collapse
I'm afraid it's not.
Starhero said:
I got my Audiovox XV6600 (verizon)
Click to expand...
Click to collapse
Starhero said:
error, so I tried it with the _noid updater. First time, got the id error again, second time, continued with the update BUT, NO PROGRESS happens on the radio update and that is the first update!
Click to expand...
Click to collapse
Starhero said:
Here is what is listed in my Device information of the phone. Remember I can use the PDA side of this phone, but that is all. NO phone, NO inet, and it makes sense too, it is like I don't have the drivers for the radio.
Click to expand...
Click to collapse
That is expected.
If you tried to flash your phone with a ROM image you pulled from here, it will not work. The wiki states that your phone is a CDMA phone, not a GSM phone. WM5 and 6 ROMs will not work with that phone.
The only thing you can try is to flash it with the official ROM from VZ and talk to them if it won't take.

I used the ROM from my service provider, but since the phone has screwed up, for some reason it won't flash it.
Also, I am currently at my friends house who has Windows XP, I leave tommorow for home. At home I have Windows Vista Ultimate, I am well aware that is it either impossible or very hard to flash on Vista. Is there a way around it with out installing XP?
Keep replieing please, I will be checking, just a busy 20 year old (almost 20).

Starhero said:
I used the ROM from my service provider, but since the phone has screwed up, for some reason it won't flash it.
Click to expand...
Click to collapse
Ah, I read your original post as the last ROM you tried was a WM5/6 ROM you found here.
Starhero said:
Also, I am currently at my friends house who has Windows XP, I leave tommorow for home. At home I have Windows Vista Ultimate, I am well aware that is it either impossible or very hard to flash on Vista. Is there a way around it with out installing XP?
Click to expand...
Click to collapse
Yes. It involves installing some USB drivers, older ones I think. You will have to search the forums for that, as I don't know what is involved as I know better than to run Vista.
Knowing which ROM you tried and rereading your original post, with the very limited experience I have with the Harrier, I would think that yes, the CDMA radio is 'pooched'.
You /might/ have some luck with a hard reset. It's worth a shot, but with those errors at the boot screen, I'm going to have to side with the person you talked with on the phone.
Beyond that, I'd search the forum for harrier and radio rom and see if you can find anything.

Serial v1.02 screen
I, too, lost the radio ROM recently. I got with same p DM FAIL" and "r DM FAIL" errors display on boot. Verizon replaced the pda with one of rom date 02/07/06 ver 2.07.00.
I tried to do the manditory update on the new XV6600 from the Verizon download website using my Vista workstation and ActiveSync (HA_VZW_207_117_01167_A12.exe).
The update failed and now the pda screen reads "Serial v1.02". In no longer connects to ActiveSync via the cradle, and it is totally unresponsive to the keyboard, buttons, hard reset, etc. What do I have, and what can I do with it?
Also, is it Vista that is blew up the upgrade? I had done this same upgrade on my original unit via XP.

Still haven't fixed it
and I haven't gotten another phone yet cuz I am a cheap a$$
As a despreate atempt can someone send me an ORINGINAL radio rom( the latest or maybe a step before)?
Idk exactly how to do such a thing but i figure my email is good
[email protected]
If someone has another idea PLEASE tell me

There seems to be no good answer for this....

Ok, I posted a thread on the main wizard forum and I'm trying again here since this is a little more on topic in this forum.
Here goes with all the technical specifics I can add in.
I recently got an HTC 8125 (I've had one before and never had this problem)
I immediately CID and SIM unlocked the phone using lokiwiz's unlocking program.
I inserted my tmobile sim into the cingular 8125 and all was great.
I upgraded the ROM to the TNT 19199 batch of WM6.1 Everything is still great.
The phone worked awesome, the next day I downloaded the T-Mobile UK radio version 2.19.11.
I flashed it to the phone and everything seemed fine, the program finished and the phone restarted.
Upon restart I was greeted with a no service message and the phone behaves as though it is shutoff. No big deal, right? WRONG...
I went to the tmobile and cingular site and got the default roms from each just in case.
I then connected the phone to the usb and activesync would not recognize the phone, or do anything for that matter.
I used an external USB bluetooth dongle to try and connect the phone to the PC to flash the default rom and fix the radio problem, this wouldn't work either.
I then put the phone into bootloader mode, this works ok, I see the USB in the corner and figure I'm saved. Nope.
I ALWAYS get an Error Connecting from the rom software. Even though my PC recognizes the phone, active sync does not. I re-installed Activesync and rebooted my computer numerous times. To no avail.
The ONLY rom software I which has worked is the TNT 19199 but it doesn't fix the lack of radio.
Here are some other points of interest. On phone bootup I get this:
IPL 1.08
SPL 1.08
<----Notice, NOTHING in the GSM spot.
OS 1.11.1.0.1 (or whatever the numbers are for that particular rom)
The USB will recognize the phone ONLY in bootloader mode, otherwise when the phone is on the Today screen I get no recognition.
The TNT rom has worked twice when I tried it, (by worked I mean it allowed me to re-flash the same rom) Of course the TNT rom doesn't work all the time, it has given me several connection errors.
No other rom has worked as of yet, all others give me a connection error.
The battery meter will not display, nor will it tell me what type of battery or how much charge is left.
The phone will sometimes go to amber light when plugged into the wall charger but NEVER with the usb to PC cable.
I can still navigate around the windows mobile 6.1 interface though it moves incredibly SLOW. i.e. I pushed the comm manager button to make sure the phone didn't simply get shutoff and I waited about a minute and a half or longer for it to bring up the comm manager.
I need some severely good advice and some new tricks to try, I'm running out of ideas, I saw several threads under the HTC TyTn threads about similar problems and something about the IPL/SPL being important but I'm not sure what they're talking about. I have searched this forum and I have found people talking about similar problems, all the responses point to, "If you can get to the bootloader you're fine." This is incorrect.
So seriously, help me out here.
HOW DO I FIX MY STINKIN' PHONE.

I would suggest rolling back to your working configuraton by reflashing using a memory card instead of the USB.

fixed.
Actually I finally figured it out.
It seemed the reason that those roms worked sometimes but not others was this: To get the phone to recognize you had to do things in a VERY specific sequence.
You had to let the phone boot all the way into WM6 and then plug in the usb cable. Then put it into bootloader with the camera / soft reset button method. Then you waited for the nice USB connect sound, and began the ROM flash RUU program. (In this case it was the T-Mobile default rom).
Once that was done the phone acts as normal and everything is good.
Doing anything out of order or putting the phone into bootloader without it having first booted all the way to the OS would give you the connect error.

Please clarify if you're running WM6 with IPL/SPL 1.xx? I believe that's not possible to get good results that way.

IPL 1.08
SPL 1.08
<----Notice, NOTHING in the GSM spot.
OS 1.11.1.0.1 (or whatever the numbers are for that particular rom)
TNT 19199 batch of WM6.1
Wm6.1 on ipl/spl 1.xx,strange ,how do you explain this,how did you manage to get wm6 installed with ipl/spl 1.xx,cuz it only works on ipl/spl 2.xx and higher. Are you sure its TNT 19199 series wm6.1 Rom ?

no four colored boot screen?

Hi guys..
I'm using O2 XDA IIs, and I'm trying to upgrade to WM 6.5.
I've downloaded the ROM and other misc applications to upgrade, and also read the walkthrough in the XDAdevelopers Wiki page. But I find my device have no four colored boot screen but instead an O2 image with some color information as such :
Code:
R : 1.02.00
G : 1337.32
B : 1.31.00 WWE
in the bottom right of my screen. I also can't see the four colored screen with options to format storage which is one of the point mentioned in the upgrade section.
That's why I've been hesitating to upgrade it since I have this phone, because I can't follow the upgrade walkthrough completely which might caused my phone to brick.
Anyone can help?
Thanks

the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.

Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck

Chef_Tony said:
the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.
Click to expand...
Click to collapse
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
thanks for the answer.
egzthunder1 said:
Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck
Click to expand...
Click to collapse
yes, I've always searched for more and more informations before doing something this risky. I'll visit the Q&A thread after posting this reply. thanks for the support.
---
btw, sorry if my English is mixed up. it's not my primary language, so please endure with my bad English.

for the bootloader mode, you might have to press and hold the power+record button a little longer while resetting and only release them, when the display is grey and shows SERIAL on top and v2.0x (where x is between 5 and 7) at the bottom.
the mentioned hard reset method is also only suitable for windows mobile 5 and higher. for windows mobile 2003 a hard reset is done by simply pressing power+reset (also maybe holding the power button for a second). there is no hard reset necessary before the upgrade, but afterwards, and then, using a higher rom, you will have the 4 coloured screen with the menu. there is really no way to make a dry run on this.
as a first time upgrader it would be much easier for you to use a windows xp machine. it simply works because activesync provides all the necessary drivers, for syncing (of course), and also for flashing, while on vista/7 you have to replace the driver with a custom one depending on your version (x86 or x64). those drivers are not digitally signed, which, especially on x64 machines means more trouble to go through. in d-two's thread, you will find a how-to for vista/7 flashing if you find no other way. i think that is just an option for experienced windows and blueangel users, that are already running a cooked rom and want to change to another one. with a first time upgrade you have so much stuff to read through, so many more steps to actually prepare the device for the first time upgrade... xp would be your better choice.

alphadeeto said:
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
Click to expand...
Click to collapse
There is a set of instructions for Vista in the wiki (the ones you are referring to). They seem to work well afaik, but I agree with Chef... do it from a XP computer to avoid any issues.
Bootloader (the easiest way) is to hold power +record and then put the stylus in the hole. Doing the three of them at the same time might not get you anywhere. For the hard reset (WM5 and up), you can simply use the stylus and as soon as you get the stylus out, hold the two side buttons (camera/WMP and record) and you'll be able to see the options mentioned by Chef.
Good luck!

thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.

alphadeeto said:
thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.
Click to expand...
Click to collapse
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.

egzthunder1 said:
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.
Click to expand...
Click to collapse
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.

alphadeeto said:
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.
Click to expand...
Click to collapse
You have to use a newer driver which if I am not mistaken comes with WMDC 6.1