XDA 2 with xda IIi firmwire - MDA II, XDA II, 2060 General

Is this possible? i have SE on my XDA2 but its not installed properly. When its finished transfeing the nu rom image accross, its starts installin stuff but crashes on a messag sayin it might not display correctly
so i was just wondering if the IIi firmwire wud work

no rom have to be 100% made for a device to work

Your phone is not crashing when it gives you that message.
It just means the program being installed is not programmed specifically for WM2003SE.
Just click 'ok' and it will continue.

Related

Error 112 CE ROM Update Error

Hi, Don't know if anyone can help. I had a perfectly working XDA2 up until I tried to upgrade the ROM the other night. Now I have a useless hunk of junk that states "error 112 CE ROM update error. I have browsed every fix given on the forums, but to no avail. As my unit is covered by warranty (and I may possibly be getting a XDA2s as a replacement heh heh") I am not too bothered, however although a newbie I would still like to know if there is any way I can fix this problem that I haven't yet tried, just for future reference. At the moment the only display I get, on an unlit screen is either serial V1.03, when not in cradle or usb v 1.03, when in cradle. I have tried soft reset, hard reset, tried a coupe of rom upgrades, disbled active sync, and even tried prayer and using the force! Unfortunately my jedi powers are not sufficiently develpoed enough, so I would be very grateful if you could help me out here. Incidentally, this site is fantastic! Thank you to all who are resposible for it, and long may it continue. Merry Xmas!
You could try flashing with the launch rom from O2, I dont have the link for the download but I am sure somebody else has. The launch rom was available for download so you could revert in case of problems.
cruisin-thru said:
You could try flashing with the launch rom from O2, I dont have the link for the download but I am sure somebody else has. The launch rom was available for download so you could revert in case of problems.
Click to expand...
Click to collapse
I had same eror 112 CE rom bla bla bla... on my comp.
Some program from my comp. crashed upgrading every time.
Solution that worked for me was clean computer with only activesync instaled and everything worked fine with same ROM from before.
Thanks guys, will try those methods. Nothing to lose eh! Merry XDA-MAS to you all. Ho ho ho!
I had the same or similar problem, just upgrading from the official 1.72.181 a window came up telling some thing was wrong, do a hard reset and try again.
After the hard reset all I can see on the unlighted screen was a Serial 1.06.
Launched the upgrading program again with the PDA on the craddle and it seems to be performing correctly and I can see the upgrading process in the PDA screen if alighted with a torch.
May be if you try it again you succeed.
Jose Adell

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

Can't start my XDA's botloader

Hi guys,
Recently I updated my XDA Orbit with the new WM6.1 Diamondish ROM. Everything went great until I tried to install the Oops 6.1 ROM. Before trying to install the Oops ROM I tried to unlock the CID just in case (with your Artemis_USPL tool)... Half way through the setup screen displayed an error saying "Connection error... Please check the USB connection...". Just to clarify I never managed to install the Oops file.
Then I tried to install the original XDA WM6 ROM but with no luck as I got the same error again. Then I tried to start the bootloader manually (by pressing the voice recorder button along with the Reset one) and instead of the usuall 3 colour screen I got a blank white one. Afterwards the phone froze and I had to reset it so that I can use it again.
I did a small search on your website but because I wasn't able to find another similar case I decided to start a new thread.
Currently my phone works perfectly fine with my previous Diamondish ROM, but I seems that I can't install anything else.
Could it be a corrupted bootloader? If so, how can I fix it?
Any help will be much appreciated.
Thanks in andance!!!
Take out your MicroSD card and then try and flash
You were right! Once I got my memory card off my phone, the bootloader started as usual. Cheers mate!!!

[Q] Error: Unfortunately, the process com.google.process.gapps has stopped

I have Nexus 4 on the latest version of software. Couple hours ago, I started seeing the following error message as soon as I unlock the device.
“Unfortunately, the process com.google.process.gapps has stopped.”
This message isn’t going away. I click ‘ok’ and it comes back the next second. Hence it making it very hard to use the phone even for simple tasks that require a simple touch or a click.
This phone is not flashed with a custom rom. Currently running 5.01 version which I believe is lollipop.
I have searched online and on this forum. I have yet to find a solution. People have posted stuff that works randomly.
My phone is unrooted I believe. Is there a way I can flash google apps that can fix this. Do I need to root it first for this? Where can I find the correct version of g apps to flash?
My phone is almost useless. This popup keeps on coming every 2 seconds. Incoming/Outgoing texts are sporadic.
Anyone has any inputs towards the solution.
thanks.
If your phone is running stock 5.0.1 then I highly recommend you to reflash the stock firmware again.
You only need the google developer image and the wugfresh toolkit to flash the image through a pc.
Bro u will hv to root ur fon den u ll hv to unlock bootloader n den u can flash any google gap frm cynogen mod of nexus 4 or frm a rom similar to ur fon bt fr nw without root it is jst nt possible

Categories

Resources