[Q] last update for Multi-Touch from SE - XPERIA X10 Q&A, Help & Troubleshooting

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...

Related

New debrand method for 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????????

[Q] Help¡¡¡ My X10 stuck at sony ericsson screen

Hi , im such an idiot i was tying to change my xperia x10 theme , overwriting the framework.res.apk with rootmanager but i forgot to set the correct permisions , then my phone rebooted itselft and got stuck at the sony ericsson screen , i tried to flash again the process goes ok but when i tried to turn it on again , it's still stuck at SE screen ; please help me i dunno what to do :S
New info . i tried every 2.1 firmware with no luck , but i downgraded to 1.6 and then flashed to 2.1 again and it worked , if any1 have this problem add me to msn [email protected] , TY
Glad you sorted it out. In future questions like this should be posted in q and a section.
Sent from my X10i using XDA App
The framework can't be copied over, it needs to be pushed and installed.
XperiaX10iUser said:
The framework can't be copied over, it needs to be pushed and installed.
Click to expand...
Click to collapse
I always done theming by root explorer without problem :/
soulz3r0 said:
New info . i tried every 2.1 firmware with no luck , but i downgraded to 1.6 and then flashed to 2.1 again and it worked , if any1 have this problem add me to msn [email protected] , TY
Click to expand...
Click to collapse
How did you downgrade?
How did you downgrade?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=683793
Or...
You could just flash again only using system.bin and everything you had would be there.
;-)
You also will need loader.sin
I did this a couple of times and work for me; I only need to root again
Good luck!
PS: In the firmware folder, you need to leave ONLY this 2 files: System.sin and loader.sin. Backup and delete all other files like amss.sin, cache.sin, etc.

[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

[HELP] Q&A Thread - MUST POST ALL QUESTIONS HERE

In an effort to keep the thread clean with developments and ROM's due to the fact we dont have a general section either this thread has been opened for all the support and help questions that people ask.
Please use this thread for all GENERAL SUPPORT questions regarding the RAY, this will keep our thread clean and easy for everyone to find ROM's and THEME's
Once you have asked please await someone to help and please thank them after by hitting thanks
We all need to keep our thread clean
Now including ROM LIST
Chiefy's Miui
Miui by iriijo
aire 4pda
CM7.2.0 FXP
Miui by Seatone
MiuiV4 iriijo
CM9 FXP
ICS by szl.kiev
RayOnium
Kernels and themes to be added
(if your rom is not listed here please pm me and I will add it)
Hello, Thnx so much for this thread.. i like the stock sms app in ray but the txt is so small. Is there a way to enlarge them? Thanks for your help. Waiting for the response...
nightwing_sw said:
Hello, Thnx so much for this thread.. i like the stock sms app in ray but the txt is so small. Is there a way to enlarge them? Thanks for your help. Waiting for the response...
Click to expand...
Click to collapse
None that i know of. Maybe with some apk editing we can fix that, but i don't know. Ray's screen is too perfect that all the text is too small..
nightwing_sw said:
Hello, Thnx so much for this thread.. i like the stock sms app in ray but the txt is so small. Is there a way to enlarge them? Thanks for your help. Waiting for the response...
Click to expand...
Click to collapse
You can use a third party app and customise everything
Hi all. I am really excited to install custom ROM in other thread. But I don't want to lose my apps and settings. Is there a way to backup and restore them after flashing? You know, need not an hour to do that. Thanks.
Sent from my ST18i using XDA App
Ridho1 said:
Hi all. I am really excited to install custom ROM in other thread. But I don't want to lose my apps and settings. Is there a way to backup and restore them after flashing? You know, need not an hour to do that. Thanks.
Sent from my ST18i using XDA App
Click to expand...
Click to collapse
You can download an app from the market such as titainium backup or my backup, that will back up all your apps and data, once you install your rom download the app from the market again and restore. All of your apps will be restored
There are a few paid and none paid apps in market, I use paid version of titainium backup but i have used my backup in the past
nightwing_sw said:
Hello, Thnx so much for this thread.. i like the stock sms app in ray but the txt is so small. Is there a way to enlarge them? Thanks for your help. Waiting for the response...
Click to expand...
Click to collapse
if your phone is rooted, you can edit file /system/build.prop. at string ro.sf.lcd_density=240 (9 from bottom) and change density to 260 or 280, than ALL text elements will slightly bigger. need reboot after changing.
Well frankly i don't think the messaging fonts are smaller... It's quite comfortable...
That lcd build.prop method was very common in Sensation section... but there we used to decrease it to 204 and with that you get 5x5 application drawer inn HTC sense...,don't know how it will behave here...
secondly, users reported that some market applications show incompatible if you change lcd density...
chiefy009 said:
You can download an app from the market such as titainium backup or my backup, that will back up all your apps and data, once you install your rom download the app from the market again and restore. All of your apps will be restored
There are a few paid and none paid apps in market, I use paid version of titainium backup but i have used my backup in the past
Click to expand...
Click to collapse
or use Astro File Manager to backup your apps, it's free though
and download the latest version
Hi Gents
I have my phone rooted with unlocked bootloader and i use stock rom .42 with Doomkernel.
Now when I connect my Ray to PC, PC Companion says that new firmware is available for my phone (.62). Do you know what would happen if I would start updating through PC Companion? Brick? Loosing root? Nothing? Simply updating? What is your oppinion about that? Thanks for support.
Mylow777 said:
Hi Gents
I have my phone rooted with unlocked bootloader and i use stock rom .42 with Doomkernel.
Now when I connect my Ray to PC, PC Companion says that new firmware is available for my phone (.62). Do you know what would happen if I would start updating through PC Companion? Brick? Loosing root? Nothing? Simply updating? What is your oppinion about that? Thanks for support.
Click to expand...
Click to collapse
Don't.think.you get brick doing it by.USB only.over the air.
My.bootloader is unlocked when I tired to update it told me I couldn't as running a moddified rom?
sent from my gorgeus Xperia Ray
I'd recommend reverting to stock form again(relock bootloader, unroot, stock firmware), then update
better safe than sorry
Any stable CM7 and MIUI ROM with fully wOrking everything in this Section?
ICS for Xperia Ray
HI Guys,
I am planning to buy Xperia Ray, but i didn't find any ICS custom ROM for this.
so here are my questions:
1. Will Sony Ericsson port ICS on this phone ?
2. Is there any ICS custom ROM for this set ?
Thanks in advance.
alidsd said:
HI Guys,
I am planning to buy Xperia Ray, but i didn't find any ICS custom ROM for this.
so here are my questions:
1. Will Sony Ericsson port ICS on this phone ?
2. Is there any ICS custom ROM for this set ?
Thanks in advance.
Click to expand...
Click to collapse
There will be ICS on March/April this year. Don't fret. There are some beta/Alpha ROM here on MIUI version and CM 9 version.
has anyone been successful in using link2sd?
Changing launcher
hey guys,
i´m having some trouble with changing the launcher components....
according to THIS:
monkeytown said:
hey,
habe euch hier mal meinen veränderten arc launcher hochgeladen......vllt. hat ja jemand interesse
screens:
1
2
3
4
ansich wurden nur der homebutton, dock und die folder icons geändert
Click to expand...
Click to collapse
i already did it some time ago...but now i can´t get it to work again and this file doesn´t exist anymore
my steps are:
- open .apk in betterzip
- take out some .png and change it
- replace the .png
- save the .apk
- sign it
- install
- error, app not installed
i did some searches and found something about deleting the files of the "META-INF" folder, but that didn´t work either
i guess it´s related to the launcher not just being a launcher but also a system-file or something
so...what am i doing wrong?
yujin_11 said:
I'd recommend reverting to stock form again(relock bootloader, unroot, stock firmware), then update
better safe than sorry
Click to expand...
Click to collapse
Hi, and is there any way to relock the bootloader if it was unlocked through the "official" way? If there is can someone link it which is the safe? Thanks
monkeytown said:
hey guys,
i´m having some trouble with changing the launcher components....
according to THIS:
i already did it some time ago...but now i can´t get it to work again and this file doesn´t exist anymore
my steps are:
- open .apk in betterzip
- take out some .png and change it
- replace the .png
- save the .apk
- sign it
- install
- error, app not installed
i did some searches and found something about deleting the files of the "META-INF" folder, but that didn´t work either
i guess it´s related to the launcher not just being a launcher but also a system-file or something
so...what am i doing wrong?
Click to expand...
Click to collapse
Just put the apk in system/app change permission to rw-r-r and restart.
you mean copy / paste with a file manager or install??
and why change the permission? the original launcher has other permissions (i´m just curious)
/e: oh ****, it worked
thx man!
can it do it the same way when modding the framework-res.apk?

HELP PLS

Hi, please I need sk17i .ftf file of version 4.0.2.A.0.xx GERMAN.(orAUSTRIAN) (doesn`t mater if is Vodafone, Orange...etc)
Pleas I want to flash this to my phone!
Please HELP!
Why do you need sepcial german version? Just flash the one in someguyfromhells thread (which is pinned) and set language to german. Everything is working very good, even if this is a hungarian version
Sent from my SK17i running Jelly Bean via CM10
mihahn said:
Why do you need sepcial german version? Just flash the one in someguyfromhells thread (which is pinned) and set language to german. Everything is working very good, even if this is a hungarian version
Sent from my SK17i running Jelly Bean via CM10
Click to expand...
Click to collapse
because I have qwertz keyboard and I know about the xperiakeyboard app in the forum, but it doesn't work in google search widget!
But you can replace keyprint.xml, afterwards you will have qwertz, too. Just search on google for xperia mini pro qwertz keyprint.xml. There should be a one on android-hilfe.de you can download and replace the current one with the new for qwertz. For that you must have a rooted device.
So flash 4.0.2.A.0.42, root it, open root explorer, copy the downloaded keyprint.xml and replace the old one, unroot and update over the air to 4.0.2.A.0.62 (only do the ota update with locked bootloader).
Or is your problem a different one regarding the hardware keyboard?
Sent from my SK17i running Jelly Bean via CM10
I dit that , but still in my google search widget it doesn`t work!
Please I need a german/Austrian version!!!
you may try this. my sk17i works with this firmware but its .431 not the latest .587 firmware
jobayer said:
you may try this. my sk17i works with this firmware but its .431 not the latest .587 firmware
Click to expand...
Click to collapse
There's no german verison...
lupascu69 said:
I dit that , but still in my google search widget it doesn`t work!
Please I need a german/Austrian version!!!
Click to expand...
Click to collapse
On which software version are you currently on?
Could you please upload a screenshot, because it should work. Or try clear data of the google search and reboot, it must work I'm from germany, too, and I used this stock 4.0.2.A.0.42/62/69 firmware for a long time and everything worked great...

Categories

Resources