Hello
I have an XDAII1 PH10C
Ive had a few issues with TomTom etc and have downloaded an update or two - including the official O2 update.
Unfortunately me XDA keeps freezing and Im getting pretty upset with having paid £400 for nothing.
When I did the O2 upgrage I got the following :-
The file "rofs_target.zip" was not copied sucesfully. To re-install, you will need to get the source .cab file again. Continue with Setup?
Ive even let both batteries run down completely in the hope of restoring original O2 set-up - but I get a Country Error code when I re-install the upgrade.
My hardware settings are :
ROM 1.11.00 WWE
Date 01/27/05
Radio 1.04.00
Protocol 1337.42
ExtROM [this is blank]
Ive got the chance of returning to O2 support to try and sort problem, but I need original O2 set-up or they will charge me £96+vat for re-setting XDA.
PLEASE - does anyone have solution for solving [blank] ExtROM issue or the original O2 settings to solve the repair bill problem.
Thanks
Paul
what types of sd card are you using
sometimes i get that error as well but all i have to do is re run the no id app and it works 2nd time
I have a PQ1 1GB card, but dont have that inserted when I download updates or reset PDA.
Paul
re-run the O2 update if it errors with country ID error then just start it back up again it should then work.
It looks from the specs you posted your using the latest 1.04 radio. i assume you installed PUGs new update version ?
Hi
Yes I tried Pugs version, and the ExtROM was still blank.
So, Ive gone back to an O2 version - and the ExtROM is still blank.
I need to reassure myself that I have ONLY O2 software on the XDA before I send it in for repair as it will be free - if they find any other stuff on there they will charge me c£100.
Paul
PS Im still having major TT5 issues. Today it froze and I had to hard reset and then tried to re-install TT5. Only to be told it was already there and did I wish to overite. When I said yes, the today screen came up and theres no sign of TT5 anywhere.
Bloody XDAIIi is doing my head in.
Have you downloaded the latest O2 ROM from the XDA2i mini site?
When you are installing it have you got your anti-virus software turned off?
Yep - O2 download.
Yep - AntiVirus, Internet Security & Anti-Spam all Off.
Ive just done the download again and still got the rofs_target.zip message.
Paul
Hi there, have you tried unlocking the extended rom by any chance? This will cause the storage to be locked and cause the extended rom to stop installing past a certain point (Happened to me). There are instructions on this site on how to unlock it, do a search for unlock and my screen name (pug).
Hope this works.
Pug
I found the link you refer to and downloaded the exttools.200.exe and ran it on XDA.
I then tried the official O2 update again and the XDA has FROZEN !!!!
It is now stuck on Serial v1.01 and WILL NOT alter no matter what I do.
Ive soft-reset, hard-reset and done the soft-off-action button thing - and nothing.
When I place in cradle, the PC plays a tune as if to say it knows the XDA has been connected, but I cannot get activesync to recognise the XDA.
Now what can I do please ?
Im particularly worried that I now cant remove the exttools.200.exe from the XDA and will have to return it for repair with that dodgy software on there - they will definately be charging me for a repair now.
What can anyone suggest please ?????
Paul
Related
Hello,
I was today handed a fried XDA 2.
My boss had attemted to flash it and it failed for whatever reason.
Now i will say from the outset that i have only ever flashed my XDA1 with a XDA-Developers ROM and it was a breeze.
The ROM file HE flashed with was called.
Xda_II_Upgrade_v16050.exe
Now when you switch the thing on.. all you get is a a small amount of txt saying
'Serial'
'v1.06'
and nothing else..
What have i done? Well i have sifted through the articles on here.. and found this rom
XDA-developers-SER-v12.exe
I have installed this on an SD card using xdatools.. WHOLESALE.. i.e. no moding of the files...
I have looked at 'http://wiki.xda-developers.com/wiki/HimalayaRomFlashing'
but as i can boot into the device.. i cant get the info it requires.
I am open to any and all help. And I'll even buy you a pint!
I am really at a lose.
Thanks in advance Guys and Girls.
It may not be as bad as you think.
It is in bootloader mode - currently in Serial mode and if you put it in a cradle connected to a PC (with ActiveSync installed) the bootloader should change to USB v 1.06. From this point you should be able to load a normal ROM from the manufacturer.
I have an i-mate, so am not sure what the current ROM version for the XDA II is, but I'm sure others will chime in with this information.
I upgraded to this version, not knowing I already had this loaded. You need to check the extROM version before upgrading as this appears to be way the official upgrades seem to change.
I had no problems and it was done through the Active Sync process
The file can be found here if you haven't already got it... http://www.my-xda.com/downloads.html
Try it again. It does take about 90 mins.
Regards
Nope... Nadda... Zip... Zilch.
Roit...
When i dock the pesky thing in the USB craddle.. it does display USB and v.1.06.
Activesync shows NO sign of knowing the XDA is there.
The ROM found at http://www.my-xda.com/downloads.html as suggested by flintanis fails with a ERROR 100: MODEL ID ERROR.
BRosenow what do you mean by 'load a normal ROM form the manufacturer' is that not what i have just tried?
Once again a pint for all contributors.. and my first born to the dude with the solution.
Cheers.
ActriveSync won't activate because it's in Boot loader mode but you can download the latest ROM Update from the manufacturer or cellphone service provider and load that to flash the ROM and complete the process.
If it's a UK XDAII, get the update at www.my-xda.com .
It appears the previous user tried to flash it with a ROM from another manufacturer (Q-Tek/MDA II/i-mate). You are now receiving a Model/Country ID error. I have not experienced this myself, but I have read posts in this forum on how to fix it. Do a search and I bet you will find it.
- OR - any user who has experienced this and successfully flashed his ROM could chime in here and give jonathh some advice . . .
After much ado about nothing..
i have returned to again fix this XDA2 (the joys of pesky FT employment; make your minds up guys.. you want this XDA2 fixed or not?)
Right i *think* with quite a high level of certainty that the XDA2 currently in my grubby mitts was purchased in Malaysia/Sinapore.
Now.. am i correct in that flashing it Xda_II_Upgrade_v16050.exe from http://www.my-xda.com/downloads.html
Would cuase the problem i have now.. or at the very least wont go on on the XDA2 now because it is a UK ROM and a Malaysia XDA2?
I have flicked thru the pages on here.. and i cant seen to see how to solve this!!
PPllleeasseee help
*sobs, and gently rocks back and fourth*
I think there is a bit of confusion going on in this post!
The first ROM you tried (XDA-developers-SER-v12.exe) is for XDA1 - NOT XDA2.
The best place to get the latest UK XDA2 ROM is http://www.sourceo2.com/O2_Developers/Devices/O2_Xda_II/XdaIIRom.htm
and i *believe* that the place to download the Malaysia ROM is
http://www.myxda.com/XdaII/serviceandsupport/template/XdaIISoftwareUpgrade.vm (note the absence of the '-' between my and xda...this is the Asian O2 website)
See if the ROM from either of those sites will install
Hope that helps!
How about scrambled?
Ok, thanks 'pope'
*none* of the roms suggest work..
Xda_II_Upgrade_v16050.exe reports unknown country code..
and the recently suggested
Xda_II_LaunchROM_v10311.exe just sticks on the 'checking for information' left it for over an hour! BUT doesn't report unknown country code like the other one.
I cant get the XDA2 rom from the Asia site, as after i registerd my XDA2 it reports i dont need the damn update... anyone got it already?
I have extracted the core files from both these exe's and tried to copy them to an SD card(the NBF fille) using XDAtools.. and xdatools report the files are invalid.
I am lost and clueless!
HHHEEELLLPPPPP
Well that didn't work...
I got my grimmy grits on another XDA2 and using XDAtools sucked the ROM off of that.. and then.. again using XDAtools squirtted it out onto an SD card..
But i am unsure what i have to do then? is this latest approach possible??
Comments welcome![/code]
Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?
mark8barnes said:
Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?
Click to expand...
Click to collapse
O2 will fix this for you if it happened as a result of flashing with their rom.
By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.
I did feel braver, and copied the O2 Cabs into the IMate Extended ROM file. Then I deleted the IMate cabs I didn't want, modified config.txt and prayed! Everything seems to have gone fine, and I'm now re-installing all the software. Already there seems to be a significant speed increase over 1.60.
I'd recommend taking this step before you flash the ROM, rather than doing it twice like I did.
mark8barnes is the man!
I didn't do the mods.. just as per your original post.. and it worked!! Yay
Thanks mate you da man!
Now i do have a query tho.. if i did suck the rom off using XDATools.. how would i get it bck on again?
Cheers all you guys..
Fried XDA
Hello Mark
Me too, I flashed my ROM with the UK version with the same result.
The link to the iMate ROM no longer exists, can you help me please. I'm a real novice at this.
Thank you
Ben (Aust)
mark8barnes said:
By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.
Click to expand...
Click to collapse
I've currently followed the instructions for the 1.31 with Arabic and different radio file because that's exactly same original hardware as my UK O2 XDA IIs.
But I've ran the BaUpgradeUt.exe and it confirmed the version changes, but now it doesn't seem to be doing much.
Phone has gone dark and simply says:
USB
v2.06
And the Upgrade program says: Checking the information on the device please wait.
And a warning not to disconnect it.
Erm this is my first flashing so just a little worried I've toasted my new device :-( I can appreciate it takes a while to transfer 30Mb odd over USB, but it hasn't done anything for almost 10 minutes now :-(
Help please? :-(
Thanks!
And I think I've solved my own problem. Everything you need really is in this forum... somewhere
For everyone else who stumbles over this looking for same thing. I simply took battery out for 30 mins (to flatten backup I assume) and then hard reset it (comes up with serial v2.06 at point you unplug from cradle) and then restarted PC and re-ran update program and SEEMS to be going okay at the moment!
Hi,
I have the O2 XDA IIs just like you too but still with the original ROM. You can get a copy of the original ROM from O2 now off their myxda uk site if there are any problems.
Have you got a step by step guide of how you upgraded to 1.31?
Cheers
Hi,
Take a look at the Wiki site. It has all the info on there. I'm now running a 1.31 main ROM (was originally 1.12), a 1.06.02 radio (originally 1.02 I think) and an extended ROM that is hacked up from Orange's (the network I'm actually on!) as well as my own choice of programs etc. Wiki has all the info! It rocks! Thanks to the guys (and gals?) who write it!
I'm new round here, but just received a T Mobile update. The file is MDA3_TMUK_v106160_SHIP0307.exe I've put it in the root of the ftp server, since wasn't allowed to put it in a more appropriate place. Hope that's OK.
BTW it does seem to have improved my audio quality, which was the reason I asked for it. It didn't come with release notes, so I don't know what else is included.
Strangely, although the updater worked, and as I say it has fixed my problem, when I look at device info it still shows ExtROM 1.06.117 WWE.
What have I misunderstood?
I think this is only an update to give Blackberry access.
Okay guys,
So you know the next question... can anybody extract the blackberry app so I can try it on my XDAiis as the other ones don't generate a PIN!
yes please, same for me. I would love to have the UK blackberry application.
thanks in advance for anybody who can remove the BB application out of this ROM update.
Ronald
T-Mobile UK Official Rom Update
I have just received this update as well.
Can one of the technical wizards on the site (such as MDAIII user) have a look at what is in the extended ROM, as well as Blackberry.
T-Mobile say that they have included a number of other patches for bluetooth etc. Could someone list exactly what has been changed over the base ROM.
After buying my device nearly 6 months ago and waiting this long whilst all my O2 and Imate cousins have had lots of upgrades to the radio and base rom, I am deeply unimpressed. :evil:
Thank you in advance for any assistance.
J
Same Here!
Hey all,
Well Jason, I feel exactly the same way. :roll: Been long waiting any updates and hopefully this update solves some of the following problems. Just doing a Full Backup, before update is applied! I will reply when installed with any updates to software revisions for bluetooth/rom/extended rom/etc.
*Such as Bluetooth dropping its connection from Weak to Good continuously when connected to me Jabra BT200.
*Another problem is that when firstly I soft reset the device it hangs whilst booting on the second T-Mobile screen, and have to soft reset the device 2/3 times rapidly before it boots properly. This can be a problem if its hung and you urgently need to make a phone call.
Anyone else having these problems?
Apart from that everything else seems to be in working order.
Sunny D
I downloaded the upgrade and ran it agaist the new tool.
This seems to be a 3 version of the encription as the tool will not open the file.
unless somebody posts the cabs ( In a subdir of the root of the ftp site) I can't look at them.
As per my above post shows I was just about to update my phone but no-one said it would lock my networks!.....I just didn't think of that!
Well I've just installed it and it has Locked the networks. It was unlocked to all networks, and not anymore.
Looks like I'll have to pay again to unlock it! Unless someone can help me unlock my MDA III!?!?
---------------------------------------------------------------------------------------------
Rom Version: 1.06.00 ENG (No change)
Rom Date: 08/05/04 (No change)
Radio Version: 1.00.00 (No change)
Protocol Version: 1337.30 (No change)
EXTROM Version: 1.06.160 ENG (Wasn't displayed before update on phone)
Bluetooth: Build 3500 (Was Build 1900)
---------------------------------------------------------------------------------------------
So overall probably just a Bluetooth Update/Blackberry support and Video MMS. Not a great update, probably not worth the update considering I can only use my T-Mobile Sim for now!!!
Well MDAIIIUser what cabs do ya need? I'll try!.....Copy them of my Phone or PC??....& need to know where to find them??
Sunny D
Did I understand what you wrote
you had a phone that was sim locked
you had it unlocked so that you can use any sim
you ran the above upgrade on your unlocked device
now you have a locked device and you can't use any sim that you like but have to use a t.mobile sim
Well that is what I understood
As for the cabs
They are in the extnded_rom folder that is hidden
you need to download the tool, check wiki for the link (if its still around)
Zip the file, and uploaded it
http://wiki.xda-developers.com/index.php?pagename=BA_ERK_Tools
ta
If you paid T-Mobile to unlock your MDA they should unlock it again for you without charge.
Anyone managed to get the Blackberry CAB out yet?
MDA III UK Upgrade Didn't relock my phone
I have tested out my phone after the upgrade and I am pleased to advise that it is still totally unlocked.
T-Mobile unlocked the original ROM for me for the £15 charge and the phone has stayed unlocked even after the upgrade (just as well!).
SunnyD - thank you for your work in helping to analyse what is new in the extended ROM.
Hi guys. Never posted before but been around.
Was once able to access the ftp but lately I get a permission denied message. Anyone got any advice on how to overcome this?
Found the ext rom 1.06.160 ENG on ftp site and linked it to wiki, Thanks sunnyd24.
Will cook it and post in wiki as well as update this thread.
The file you are looking for is:
htc_pocketpc_tmo_england_2.0.0.25-18.cab
The rest of the rom seems the same (looked at it for 30 secs)
Managed to access the ftp in the end. Was being stupid really... :?
Posted this ship.exe in wiki
Moved it from root to the correct folder
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
Files to Examine......or Use!!
Hello all,
Not a problem Jason, we are all here to help each other. Well I just tried another sim (old O2 & Orange) after the success you had, & guess what It is unlocked!!!!
I've got a problem with a new O2 sim i'm using. Its new & was working in the phone before the update and kept sim card whilst the update. And now cannot use that sim in the phone for some reason!
Its wierd how an old O2 sim works fine but the new one has problems.
:?: Anyone got any ideas??
Well as for helping everyone with version info for MDAIIIUser I am going to upload the new extended rom files to the FTP Site (and attatched below as a Rar). Hope it helps everyone!
Well all for now,
Regards,
Sunny D
Passwords
Has anyone got the passwords for this old ones dont work
Passwords
Has anyone got the passwords for this old ones dont work
Sunnyd24
Both the ship and exteneded rom for the 1.06.160 have been posted in wiki (as per the posts that i wrote before) Think the only file you need to attach is the one for BB (as ...)
Hi All
I have a SPV M2000.One day the phone stopped working. Everything was all right, it did ask for pin but then didn't even looked for network,was immediately saying NO SERVICE. I tried few sim cards - the same.
So then I wanted to reinstall the ROM, I downloaded the official from Orange UK , tried to install it,and it shows ERROR 114, Radio Rom Upgrade Error.
And the phone now is in bootloader mode and I can't do anything!
I downloaded different ROM from xda-developers ,at the beggining with a country error, but i managed to fix it and now with this ROM it's the same thing. ERROR 114. I tried everything, hard,soft reset, Pc reset etc. Nothing works!PPC still in bootloader mode!
Please tell me if you know what else can I try!
Guys,come on,really noone knows???
Have you read WIKI? Follow the first method to flash your ROM. Have you remembered to plug in your power supply to your cradle when you flash your device?
Heres another thread on NO SERVICE Plz help... No Service after radio upgrade. Happened to me. Read it and see the advise by MDAIIIUser and TheLastOne. If all else fails, bring it to the shop.
I had a very similar problem....
First I tried to update a whole package that means rom, extended rom and radio
The radio update is always the first one and there always upgrade error 114 occured.
So I updated every part seperately and it works except the radio. So I tried alot but it just didn't work..even downgrading was impossible. MDAIIIuser and happy goat tried to help me as well as they could but nothing had an effect.
So I read in another forum that asus mainboards have some problemes with these radio updates....I thought they were joking...but I tried the radio pdate at another pc and it worked!
I know it sounds a bit stupid but I was desperate and at last it worked!
You can read it here :
http://forum.xda-developers.com/viewtopic.php?p=89657#89657
TRied that method.Doesn't work
Any other ideas?
One more thing.Is it normal that in bootloader mode when I plug the power cable in the charging LED is not working?it was working before.
The battery is charged ,but shouldn't it show that the power is connected anyway?
EDIT: this is a reply to the first answer.
So you think I should try on another PC?I will today!Hopefully it will work.
So I managed to install new rom on a different computer! I think that there was a problem with active sync.I used the one that was installed from my old XDAII.Could that be the reason?Now i installed the one provided with a M2000.
But it doesn't work anyway
Still NO SERVICE message.
ANy other ideas different than taking it to Orange?
Hi rottie,
No Service could mean anything. Could your SIM card be faulty? Device SIM locked? Or hardware faulty? You cannot just use any ROMs you find at ftp. Try to flash your device with full shipped rom at http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade. Use the first method and upgrade using MaUpgradeUt_noID.exe to bypass the Country code error. Remember that you'd need to run MaUpgradeUt_noID.exe twice.
Read wiki carefully, it has alot of precious information. Cheers ^^
Before you update any version you should be sure that your radio is
compatible with your device. Usually all radio upgrades should be
independent off the language of the device but as I understood (could be
wrong) there are differences because of the servicenetwork frequency.
So you must be sure that the chosen radio is compatible and that your
device is not simlocked.
So perhabs you should chose an upgrade of your provider.
But perhabs itis better not to risk your guarantee of your provider by
using updates or components of other providers! Because there could be
the possibility that your device is damaged and you should bring it back!
Good luck!
Guys, you get me wrong.I'm not trying anything what I'll find.
1)One of the ROMs that I tried and the one that I left now is a ROM downloaded from orange.co.uk for SPV M2000. So there can't be any incompatibility, don't you think?
2)I have 2 sim cards,both from Orange,I was using both of them before in my M2000 which is sold only through Orange so there can't be any simlock problem,don't you think?
3)I used only that orange ROM, original and the I-Mate one.None of them were working good,always NO SERVICE.
I bought the phone second hand,with box,all accessories etc. But I don't have a receipt :? And of course have lost the guy's number.That's why I want to try everything before going to the service.
I think this phone is network blocked, probably been reported damaged or stolen, once the insurance or replacement is issued a block is put on the imei of the phone that was subject to claim.
Available at least in www.myqtek.se and www.myqtek.fi.
Changes: Updated client for streaming media. New radio version.
Although I cannot get upgrade to start properly, always gives me error 262 at 0%.
Thanks for the update! I've downloaded and will flash the new software in the morning (I want to charge the battery a bit first).
I hope radio is more stable with this software - I've been to Denmark and the UK this week and in both countries call were broken and the phone lost connection with the mobile network (No service and Searching). Same problem that I've had before, even though I have tried changing the sim card. If it wasn't for these problems it would be a great smartphone, but now I find it to be a very crappy phone. Let's see if that changes now!
what's the AKU of the new ROM?
Finally got the update to work, had to do it according to these instructions: http://forum.xda-developers.com/showpost.php?p=1050547&postcount=6.
OS version is now: 5.1.465 (Build 15673.3.3.1), BUT radio is 1.29.00.10 and not 1.38.00.10 as it says on the ROM package. Can someone confirm this? As I had the 1.32 IU Test version installed previously and although I went first back to 1.30 I didn't check what the Radio version was so I don't know if 1.29 radio is something that was left from the 1.32 version or if 1.34 just has the same radio as 1.32.
1.32 was pretty promising version and I hope this one will be even better. I've had no major issues with these newer versions, although just a few days ago the phone ate the battery from 100% to about 15% in two hours when I was in a movie theater and the phone was not supposed to be doing anything!
I too have problems upgrading - I get error 262 at the beginning of the flashing. When I restart the MTeoR it starts WM as usual, so it seems it hasn't started flashing yet. This happens on two different computers. Any suggestions, please?
Note: I am able to flash 1.30.251.1 with any of the above computers. Only the new 1.34 is a problem. Could the install program be faulty? If so, it is pretty bad considering it is an official release.
New Rom
Hi,
Can you put it on rapidshare of megaupload ???
cor
http://rapidshare.com/files/22706498/852727-mteor_upgrade_2.zip.html
New Rom
Thanks for putting it on rapidshare.
I found the problem about the 262 error.
Just use a older update program with the new
rom file and everything is OK.
What language include new rom?
I didn't know how to do that , but after having checked a number of threads etc this is what I did:
1. Extracted the files in the exe file RUU_BREE100_1.34.251.1_1.38.00.10_HTCEUR_SHIP using WinRAR.
2. Did the same with RUU_BREE100_1.30.251.1_1.16.00.10_HTCEUR_Ship
3. Removed the nbh file from the 1.30 directory and replaced it with the file from the 1.34 directory.
4. Ran ROMUpgradeUt.exe
It all worked, and I have now upgraded the Rom. Thanks!
jpalo: radio is 1.38.00.10, just as the file name says.
My radio didn't update first time either.
I found I had to use the 1.30 installer and it would only update the second attempt when it was already in the bootloader.
I then used the 1.34 updater and it then updated the radio.
Well I just updated mine and Yippeeee!!!!! Finally I have the EDGE "E" at the top. 'Bout freakin' time. My radio does still say 1.29 but I have noticed that before the update my phone was only on 2 bars, now it's steady on 4. Browsing seems to be much quicker now as well. Time to start reloading and testing.
Try updating with the 1.34 .exe and .nbh once you have managed to get to 1.34 the first time (ie just run the updater direct as you should normally)
My OS is 5.1.465 (Build 15673.3.3.1)
Radio Version is 1.38.00.10
So I guess that would make it AKU 3.3.1
No problems with it so far and have unlocked it to import the Vodafone settings as I would before, now to restart my mission to actually be able to load the UK Vodafone wap sites.
Dl also, and will try it out.
Electronic Punk said:
Try updating with the 1.34 .exe and .nbh once you have managed to get to 1.34 the first time (ie just run the updater direct as you should normally)
My OS is 5.1.465 (Build 15673.3.3.1)
Radio Version is 1.38.00.10
So I guess that would make it AKU 3.3.1
No problems with it so far and have unlocked it to import the Vodafone settings as I would before, now to restart my mission to actually be able to load the UK Vodafone wap sites.
Click to expand...
Click to collapse
Do you mean you "application" unlocked it? When I tried the old tired and true way of running SDA Unlock tool it tells me it can't be unlocked. I also can't make any registry edits, it won't save my changes and gives an error. What did you use to unlock it? Thx.
I ran the registry editor (same as before), made three registry changes.
Rebooted, ran the unlocker (which is now allowed)
Rebooted again and ran the unlock tool and said my phone was unlocked.
The steps I followed are here:
http://www.modaco.com/Mteor-application-unlock-solution-t244205.html
staffann said:
...I've been to Denmark and the UK this week and in both countries call were broken and the phone lost connection with the mobile network (No service and Searching). Same problem that I've had before, even though I have tried changing the sim card. ...
Click to expand...
Click to collapse
I had the same problems with my phone really bad. Finally got fed up and sent it for repair.
Got it back about 10 days ago, and haven't had any problem since. I'll wait another week or so before I really give it a clean bill of health.
The fix was quite simple... They replaced the mainboard... So it seems like there really was a hardware problem.
Royan
Royan said:
I had the same problems with my phone really bad. Finally got fed up and sent it for repair.
Got it back about 10 days ago, and haven't had any problem since. I'll wait another week or so before I really give it a clean bill of health.
The fix was quite simple... They replaced the mainboard... So it seems like there really was a hardware problem.
Royan
Click to expand...
Click to collapse
Sent in one last week, same problem, it cuts calls and cant find network and so on.
Royan and BarateaU: please keep me posted!
I'll try to let you know as well if the ROM upgrade solved my problems.
Looks like the 1.34 update has been removed from www.myqtek.fi and www.myqtek.se (although it is still available via some URL tweaking).
Running the ROM update again now succeeded without any 262 errors and radio was also updated to 1.38. Thanks for help.