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.
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? )
I decided to reflash my wizard after it continually getting slower and slower after a year. I haven't done it in awhile. It is already unlocked. I flashed the 1.05 rom and it was working. I was going to go up in steps ending with the touch rom. I flashed the wrong rom evidently and now am downgraded to 1.01 on spl/ipl and os 2.26.10.2. The wizard won't activate Activesync and I can't get any communication. I tried rebooting the pc and the wizard multiple times. Still nothing. Need something quick to fix this. Everytime I tried to launch a rom flash I get an error 206.
digitalmayhem said:
I decided to reflash my wizard after it continually getting slower and slower after a year. I haven't done it in awhile. It is already unlocked. I flashed the 1.05 rom and it was working. I was going to go up in steps ending with the touch rom. I flashed the wrong rom evidently and now am downgraded to 1.01 on spl/ipl and os 2.26.10.2. The wizard won't activate Activesync and I can't get any communication. I tried rebooting the pc and the wizard multiple times. Still nothing. Need something quick to fix this. Everytime I tried to launch a rom flash I get an error 206.
Click to expand...
Click to collapse
If it was already CID unlocked,there was no need to downgrade again 1.05,once CID unlocked will remain unlocked forever,unless you intentionally don't flash back the locking code back on to it.
Now try to get into Bootloaders (multicolor screen) hook up the phone with pc via usb cable and check small usb appear at the bottom of the bootloaders,if it appears then download the official stock rom and flash to recover back to the default status,then download the WST 4.2.2 tool and run the 'CID Action' button to verify the CID lock/unlock status of the phone.if its still CID unlocked then upgrade to any wm6 rom of your choice,otherwise perform the unlocking method again.If the usb doesn't appear,then you have a connectivity problem,check the usb cable or the mini usb port of the phone is faulty.Assuming you are doing on winXP.
"and check small usb appear at the bottom of the bootloaders..."
I don't understand what your talking about when you say bootloader. The bootloader is the ROM installation program is it not. How do you check an icon in that? If you mean system trays on the PC or PDA, no USB icon shows. I got no radio or sync services working. The OS is corrupted and operates extremely slow. I can't get any kind of communication between the PDA and PC. Not even through windows explorer (running XP). It's not the cable, I just used it to downgrade to 1.05 and it was working fine. It wasn't until I tried to upgrade to back up, and selected the wrong ROM off my USB storage, that it flashed the wrong ROM and caused all this. Mostly because I hate trying to remember what the longs string of digits mean on each ROM. Especially after I haven't looked at all the files and haven't done a flash in a year.
So no communication. That's the issue.
So does anyone else have any info? As I stated, I can't get any communication between the MDA and the PC. So I don't know how I can flash a stable ROM.
I repeat again,Get the phone in Bootloaders mode (multicolor screen) by pressing and keep holding down the camera button and at the same time either 'Soft Reset' or 'Power On' the phone,but keep holding down the camera button,till phone boots up in Bootloaders mode(multicolor screen),hook up the phone with pc via usb cable and check if small usb appears "At the bottom of the Bootloaders Screen" and not in the system tray of the pc. If it appears then follow the advise I gave you in my above post,but if doesn't appear then you have a connectivity problem.
digitalmayhem said:
"and check small usb appear at the bottom of the bootloaders..."
I don't understand what your talking about when you say bootloader.
Click to expand...
Click to collapse
The Wiki as all the (basic) info to get you started.
It doesn't work
I can get into Bootloaders mode with usb at the bottom. BUT, I can't get any connection to ActiveSync, any of the ROM update utilities and no radio network connections. That was the specific thing I'm telling you. If the Desktop and the PDA won't talk to each other, what am I gonna do? It's not the cable either. The Wizard Tool will not pick it up either when I used it to try to get device info. If your going suggest any kind of ROM or software off the forum, please specify exact version and title so I don't have to go through 100+ pages doing a search to find a specific piece of software off a vague title such as "stock ROM". You may know what it means because your always on the forum. When someone hasn't been back here in awhile they aren't going to remember some arbitrary string of numbers and letters indicating a certain ROM that they haven't used for a year. Too many of you "regulars" get all pissy about things when someone asks a question. If someone keeps asking the same questions, it's because the forum is NOT laid out in an easily searchable fashion unless you have specific search criteria for things such as CUSTOM_RUU_Wizard_1050412_WWE_10111210_WWE instead of "stock ROM".
Have you read the Wiki?
http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies
Or other posts?
You'd know by now that in bootloader mode ActiveSync or any other tool (that uses ActiveSync) can't communicate with the phone but that it's possible to upgrade a ROM using the official upgrade utilities.
Have you tried making a search and getting hundreds of undesired and repeated posts which makes you lose days searching for a specific thing?
If you'd been here as long as many of us you'd also be tired of people asking same questions. I was once a fresh member and i would always 'waste' my time than others'.
Also the forum search feature has been enhanced by using Google's search engine instead of internal.
There is simply no way I can express my deep and sincere gratitude for the information available in this forum. Let me explain and I think you may understand why.
Several days ago my wife and I received a couple of HTC 8125's from Ebay. Being a tinkerer I wanted to see what I could do so I upgraded mine to Mobile 6 with Touch-Flo.
The wife was skeptical and waited to see how it worked out. Of course she eventually decided to go for the Bling and handed me hers to upgrade as well.
As soon as the upgrade started on hers the pda went bootscreen and locked up. Sooooo I'm sweating bullets and searching the forums as fast as I can go before she finds out. Then I find this thread and the last post... Don't need Activesync to update as long as the device pops up a little usb on the screen when you plug up... I flashed the 8125 upgrade and *Bang*! Back in business. Continued the upgrade and all is well. The wife is now walking around with her "Bling" and happy and I am off the hook!
Thanks for the GREAT FORUM!
Rowdyone said:
There is simply no way I can express my deep and sincere gratitude for the information available in this forum. Let me explain and I think you may understand why.
Several days ago my wife and I received a couple of HTC 8125's from Ebay. Being a tinkerer I wanted to see what I could do so I upgraded mine to Mobile 6 with Touch-Flo.
The wife was skeptical and waited to see how it worked out. Of course she eventually decided to go for the Bling and handed me hers to upgrade as well.
As soon as the upgrade started on hers the pda went bootscreen and locked up. Sooooo I'm sweating bullets and searching the forums as fast as I can go before she finds out. Then I find this thread and the last post... Don't need Activesync to update as long as the device pops up a little usb on the screen when you plug up... I flashed the 8125 upgrade and *Bang*! Back in business. Continued the upgrade and all is well. The wife is now walking around with her "Bling" and happy and I am off the hook!
Thanks for the GREAT FORUM!
Click to expand...
Click to collapse
Thankz !
We all highly appreciate it,glad you got it working .Thats what this Forum is sooo famous for "Help & Care"
Have just upgraded my Wizard to WM6 I encountered a couple of problems along the way but the most frustrating by far was having everything perfect with the notable exception of being unable to send or receive text messages. Every time I tried to send I got the pop up to say "Phone not ready wait 15 seconds then try again"
THE FACTS
Its a G4
Originally sold as UK O2 XDA Mini S
Paid to unlock
Flashed to UK T-Mobile WM5 and used for work
Flashed to UK Orange WM5 and used for pleasure
Upgraded to the gorgeous (well I like it) SNN Diamond Edition ROM http://forum.xda-developers.com/showthread.php?t=403096&highlight=SNN+Diamond
THE PROBLEMS
All RUU packages failed with a variety of error codes but the visible sign of failure was the display going blank and not firing up again. The solution was written in one of the upgrade guides "remove the SD card" (so glad I didn't post on that one. DOH!!) Read this it really helps http://wiki.xda-developers.com/index.php?pagename=Wizard Windows Mobile 6 for newbies
The SD Card wasn't being recognised after upgrade. I couldn't be sure how I fixed that, it could have been one or more of the following:
Repeat ROM Upgrade
Hard Reset
Soft reset (5 times as it seems to speed everything up)
Switch off phone (hold down power button and say "Yes" when asked)
Insert SD
Power Up
Synch with ActiveSync 4.5 & Win XP (connection only so untick all the boxes)
Synch with Windows Mobile Device Centre and Vista
Remember to check the memory status (Start/Settings/System/Memory)
Well whadda you know, the SD card is recognised!
OK it's not scientific I'll grant you but if it helps someone then it wasn't wasted two finger typing time.
No text messages, after much searching and reading inconclusive threads I went for a Radio ROM Upgrade. I flashed 2.71.11 but have a look at the Wiki and take your pick from the 3 listed. Bingo!! http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
CONCLUSION
Read everything before you begin, there is loads of information here, some of it conflicting which leads me on to ...
There's more than one way to skin a cat, maybe one guide might not work for your phone in your country with your Telco, just try another until you find a method that works for you. Absolutley DO NOT ignore the dire warnings though, Wizards are useful as paperweights but much more useful as PDA phones.
Don't expect much help from your service provider, Orange were strangely unhelpful when they found out I am using a phone they never sold in the UK with a cooked ROM and one of their SIMs that was sold with a Nokia Slide. Honestly, what do I pay these guys for!!
Don't despair, throw the darn thing through a window or, when confronted by a black screen, reach for the Big Hammer. Take out the battery, wait, put it back together and power up.
Do give thanks, to the guys and gals who give away their hard work in the form of cooked ROMS, who spend hours writing user guides and making screenshots, who build mini apps to simplify the process and who answer the same question a zillion times on the Forum.
Thanks Guys!!
Right, having got the Wizard running like a dream I have here in front of me an SPV C500 Typhoon and an SPV M600 Prophet. Oh and is that a Kaiser that work gave me, locked to T-Mobile, dare I?
I've got a Wing from T-Mobile and I was checkin' on HTC's site... I dont' see any RUU files for that particular phone... T-Mobiles site had an RUU for me but it requires an activesync connection,
Now I've gone and proper bricked the (insert bad word here) so it won't even make an activesync connection anymore,
I was tryin' to put a lite version of one of the touch IT releases on there, all i've got now is a solid white screen. Phone will make noise when it's slid open; and the screen has an auto timer dim, but no display....
The RUU I got off t-mobiles site runs off an exe (do they usually?) Problem with it is that it requires an activesync connection which the phone can't make at the momment because of it's current state...
Is there an alternative to activesync that would help me out in this case? I know when I effed up a Linksys router I was able to tftp the firmware, not sure if there is anything like that I can do in this case. It only happened this morning though and the phones not active anyway so I'm going to continue looking (It's awaiting activation but it's now the weekend so I've got at least 2 days to work on it anyway.)
You may notice; I'm entirely new to this however I did look into it enough to ensure that I had an RUU to begin with before I tried any of this... Also, I have a second wing that's still set the way it was @ stock... Would that help in any sense?
Another question I had is what exactly is a lite version; from my understanding it was WM6 w/o the bloat... I'm begining to wonder if it's an OS with no tools not even a phone tool (I wouldn't think so but maybe I misunderstood.)
Thanks for any and all help or even suggestions to resolving my first brick
Edit: I'm begining to think my option is to try to submit it under warranty but I'm sure they can look at whats currently on the phone and I've got a hunch that right there will get me an outta warranty fee...
Edit2: I may have wound up able to answer my own question, (I'm at work atm and don't have access to test anything till 9pm tonight so I thought I'd post incase I was overlooking something, or incase I was able to find something to help others.)
I read;
JDawgZX11D said:
"If you had the same problems as I started with, and that it will not boot past the T Mobile screen, here is what you do.
RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship
Download the orignial T Mobile rom, it is on this website about 300 times (I guess I was not the only one). I am sure you have winrar, open up this file in winrar. There are 8 files inside of it. The one you are most concerned with is \RUU_signed.nbh this is the original operating system. Get yourself at a minimum a 128mb micro sd card. Format it to FAT32 and copy the before .nbh file to the root directory. Rename the file to Heraimg.nbh That way if you start with a brick, you can end up with a shining penny! So when it is bricked, you do a hard reset. Hold the camera button and the voice record button, then push the stylus in the reset button. as long as you pushed in the micro sd card in the slot, it will reload. When it asks you to push this button it, they mean the volume down button. After about 15 minutes, your brick is no longer bricked. It will do it's thing and then soft reset on its own. You are back to factory default, YEA!!! Remove the Micro SD card out at this point."
Click to expand...
Click to collapse
I will try this later, thank you.
Fixed it
What I didn't realize is that you can still install an RUU via USB w/o activesync through the phones bootloader and the EXE from the comp.
THanks for the help anyway