New debrand method for mini - Sony Ericsson XPERIA X10 Mini

The following is just a product of assumption and it is NOT tested. It may brick your phone
Since the last update of SEUS, Sony Ericsson made it almost impossible to unbrand the X10 mini (with the blob_fs file changing method).
However SaintyUK has given us a nice guide about debranding the X10 mini pro here
So let's assume it is working for the X10 mini. The only different thing we need is a new "build.prop" file (UK Generic from a X10 mini)!
See SaintyUK's post for instructions, if anyone is willing to try it.
*EDIT* I have uploaded a different build.prop with changed values in the version of the FW. This might work.
*EDIT2* From the latest results of the members that have tried SaintyUK's method with the attached build.prop files, it seems that it is actually working.
PS:All credits to SaintyUK for his great guide.
DISCLAIMER:MEMBERS HAVE CONFIRMED THAT THIS METHOD IS ACTUALLY WORKING BUT I HAVEN'T AND THEREFORE I AM NOT RESPONSIBLE, IN ANY WAY, FOR BRICKED PHONES.

This method worked for me. But if your current FW version is not 1.2.A.1.174, dont't use the attached file directly!

ra3al said:
This method worked for me. But if your current FW version is not 1.2.A.1.174, dont't use the attached file directly!
Click to expand...
Click to collapse
A little more info, could be quite usefull!
You said "don't use the attached file directly. You mean that in a mini with FW version 1.1.A.0.8 this build.prop (1.2.A.1.174) is not going to work?
But in a branded 1.2.A.1.174 it should work right?

Good on you DaRk_dOg

SaintyUK said:
Good on you DaRk_dOg
Click to expand...
Click to collapse
Thank you sir,
But we would be even better if we could finaly solve it!
If what ra3al said is true then we might need the build.prop from 1.1.A.0.8
But someone must confirm it first. I cannot confirm it myself because i've already debrand my mini the old fashion way (blob_fs) long time ago

At least it worked for ra3al, thats great as even it helps one person thats good
We maybe able to edit the the values in the file. Thats what I did for the X10 Mini Pro. I found the CDF number (post 2 of my thread) and inserted it into the file!

Dosn't work... The original build.prop gets restored after reboot. Used root explorer.. Also somewhere in the forum there is a target-World build.prop
Sent from my E10i using XDA App

Ok i've edited the build.prop with the value for E10i Generic UK (1237-0392). Also this build.prop is from a E10i 1.1.A.0.8
Hope this will work.
(First post updated)

It was a root explorer issye. Working with latest versuon. Place build.prop in system then repair through seus.
Sent from my E10i using XDA App

DAXGr said:
It was a root explorer issye. Working with latest versuon. Place build.prop in system then repair through seus.
Sent from my E10i using XDA App
Click to expand...
Click to collapse
The first build.prop? Or the one i added today?
Could you also tell me your FW version?

so, which build.prop should I use to debrand my x10 mini? Buildprop11A08BrandedE10i.zip or E10i_build.prop_UK_Generic.zip?
my current version is:
Phone Software Version:
1235-3408_1.1.A.0.8
GENERIC - user
File System Version:
WORLD-1-8_1.1.A.0.8
Thanks.

So placing this file in the folder and then updating will be unbranded?

Yes thats correct SEUS will hopefully debrand. Try the 'E10i_build.prop_UK_Generic.rar' file first if not try the other file (see first post)

Thanks it worked... Now i'm 1.2.A.1.174

It works using any build.prop with file system version World-1.8-....
Sent from my E10i using XDA App

e10a
Would it work with E10a version.
Also, if it's not much asking, could someone write a guide for the mini?
Thank you devs very much...you rock!

chagolucho said:
Would it work with E10a version.
Also, if it's not much asking, could someone write a guide for the mini?
Thank you devs very much...you rock!
Click to expand...
Click to collapse
You cannot use any of the build.prop attached, as they only work for E10i. On the other hand if you find a build.prop of an E10a Generic UK it could work.
*First post updated*

You mean't E10a right DaRk_dOg?

SaintyUK said:
You mean't E10a right DaRk_dOg?
Click to expand...
Click to collapse
Yeap! I'm terribly sorry, made the correction!

But it MUST be from UK???
I dont think we would be able to get a E10a build.prop from there...
And the following question would be...does somebody have a E10a generic build.prop????????

Related

Easiest way to 2.1 nordic stylee

2.1 is out and you can get it yourself within a matter of minutes, root ya phone with the one click universal android root app then use root explorer to change the default.prop in system to register your device as nordic and voila reboot device connect via seus , 2.1 DOWNLOADING! AWESOME HUH?
heres some links for ya to follow method i just said
one click root
Provided below as an attachment, simply download onto your x10 and install, then simply click root button,
nordic change
1. DownLoad the file attached Default.prop
2. extracted it an save it anywhere on your SD-Card (so you can find it later)
3. Open Root Explorer open folder sdcard where you save the downloaded default.prop (PLZ MAKE BACKUP FROM THE ORIG. default.prop !!!!!!)
4. Click long on default.prop at the menue click copy
5. go back and open system folder
6. on the right upper corner click r/w
7. click paste
8. restart the x10
9. Run SEUS and start to download nordic 2.1
Did you miss this thread - NEW 2.1 Update for ROOTED X10 -easy way-, or these...
Debrand to Nordic Combined (B) Quick and update to 2.1
X10Flash 2.1 final & 2.1 Firmware
x10 Flash 2.1 Final + Global World Firmware 2.1
DID you miss the fact that neither of these provide an easy all in one solution which included the one click root too?
No so move on cowboy
androidfanboi said:
DID you miss the fact that neither of these provide an easy all in one solution which included the one click root too?
Click to expand...
Click to collapse
Did you miss the fact that the first two links describe the exact same method, or that the other the other two don't require rooting at all. Adding a link to your post doesn't warrant you having to start yet another thread on the exact same topic, with almost similar wording as an existing thread on the same page you've posted yours.
So read the rules boy!
XperiaX10iUser said:
Did you miss the fact that the first two links describe the exact same method, or that the other the other two don't require rooting at all. Adding a link to your post doesn't warrant you having to start yet another thread on the exact same topic, with almost similar wording as an existing thread on the same page you've posted yours.
So read the rules boy!
Click to expand...
Click to collapse
Why dont you try having your own medicine and read BOY! the other two do require ROOT but dont state how to get it so iv bunged it all in one, why dont you go find yourself a life to spend your time on rather than replying to me you retard, there will be beginners that will find this useful as its all in one post
androidfanboi said:
the other two do require ROOT
Click to expand...
Click to collapse
Nope, all they require is the ability to put your phone in to "flashmode". I suggest you do some reading!
androidfanboi said:
but dont state how to get it
Click to expand...
Click to collapse
All that is missing from - NEW 2.1 Update for ROOTED X10 -easy way- - is an attachment which didn't require a new thread with the same information to add it.
androidfanboi said:
why dont you go find yourself a life to spend your time on rather than replying to me you retard
Click to expand...
Click to collapse
lol, showing your level of maturity with that one.
Do all of these methods work on the mini pro? Thanks.
3dawg said:
Do all of these methods work on the mini pro? Thanks.
Click to expand...
Click to collapse
See the "mini" forum, I think you'll find the appropriate files there.
XperiaX10iUser said:
Did you miss this thread - NEW 2.1 Update for ROOTED X10 -easy way-, or these...
Debrand to Nordic Combined (B) Quick and update to 2.1
X10Flash 2.1 final & 2.1 Firmware
x10 Flash 2.1 Final + Global World Firmware 2.1
Click to expand...
Click to collapse
So, which link will be good?
Is it possible to just add the "Nordic" part at the top to my current default.prop file. Or does it need everything in the file?
EG, Just change the bold sections:
ro.semc.version.cust=1234-8465
ro.semc.version.cust_revision=R9A
ro.product.name=X10_1234-8465
ro.semc.country=Nordic
ro.semc.product.brand=Generic
ro.product.brand=SEMC
ro.product.device=SonyEricssonX10i
ro.product.manufacturer=Sony Ericsson
ro.semc.content.number=PB10
ro.product.model=X10i
ro.semc.ms_type_id=AAD-3880056-BV
ro.email.domain.0=hotmail.co.uk
ro.email.domain.1=o2.co.ukro.email.account-name.0=Hotmail
ro.email.account-name.1=O2 E-mail
ro.email.incoming-protocol.0=pop3
ro.email.incoming-protocol.1=pop3
ro.email.incoming-server.0=pop3.live.com
ro.email.incoming-server.1=mail.o2.co.uk
ro.email.incoming-port.0=995
ro.email.incoming-port.1=110
ro.email.incoming-encrypt.0=ssl+
ro.email.outgoing-server.0=smtp.live.com
ro.email.outgoing-server.1=smtp.o2.co.uk
ro.email.outgoing-port.0=25
ro.email.outgoing-port.1=25
ro.email.outgoing-encrypt.0=tls+
ro.mms.auto-download=true
ro.mms.roaming-download=false
ro.semc.message_max_size=307200
ro.product.locale.language=en
ro.product.locale.region=GB
ro.mmi.standby-ringtone-volume=6
ro.ciphering-indication=false
ro.semc.ecclist.type.0=Police
ro.semc.ecclist.number.0=999
ro.semc.ecclist.plmn.0=FFF FFF
ro.semc.ecclist.non_ecc.0=false
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.homepage.url=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=sehome
ro.browser.bookmark.title.0=Sony Ericsson
ro.browser.bookmark.title.1=Sony Ericsson Support
ro.browser.bookmark.url.0=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=sehome
ro.browser.bookmark.url.1=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=contactus
ro.home-screen=com.android.launcher
ro.facebook.enable=true
ro.twitter.enable=true
ro.picasa.enable=true
ro.flickr.enable=false
ro.youtube.enable=true
ro.semc.hidden_pull_interval=168
ro.semc.enable.fast_dormancy=true
ro.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.yt=android-sonyericsson
ro.com.google.clientidbase.am=android-sonyericsson
ro.com.google.clientidbase.vs=android-sonyericsson
ro.com.google.clientidbase.gmm=android-sonyericsson
ro.semc.emanual.url_semc=http://www.sonyericsson.com/cws/support/
ro.email.num=2
ro.semc.ecclist.num=1
ro.browser.bookmark.num=2
ro.drm.whitelist.num=0
ro.build.fingerprint=SEMC/X10_1234-8465/SonyEricssonX10i/es209ra:1.6/R2BA026/1277951075:user/rel-keys
Never mind, I was hoping it would grab the update over wifi.
TrietHocNhanSinh said:
So, which link will be good?
Click to expand...
Click to collapse
They are all good, but you'll find it easier using one of the last two.

[Q] X10 Mini Pro showing E10i

Hello,
My X10 mini pro is showing model:E10i in all applications and secret menu.
I have installed last version from SEUS 2.0.A.0.504, APP2SD and Jitter.
Does anybody know why this happened.
After noticing this I tried to type sms with querty and screen is no flipping.
How can I put back U20i?
Thank you.
n4s said:
Hello,
My X10 mini pro is showing model:E10i in all applications and secret menu.
I have installed last version from SEUS 2.0.A.0.504, APP2SD and Jitter.
Does anybody know why this happened.
After noticing this I tried to type sms with querty and screen is no flipping.
How can I put back U20i?
Thank you.
Click to expand...
Click to collapse
Maybe u've install update zip using recovery..then to solved it..use binary flash to get back ur original firmware number..gd luck
Sent from my E10i
you flashed build.prop from another model.
Just use RootExplorer to replace build.prop from the correct model (download correct flash and extract it), or maybe you could just edit it.
I will try it! Thanks
It worked
Thanks!
If any one have same problem build.prop can be found here:
http://forum.xda-developers.com/showthread.php?t=857284
good. im glad it worked

[FLASHTOOL GUIDE] HOW TO for n00bies

Hi all
PLEASE. DON`T USE JIT OPTION THIS WILL MAKE YOUR PHONE STUCK ON BOOT!!!​Devs already working on this issue​Thks for kiwiBratwurs for calling this out​
Since some guys having trouble using flashtools and how to abuse it , this is a "HOW TO FOR N00BIES".
Please visit the main thread for question
If you need/want upgrade your X10i baseband to the last one released by SE (X10a_2_1_A_0_435) and get 2.1.54, please go HERE (all credits to steve.adams.x10)
With this tool you can go SWITCH FROM/TO android 1.6 and 2.1. Just download the firmware rom links posted down and choose.
Please, if this thread was usefull for you in some way don`t donate me anything. Just ckick on THANKS, RATE THIS THREAD on top and vote on POLL . If you want to donate please do but on the right guys who made this incredible tool for us to use. Androxyde and Bin4ry.
I`ve only tested this on X10 even so this should work on every X family. If you`ve tryed on other X family and been successfull please send me a PM with that information and a link to firmware so that i can update this thread. Thanks
Very soon will be some improvements on this tool. Please stay tunned on the main thread (just to tease lol) Please don`t ask absolutly nothing about this. I just ignore.
INDEX
EASY WAY (*.ftf files)
HARD WAY (*.sin files)
How to root and more...
Apps that you can delete
Something was about to happen on next version LOL
----------------------------------------
----------------------------------------
WHAT YOU NEED:
Flashtool from HERE
----------------------------------------
----------------------------------------
CREDITS TO:
Androxyde
Bin4ry
Everyone from XDA
and myself of course for making this
----------------------------------------
----------------------------------------
Regards,
Ricardo Rendeiro
nice guide men! =) +10
I already know of at least 1 noobie that got a bit mixed up with these "X10" guides.. I was trying to work out what they were doing wrong trying to flash their mini then I went to the guide they were following (this one ^) and found out they were following it to the letter!! (which ment installing dual touch on a mini!!)
So its not really the best for "Noob's" unless they have a big X10 (not a mini or Pro) or at least something should be added to let them know not to install dual touch
I still don't see why .Sin files are refered to as the "Hard way" I still use the Flash tool I tested for Bin4ry last year when we all updated to 2.1 Nordic... no fancy GUI but simple as, and I have never had a problem flashing my phone.
Still.. nice work (I'm so old skool I didn't even realise there were ftf file's until I read this guide )
Kiwi
kiwiBratwurst said:
I already know of at least 1 noobie that got a bit mixed up with these "X10" guides.. I was trying to work out what they were doing wrong trying to flash their mini then I went to the guide they were following (this one ^) and found out they were following it to the letter!! (which ment installing dual touch on a mini!!)
So its not really the best for "Noob's" unless they have a big X10 (not a mini or Pro) or at least something should be added to let them know not to install dual touch
I still don't see why .Sin files are refered to as the "Hard way" I still use the Flash tool I tested for Bin4ry last year when we all updated to 2.1 Nordic... no fancy GUI but simple as, and I have never had a problem flashing my phone.
Still.. nice work (I'm so old skool I didn't even realise there were ftf file's until I read this guide )
Kiwi
Click to expand...
Click to collapse
Hi,
If you read well you don`t see any dualtouch on mini or mini pro. I can`t be blamed if people get so excited and don`t read can i?
I put that way (hard) because it`s harder. Well not harder but need more stpes to accomplish final result.
And last. From 026 version and next we`re only be able to flash through this type of files(ftf).
Hello =)
Thanks for your work! First, my english isn't very rich so dont blame me if i make some mistakes =S
So i tried to activate JIT after rooting my x10 mini using your flashtool. Everything was right until the reboot. It is said in other forum the reboot would take at least 5min but in my case, it took more than 1hour!!
So now i'm stuck on the SE logo for more than 2 hours (lol). Can anyone help me solving this problem please?
Thanks !
Reuberts said:
Hello =)
Thanks for your work! First, my english isn't very rich so dont blame me if i make some mistakes =S
So i tried to activate JIT after rooting my x10 mini using your flashtool. Everything was right until the reboot. It is said in other forum the reboot would take at least 5min but in my case, it took more than 1hour!!
So now i'm stuck on the SE logo for more than 2 hours (lol). Can anyone help me solving this problem please?
Thanks !
Click to expand...
Click to collapse
It`s not comon to happen but it may happen LOL
Flash again and repeat JIT procedure and see
Thanks for answering so fast! ^^
But i cant get my phone in flashmode, thus i cant flash it with a new rom ?
i hope my phone is not dead forerver lol =S
EDIT : Yes!! I have recovered my phone ^^ Made a research and found this thread : http://forum.xda-developers.com/showthread.php?t=924945
With the home+Back+power button trick, it is perfect!
Anyway, thanks for your tuto!!
Reuberts said:
Thanks for answering so fast! ^^
But i cant get my phone in flashmode, thus i cant flash it with a new rom ?
i hope my phone is not dead forerver lol =S
EDIT : Yes!! I have recovered my phone ^^ Made a research and found this thread : http://forum.xda-developers.com/showthread.php?t=924945
With the home+Back+power button trick, it is perfect!
Anyway, thanks for your tuto!!
Click to expand...
Click to collapse
GREAT
I´m not familiar with mini, so...
Reuberts said:
Hello =)
Thanks for your work! First, my english isn't very rich so dont blame me if i make some mistakes =S
So i tried to activate JIT after rooting my x10 mini using your flashtool. Everything was right until the reboot. It is said in other forum the reboot would take at least 5min but in my case, it took more than 1hour!!
So now i'm stuck on the SE logo for more than 2 hours (lol). Can anyone help me solving this problem please?
Thanks !
Click to expand...
Click to collapse
this is same thing happening to me too, i used flash tool earlier (2 hours earlier), now i rooted and optimized my mini, it rebooted and is stuck at SE Logo, i guess JIT is not correctly integrated in mini through this tool, am re flashing now...
ahub1988 said:
this is same thing happening to me too, i used flash tool earlier (2 hours earlier), now i rooted and optimized my mini, it rebooted and is stuck at SE Logo, i guess JIT is not correctly integrated in mini through this tool, am re flashing now...
Click to expand...
Click to collapse
i`ll check that with the DEV
thks for feedback
hi people !
i tryed flashing my x10 mini with this manual. but process is wery slowly. from 2 houwers i flashing only: kernel, amms, fota and dsp... This is only 40 Mb... The system files is 230 MB. My buttery can't working more then 4-5 howers when phone is flashing, how i can flashing qucly? May be i do something wrong?
Win 7 32bit, releases of fireweare and flashtool is latest from this site.
Hey dude, I think you might be trying to flash the X10 firmware on you mini... not a good idea... (as the X10 firmware is way bigger and won't fit on a mini, not that it would work even if it did fit )
I suggest downloading the right version for your phone.. a mini is an E10i/a and a pro is a U20i/a
and @Rendeiro.
Thanks for adding the warning to the top of the Noob guide should save us some headaches until the new version is out and working (then we can work on a mini instruction set.. seems a waste of time re writing it until the new version is released)
you da man!
Kiwi
kiwiBratwurst said:
Hey dude, I think you might be trying to flash the X10 firmware on you mini... not a good idea... (as the X10 firmware is way bigger and won't fit on a mini, not that it would work even if it did fit )
I suggest downloading the right version for your phone.. a mini is an E10i/a and a pro is a U20i/a
and @Rendeiro.
Thanks for adding the warning to the top of the Noob guide should save us some headaches until the new version is out and working (then we can work on a mini instruction set.. seems a waste of time re writing it until the new version is released)
you da man!
Kiwi
Click to expand...
Click to collapse
[MOD][rendeiro2005]Cyanogen6.1.1_v03
I''m having the following error when trying to start flashtool, any idea's?
java.lang.NullPointerException
at gui.FlasherGUI.initLogger(FlasherGUI.java:112)
at gui.FlasherGUI.main(FlasherGUI.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
Click to expand...
Click to collapse
My only question is:
I want to flash a E10i (2.1.1.A.0.6) firmware on my E10a (2.0.A.0.504) firmware.
My phone is a Xperia X10 Mini (not a PRO). Can i use this FlashTool to do it? Will i get any trouble with it?
The flashtool is an universal x10 tool. It was build to work on every x10 family, so yes. Use at your will
mmota13 said:
My only question is:
I want to flash a E10i (2.1.1.A.0.6) firmware on my E10a (2.0.A.0.504) firmware.
My phone is a Xperia X10 Mini (not a PRO). Can i use this FlashTool to do it? Will i get any trouble with it?
Click to expand...
Click to collapse
Sent from my X10i using XDA App
Hi... I have this problem, first my phone is an xperia x10 mini pro, ok i use the U20i NLU20i ITA - Thks to ginoscopesce for this one, but now my phone is carrier locked to Italy i guess. What can i do cause now is only a music player i cant use my SIM card. Thanks.
Flash Tool From GITHUB doesn't work
please delete

[Q] Do you have the original x10 keyboards to install??

Does anyone know where to find the original x10 keyborads, including the japanese and korean keyboards?
Please reply me with links or attach files.
Thanks.
I tried looking, I hope this one is it.
Put it in the system/app folder and reboot
Credit: http://forum.xda-developers.com/showpost.php?p=10192482&postcount=7
Thanks for your attachment.
I tried the file already, it is not the original x10 keyboard......
I am looking for the keyboard from the latest firmware.
Thanks again.
darkgoth678 said:
I tried looking, I hope this one is it.
Put it in the system/app folder and reboot
Credit: http://forum.xda-developers.com/showpost.php?p=10192482&postcount=7
Click to expand...
Click to collapse
Thanks for your attachment.
I tried the file already, it is not the original x10 keyboard......
I am looking for the keyboard from the latest firmware.
Thanks again.
Wouldn't it be eaiser if you backed up all your stuff and flashed 1.6? It would give you all those keyboards.
Or you could find a 1.6 rom and just look through it till you found the keyboards
Sent from my X10i using XDA App
darkgoth678 said:
Wouldn't it be eaiser if you backed up all your stuff and flashed 1.6? It would give you all those keyboards.
Or you could find a 1.6 rom and just look through it till you found the keyboards
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I would do that if I know where to look for those keyboard and how to pull them out as apk files.
found something at japanese site
i think its from arc but almost same as x10's kb.
wait a bit...
hotfile.com/dl/107798359/85de580/309_newpobox.zip.html
flash this with xrecovery
worked for me
edit:screenshot attached
Sent from my X10 using XDA App
forgot to post...
i'm using J's cm7.0 rc2 v10.
custom fonts applied.
the site says it should work with 2.1 or 2.2...but im not sure.
utubo_sk8 said:
forgot to post...
i'm using J's cm7.0 rc2 v10.
custom fonts applied.
the site says it should work with 2.1 or 2.2...but im not sure.
Click to expand...
Click to collapse
Thanks alot!!
Now I just need the korean keyboard~~

[SOLVED] force update by editing build.prop, Also: [WIP] list of CDA strings!

Hi all,
I was fed up with waiting for an official update for my branded SK17i (with azerty keyboard so I couldn't just flash the generic global and anyway, I rather wanted an update through SEUS).
So I found out that it's possible to fool SEUS into thinking your phone belongs to another region by editing the region codes (CDA strings, they're called, apparently) in /system/build.prop
Prerequisites: only a rooted phone and a way to read and change files in the system directories (either via ADB or via a root file explorer like ES file explorer which I used). No need to unlock bootloader as seems to be required for other flashing methods!
So for those of you who wish to try the same, I'll try and compile a list of region codes. Feel free to post your region code (it can be found in /system/build.prop)
and I'll add it to this list!
PHONE: Mini Pro - SK17
1251-0622 - Generic - French - AZERTY
1250-5673 - Mobistar - Belgium - AZERTY
1254-0468 - Generic - Belgium - AZERTY (thanks to Swimon)
1248-7407 - Generic UK - QWERTY (thanks to Raph4)
1249-8051 - Generic Baltic - QWERTY (thanks to Raph4)
1249-8044 - Generic Nordic 1 (SE/FI) - QWERTY (thanks to Raph4)
1249-8053 - Generic Nordic 2 (NO/DK/IS) - QWERTY (thanks to Raph4)
1250-2159 - Generic Iberic - QWERTY (thanks to Raph4)
1250-0859 - O2 UK - QWERTY (thanks to Matchstick)
1249-1887 - Generic - German - QWERTZ (thanks to Ragalthar)
A whole list of SK17i codes(thanks to koperta4512)
Phone: Live With Walkman - WT19
1254-1864 - Czech: T-Mobile (thanks to strby)
A whole list of WT19i CDA codes(thanks to boyq)
Phone: Mini - ST15
A whole list of codes(thanks to koperta4512)
Phone: Arc - LT15
A whole list of codes(thanks to koperta4512)
Phone: Active - ST17
A whole list of codes(thanks to koperta4512)
Phone: Ray - ST18
A whole list of codes(thanks to koperta4512)
Phone: Neo V - MT11
A whole list of codes(thanks to koperta4512)
Phone: Neo - MT15
A whole list of codes(thanks to koperta4512)
Phone: Arc S - LT18
A whole list of codes(thanks to koperta4512)
Explanation of the country codes in the links found above: Here, thanks to MSTHETERROR
NOTE: while this fools SEUS into doing a firmware upgrade to a localized firmware, it is of course possible to just accept having a generic world firmware, and to just set the language of your hardware keyboard (see this guide here: http://forum.xda-developers.com/showthread.php?t=1224511 )
(below is the original post)
Hi,
is there any way to fool my Xperia Mini Pro (or PC Companion) into thinking it should be a generic French phone instead of a Mobistar Branded one?
I'm fed up with waiting for an update to .58 while everyone else has got it, and I'm not willing (at this time) to unlock the bootloader in order to flash with flashtool.
Maybe there's a text file somewhere that can be edited so the phone thinks it's an unbranded one?
My phone:
Belgium - Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: changed into 1251-0622 which should be generic french...
Click to expand...
Click to collapse
dryhte said:
Hi,
is there any way to fool my Xperia Mini Pro (or PC Companion) into thinking it should be a generic French phone instead of a Mobistar Branded one?
I'm fed up with waiting for an update to .58 while everyone else has got it, and I'm not willing (at this time) to unlock the bootloader in order to flash with flashtool.
Maybe there's a text file somewhere that can be edited so the phone thinks it's an unbranded one?
Click to expand...
Click to collapse
Use wotanserver!
Gustavo RD78 said:
Use wotanserver!
Click to expand...
Click to collapse
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Peppoid said:
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Click to expand...
Click to collapse
Only dont put WT19i because then you will recieve the WT19i update
dumraden said:
Only dont put WT19i because then you will recieve the WT19i update
Click to expand...
Click to collapse
Lol
Don't worry, in your build.prop will be the right device written
If this should work, we could open a thread like that
Peppoid said:
Hi. As the mate writes upstairs, this one is a solution.
There's another one. It worked in X10 Eclair times.
Try editing your build.prop file. Look in /system/build.prop.
Open it with RootExplorer and edit ro.semc.version.cust=xxxx-xxxx and ro.product.name=WT19i_xxxx-xxxx where x are your region firmware brand.Mine is 1254-1854, German.
Then edit the ro.semc.version.cust=xxxx-xxxx file in /system/etc/customization/settings/cust.prop
Save and exit for every file you modded.
Reboot your phone. Turn off and use SEUS.
I hope it works
Click to expand...
Click to collapse
Ok, so:
Code:
Belgium: Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: Since I couldn't find any other product names around, I decided to give Wotanserver a try... however, upon downloading the client, it continually tells me it's old and needs to update. Anyone around who used it before?
oh, and by the way, if anyone has a non-mobistar belgian AZERTY mini pro (with .58 firmware), please share your region code with me I'd love to have normal OTA updates working...
dryhte said:
Ok, so:
Code:
Belgium: Mobistar branded:
ro.product.name=SK17i_1250-5673;
ro.build.fingerprint=SEMC/SK17i_1250-5673/SK17i:2.3.3/4.0.A.2.335/sPb_3w:user/release-keys
EDIT: Since I couldn't find any other product names around, I decided to give Wotanserver a try... however, upon downloading the client, it continually tells me it's old and needs to update. Anyone around who used it before?
oh, and by the way, if anyone has a non-mobistar belgian AZERTY mini pro (with .58 firmware), please share your region code with me I'd love to have normal OTA updates working...
Click to expand...
Click to collapse
Hope it works. Give a try.
Bye
Peppoid said:
...
Hope it works. Give a try.
Bye
Click to expand...
Click to collapse
Peppoid, I don't think that will work unless you phone is specifically Belgian? (you don't have a SK17 either)
I don't want to end up with a QWERTY layout instead of my AZERTY keyboard... (I know I should have chosen a QWERTY phone instead, but hey, 70€ cheaper tickled my fancy )
I have a belgian Mini too (sk15i), it's unbranded and the software version is also .42 and not .58!
I think the software update is just not released for our region.
Crossing my fingers now... I found that 1251-0622 is generic french; I updated all occurrences of the location code in build.prop and now SEUS is downloading an update. We'll soon know if the azerty for FR is the same as for BE And we know now that editing build.prop works if we want to fool SEUS into thinking we're in another region.
Well, it worked so now let's start and compile a list of region codes known to work! If you reply to this post with your region code and hardware keyboard layout (QWERTY/QWERTZ/AZERTY/DVORAK ) I'll add them to the first post!
LOL - nobody interested in building this list? It's an additional way of getting newer firmwares on your phone B-) apparently this was quite a popular topic in the Xperia X10 forum...
Sent from my SK17i using XDA App
X10 who?
Hey, nice job!
I'd love to get the code for the Latin America region.
What's the difference of updating with SEUS and PC Companion?
Thanks!
tianGO said:
Hey, nice job!
I'd love to get the code for the Latin America region.
Click to expand...
Click to collapse
Maybe someone is so good to share it with us
tianGO said:
What's the difference of updating with SEUS and PC Companion?
Click to expand...
Click to collapse
My guess is that it should be exactly the same... Except that seus does nothing else than updates/restores whereas pcc tries to be everything to everyone ;-)
Sent from my SK17i using XDA App
Hey,
after long searching i'm glad to have found this post. I also have a branded phone of Mobistar and still stuck on 4.0.A.2.335 and i've tried everything described in this post, but i'm unable to succeed...
Things i've done:
- rooted my phone with Root / Unroot Sony Ericsson Xperia 2011 v1.5 (http://forum.xda-developers.com/showthread.php?t=1346198)
- installed ES File explorer and located the build.prop file
but i can't save the file and i'm unable to change the file permissions.
Can anyone help and tell me what i've done wrong???
Many thx in advance
fredgoddeeris said:
Hey,
after long searching i'm glad to have found this post. I also have a branded phone of Mobistar and still stuck on 4.0.A.2.335 and i've tried everything described in this post, but i'm unable to succeed...
Things i've done:
- rooted my phone with Root / Unroot Sony Ericsson Xperia 2011 v1.5 (http://forum.xda-developers.com/showthread.php?t=1346198)
- installed ES File explorer and located the build.prop file
but i can't save the file and i'm unable to change the file permissions.
Can anyone help and tell me what i've done wrong???
Many thx in advance
Click to expand...
Click to collapse
I'm at work atm so can't go into too much detail, but what I did is:
- copy the build.prop file with es file explorer to my sd card
- edit it while connected to my pc & save
- make sure my es file explorer has root access (check settings, maybe there's a flag that must be set first)
- copy back the build.prop file (I didn't change any file permissions IIRC)
dryhte said:
I'm at work atm so can't go into too much detail, but what I did is:
- copy the build.prop file with es file explorer to my sd card
- edit it while connected to my pc & save
- make sure my es file explorer has root access (check settings, maybe there's a flag that must be set first)
- copy back the build.prop file (I didn't change any file permissions IIRC)
Click to expand...
Click to collapse
THX SO MUCH !!!!
was finally able to update
stupid Mobistar...
fredgoddeeris said:
THX SO MUCH !!!!
was finally able to update
stupid Mobistar...
Click to expand...
Click to collapse
;-)
Sent from my SK17i using XDA App
Hi,
as I promised (but with some delay )
hope it will help you.
'cause I'm not really sure what you're trying to achieve. Could you maybe explain it one more time?
swimon said:
Hi,
as I promised (but with some delay )
hope it will help you.
'cause I'm not really sure what you're trying to achieve. Could you maybe explain it one more time?
Click to expand...
Click to collapse
Okay, so if you edit this build.prop file (and just change the CDA code, in your case 1254-0468, to another existing SK17I code) you can fool SEUS into thinking that you have a phone from another region or operator, and give you another firmware than you would've gotten, or even give you an update even while none was available for you. Not useful for you, but very useful for people with a branded phone like me, who want to debrand or just update it.
Sent from my SK17i using XDA App

Categories

Resources