When installing WM 2005 getting error 103 rom image file not - MDA II, XDA II, 2060 General

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

Related

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

Possible Brick (8125) G4 - At Bootloader Screen

Resolved. Topic Can be Closed / Deleted.
Hello, I am new to the forums and new to reloading phones but fairly tech savvy otherwise.
I have a Cingular 8125 G4 Phone.
Current IPL/SPL
IPL 2.21.0001
SPL 2.21.0lip
-Can Access Bootloader Screen
-I successfully Unlocked it
-Updated the ROM to WM6
-Come to find it operated much slower then my WM5
-Tried a Different ROM
-Left the Room while it was uploading
-Cat attacked the cord or the phone
-Was Detached during the update process
-Rebooted Phone, stuck at the Basic Splash Screen
-Attempted to do a hard reset. Was able to access this screen, format, but would return back to flash screen and just sit there.
I have spent a couple hours going through the information on the forums but to no avail. I fear I have got a paper weight but was wondering if anyone had any suggestions.
Normally I would keep searching however this may prove to be time sensitive and need all the help
Thank you in Advance
Yours Truely
WTFPWN by Cat
Rick
As Murphy's Law would have it, soons as I post this I come across another post that told me to re-flash and for some reason after attempting to reflash 3-4 times, this time it appears to be taking it. I will keep you folks posted
However The link is broken for the official Cingular 8125 WM5 (What was shipped with the phone). If anyone has a link I would appreciate it if someone could send it to me. I will post once I have received.
Thank you very much.
Phone has recovered. However I would like to restore it back to Factory Defaults for reasons that are my own. I feel I can do it but do not have the Factory Image link.
The Following Link appears to be broken:
http://www.htcamerica.net/support/8125/software-downloads.html
This Topic Can now be closed I found the original Rom at
http://rapidshare.com/files/188635235/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_cingular.rar
Found it after searching on the board for a while.
Adding Keywords for Search Engine to Pick up on so people having similar issues won't have to look as long as I did
AT&T 8125 G4 IPL&SPL
Version 2.25
Original ROM
it's hard to say what rom it had since i got it with wm6.5.
i found a link on this forum to a file called RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_cingular.rar
it seems to be one of the many originals, so i'll try to flash this one as soon as i can figure out the connection issue with ActiveSync. I tried both 4.0 and 4.5 but they both fail to connect i need to fix the pda's display (or wait until it solves itself, like the previous time) in order to troubleshoot the connection error
hi. I hapened for similar trance.
First download RUU_Wizard_Cingular_8125_WIZCNG01_G3_G4_2006_11_May_225_225_225111_22511102_022511_CWS_WWE_Ship2
(seek in google)
Second quit the battery (100% charged) and put again. Power the 8125.
Third reset your PC wihout the 8125 connected.
Fourth connect the 8125 and execute the file donwloaded.
I hpe to help.
(sorry my ugly english, I spoke español)

missing file!! RUU_ETERNITY_Radio_Signed_17.5006.08.27_17.08.50.0 6.7z

hi,
i've been trying to flash my htc titan (eternity x310E) , i have updated the rom using RUU,
i started by, following the steps in file DFT_HSPL_WP7SG1, after that when HSPL was set up, my phone restarted and got frozen on htc logo screen but i read a similar problem in a forum and the user had continued installation of DFT Eternity 24 langs Freedom V1 Pearl Edition after which the user stated his similar problem was solved.
so i also followed the same step. it got installed successfully but the starting screen problem persists. in an another forum it was stated that i need to update my radio by flashing this file "RUU_ETERNITY_Radio_Signed_17.5006.08.27_17.08.50.0 6.7z"
i checked this file in several locations and websites but everywhere its missing or no longer exists.
SO if this is the solution to my problem can you please tell me where i can find this file.
please help me as i am new to this and donot know much about this whole thing.
thank you

Desperately Asking For HELP!!!

Hello, guys! It's now my 2nd post asking the exact same help. I'm very desperate to fix my phone : Asus Zenfone 5.
I have been looking for solutions for a long time, I'm not easily quit on googling. So far, this problem is one that haven't been fixed and very unlikely to be fixed
I have contacted many people including that Taiwan guy who is an expert on Zenfone 5 (forgot the name) and I'm EXTREMELY DESPERATE
I know this problem might be similiar with other case, but this one seems to be rare, because I have not found the solution.
Here is the timeline before my device got soft-bricked :
1. I upgraded to Lolipop with a different version of it's recovery, but still worked.
2. One day, ANR Keeps reporting that SystemUI has stopped. Rebooted and the phone went bootloop.
3. (probably the problem) I flashed wrong version of recovery (I think it was kitkat's recovery) and after then, I'm not able to get into DROIDBOOT.
I have tried several ways :
1. Sending package to my phone over ADB Sideload (It says something like error mounting blabla)
2. Flashing with xFSTK (It says something about driver, and I googled it. Found everyone with the same problem, endless solutions)
3. Downloaded about 1 gig of files (DEBRICK Files) and still, gets stuck somewhere.
So anyone have a solution for me, please?? I'm totally desperate right now, I lost hope. Never had this kind of problem, the thing is that so far, I never had such never-solved case in my life, I will always
find a solution from Google even that would take a long time. I have been searching passively for about 8 months, and I got none of those works
I will be very thankful if anyone would try to help this problem, I will bring detailed information you want, because I don't have solutions left.
Sorry for bad English
Thank You so much!
Christ, I was sure that I ticked it as a Q/A.
how to help? you are just telling about softbrick.

Categories

Resources