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
Related
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 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
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!
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)
I bought a second hand O2 XDA atom exec recently. So far I like the phone, except it seems a bit sluggish sometimes (compared to my HTC harrier WM2003) and the wifi will NOT turn on. I tried using the O2 wireless manager, and the WM wi-fi utility. They both fail to turn the wifi on. The wifi self diagnostic returns "GetAdapterInfo() return FALSE..."
After doing some web searching I am aware that it has 802.11b. I figured that its probably a driver issue. From what I understand the only way to install drivers is to flash it with a ROM that has working wifi.
Im not sure whether to stick with WM5 or move to WM6.
My current:
WM 5.0 OS 5.1.195 (Build 14955.2.3.0)
Version:
CMOS: 55.44
ExtRom: EX0033
Hardware: C1
Radio: R060822N_MN2ARC_RS00013
ROM: 20060721B1WWE
Ive noticed that most ROMs don't state if bluetooth/wifi/FMradio is working, or which input methods work, (ie. transcriber, block recognizer etc). Is there a way to tell without installing it on the device first?
Thinking of using either: (it won't let me post links.)
wiki.xda-developers.com/index.php?pagename=ATOM_Exec_Upgrades (the WM5 roms)
forum.xda-developers.com/showthread.php?t=397725 High Performance Abusalza's in Blue WM6.1
forum.xda-developers.com/showthread.php?t=396799 ATOM EXEC WM6.1 20080417A6WWE ~ ULTRA LOW BATTERY CONSUMPTION [For Evaluation Only]
Any help or comments would be greatly appreciated.
Thanks in advance.
ROM upgrade froze at 73%
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
knoppies said:
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
Click to expand...
Click to collapse
mines is froze at the boot screen how to do i fix it any ideas
I had an O2 XDA atom exec and so far when i had i was able to use the wifi promptly without any hassle. I just turned on the wifi and searched a connection then poof, i started browsing the net already. The battery however drained fast. If you are having trouble with the wifi, as you have stated that it gives error issues maybe you should have it reprogrammed or check if first if you have open wifi connections.
theblogpostwriters.com
i got one recently. Wifi connection isnt going well. I did once connect it to my 802.11b network, but a few minutes later it doesnt and never able to connect successfully
confused
the developer itself doesn't provide the legal upgrade of 6.5, or i mustn't have known it..
knoppies said:
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
Click to expand...
Click to collapse
I rather think that you should first check whether your phone is really bricked, to read the instructions regarding this and to see how to recover from the brick click here!
After you have recovered you phone, I recommend that you use Windows Mobile 6.5!
Thanks!
Always glad to help!