Related
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????????
Hi,
did any one have the last update from SE for Multi-Touch ?
I tryed to change the No. in build.prop file to
1238-6349
and i updated my x10 with update service again
now i have multi-touch but the market is gone
if any one have this update pls give me the nombers of build.prop file
Genaric, Global or Nordic
waiting for you guyz
really this update very important for me coz it has Arabic font without any problem
try this thread: HERE
Tehouster said:
try this thread: HERE
Click to expand...
Click to collapse
thanks any way
but
u didnt get my point
i want to ask did any one has the update with this build Number
2.1.A.0.435
if it does i want the build.prop file
try here instead... http://forum.xda-developers.com/showthread.php?t=933920
Ghaith Alshareef said:
Hi,
did any one have the last update from SE for Multi-Touch ?
I tryed to change the No. in build.prop file to
1238-6349
and i updated my x10 with update service again
now i have multi-touch but the market is gone
if any one have this update pls give me the nombers of build.prop file
Genaric, Global or Nordic
waiting for you guyz
really this update very important for me coz it has Arabic font without any problem
Click to expand...
Click to collapse
search, search, search...
go HERE follow HOT-TO HERE
search, search, search...
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
6.0.A.3.73 CE1
Hi everyone
I just updated my phone thruu Update Service to .73 and done by FlashTool an FTF file.
This FIRMWARE have a great thing in "Messages" an option (Cost saving) to convert special characters to send more text in each text message.
it just converts letters like : ą ł ż etc to plain a l z . in that way it will not take so many space in message,and u can send more text
Thats the difference what i have notice from generic UK (maybe other countries dont have this too )
This is the cleanest version .
it dont have :
Music Unlimited ,Video Unlimited and bloatware.
and the rest : WisePilot ,antyvirus ,top contacts etc u can just uninstall.
I hope so i have done it in right way, that was my first time xd : take 2 biggest files from Update Service blob folder ,in flashtool select decrypt , (moved all files ,( *.sin) )...and thats it , it was ready in flashtool firmware folder :>
I have uploaded this to MediaFire in 3 parts RAR (use WinRar or other soft to extract)
packed size : 266MB , unpacked : 490.356 KB
Correct FTF .removed partition-image.sin
I have flashed this FTF to my xperia S and it WORKS for 100 %
links :
http://www.mediafire.com/?lej8hf4ii05k67z
http://www.mediafire.com/?kieip5ia3esdk6d
http://www.mediafire.com/?tv110g0jghh2bs4
Note: I'm providing this as it is and I'm not responsible if something goes wrong! Flash it at your own risk!!
Have a good weekend
This has already been posted by lollylost100.
http://forum.xda-developers.com/showthread.php?t=1593814
Should have posted in this thread?
Excuse me? dont u see this is the .73 version? xd
It is even in RED colour at begining
edit: erm hm maybe the title is a bit confusing , shame that i cant change it now . :/
augie7107 said:
This has already been posted by lollylost100.
http://forum.xda-developers.com/showthread.php?t=1593814
Should have posted in this thread?
Click to expand...
Click to collapse
This is for generic firmware 73. The link you are referring to is for generic firmware 67. Therefor it requires a separate thread.
Sent from my LT26i using Tapatalk 2
would this work in the uk?
andoridkiller said:
would this work in the uk?
Click to expand...
Click to collapse
mate i LIVE in Nottingham and it works perfectly :>
I got the following error when trying to flash this image:
13/006/2012 18:06:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0076";ERR_DYNAMIC="failed to set ta config";
HighHo said:
I got the following error when trying to flash this image:
13/006/2012 18:06:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0076";ERR_DYNAMIC="failed to set ta config";
Click to expand...
Click to collapse
Same here...
HighHo said:
I got the following error when trying to flash this image:
13/006/2012 18:06:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0076";ERR_DYNAMIC="failed to set ta config";
Click to expand...
Click to collapse
hm now i have compared with SG version , what is inside , so my have 1 new file partition-image.sin
it should be here? xd i have selected all files (when decrypting) .so donno .
just a second i wil try something .
edit : i have corrected this , i have removed this partition -image.sin ,becouse it was stoping at this point of flashing xd
i have flashed this FTF file to my device , and it WORKS
btw .i havent know about that partition file xd
UPLOADED new links
augie7107 said:
This has already been posted by lollylost100.
http://forum.xda-developers.com/showthread.php?t=1593814
Should have posted in this thread?
Click to expand...
Click to collapse
First read, know it, then speach.
---
Thanks for the firmware!
Just to confirm, new uploaded image does work.
Thanks.
So if I flash a new firmware. Will I lose root? I am currently using the .67 provided in the sticky.
Yes, you would lose root, someone I'm sure will soon make a root image from this file. Alternatively you can add root yourself there's some posts already that explain how to do it. Unfortunately I don't have an unlocked bootloader to create the required image.
xshunin said:
So if I flash a new firmware. Will I lose root? I am currently using the .67 provided in the sticky.
Click to expand...
Click to collapse
Hey. Yes u will lose root , but probarly u can root again, there was somebody explaining that here on dev xd
Sent from my LT26i using XDA
HighHo said:
Just to confirm, new uploaded image does work.
Thanks.
Click to expand...
Click to collapse
Thanks, good to know that ;-)
Sent from my LT26i using XDA
Downloading and rooting
HighHo said:
Yes, you would lose root, someone I'm sure will soon make a root image from this file. Alternatively you can add root yourself there's some posts already that explain how to do it. Unfortunately I don't have an unlocked bootloader to create the required image.
Click to expand...
Click to collapse
Ah okay! I think I saw that thread as well but I need to search for it~
xshunin said:
Ah okay! I think I saw that thread as well but I need to search for it~
Click to expand...
Click to collapse
can you post the link ,please?
thanks
i feel its a bit slow on my device
If I can find it sure~
Sent from my Xperia S
Hi,
Recently I tried some MODs from mini/minipro/active subforum. I dont know which exactly but I assume one of this mods changed my system information from my original Sony Ericsson Live with Walkman to Xperia Arc that is displayed on my settings>about menu.
Even Sony Pc companion is showing my device as xperia arc instead of Live with walkman wt19i.
See attachment
How can I fix it?
Edit /system/build.prop, probably ro.product.id or something similar, or just copy the whole build.prop from the rom you started with.
Sent from my cm_tenderloin using Tapatalk 2
Noob friendly description please?
dihan91 said:
Hi,
Recently I tried some MODs from mini/minipro/active subforum. I dont know which exactly but I assume one of this mods changed my system information from my original Sony Ericsson Live with Walkman to Xperia Arc that is displayed on my settings>about menu.
Even Sony Pc companion is showing my device as xperia arc instead of Live with walkman wt19i.
See attachment
How can I fix it?
Click to expand...
Click to collapse
while u try some mods, there must be mod which is replacing/edit your build.prop located here: /system/build.prop
here is my lww backup
ro.build.display.id is the one which shown on about phone CMIIW
not sure which string that detected by PC Companion
rheezz said:
while u try some mods, there must be mod which is replacing/edit your build.prop located here: /system/build.prop
here is my lww backup
ro.build.display.id is the one which shown on about phone CMIIW
not sure which string that detected by PC Companion
Click to expand...
Click to collapse
I dont know how to start with the text file you gave me. But thanks anyway
search for build.prop editor on market.
take a look at the original build.prop (with a text viewer) and spot where the phone model is mentioned.
then using the editor change the same lines to the ones using the values from the original.
save and reboot
Sent from my WT19i using Tapatalk 2