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, 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)
Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
I just recently acquired a HTC Touch Dual and really like it but am having a few issues with it. First, I get tskschedule, repllog, and clocknot notification errors. I've noticed a few threads regarding this issue but haven't yet found a solution so any suggestions would be most appreciated. The second problem is that my battery indicator doesn't seem to be working properly, it stays at 90% and doesn't change regardless of how long I use it for. This caused the phone to die on me in the middle of a conversation. So if anyone has an idea on how to fix either of these two issues, that'd be great.
Hard-Reset or flash another ROM (for example Original HTC Shipped 6.1 or one of the custom ROMs which where offered here in your language).
I bought the device used and unlocked off of eBay, will hard-resetting it keep it unlocked? Also, I'm very much a noob to phones and don't have any clue about flashing roms, what are they exactly and how do I do it? Thanks for the quick reply.
Hard-reset = Original state of the installed ROM
For flashing there are lots of tutorials here (I don't know which is your native language, so I can't post links to some ROMs - I have nearly tested all of them ;-)). Best you try flashing first original HTC ROM. Very easy (you said it's already unlocked), just connect the phone to pc via USB and start the flashingtool. After flashing hard-reset to be sure that all settings and files were restored to original state. That's all.
Don't forget to backup contacts, emails and so on before hard-resetting/flashing! Files on storage-card will be ignored, you don't need to backup them!
im from the us, so my native language is english. do you have any suggestions or links for the better flashing tools? after flashing to my original rom, my phone will stay unlocked right? because it doesn't it'll create more problems for me then i am having right now. thanks again
My native lang is German, so don't worry about my English ;-)
Unlocking is easy, just use hardspl and uspl. I have unlocked my phone only once a time and never had problems after or while flashing (done 15 times or more!). Once I killed my phone with a bad Rom (endless boot-sequence), but you can go into bootloader by pressing "Power-Button + Camera-Button + Reset", so you're always able to flash another Rom and/or could unlock the phone again. Nevertheless I can give no guarantee.
First you could try to download from HTC website. You need the serial-no. which can be found after removing the battery. If you have a look at niki upgrading/flashing forum you'll find also links to the original ROMs.
You can also try the latest WWE/english ROMs offered in this forum at the first 1-2 pages. I tried Gullum's TF3D and Lilly's ROM, both are great and have Manilla included (if you don't like it, the old HTC Home plugin is included in HTC Rom), but I prefer german ROMs. The Niki Project Rom didn't work for me (bugs in Outlook and Office Mobile).
All Roms include the flashing tool, it's really easy to use.
thanks buddy, i'll give it a shot and let you know how it goes
do i have to use a sspl before a hardspl? i have a neon and havent yet found a sspl for it yet. how dangerous is it to use a hardspl? im very new at this so thats why i have so many questions. thanks again
For me everything worked without problems. So I can't say how "dangerous" it is. Most users don't have any problems. To be sure get latest ROM from HTC or your provider, so if any problems occur, you're able to flash the original ROM back via bootloader.
As far as I know you only need to hardspl, but I did sspl first and then hardspl.
I think we need to clear up a couple of things and kind of slow down before you brick your phone
Generally, there are 3 types of locking for these phones.
First, there is SIM locking that everyone is familiar with and locks your phone for use on only one network.
Secondly, we have CID locking - which locks the software\firmware on your phone to that supplied by a particular carrier (for example, if your phone is CID locked to AT&T, you can only flash a ROM from AT&T and not HTC or a custom ROM).
Lastly, and least to be concerned about, is Application locking. I've not heard of any of the touch duals being app locked so we can safely ignore this.
I'm guessing that you meant your phone is sim unlocked in which case, I'm 99.9% sure that none of the ROMs that you can flash will change that.
If yours still has the carrier ROM on it, it is most likely still CID locked so you need to get that off first.
Once that's done, you need to HARD SPL installed (the SPL is the bootloader bit, SSPL is just a "software" version of it that can run but doesn't install anything) If you put HARD SPL on, then it is almost impossible to brick and ruin your phone - but until that is on, don't try flashing custom ROMs or radios etc. as you're asking for trouble.
Also, until you have HARD SPL on, be careful about flashing anything - make sure you don't run apps while it's going and shutdown anything that could interfere. Take basic precautions and you should be fine.
But TBH, if you're new to these phones anyway, and the ROM is right for your carrier, I'd leave it as standard - I personally always find something wrong with the cooked ROMs - missing T9 dictionaries \ SMS not working \ MMS not working \ some other detail that was missed, and I always end up going back to either my stock ROM (T-Mob UK WM6) or the HTC Update (WM6.1) but I don't notice the difference if I'm honest.
People say that whatever ROM they have on is the fastest they've ever tried but in my experience (and I'm on my fifth or sixth generation of WM phone) the difference is marginal at best and certainly not worth the trade off of broken features and multiple reboots.
So, my advice is, by all means, have a mess with other ROMs but be careful, get HARD SPL and make sure you have a ROM to go back to.
Oh, and try a hard reset (or Clear Storage from control panel) after syncing everything up to try and fix your current problems
Cheers,
Smiffy.
i was thinking about trying a hard reset prior to flashing a rom. i cant download a rom from htc and am unable to find one from att (my carrier) so as of now, i dont have a rom to fall back on. i bought the phone used and unlocked, so will a hard reset keep it that way (basically, what will a hard reset do exactly)? i am referring to a sim-unlocked state. the centennial wireless splash screen still shows up so im guessing it is still cid locked? do i need to unlock the cid before hard-resetting it? thanks for the help
The hard reset basically wipes and user-related info and returns it to a factory-fresh state - if one ever starts playing up, this is what should be done before you flash a new ROM, and yes, it will still be SIM-unlocked afterwards. It will alos go through the setup routine again as if you just took it out of the box
There are other places to get the HTC rom from - it's actually quite a good one too as it will set up all the data\MMS settings for your carrier too.
If you're not worried about any warranty, then it's good as a fallback though search on here and see what results other people have with AT&T.
CID unlocking is fairly easy if I remember - been a while since I did it and I have a different model than you. Just make sure anything you use is listed as OK for a neon
HTH,
Smiffy.
so i did a hard reset, and there hasn't been a change in the battery issues. so maybe the battery is faulty? would flashing a different rom help or should i just get a new one? thanks again
If the ROM is at fault, then flashing a better ROM would help, yes. If the battery the faulty, then even a ROM that is much more energy efficient would help little, only delaying the inevitable.
how would i know if the the problem is from the rom or the battery? other than trying a new battery that is
aight, so i got the hardspl for the neon. will that cid unlock my phone cause i cant find a cid unlocker for the neon 300. what would happen if i didn't cid unlock my phone before flashing a new rom?
Nothing would happen. Either it refuses to flash on beforehand, or it'd stop at about 1% from the start not touching your existing rom.
Hardspl is indeed the way to cid unlock your phone, as far as I know.
Please Help!
new problem here, my new battery just arrived a couple of days ago. i inserted it in my phone then let it charge before turning it on. my previous problem was that with old battery, the amber light would start blinking but not remain steady and tell me that my battery was very low then eventually turn off. the new battery's amber light was solid and i left it plugged in for 10ish hours because the light never turned green. i finally turned it on, but eventually the same problem arose. i hard-spled it then flashed a new rom which helped for a little while. the light stayed steady and the battery status rose up until 100%, but the light stayed amber. then if there was any shift in pressure on the chord, the light would start blinking and the battery would immediately read 5%. now the new battery isn't any different from the old one. does anyone have a suggestion? it would be greatly appreciated.
Anybody? Help? At the very least would anyone have suggestions of good repair sites? Thanks in advance
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)