Qtek 9090 wont upgrade - MDA III, XDA III, PDA2k, 9090 General

Hi i am new on this forum ,i have a qtek 9090 unlocked bought on ebay
it runs windows 2003 and when i try to upgrade to wm6 ,the process starts and and it goes into USB V2.08 and pc makes a usb has been removed sound and the installer gives me a error msg
ERROR 120:COUNTRY ID: ERROR
and when i do a soft reset it comes up with a new installtion of (wm2003 which i hate)
this is getting to my head as i need to upgrade my PDA
can anyone help me
send me some links with the correct software and stuff please

you need to put the device in bootloader mode before connecting it to the pc by pressing reset+power+record and use the MAupgradeut_noID instead of the BAupgradeut to upgrade your device. if you don't have the MAupgrade tool present, you can download it from this post of mine:
http://forum.xda-developers.com/showpost.php?p=3768875&postcount=3
by doing these 2 points, you can avoid all error 101, 110 and 120

windows 6 for qtek 9090
does anyone have links to the new wm6 for qtek 9090

try this: http://forum.xda-developers.com/showthread.php?t=482997

No service
upgrade done and the phone worked for about 3 days now is says no service and wont pick a network

first make sure you didn't soft-reset the device the wrong way, meaning restarting the device by releasing the battery lock, because restarting it like that generally starts the device w/o radio, meaning no phone function. to avoid that, simply soft reset again by pressing the actual hardware reset pin.
in second thought, you might wanna post the values shown in the boot screen, maybe another radio rom might do the trick.
if neither of that worked, maybe you should try another sim card or a different location for testing network coverage just to figure out, if it might have something to do with a network failure.
if still however nothing worked, which i wouldn't hope, it still could be a bug with the particular rom and you might try another rom.
and at last, if that didn't help, you might have a broken radio receiver and as a harware fault would require you to repair or replace the device, but that is rather unlikely, so you are probably lucky and can fix it yourself.
please post back if and when you figured out, what the problem was, so we can all profit and learn off it.
with best regards,
Chef_Tony

Related

Qtek 2020 frozen after rom upgrade

I have a qtek 2020 with v1.52 rom. I downloaded the new Italian rom (1.72.04ITA) from www.windowsmobile.it and I tried to upgrade it.
After erasing internal rom the upgrade process stopped with a fault message:
Error 112: ce rom update error
Now the display is dark. I can read “serial” or “USB” on it.
What’s happened?
I tried again 10 times but nothing.
It seems that connection between pc and qtek wasn’t correctly established. This because the little activesync icon (bottom right) is now always gray, never green.
Help me please!
Hm...
When OS is not started, PC ActiveSync cannot connect to your device, i think this is indeed...
But open Windows Task Manager and kill process wcescomm.exe (this is that tray icon of ActiveSync) and try to run update again...
HTH
> open Windows Task Manager and kill process
> wcescomm.exe and try to run update again
I tried but nothing.
I also tried to execute XDAtools but I recieved the following message:
Cannot execute the remote communication program.
Please make sure that USB/Serial cable is properly connected.
What can I do?
Does your device changes the screen from "Serial... blablabla..." to "USB... blablabla..." when you put it into cradle?
If so, what update writes when you try to run it (after putting device into cradle and killing activesync)?
> Does your device changes the screen from
> "Serial... blablabla..." to "USB... blablabla..."
> when you put it into cradle?
Exactly
> If so, what update writes when you try to run it
> (after putting device into cradle and killing ActiveSync)?
I can read following messages:
* Message 1 *
Cheking info on your pocket pc. Please don’t disconnect.
-----------------------------
* Message 2 *
Your pocket pc software is about to be update from:
Device CE image version: (now this is blank, the first time I attempted the upgrade was 1.52.00ITA)
Device CE extended image version: (now is blank, first time was 1.52.93)
Device Radio image version: (now is blank, first time was 1.06.1)
To
CE image version : 1.72.04
Extended image version: 1.72.128
Radio image version: 1.14.00
-----------------------------
* Message 3 *
The current software is being erased
Stage1: erasing ROM. Please wait
(But bar will stay at 0%)
-----------------------------
* Message 4 *
(After 2 minutes)
Error 112: ce rom update error
Any ideas?
Stupid question, but do you have pluged charger to cradle? I assume that so...
On other hand, I searched through this forum and found this links:
http://forum.xda-developers.com/viewtopic.php?t=10333
http://forum.xda-developers.com/viewtopic.php?t=8835
HTH
I tried, but nothing.
Anyway thank you for your reply
Hm... I was solving this issue yesterday and try to download update again (some corruption may come when update is downloaded) and flash it again...
I did it. I downloaded and tried also other international rom version, but nothing to do.
I’m going to call the costumer service ...
This is strange... :evil:
Unhappy, we are so far from each other... I want to help you...
Do you by chance have your cradle plugged into a USB hub? There have been many reports of problems in this configuration.
If so, try it with the QTek cradle plugged directly into the computer.
If not, a call to the service center may well be in order.
> we are so far from each other...
> I want to help you
You are very kind. But I live in Rome ...
> have your cradle plugged into a USB hub?
No, it is plugged directly into pc
Service center seems to be the only chance
:roll:
Me too..
Hi!
Just experienced the exact same thing :-(
I hate it!
I has done it one time before, and then I had to send it in to be repared. I dont know what they do, but I got it back working again.
But now when I saw the new official 1.72 rom, I wanted to give it another try.... but... now its dead again, doing the exact same thing as yours...
any news?
Regards
Peter.
You are very unlucky.
Today I’m going to call service center.
I hope they’ll solve problems quickly.
I’ll tell you what’s goin’ on.
Working!
hey!
I actually got it back to life!!
I took a different PC, connected my qtek and just started the upgraded again, even though the activesync wasnt connected. It started to upgrade, and my Qtek is now back to normal with 1.72!
Try if you can, with af different PC...
Today my service center replyied to my email regarding this, sayning that they couldnt help my, and there was no guarantee since i tryied to upgrade my self :-(
So, good thing i did it my self
I was thinking about it because I had some problems with usb ports on my pc. So this morning I tried the upgrade from another pc and ... YEEEAH.
I make it !!!
Now qtek 2020 works again !!!
Yeah!
Congratulations!
Good thing we have this forum
Experienced any problems with the upgrade yet?
yes.
still problems with bluetooth connection: no signal available from gps reciever. :shock:
problem solved by downloading bluetooth tools from:
http://bluetooth.i-networx.de/index_e.html :idea:
now it works fine.
bye
hi,
i just received my o2 xda 2, i decided to upgrade to 1.60 when i saw 1.72 it's out:
1st quest:
where could i find 1.72?
Does the qtek one works with my xda?
thnx
ciao mario!!come ti va col gps BT e tomtom3?
Hi!
I would definetly not try to do any upgrade as long as the upgrade isnt directly comming from your service center. All the XDA upgrades I tryied on my Qtek didnt work at all...!
Be carefull!

ROM Upgrade of Imate-Jam (O2 XDA2 Mini) Failure, HELP!!!

Dear all,
I just got my imate jam (sold in Telstra shop in Australia) on last Friday, yesterday, I tried to upgrade the ROM as followed the instructions from http://www.clubimate.com/.
As imate jam has only one USB port which is connected to PC (Microsoft Active Sync 3.8) and there is no cradle, only 30s after I tried to update the ROM, then the USB is disconnected suddenly, and after that my Imate Jam has a black screen (it's like the backlight has been set to the lowest setting). I can see the word Serial 1.0, and if I try to connect to the USB again, it will display USB 1.0. Nothing more than that. Soft or Hard Reset doesn't change anything
Anyone knows how to bring it back to life, otherwise, I will return to the Shop since I only bought it for 3 days, hopefully, they will give me a new unit to replace this "dead" Jam :evil:
When I did the upgrade, the battery is at 100%, so there is enough power, but I can't understand why.
The ROM & Instruction are download from the page
http://www.clubimate.com/index.asp?PageAction=JAM
I've downloaded the Generic version of the ROM with the name ma_cdlsku1_wwe_10300_143_10100_ship.exe (28 MB)
with the following information :
The details of the current ROM image (found under Start -> Settings -> Device Info):
Rom version 1.03.00 WWE
Radio version 1.01.00
ExtROM version 1.03.143 WWE (Generic)
(PS. Sorry you may not be able to see that particular page and instruction if you are not a member for that site)
Any suggestions are highly appreciated.
Cheers
Wallace
PS. One more question, how likely is it for the Imate Jam / O2 XDA2 Mini to upgrade to Windows 2005 Mobile once it is available??
You are luckily in the Bootloader mode. I crashed during my PDA2K upgrade and found settings to get it into Bootloader mode and the upgrade was able to rerun and put the ROMs back in place. Try disconnecting, rebooting your PC (start clean), then, with the Jam in Bootloader mode still, relaunch the upgrade utility. Let me know if that works.
Also, do a search here on how to get the Bootloader to launch on your JAM if you need to pull your battery and power it back up again to it.
Oops ...
I've returned my imate Jam to the shop, and for some reason, they can do a hard reset on the phone (which I tried to press the power button and the reset buttons many times before), and so the screen comes up ...
And of course I told them I lost confidence in the phone blah blah ... and I want to replace a new phone ... So now they have sent my phone back to Telstra and need the Telecom's approval for a replacement unit ...
Once they approve it (it takes a week they said), I will ask for an O2 XDAII Mini instead. As in Australia, the imate phone has been customized by Telstra so it will by default shows the ugly logo of Telstra, whereas O2 will still display O2, and it has the options to choose which provider under "programs" ...
In the first 2 days, I need to soft reset the imate jam quite a number of times, I set the password so after the phone is unused, it will be locked ... but sometimes when I tried to unlock it, I couldn't ... I mean the number pad (virtually in the screen) has no reaction when I pressed it ... so I was forced to reset the imate jam a number of times, I suspect it might be problems from Telstra's customisation to the phone, but anything can happen so I just guess ...
Hope to get a new replacement phone soon ... as I only got the phone for 3 days ...

Help / Advice Needed Regarding o2 Rom Upgrade for XDA IIi

Hi,
I am in the process of upgrading my rom using the rom upgrade from the o2 www site.
Its been stuck on the
'checking the information on your device....Please wait.....Please do not disconnect your device from the PC or power supply until the upgrade is complete'
window for some time now. I dont know if its hung / crashed or in the middle of upgrading.
I dont want to chance it by removing the unit from the sync cradle but at the same time i dont wanna just leave it there for hours if its not doing anything.
Can anyone help ?
Steve
ps - the window I am speaking about came after the big window stating what your current rom / radio stack was and what they would be updated to giving you the option to click 'update' or 'cancel' I chose 'update' and got the message which I described earlier
Try this on a different PC...I'm assuming the phone itself is still functioning.
I had this a while back with the XDA2 and found that by attempting the upgrade on a laptop I had, it worked great without the hang.
I would then remove ASync completely (including registry items) and then reinstall it.
Cheers
Ant
I had this happen, I just shut down and restarted the installer program

Bootloader dead / Recovered

Hi,
I made a mistake with flashing QTEK S200 with wrong file.
Bootloader was modified. Device can not start at all.
It can not even go to bootloader screen (red-green-blue).
As consequence, no USB connection can be established.
What is the solution? I guess utilities can not be used, because they assume connection to USB, but there is no connection.
Not big deal, because it was not working well anyways, but would be interesting to know a solution in this case. Many ppl. would be happy to know how to manage this situation, I guess.
later.
Not very good news, service center said they don't know how to fix it, but kept the device to make few things with it.
Clearly, bootloader was overwritten.
Will see. Somehow they manage to identify type of rom is installed from i-mate.
So, think before you make any flashing
re: another service said they will do whatever needed, up to replacing chip with flash. I am not ready to go that far yet.
feel like i am missing something
It appears to be a real problem with flash.
No connection to computer with USB.
With power supply connected blue-green-?? screen, but I cannot connect to PC of course.
With USB cable connected blue-green-?? screen does not come up.
I figured out that pins 4 and 5 are shorten when power supply is connected. I did this with USB connection to PC, but still not connected.
For sure, USB is not functioning on device.
Will get new device, but very interested on how to repair this one. I disassembled it completely. There is no way to replace the flash chip at home, you need specific equipment and chip, of course.
What I need is surcuit diagram for S200 or similar, particularly part of diagram related to flash, radio module is not needed. Is there any possibility to get it? If I have it, I think can reprogram chip.
Thanks.
Hm. It looks like extreemly difficult to get pins layout on motherboard.
JTAG is the only solution left to access chips direct. But we need to know where JTAG pins on motherboard.
Recovered S200.
Finally very good news!
Prophet S200 was succesfully recovered with help of Arc.
He managed to discover JTAG pins, afterwards re-flashed SPL and ROM.
REALLY GOOD JOB!
Want to say special THANKS to Arc!!!
Device go live again.
Until next experiment....
But procedure to recover is in place.
Regards,
fdp24
i have a dead one too
Hi there,
I have a dead one too can you tell me how to fix it please?
dead, as in my ppc k-jam is dead
basically it hangup and i soft restarted, tried hard reset. it didnt help either. i tried restoring to factory default same thing it hangup. now it doesnt shows any signs of life . i lost my life, my buddy.
My Orange SPV M2000 will not start anymore after update. I only see Serial (on top)............ V2.07 (underneath)
I tried to update my ORANGE SPV M2000 to Tmobile's newest rom by extracting the exe. file and using maUpdateut. It started well and all of a sudden gave error "country code................"
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
fdp24 said:
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
Click to expand...
Click to collapse
I know how to open device and solder some wires to testpoints. Do you have any information where the pins are located and what software and what JTAG adapter you used? I really need to get my phone working again. It was quite expensive to purchase and to ship it to my country. Please don't destroy my hope.
hello friends,
my cousin recently buy O2 XDa ( wallaby ) for cheap one, i check on device it seems cann't boot to windows but if i hard reset and came up red, green, blue and if i press ok it came up with test all thing i confuse all the test is OK, can you all tell me how to repair the phone and waht is the problem?
thank you
dead device hope on the horizon
note my device and troubles is on the xda2
hi - i have had exactly the same issue - i have managed to reload the rom i was trying to swop and here is what i did .... it took ages and lots of patience and it is not an exact work of science but if you try my method 2 or three times it actually comes back to life ... honest !!
down load an xda2i ( yes xda2i )rom extract it using winrar or zip on your pc place dead xda2 into cradle regardless of whats on screen run himupgradenoid - the rom will run and start to load onto your device it will fail once it has failed remove xda but do nt reset - take copy of original rom which was on the device prior to your failed upgrade and extract as above. replace xda into cradle might be detected or not dont worry - run the himupgradeut from your previous working rom and wait it takes ages to connect but eventually heypresto ... you will have a working device. i know cos i done it !!! - i have not resolved all my problems yet - i still want to load latest 02 rom but even after entering correct device data into nbfs using batch file method the device crashes saying incorrect counry id. - i accidently created my problems by accidently running the wrong upgrade rom and i guess it changed somthing on my device " country code" however when i use method above to get original rom inplace and working when i extract device data into windows folder on device i still see the wwe ( world wide english) so i am still in a pickle - can anyone help me .
hello
i'm working on the project of flashing the bootloader into a totally erased and dead phone. can you send us the test points from the prophet please? and if you know their location on a WIZARD. thank you..
Somebody here Please tell what soft to use with JTAG to recover da bootloader!!!!!!!!!!!!!
get the JTAG pins for me, I will send you soft.
Wizard and Charmer pins are both needed.
hi, i've succesfully wrecked my Blueangel PH20B by flashing a modded wm6-universal-rom... i've got all the hw & sw to resurrect the phone but the jtag pins on the BA-PCB...
can someone give me a hint where i may find them? (i'm not wanting to bake the pcb as i know i'll wreck it comletley)
thanks in advance,
mario
Same problem here
Hi,
I believe I'm having the same problem
Please help me
Thax a million
so can you help me i need to write the wizard(g4) bootloader or thell me how can i do this
T-Mobile USA SDA II
Me also, i'm i need of re-writing boot-loader of T-Mobile USA SDA II
well, ok I understand that you can get the Jflash_mm working with PXA systems, you can write the definition for yourself, as for the CPU.
but I have serious doubts that inspire me to suggest you will have tiny chance to actually program a DiskOnChip Millennium series (or familiar) chip used in many platforms (actually I believe most HTC devices).
after all this means that if you are not working for (or in affiliation or partnership with) SanDisk, you are not in position to program bootloader to (not limited to) UNIVERSAL, WIZARD, PROPHET, and CHARMER (and if I remember well, BLUEANGEL and HIMALAYA) devices over JTAG.
any news............

Money ahead: Need serious help with my hx2000 / hx2490

Hi there!
I am in serious need of help with my iPAQ hx2490. Yesterday, I tried to do the
official HP ROM Update. Everything went well, up to about a point when the RUU told me that there is a connection problem with my device.
The update went to just about half way through, and I didn't touch anything, I just left the device in it's cradle.
Anyway, my problem now is, that the device won't start the OS, I can't get past the HP welcome screen. The loading bar fires up, and completes it's way to the right, but after that: NOTHING!
I have tried soft, hard and clean reset, without any help. When I do a clean reset, the display shows "Formattin PS", and the loading bar reaches the right. But after that: NOTHING again!
I tried flashing everything again, from WM 2005 first and second edition, even WM 2003. The result is always the same.
I can get it into Pre-Bootloader, normal E-Bootloader. I do get a "USB Connected" message, and I do get the following "USB" message on the screen.
Now here's the odd thing (and I do hope that all you experts are dying to solve this mystery!): when I do the update again, at either 84,1% or sometimes 85,1%, the iPAQ shuts down, and starts again. But this doesn't stop the RUU from continuing!!
I've tried everything I can, I read all the infos in the forums concerning iPAQ problems, but they're mostly concerning entering bootloader, which is NOT my problem.
Money ahead: I'll donate 10€ to the person who is able to solve this riddle!!
The money can go to either this website or the person's own PayPal account.
oh I forgot: I did try ChrisMRulz bootloader method, but I wouldn't work for me. I managed as far as the MTTY program firing up, and I do get a WCEUSB prompt, but can't enter any commands, and the nbf file doesn't get uploaded!
PROBLEM SOLVED!! Sorry.....
Can you tell us how?
Maybe it will be helpful for others that have similar problems in future.
Sure, I can do that:
I managed to flash the official International English ROM Update to my german hx2490 iPAQ. I just used the trick that you have to start the correct HPRUU.exe for your country-specific device, but just before you hit the last "Update" button, you change the .nbf file with the one you want to flash.
But you have to rename it to according filename the HPRUU.exe originally loaded,
if you don't rename it, the update utility will crash.
By doing so, I was able to flash the above mentioned ROM to my device, and after that I just flashed my country-specific ROM.
Now I'm back and running WM5.
If further explanation is needed, I'll gladly help out someone with the same problem.

Categories

Resources