Hi guys,
I was playing with my ipaq and like some others in this forum I've got a DVT version of the hardware.
I noticed that some of the keys don't work after playing with some ROMs. This is proving to be a bit difficult because some are the loader keys.
mute and camera don't work. There are a few others on the face like Windows, 4, 6 and some others.
I think that this occurred when I flashed a 914 ROM by mistake and then the unit was fairly trashed, would not work with SD loader anymore and screen was wacky. I did find some posts on how to recover that using DNR and I got it working again with both original OS and WM 6.5. I also managed to get the FW updated from 0.78 to 0.89 (I think that was the version). I used the HP SP to update the device and used a hacked DLL to get past the update not working on my DVT hardware.
I hope some of you experienced folks out there will have some further suggestions on how I can get my keys to work again. I thought doing the full flash with the HP SP40097 would have worked but it did not. All the flashes finished without an error however.
I guess my hope is that somebody out there has a complete image of the 256MB ROM that I could use to re-image mine with. Who knows if that is possible.
thanks
Related
when installing wm 2005 im getting the error 103 rom image not found and thats it it wont install please help
Hi justin, I'm getting the same error too. I wonder if you found a fix yet or not? I seem to be stuck in the bootloader mode and nothing will take me out of it. I have bootloader vs 1.06.
What happened was I was upgrading to wm 2005 and kept getting the country code error 120 so I went thru the steps that I found here and I put 2 files on my qtek2020 HimaClearJumpCode and HimaGetDeviceData then by mistake I executed the wrong file and it took me to the bootloader mode and it will not come out now. I never intended to ever execute the file but I have a nervous tick and my stylus hit it and double tapped it and viola I'm stuck in the bootloader hell loop.
I'm not really a novice with my qtek2020 I have upgraded and downgraded and manipulated it in many many ways but this one has me stumped. I have searched these threads until I'm blue in the face. I only found on thread that even mentions my problem but it does not give any fixes.
So if anyone here can help me fix this I would appreciate it. I hope I don't have a paper weight
Hello Guys,
Disaster. I tried updating to the new ROM from the O2 website and it fails with : "ERROR114....
Tried the version from this great forum and guess what? same error.....
HELP !!!!!!!!!!!!!!!!! :shock: :shock: :shock:
My XDAIIi was brill. Now its dead...
Try putting the 2i into bootloader mode by pressing the power button, action pad down and the reset button at the same time. The screen will say serial with a version number at the bottom. When you connect it to your computer this should change to USB. Then try running the update again.
If you are using the modified version I posted on this site then the install will fail. Just run the program MAUpgradeUT_noid.exe a second time without touching the 2i at all.
Hope all goes well.
Hi Pug,
Unfortunaely that has not work. see screen shots attached.
can anyone tell me what this damn error is pls...............
oh by the way the iMate PDA2 rom fails as well with the same error. !!
If both your devices are failing to upgrade the problem must lie with your computer somewhere.
Are you using firewalls like zonealarm which may be interfering with the update process. If so try disabling them.
I assume you are connecting using USB and not serial. Do so if for no other reason than it's faster.
Are you using Activesync 4? More stable for upgrading than 3.8 but lacks sync over LAN feature - not a great deal if you've never used it. You can find this on the wiki link top left of this page.
Try downloading the packages again. I've posted the radio rom here as thats the one you seem to be having immediate problems with. Download it and overwrite the one on my modified rom.
I'll post more if I think of anything as I'm suffering a hangover right now and can't think too much cos it hurts. :?
thnx pug,
really appreciate your help. yes iam running firewall (norton). I will try your modified radio and advise. fingers crossed. and thnx once again.
using activesynch 4 as well from this forum
Hi pug,
Sorry the radio did not work. renamed the radio and ran update and the update works for nk.nbf and ms.nbf files. without radio the phone does not work but proved that there is no problem with my pc or usb cradle etc. the problem is the radio.
my IMEI is 354962000270150.
the radio file from the Launch rom from O2 does not work, so either my IIi has a damaged component or something else that I am not aware of.
copied your radio file to the other iMate upgrade and it still fails with the same error 114 !!
Any other ideas or suggestions pls, its really depressing to loose the XDAIIi permanently.
Oh I forgot to mention that the IIi is also unlocked and the ExtROm is unlocked as well. Will this make a diffeence?
The fact that the 2i is unlocked won't make any difference. The EXTRom on the 2i can't be unlocked and always results in the storage being locked which will stop the phone being updated. Maybe not at the actual update stage but certainly further down the line after the hard reset.
Ok now I have have tried various things as posted in this forum in various sections. Still get the same error.
Originally about 3 months ago, I had to hard reset, then I used the Launch ROM from the O2 website. I still have that original exe but that also NOW fails. I am now running out of options.
Any other ideas?
It might be that because you have unlocked the Extended ROM that it causes this fault, either that or you device has an internal problem which you cannot fix.
Take it back to the shop they will replace it.
114 error
I got my XDA2i back from O2 after a warranty mainboard replacement and decided to upgrade with the new O2 rom..horrors.. I got the 114 error and repeated efforts failed to cure it. I then inatalled a/sync on another PC and ran the upgrade from there...
Bingo! it worked..always worth a try if things defy logic.
Probably an old firewall that didn't uninstall properly.
One thing though, does anybody know when my backup battery will kick in and charge.
It arrived back from O2 completely dead but even with the main battery full it doesn't want to take a charge yet??
Hitla
Just humour me and try the radio upgrade on another PC... That's how i got round my 114 error
To all the people who have advised me... thank you.
I have tried the upgrade on 2 other laptops I have, one with Activesync 4 and one with Activesync 3.8.
AND..... the same failure error.
I have now taken it back to O2 and they have taken it in for repair !!
Should rcv it back next week hopefully repaired or replaced !!
Will keep you guys posted.
Once again great forum and great posters with serious technical advice.
Well done keep it up.
Soory guys,
Have been away for the last few weeks, so unable to update you all.
Well O2 replaced my device. It has the new ROM but the old radio !!
I would like to thank all of you advised me.
Hi,
I just downloaded the O2 Rom-Upgrade.
To keep my 2020i in German I only did a Radio-Update from 1.02 (ran the installer and copied the files to a different directory together with the AllUgrade kindasomething.....)
The update worked, it always worked this way, but after the update the Radio showed up as 1.00.00 (MUST be 1.03, at least that is what o2 says....)
Any idea?
Thanks, Günter
P.S.: I should add that the phone works..
OK, firstly please excuse me if I've asked something that's already been answered. Spent quite some time searching both this site and through google and can't seem to find anyone else that has the same problem.
I've attempted to upgrade my O2 XDA on a number of occasions and always seem to hit the same problem after booting the device.
When cold / warm resetting the device, it always freezes before the today screen launches. At the moment I am staring at the OzUp bootscreen. The device only ever seems to freeze when upgrading the rom past PPC 2002. I've tried (from RomKitchen) wm2003 beta, final, se all with the same result.
There's a couple of bits of information that I can give to possibly help out with a diagnosis:
Wallaby Bootloader V5.22 (does anyone have pre-V5.17 for me to downgrade to)
Working OS Version V3.17.03 (but generally ANY PPC2002 build)
Radio Stack Version 4.21
I also get "G32S54" when booting if that makes any sense to anyone
I do seem to have a problem with the IrDA on the device. Under PPC 2002, any attempted infrared activity will instantly lock the phone, requiring a cold boot to continue. Seeing as I can't find anyone else with the same problem as me when upgrading the OS, I am sort of guessing that this might be the cause of the problem.
However, I've also tried unlocking the XDA (using XDAUnlock) and this also fails (I'm assuming because of the bootloader version). The phone is simlocked onto O2 UK. This could also be a cause of the upgrade fault.
Any advice on this would be greatly appreciated.
Oh, one thing which makes things all that little more bizarre. From RomKitchen, I tried "R.30.07 ENG Rogers" which seemed to work with no apparent problems, only the PDA side of things works great, but with no backlight, and the phone doesn't work either (and so I binned that idea lol)
Hey,
Right, so in my great wisdom I managed to drop my TyTN on its face on the kitchen floor one day and since then it just doesn't do GSM.
On boot, it says "No GSM" below the boot logo, and anything to do with GSM (opening the phone app) causes the device to run slow for a little while then return back to normal without launching the phone app or throwing any error message. Its stuck in permanent "flight mode" as it were.
Sending the phone back to the provider, they turned around and said "On inspection it was found that 3rd party software was loaded on the unit and damaged the unit. Unit is returned without repairs done to it."
I was using one of the ROMS from the forums here which worked fine for a few weeks up till the drop. (I do know which one but I'd prefer not to give anyone a bad name where its not called for, so prefer not to mention it directly).
I will say that it was a fairly new release in june.
Also currently have on boot.
IPL-1.04
SPL-1.40.Olipro
Have since tried re-installing version roms which have made no difference at all.
So:
1: is it possible that the updated OS and flashing the radio etc could have cause the problem described?
2: How do I return the phone to its original radio version and a generic (officially supported) WM5?
3: Is there anything I can do from my side to fix the problem?
Many thanks
-RobH
Have you tried flashing the original ROM that it came with... Then you can probably take it back to another warranty shop or to HTC for repair... You can also upgrade to Olipro 2.10, you can search for the files, I'm just to lazy to look for it now... If you can't find let me know, and I'll look for it...
Once you upgrade to Oli 2.10, it may make a difference.. Have you tried flashing the radio...? It could very well be a hardware problem that occurred during that sudden stop on the floor...
I'm not to helpful, sorry...
Rob,
Obviously the fall messed up your TyTN, and HTC now refuses to work on it (read save money) because you are running a non-standard firmware. Well, screw that!
Have a look here to start the downgrading process.
Then, go to Leaf's site and download the AKU3 firmware from the Members section.
Flash it to your TyTN.
Then take it back to a different repair centre (not too sure about your options in Grahamstown) and tell them you dropped it, and now it is not working anymore.
Right so trying to get the original (well an club-imate approved) rom installed so that I can try the repair center again...
Based on this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Image is HERMIMG_CDL_1.31.305.2_SHIP.nbh
(Extracted frin JASJAM_wwe_1.31.305.2_1.31.305.104_1.21.31.10_ship.exe)
I get the following:
<Gray screen with blue txt>
HERMIMG.nbh -
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS -
Update in Progress...
</End screen>
And thats where it sits.
Even when trying the recommended usb/HardSPL methods, its gets to about 14% and hangs. I presume due to the GSM module being damaged.
I've also tried .nbh's that only have the GSM stuff, and using the microSD method, it gets about 5% along the progress bar and then halts.
EDIT: I've managed to flash it with an original rom excluding the GSM stuff. Will see what happens at the repair center...
-Rob
Excellent, hope you get it sorted!
Helo all - I could really use a hand here. This is the second time I have faced this issue.
When trying to make a call on my 614c when the battery is low, it crashes. Upon reboot, the radio no longer works and I cannot make any calls. It just goes into a permanent "Seaching" mode.
What I've tried:
Reboots - warm and cold
Removing the battery for 30 mins
Reset to defaults
Multiple different ROMs including upgrading and downgrading the Radio
No luck.
Last time (3 months ago) I ended up sending it to ipaqrepair to be fixed.
They said:
"the un-official hacked ROM installed in combination with a corrupt / mismatched GSM Radio ROM, these are the root cause of the issues"
I had actually NOT installed a non-official ROM until after it stopped working in a desperate attempt to fix it. But when they got it, it was a 6.5 ROM.
This time, I had upgraded it to 6.5....but I have since downgraded to the official ROM an installed the. .89 Radio update.
It wont work at all and I can't justify mailing it away for another expensive repair.
Any ideas or assistance would be greatly appreciated. Thanks.....
Any ideas? How can I effectively "blow away" all the software/drivers and set the device up as new? IpaqRepair said it was corrupt software last time....
I've installed different ROMs via flash.dio and I tried the HP radio upgrade RUU_1.8.0_081208_MP_M089_WWE. Are their files or settings that the installs I am doing do not affect - and if so, how do I repair/replace them?
Using Sim Manager, it says the phone is not ready. It's just like the phone radio won't initialize...
This phone originated overseas (Europe) - could that be somehow causing this issue since I'm using it in the USA? Something locking or changing and no longer compatible?
Not sure what else I can do and am missing my phone. Any ideas or assistance would be greatly appreciated.
Still fighting with this....maybe onto something now?
When I get the asset viewer information for the phone it shows the radio is present and the firmware number.
the Stack Version, Bootloader Version, Filesystem Verions and Radio GDFS versions are blank.
It does show the IMEI.
I'm guessing I'm missing file/data for the radio....but reinstalling the Radio ROM HP offers has not helped (maybe not complete - just an upgrade?)
Thoughts?
Anyone have a copy of the original ROM and .81 Radio ROM?
Maybe rolling it all the way back might get it operational again....
Official Drivers/Rom/Radio for 614c
Hi,
You can download official drivers from HP website. The forum does not allow me to post the link. Just search for "official 614c drivers" in google and you wil get the link.
Also note, please install using WINDOWS XP os as installing this using other os such windows 7, windows vista etc is not possible.
Okay - I tried installing the software from the HP Website using XP - but it still isn't working. It's just like the software for the radio is corrupted and it won't replace it (does not list the versions like it should when you look at the software inventory).
Is there any way to manually do this? Any advice or help would be greatly appreciated.
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
-Alpha- said:
If anyone can help me get this resolved, I'm definitely buying them a beer.
Basically the GSM just seems to be bricked. Last time a software fix resolved it, but I'm not sure what software needs to be installed to get the radio working again.
What is the best way to blow it all away and start over? Is there a way to manually delete the radio files - or to look at them for versions/dates to see what is corrupt or mismatched.
Click to expand...
Click to collapse
Just bumping this thread...would love to have this phone back.
Bumping once again - still in hopes of fixing this phone. Can anyone help?
-Alpha- said:
Bumping once again - still in hopes of fixing this phone. Can anyone help?
Click to expand...
Click to collapse
I guess, you will get enlightenment for the problem on your device at http://forum.xda-developers.com/showthread.php?t=455840
Bump.....
Still hoping for a solution. I have gone to a Glisten now, but do not like it as much as the 614c.
I'm open to any suggestions.