Please could someone upload the O2 UK firmware. I've been having problems charging my phone so I tried to restore my phone to original settings but it didn't work so then I flashed the generic world firmware which hasn't worked either. I would like to reflash back to stock O2 so I can take it back to the shop.
Many thanks in advance
batjon said:
Please could someone upload the O2 UK firmware. I've been having problems charging my phone so I tried to restore my phone to original settings but it didn't work so then I flashed the generic world firmware which hasn't worked either. I would like to reflash back to stock O2 so I can take it back to the shop.
Many thanks in advance
Click to expand...
Click to collapse
The version of the firmware that PC Companion installs is determined by the system/build.prop file so if you root the phone and modify the build.prop so it has the correct model number (or just overwrite the build.prop with a suitable one).
PC Companion will then automatically reinstall the O2 firmware version if you go through the Phone Software Update option and do a Repair.
(If your phone is an Xperia Mini Pro I have a suitable build.prop file if you want)
Matchstick said:
The version of the firmware that PC Companion installs is determined by the system/build.prop file so if you root the phone and modify the build.prop so it has the correct model number (or just overwrite the build.prop with a suitable one).
PC Companion will then automatically reinstall the O2 firmware version if you go through the Phone Software Update option and do a Repair.
(If your phone is an Xperia Mini Pro I have a suitable build.prop file if you want)
Click to expand...
Click to collapse
Thanks for your reply. That would be excellent if you could provide me the correct build.prop
A .zip containing the UK O2 Mini Pro (SK17i) file should be attached to this post.
You should be able to use Root Explorer (or similar) to backup the existing build.prop and then replace it with this new one.
After that you just need to reboot the phone then connect it to PC Companion and tell it to repair the current firmware.
Matchstick said:
A .zip containing the UK O2 Mini Pro (SK17i) file should be attached to this post.
You should be able to use Root Explorer (or similar) to backup the existing build.prop and then replace it with this new one.
After that you just need to reboot the phone then connect it to PC Companion and tell it to repair the current firmware.
Click to expand...
Click to collapse
you da man!!
Do you have a build.prop or info i need to edit to restore Orange UK on a SK17i?
Ive unbranded my phone and now it wont accept any simcard. So i want to restore it to the network image.
If anyone has a stock Orange UK SK17i flash file that would be awesome..
Related
so basically i have generic x10i uk r2ba020 f/w on my rogers x10a phone..
i kept having problems with wifi and i'm thinking it might be because of the firmware i have currently, so i want to bring it back to x10a (rogers f/w)
however, i've tried the flashtool in jerpelea's thread, the one-click apk file, and they both keep giving me this error
right after i connect the phone in flash mode, i get
'invalid or corrupt 'jar' file'
i can't use omnius because i need to purchase licenses and it's no longer free..
is there any other way for me to get this phone back to x10a??? i'm really worried that i won't even be able to update to 2.1 when the update comes out..
-----------
edit : can't seem to delete this thread...
i couldn't get it working on xp, but after many tries, I got the file working on win7, with one of the problems being the deviceid.txt being saved as unicode not ansi...
anyhow.. everything works now. thanks
back in november when Brazil 2.1 for X10a came out I did the upgrade by changing my default.prop to the Brazil values (1234-4836) from 3 australia and then doing a repair. It upgraded OK (it was the Brazilian version because I had Orkut and a couple of other apps) and was working perfectly. A couple of days ago the android market was upgraded and last night I noticed that they fixed it up. Today when I use the market it causes a reboot and when looking into this I noticed that my phone is now showing it is a X10i. Looking in the build.prop file its showing as X10i_1232-9897 which is GLOBAL-GGL GENERIC. Is this correct in that I upgraded to X10a Brazil software but it is showing as x10i global ?
You probably used the optimizer or something like that? It changes the device to x10i.
yes, jited the phone a week or so ago. Is it going to cause a problem with an x10a being identified as an x10i ?
mentat6059 said:
yes, jited the phone a week or so ago. Is it going to cause a problem with an x10a being identified as an x10i ?
Click to expand...
Click to collapse
i think not..
but just try all the function to conform...
mentat6059 said:
yes, jited the phone a week or so ago. Is it going to cause a problem with an x10a being identified as an x10i ?
Click to expand...
Click to collapse
You can edit the buid.prop(edit this for 2.1) and change it back to X10a and the correct CDA
http://forum.xda-developers.com/showthread.php?t=824711
either the Root Explorer or ADB method will work. Will also get you back to the Brazil updates when they come up
Thanks, I assume where it has ro.product.name=x10i_1235-7379 I change the x10i to x10a (as well as all other ocurrances of x10i) ?
mentat6059 said:
Thanks, I assume where it has ro.product.name=x10i_1235-7379 I change the x10i to x10a (as well as all other ocurrances of x10i) ?
Click to expand...
Click to collapse
Yes and also change the X10a_XXXX-XXXX to whatever customization you are running.
mentat6059 said:
Thanks, I assume where it has ro.product.name=x10i_1235-7379 I change the x10i to x10a (as well as all other ocurrances of x10i) ?
Click to expand...
Click to collapse
Yes, there are 3 xxxx-xxxx and six (?) X10x,
Install Service Menu app, under Service Info, Model info you should see X10a,
under Service Info, Software Info, Customization Version should be 1235-7379
----------
im_iceman said:
Then using root explorer I edited "build.prop" from within the system folder.
I changed
ro.semc.version.cust=xxxx-xxxx
and
ro.product.name=X10_xxxx-xxxx
I changed the xxxx-xxxx to 1232-9897 (World generic)
saved the settings and exited from the file.
I also changed the ro.semc.version.cust=xxxx-xxxx file in...
/etc/customization/settings/cust.prop
saved and exited.
Then I switched the phone off and on again..
Then off one more time..
Then I used SEUS...
It will say that you have the latest software (because you do!).. but if you do a repair then it will replace your current one with the one associated with the codes you entered...
and bingo.. job done..
CODES here..http://forum.xda-developers.com/showthread.php?t=826875
Make sure you use the first of the codes for your brand/region.
Obviously this only works with firmware that has been released into SEUS.
UPDATE - IF SWITCHING BACK TO A REGION THAT YOU WERE PREVIOUSLY ON YOU WILL NEED TO DO THIS...
(Courtesy of ARKEDK's 1.6-2.1 method!)
Clear out your db folder in either PC Companion or SEUS, which ever one you use.
Press your Windows Key+R or type "run" in your start menu.
Then insert the path to what ever program you use and press enter.
Then delete the folder named with numbers in it.
SEUS db folder can be found here:
Code:
%programfiles%\Sony Ericsson\Update Service\db\
PC Companion db folder can be found here:
Code:
%programdata%\Sony Ericsson\Update Engine\db\
Reboot your phone and use SEUS to re-install your phone to 2.1.
Upgrading from 1.6 to 2.1 - this method was the one I used.. http://forum.xda-developers.com/showthread.php?t=824711
Click to expand...
Click to collapse
- [TUTORIAL] -Simple way to switch from one 2.1 version to another
I seem to have the all too common problem with my X10 where it reboots when under lots of load.
I've decided i want to return it, however i'm currently using a rooted Nordic firmware, and i'd like to return the phone to standard before taking it to the store.
The phone is a Vodafone UK model (SI 1232-4285)
I've altered the settings inside build.prop to reflect the above number, rebooted the handset, then tried to reflash the firmware, however the PC Companion updater tells me "There is no software available for your phone yet, please try again later.", then ends, without actually performing the repair.
Any ideas?
It's not the SI that you want.. it's the build number which you can get from a link in here...
http://forum.xda-developers.com/showthread.php?t=828163
and make sure that you reboot the phone after amending the details before you to to reflash.
Thanks for that.
Looking at this line:
X10i VFE-UK VFE 1234-4579 1232-4285 Vodafone UK/Sensuous black
I presume i should be setting it to 1234-4579 then?
Unfortunately in the mean time, i decided to try flashing the original operators firmware, which i downloaded from the developer section, and now the phone is booting to a vanilla 1.6 OS but asking for a SIM network unlock PIN...
think you'll need to find a new firmware and reflash.. then you can try again with the firmware code.. http://forum.xda-developers.com/showthread.php?t=936733
and yes... 1234-4579
Thanks,
I downloaded flashtool and the latest 2.1 world generic and those flashed on just fine. The phone then started working again and i managed to root it, reinstall root explorer and correctly edit the build number.
SEUS then happily repaired the phone to the latest Vodafone UK firmware.
Things get stranger though, as i then tried to restore my backup i made on the old firmware to get all my contacts etc back. First couple of times i tried it the phone rebooted, so i left it to charge over night, and tried again this morning with a full battery. Backup Restore went perfectly, and it told me to reboot the phone.
Cept now it wont turn on. The phone vibrates momentarily upon pressing the power button, but does nothing else
Is it possible that some "system settings" from my backup have conflicted with the new firmware?
I'm going to try another repair now and see if that will get it working again.
you can't restore your old firmware on top of the existing firmware.. at least not without losing the existing.. If you want your old contents back but not the firmware then you'll need to restore just those elements.. what did you use to back up with?
i have LWW and my SI is listed but when i try to update using pc companion and update service it says my software is the latest.. what may be the problem?
Did you change your build.prop?
For example, in my case I bought a branded phone but changed build.prop to trick SUS to install unbranded software from my region releasing me of operator apk and limitations.
I really believe that for my is irrelevant to check my SI, maybe it's your case.
yeah but i downgrade my rom from .62 to .58 so build.prop is untouched
How did you downgraded?
Because when you change fw you should change Build.prop, I think it install a new one.
The thing is that SUS only install you FW with same specs. Check your Customization number in software info, some examples:
Generic_French_(1251-0622)
Generic_United_Kingdom_(1248-7407)
Generic_Baltic_(1249-8051)
Generic_Nordic_1_(1249-8044) [SE/FI]
Generic_Nordic_2_(1249-8053) [NO/DK/IS]
Generic_Iberia_(1250-2159)
Just take your 8 digit number and search it on google for example and you will know if you changed your build.prop or not (you should remember your original)
EDIT: As an example just to be sure what I was saying I have done the following test:
1º my cust is Generic_Iberia_(1250-2159), no update available.
2º edited build.prop with Generic_French_(1251-0622) because some guys were saying that had updated in France
3º rebooted phone
4º Now it appears that it's possible to update!!!
Clear now?
i downgrade using flashtool, tnx for your help but i cant understand what your saying
I will try to help you but I also need you to do some things.
Search in forum how to access build.prop. I use one tool called ADB MASK CONTROLLER, very easy.
When you open you will find 3 lines with the code (your code should be other xxxx-xxxx, unless you have the Generic Iberia like me):
ro.product.name=SK17i_1250-2159
ro.build.fingerprint=SEMC/SK17i_1250-2159/SK17i:2.3.4/4.0.2.A.0.62/wf_v3w:user/release-keys
ro.semc.version.cust=1250-2159
Change the code, to this for example (the French one in this case, you need to know the one you want to put):
ro.product.name=SK17i_1251-0622
ro.build.fingerprint=SEMC/SK17i_1251-0622/SK17i:2.3.4/4.0.2.A.0.62/wf_v3w:user/release-keys
ro.semc.version.cust=1251-0622
Save and reboot
oh i get it now, thankyou very much for your time
Note:
Someguyfromhell said:
Carrier/operator is able to block the updates to phones if phone is branded.
Click to expand...
Click to collapse
Hi folks,
I started off with the .475 India ROM, then installed the .475 rooted HK version, then moved to the .510 Taiwan version.
But now that there is an official .510 for India, would like to install it.
So, instead of waiting for someone to upload a FTF file, how can I change ROMs on the phone using the PC Companion?
1] Do I need to change the build.prop entries to India? What is the code for India? Currently I have the Taiwan one.
2] Once I make this change, will "Repair" using the PC Companion reninstall the India ROM, or will I still remain on Taiwan version?
3] Can we collate the various region codes in one place, so that switching ROMs might become easier?
Thanks for the help!
To answer my own question...
I changed the CDA for Taiwan, to the one for India. Connected the phone to PC Companion with the intention of "repairing" it.
But viola! PCC reported that an update was available. That turned out to be the .510 for India (I was on .510 for Taiwan).
Best part is, all my apps and settings are intact.
So, for those who want to try out firmware from other regions (mainly for the region specific apps Sony has bundled):
1] Root the phone, change the CDA entries in the build.prop file, which is in the system folder.
2] Reboot the phone, connect it to PC Companion, and Search for Update. Even if the version is same, PCC will treat the new region's firmware as an "update".
3] Note that you will lose root access, There is a "kernel swapping" method mentioned here to root the phone again: http://forum.xda-developers.com/showpost.php?p=45070025&postcount=389
This worked for me. the Vroot and 360 methods did not.