Related
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!
Dear Fellow Forum Members,
Followed instructions as per Xda_II_Upgrade.pdf, during installation got to a section where I got a message saying that the current rom is being erased a task bar was displayed which increase's in percentage as the job goes through. However the job was still at 0% completion when an error message was displayed saying the job had failed and the device needed to be undocked and a soft reset performed and then re-docked and to restart the process again. After performing the undocking of the device and software reset I get a message on the screen serial V1.0.1 when connected to the cradle the message changes to USB 1.01 and I cannot do anything else the unit does not boot into pocketpc, as you can imagine this is very frustrating as I depend on my xda2 to receive and make phone calls I would be very grateful any members know of any way to get around this problem. I must say I am a bit concerned a try and tested xda2 update has led to this problem.
Just run the update .exe file again with the XDA docked and it should just install the update again. It happened to my mate on Saturday with his XDA II and he just ran the program again.
Dave,
done as you said and all went thru fine you are a star thanks mate.
No problems it's good as a newbie to be able to actually help people.
upgrade xda2 rom ver 172187 dead os--connection error
i was trying to upgrde the rom from o2 website when error occured at stage 19% completed asking me to reset the xda2 . when i am trying to reset the xda 2 it does not boot it just shows the o2 screen with red letters of the version and does not even charge. my laptop cannot connect to xda2 and as a result i am unable to upgrade when i tried to run the 172187 .exe again it gives error 101: connection error
please help me out of this? thanks
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
On another note - I had purchased a working 2110 with a good mobo to replace this one if the flash is not repairable - is that a difficult procedure? Unfortunately, the 2110 I purchased was not working, but this may still be in the books at a later time, so some info would help.
Thanks!
Rustmonkey said:
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
Click to expand...
Click to collapse
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
reggaepoo said:
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
Click to expand...
Click to collapse
You, my good sir, are a genius - worked great! Fixed BOTH 2110s
tangwd898 said:
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
Click to expand...
Click to collapse
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Rustmonkey said:
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Click to expand...
Click to collapse
really amazing !!!!!!
I just saved my hx2110 as per your step by step instruction now.
Thank you very much.
ok, well, I thought they were fixed... now one of them freezes at the bootup screen, even when I do a clean reset... I've tried reflashing multiple times to no avail... any ideas whats going on?
ok, got everything working - reflashed the non-working one back to an original 2003 rom - which made if freeze at boot - then upgraded it via pre-bl to 1.00.00.L - from here, it wouldn't do anything after filling the bar at the boot screen, but it didn't CRASH (as in lights out) - so I ran the pre-bl again and ran the flash program for 1.00.00.L again WITHOUT swapping between the 2495 and the 2110 - just put the 2110 in pre-bl and away we went - flashed, formatted, and booted - then proceed to upgrade to WM6 via 1.00.00.H --> 1.02.00.H --> WM6 - works GREAT!!!
Thanks for the help everyone!
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Hello,
I have run into some problems with a bricked hx2110.
I was flashing the IPAQ to a new ROM WM5 (Battery was full and I read all the instructions 10 times prior to flashing). While flashing, the progress bar went to 100% then faded out immediately and it wouldn't reset (clean reset). I put the battery in my friends hx3000 series and the battery I used was completely dead. It did flash to 100% though, but not matter how many times I try 1 + 3 + reset, it doesn't reboot. If I can figure out how to get it to boot, that would be great, but I can't get anything to come up with any key combinations.
To this point all I can do is get into Pre-BL mode 1.00.04. I have tried the below scenarios on two machines, both running windows XP SP2 (USB 2.0) with the firewall and virus software disabled.
http://forum.xda-developers.com/showthread.php?t=330382&page=4
1) I have tried the above links directions and used the the Universal Bootloader (Bootloader.exe). It gets to the point where it says "The PDA should be updating now" or something similar but nothing happens. I don't get any errors regarding communications (it sees the device when I hold the "Calendar" button until it says USB; windows then recognizes the device as "HP USB ..." so I know it's communicating).
2) I tried to use the Bootloader_GUI.exe beta so that I can watch the progress indicator but it just sits at 0%. There are no error messages so it is communicating but for some reason, the device won't let it flash (and the flash utility thinks it's doing something).
3) I tried the original ROM flash from HP (SP29856.EXE) and it recognizes the device, but because the current ROM on the PDA is hosed, when it does it's "verifying" process, it comes up with "?" marks as the model number and when it goes to flash it starts at .1% then says "FINISHED" immediately. The ROM utility thinks it flashed it correctly but it didn't flash anything. I'm guessing that the verification of the PDA failed and forced the utility to not flash.
Does anyone have ANY ideas of what to try? I wish I had another HX2000 series PDA and try the "swap" thing prior to hitting the update button but I don't. All I have to work off of it my sad bricked PDA and a full battery (friend keeps charging it). His PDA is an HX3000 series.
Any ideas would be appreciated,
Thanks!
Are you using a the HP flash program that is specified for your device?
2nd - you might be able to use your buddies device in a swap as well - not sure but its worth a shot - use HPs upgrade program, let it verify, then swap your device onto the same cable - overwrite the firmware in the update program for HIS device with firmware compatible with yours and then hit update - let us know if this works...
I am using the "official" HP flash program specific for the HX2110 (from their website - SP29856), bootloader.exe, and bootloader_gui.exe
I wanted to try my friends, but he won't let me touch his because I bricked mine lol (I swore nothing would happen to his but he still won't let me try it).
Anyway, I just copied over the ROM image (from HP) and stripped out the header (now showing 64 bytes before the ECEC). The ROM is for WM2003. I copied the ROM in binary using psdwrite.exe to an 256 MB SD card. As soon as I can get the battery back, I'm going to try to flash it from the SD card. If this fails, I am going to try to play around with MTTY / USB and manually call the ROM flash and see what happens.
Having another HX2000 series would make this easy (maybe a little TO easy )!
Bootloader never worked for me - but if you can get it to manually call the flash, more power to you good luck!
Well it was worth a shot. After spending the better part of the day with the PDA, I have made no more progress (can't get Pre-Bl to update). The only option I have now is to find someone with another hx2000 series that is willing to resurrect it from the dead for me (PM me if you can help - I will pay two way fare). Until that happens, it's going in the "broken" drawer with all my old comp stuff .
Thanks to all the tips and tricks that is posted on these forums and brighthand! There is a wealth of information on this topic and without them, I would have gotten nowhere in trying to repair the device (granted, I wouldn't have been intrigued to upgrade the ROM in the first place and would still have a working PDA, but that's besides the point ).
Best of luck to you all.
1).download original ROM from HP (sp29799) -extract files
2) download http://upload.dvhk.pl/content.php?id=88892 - replace files
3) flesh device.
bay!
link crash http://upload.dvhk.pl/content.php?id=88892 - replace files
Please it can raise it again, thanks
Absolut3k said:
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Click to expand...
Click to collapse
Same here.. is there another way to un-brick hx2110 on this problem ? thx ...
Solved, my hx2100 returns to be in this world
thank you i saved my ipaq
I've searched but can't find the answer to this one - sorry if I've missed it somewhere. I have an unmolested T-Mobile UK MDA Vario 2 and I'm trying to install the official TM UK WM6 upgrade ROM.
On my desktop PC (which is properly paired to the phone through ActiveSync to sync with Outlook etc) running the exe results in a grey box with red text saying "Checking files on your PC" forever unless I unplug the phone. Then it will eventually launch the wizard. If I plug the phone in again and wait until it's synced and "Connected", the wizard will go all the way through to checking the existing version and starting the upgrade. However, when the upgrade starts the progress bar stays at 0% and the phone turns off!! Eventually it times out with a 260 error, and no changes have been made to the phone. The PC is running XP, but the only fixes I've seen for the 260 error are if you're running Vista?
I've also tried on my XP laptop - this isn't paired, so the connection through Activesync is just as Guest. The update still does the strange thing with the "Checking files on your PC" box if the phone's plugged in, but unlike the desktop PC the RUU won't talk to the phone at all - connection error before it can even verify the existing ROM version.
Can anyone help? I've been waiting for months to get WM6!
Cheers,
Tim
Phone just turns off?
OK, so now I've done a hard reset on the phone, paired it up to my XP laptop and told it not to sync anything. Now I get to the same stage as I do on the desktop - i.e. the phone switches itself off when the upgrade begins (at 0%), then the RUU times out with an error 260!
One odd thing I noticed is that if I plug the phone in with "Advanced network functionality" enabled (which it is by default) the PC tries to connect it as a new 10mb network card!? However, the RUU does the same thing whether this is enabled or not.
Getting desparate for help now - I've tried 2 different machines and even cleared the phone completely, what more can I do?
Cheers,
Tim
Try flashing from an sdcard. There are quite a post on it here, if you do a quick search you should be able to find the information and hopefully get your device upgraded.
It might be worth installig spl V7 from here before hand just in case anything goes wrong.
http://forum.xda-developers.com/showthread.php?t=296722
Working!
Thanks for the reply. Finally got it flashed using the instructions from here:
http://forums.cingular.com/cng/boar...thread.id=42389&view=by_date_ascending&page=1
Basically, you have to:
- Connect using Activesync and let it finish syncing.
- Start RUU.
- Activesync will close - ignore it and carry on.
- Eventually the phone will go into debug mode.
- Continue through the wizard - it won't be able to identify the existing rom version but this seems to be normal.
- Let it finish!
I was fiddling when Activesync closed - strangely, by disconnecting, restarting AS and reconnecting the wizard carried on and even identified the existing rom properly! It seems that it needs AS to connect to the phone initially, then it closes AS but keeps the USB connection open for the update.
Hope that helps anyone else with the same problem.
Cheers,
Tim
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.