Database Users

XDAIIi New ROM from O2 and xdaforum, both fail with ERROR114

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..

help with new mda lots of problems and i'm confused

ok i've done a bit of searching and i'm pretty sure its software related.
i got an mda pro from when i booted the phone up its had a o2 splash screen, so im assuming its had its software updated. so the phone works fine for about 6 hours or so but then it starts tt freeze up, propgrams stop responding and the phone wont do any thing. i left the phone like this for a few moments then i got a txt and the phone seamed to be working fine untill i went to use the camera and i got "the file camera cannot be opened. either it is not signed with a trusted cert or one of its components can not be found you might need to reinstall or restore this file".
ok so i had a look and found the Available Universal Versions and Upgrades
the thing is i'm not sure which is the best to use or how to do it.
what would you guys recomend i do ?
thanks

MDA Pro with O2 Rom?
Seems so that there is other Rom on it. Normally, this is not a Problem, but who knows, what was changed in this Rom.
I would recommend to download new Rom and install this.

Try http://www.my-xda.com/xdaexec_soft.html
Thats got the latest XDA update.... give it a go and then get the new 1.09.00 radio update too...
Hopefully that will sort you out!

chears i'll give that one a go and see what happpens. fingers crossed

ok so i downloaded the Xda Exec ROM v 1.13.188 from the above site followed the directions in the pdf file, connected the phone and made sure there arnt any programs running in the backgroung. when i try to runn the application to do the upgrade it says its trying to connect to the phone then gives
"error 201: get device data error
can not get device data
please make sure device is connected and run this update utility again"
only problem is that it is connected or so ms active sync says.
any ideas whats goign on or is there another way to update the software ?
thanks guys its apreciated

ok so i managed to get past that stage but
now i get
error 102 ce image file check sum error
the rom image file to be used for the update is corroupt. please download the correct device software update utility and try again.
i have no idea what that means any sugestions ?

@cusaeng, can't help with the ROM update but your initial problem of problems after 6 hours is typical of the Universal when its running low on RAM. Use an app like GSPMaigc+ which can really close processes and reboot once a day (obviously once you solve the ROM issue).

chears i'll look in to that program once i get the rom issues sorted
i've trued downloading a version of the jas jar rom and that give the same error message about being unable to get device information.
when i flashed phones befor eg a motorola a1000 you had to get the phone in to bootloader mode then use a progran to flash it is it a simaler process with the mda ?
i really dont know if i'm doing anything wrong or not

Downgrade issues.

Was experementing with S200 recently.
It appears to be a problem with downgrading device, with using standard tools. After upgrade to RUU.Prophet-2.15.13.27-2.15.13.121-02.19.21-Dopod-Asia-WWE-Ship and attempt to return to original QTEK flash, device crashed. 3 colour screen with no possibility to flash with either original flash files or another one.
The best I could do is to use same flash file with Updater.No.Vendor.ID. It would accept the file and start the process.
But looks like not easy to return to original flash, specifically, when it was lower version. It is possible, of course, with using flasher which will copy flash image direct to device without any further checks, like vendor ID or version.
Looking for the tool (flasher/updater) which will not do any check-up during the process. No vendor ID updater does not perform vendor ID check, now need something better, which will not do any check-up at all.
Please post if you have any information on this subject.
de yl1wc

I'm looking for too
I'm in the same situation. I have the latest dopod rom, but i want to go back with the last qtek french rom: no way.
Please, help us!
I think "machina god" can do this tool.
I'm just waiting for this tool, or maybe a new french rom....

why you want back dopod rom is better than qtek

Hi,
Like I was saying above, I am experimenting. I need to have a way to go back. But with No.Vendor.ID it does not not look possible to go back.
With original ROM also.
j'aime les expérimentations
a bientôt

This become critical!
I have discovered unpleasant issues with my s200, since i have switched from original qtek to lates dopod flash. These issues relates to GSM phone. Sometimes can not connect, only soft reset helps. It was never the issue befor. When incomming call and you push on volume control side button, phone is "stuck", nothing happens and no connection.
So, guess what?
I need a tool urgent to recover functionality, to downgrade to original lower number qtek flash from existing latest dopod flash. As mentioned no.vendor.id is not a solution, because upgrade process check for version number, and if the existing version is higher than one you are flashing with, process will fail.
Please advise. Don't propose to buy a new phone

hey! there is a tool called JAWFM!people say that we can use it to upgrade with ani kind of software and it doesn't check vendor I'd!!!But there is one problem-it costs 85 $!
am I right ?
may be someone have it!?
may be that "someone " give it to us ?

Have the same thing. Want to go back to russian qtek ROM, but can not

So I purchased JafWM
JafWM have physycal lock key - so there is nothing useful with getting software alone, without key it not burn firmware.
It really can burn any firmware - but not any firmware have all components. Qtek firmware have all, but JAMIN have only OS, GSM, EXT components.

Is service center the only solution??
No, no, don't tell me this. It should be a tool (ROMUpdateUtility.exe) that does not check not only vendor id, but also version of flash and evrybody will be happy about it.
Question is where is a tool?
later.

Alpine Upg hangs at Radio update-Help. PDA has no op sys now

Hi
My alpine had been upgraded to 02's new rom which took the radio back to 1.0. I don't use the Blackberry functionality so decided to try Pug's update. I also hate all the 02 stuff (no longer with them anyway) but after following the readme and forum comments to the letter the upgrade - using Alpine_Ext-1.11.162_Radio-1.04_O2stuffstripped.rar hung at the radio update bit - every time and I tried loads.
I then decided to reinstall the the 02 (my-xda site) update which also didn't work. I've now tried putting the alpine into bootloader mode and trying the upgrade with three of the files Pug kindly put up. I've rebooted my pc between, tried everything I can think of several times, each time only trying something different after trying the same way more than once and I am left with a PDA with a blank screen which only reads USB v1.01.
Sorry, additional info. I don't have to use Task Manager to end the process as I get this error which allows me to exit:
Error 114: Radio Rom Update Error.
I used Winrar (new beta version) to extract the .rar file(s).
Does anyone have any ideas?
Many thanks in advance.
Leanne

It's probably OK!
Still - don't panic - you should have found out by now that if you do a reset it will load all the original ROM info and you should be back where you started.
I suggest you read through all the posts in pugs ROM thread. In there you will find a reply from christoperwoods pointing to a patched installer located at :
ftp://xda:[email protected]/Magician/Tools/MaUpgradeUt_noID.exe
Follow the instructions and you should be OK.
After the reset try the ROM upgrade again. As long as you have external power (and I would strongly recommend using the mains adapter as USB power is not as reliable as you may think) throughout the upgrade - which takes 20-30 mins in total - you should be OK.
I would be interested in what you think of it - I actually went from the ROM version you are trying to load to the O2 .171 ROM upgrade yesterday as I was having problems with GPS connectivity on the pug ROM. I know the radio stack is only 1.00 - but it works for me.
Phil

XDA Radio upgrade hang prob.
Huge thanks for responding, Phil. Unfortunately no amount of resetting, either normally or bootloader mode has worked.
I had read through all Pugs' threads, but took your suggestion on board and re-read in case I had missed something. I also tried the alternative patched installer you mentioned - to no avail.
I've had a chat with an XDA repair house now and we think it may be a problem with the connectors, but even if it isn't I am dropping the pda into them as I have a very limited timeframe to get a fix done (it's Friday and I leave the country on Tuesday!!). A suggestion has been made of using something called jafwm (I think that's what it was) to reload the system but you need a dongle to complete the process.
I'm interested in your comment about the gps side of things as well, as this is one of the main uses for my pda (destinator) - along with reading books (ereader) and listening to books (audible).
Ideally I am looking to rid my XDA of all 02 specific stuff (except the battery monitor) and have the newest radio version as I have found 1.0 problematic.
Once I get back online again in New Zealand (where I am going on Tuesday 20/6) I will drop a reply to the forum about what truly ended up being the problem.
Anyway, once again thanks for the response and the helpful suggestions
Leanne

T-mobile branded Mega & sunnysoft - problem

Hi. I've got t-mobile branded HTC Touch2. I got through HardSPL FAQ, made backup and started to flash my phone. The main problem was the language (formely german) which I'm still trying to change to English or more preferably - Polish. When I eventually managed to do HardSPL (which involved playing with OEM_FLASHDRV.dll), I downloaded ROM_Mega_HTC_WWE_EastEurope_1-28-479-4 from sunnysoft site and succesfully flashed it. I ignored the warning about limitation to PN: 99HJZ022-00 because I've earlier read people successfully flashed that rom on many different PN's. Mine is actually P/N : 99HJZ057-00.
When I installed language localization patch I ended up looping at "Windows" logo - the progress bar goes to 100% and starts back from 0%. I've tried to hard reset many times, tried with booting it up on and on with no result. One time it popped up with and error box saying the software I installed did not match the rom I have. Weird since it came from sunnysoft site. I've tried downloading it again to exclude a CRC error and flashing itself goes perfectly well.
I'm using English for now, but I'd be nice to have polish xT9.
What goes wrong ? Does sunnysoft patch really work only on this specific P/N ? Is it worth the hassle or am I stuck with branded t-mobile ? This is my first PDA but I also have an option to get some HTC with android. Any solutions?