[Req] Porting SDE Contact and Conversation App to CM7 Roms

[Req] Porting SDE Contact and Conversation App to CM7 Roms - XPERIA X8 Themes and Apps

Can Any One port these app to cm7 rom ?
i like these app intarface but i perefer to use cm7 stable and smooth rom so i dont want use sde .
sorry for bad english

Phonebook.apk, contactsimport.apk
These are the apk you need, just put them in any cm7 Rom and they'll work without modifying
"Searching is like eating: If you don't do it you'll die"©X8invisible

X8invisible said:
Phonebook.apk, contactsimport.apk
These are the apk you need, just put them in any cm7 Rom and they'll work without modifying
"Searching is like eating: If you don't do it you'll die"©X8invisible
Click to expand...
Click to collapse
I think they have some dedicated libs but not 100% sure.

You need to pulling some framework and permission i forgot what are they.
You may copy all the framework and permission from SDE. But it risky replacing from original cm7 framework and permissions.
Sent from my E15i using xda app-developers app

X8invisible said:
Phonebook.apk, contactsimport.apk
These are the apk you need, just put them in any cm7 Rom and they'll work without modifying
"Searching is like eating: If you don't do it you'll die"©X8invisible
Click to expand...
Click to collapse
It didnt work
even i ranamed it to contact.apk but not work .
please port this like old phone.apk from se that ported to many rom like gingerxperia .

esirad said:
It didnt work
even i ranamed it to contact.apk but not work .
please port this like old phone.apk from se that ported to many rom like gingerxperia .
Click to expand...
Click to collapse
Two possible way exists.
Method 1: need to remap all resource link in the decompiled se app to match with the actual framework, and need to insert the missing resources into the framework. This method give a result what compatible with the specified rom.
Method 2: need to inject all required global resource into the app. This method give a result what compatible with all rom, but the app will contain a lot of redundant elements, what already exists in the rom (with different id).
In both method: you can find the required permissions and vendor specific framework files list in the androidmanifest.xml

pilu1978 said:
Two possible way exists.
Method 1: need to remap all resource link in the decompiled se app to match with the actual framework, and need to insert the missing resources into the framework. This method give a result what compatible with the specified rom.
Method 2: need to inject all required global resource into the app. This method give a result what compatible with all rom, but the app will contain a lot of redundant elements, what already exists in the rom (with different id).
In both method: you can find the required permissions and vendor specific framework files list in the androidmanifest.xml
Click to expand...
Click to collapse
I am noob so i cant do anything.
what about your rom that port se app to cm7 roms? plz make it with 2.1 stock look .
SDE not stable and smooth .

esirad said:
I am noob so i cant do anything.
Click to expand...
Click to collapse
A detailed example:
In this example I describe how to modify the contacts app from ST15 4.0.2.A.0.42 to work on MiniCM7 2.2.1
Needed:
Framework-res.apk from MiniCM7 2.2.1
Framework-res.apk from official ST15 4.0.2.A.0.42
Phonebook.apk from official ST15 4.0.2.A.0.42
Decompile these apps. To decompile the phonebook.apk need add the SemcGenericUxpRes.apk with the "if" (install framework) parameter in apktool.
In the decompiled code of contacts app (the smali folder) use your best friend: the grep command. You can use any GUI for this tool (for example in windows: Wingrep32).
How to identify the resource identifiers in the code?
Search with grep:
const v
You will get a lot of results. What you need? the global resources ids in the code is a 32bit hexadecimal number.
The global resource ids in this form: 010xyyyy
Where is 010 the marker of global id, x=the resource type (1=attribute, 2=identifier, 3=style, 4=string, etc...) yyyy=the identifier of the resource in the group)
The local resources is similar form: 7f0xyyyy where is 7f0 the marker of local resource, x and yyyy is same.
What do you need?
Check all global resource id with this method:
When you found a global id, for example in a line:
const v1, 0x104000a
search this id in the decompiled 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 104000a equal with: type=string, name="ok"
Check in in the decompiled MiniCM7 2.2.1 framework-res/res/values/public.xml file
You can see: the string named "ok" in the MiniCM7 framework have similar identifier: 0x104000a Now you can happy, the ids equal nothing to do...
Proceed with the next value:
For example you found this line:
const v0, 0x10402be
Check it again in the 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 0x1042be is a string, named: contact_status_update_attribution_with_date
Search this value in the MiniCM7 2.2.1 framework-res/res/values/public.xml file, and you can see: the string exists, BUT different id, the contact_status_update_attribution_with_date string have id: 0x10402a5
Now you must change the id in the contacts app, change all 10402be to 10402a5 in all smali file.
And make it with all global resource id in the app...
If you found a global resource link in the app what not exist in the MiniCM7 resources, you must do it:
For example you found a string, what not exist in minicm
1. copy it from the public.xml (from the 4.0.2.A.0.42 framework-res)
2. go to the last string in the public.xml (in the MiniCM7 framework-res)
3. add the copied line
4. modify the resource id to the last id in MiniCM+1 (in the unmodified MiniCM7 the last string is "symbol_picker_gt" with the id: 0x010403fe. The first added string must be: 0x010403ff, the 2nd must be 0x01040400, the 3rd must be 0x01040401, etc...)
5. Depends on resource type (attr, bool, string, etc...) YOU MUST copy the missing resource. For example if you add a missing resource id into the public.xml what is a string, must copy the line from strings.xml into the strings.xml of MiniCM.
This is the first method
In the second method add all resources with missing or different identifier in the public.xml of the contacts app with a local id (started with 7f0xyyyy), and insert the missing strings, styles, etc INTO the APP.
And finally, you must check the resource calls in the layout files. This is much easier.
In the layout file, the local resources marked with @resourcetype, the global resources marked with @android:resourcetype (example: a local drawable resource marked with @drawable, a global drawable marked with @android:drawable). In this case the resource id is not important, just copy the missing resource into the MiniCM framework-res from the original 4.0.2.A.0.42
So, this is the basic.
With a lot of patience and a little piece of human brain EVERYBODY can do it. With a minimal programming skill this method can be automated (for example use sql tables from the xml files to find the different identifiers related to the same resource, etc)

pilu1978 said:
A detailed example:
In this example I describe how to modify the contacts app from ST15 4.0.2.A.0.42 to work on MiniCM7 2.2.1
Needed:
Framework-res.apk from MiniCM7 2.2.1
Framework-res.apk from official ST15 4.0.2.A.0.42
Phonebook.apk from official ST15 4.0.2.A.0.42
Decompile these apps. To decompile the phonebook.apk need add the SemcGenericUxpRes.apk with the "if" (install framework) parameter in apktool.
In the decompiled code of contacts app (the smali folder) use your best friend: the grep command. You can use any GUI for this tool (for example in windows: Wingrep32).
How to identify the resource identifiers in the code?
Search with grep:
const v
You will get a lot of results. What you need? the global resources ids in the code is a 32bit hexadecimal number.
The global resource ids in this form: 010xyyyy
Where is 010 the marker of global id, x=the resource type (1=attribute, 2=identifier, 3=style, 4=string, etc...) yyyy=the identifier of the resource in the group)
The local resources is similar form: 7f0xyyyy where is 7f0 the marker of local resource, x and yyyy is same.
What do you need?
Check all global resource id with this method:
When you found a global id, for example in a line:
const v1, 0x104000a
search this id in the decompiled 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 104000a equal with: type=string, name="ok"
Check in in the decompiled MiniCM7 2.2.1 framework-res/res/values/public.xml file
You can see: the string named "ok" in the MiniCM7 framework have similar identifier: 0x104000a Now you can happy, the ids equal nothing to do...
Proceed with the next value:
For example you found this line:
const v0, 0x10402be
Check it again in the 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 0x1042be is a string, named: contact_status_update_attribution_with_date
Search this value in the MiniCM7 2.2.1 framework-res/res/values/public.xml file, and you can see: the string exists, BUT different id, the contact_status_update_attribution_with_date string have id: 0x10402a5
Now you must change the id in the contacts app, change all 10402be to 10402a5 in all smali file.
And make it with all global resource id in the app...
If you found a global resource link in the app what not exist in the MiniCM7 resources, you must do it:
For example you found a string, what not exist in minicm
1. copy it from the public.xml (from the 4.0.2.A.0.42 framework-res)
2. go to the last string in the public.xml (in the MiniCM7 framework-res)
3. add the copied line
4. modify the local resource id to the last id in MiniCM+1 (in the unmodified MiniCM7 the last string is "symbol_picker_gt" with the id: 0x010403fe. The first added string must be: 0x010403ff, the 2nd must be 0x01040400, the 3rd must be 0x01040401, etc...)
5. Depends on resource type (attr, bool, string, etc...) YOU MUST copy the missing resource. For example if you add a missing resource id into the public.xml what is a string, must copy the line from strings.xml into the strings.xml of MiniCM.
This is the first method
In the second method add all resources with missing or different identifier in the public.xml of the contacts app with a local id (started with 7f0xyyyy), and insert the missing strings, styles, etc INTO the APP.
And finally, you must check the resource calls in the layout files. This is much easier.
In the layout file, the local resources marked with @resourcetype, the global resources marked with @android:resourcetype (example: a local drawable resource marked with @drawable, a global drawable marked with @android:drawable). In this case the resource id is not important, just copy the missing resource into the MiniCM framework-res from the original 4.0.2.A.0.42
So, this is the basic.
With a lot of patience and a little piece of human brain EVERYBODY can do it. With a minimal programming skill this method can be automated (for example use sql tables from the xml files to find the different identifiers related to the same resource, etc)
Click to expand...
Click to collapse
Iteresting.. thanks for sharing this pilu BTW hows your rom?

Xmaster8 said:
Iteresting.. thanks for sharing this pilu BTW hows your rom?
Click to expand...
Click to collapse
Thanks. Rom is work in progress And little additions to my previous post: this method can work with other vendor specific apps (lg, samsung, htc, etc...). Some apps need some code editing, but the most vendorspecific app can run with this method.
And forgot a few things:
you can determine all permissions and external framework elements in the androidmanifest.xml (listed as uses-permissions and uses-library), and you can find the native function calls in the decompiled app (search the loadlibrary string in smali).

pilu1978 said:
A detailed example:
In this example I describe how to modify the contacts app from ST15 4.0.2.A.0.42 to work on MiniCM7 2.2.1
Needed:
Framework-res.apk from MiniCM7 2.2.1
Framework-res.apk from official ST15 4.0.2.A.0.42
Phonebook.apk from official ST15 4.0.2.A.0.42
Decompile these apps. To decompile the phonebook.apk need add the SemcGenericUxpRes.apk with the "if" (install framework) parameter in apktool.
In the decompiled code of contacts app (the smali folder) use your best friend: the grep command. You can use any GUI for this tool (for example in windows: Wingrep32).
How to identify the resource identifiers in the code?
Search with grep:
const v
You will get a lot of results. What you need? the global resources ids in the code is a 32bit hexadecimal number.
The global resource ids in this form: 010xyyyy
Where is 010 the marker of global id, x=the resource type (1=attribute, 2=identifier, 3=style, 4=string, etc...) yyyy=the identifier of the resource in the group)
The local resources is similar form: 7f0xyyyy where is 7f0 the marker of local resource, x and yyyy is same.
What do you need?
Check all global resource id with this method:
When you found a global id, for example in a line:
const v1, 0x104000a
search this id in the decompiled 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 104000a equal with: type=string, name="ok"
Check in in the decompiled MiniCM7 2.2.1 framework-res/res/values/public.xml file
You can see: the string named "ok" in the MiniCM7 framework have similar identifier: 0x104000a Now you can happy, the ids equal nothing to do...
Proceed with the next value:
For example you found this line:
const v0, 0x10402be
Check it again in the 4.0.2.A.0.42 framework-res/res/values/public.xml file
You can see: the 0x1042be is a string, named: contact_status_update_attribution_with_date
Search this value in the MiniCM7 2.2.1 framework-res/res/values/public.xml file, and you can see: the string exists, BUT different id, the contact_status_update_attribution_with_date string have id: 0x10402a5
Now you must change the id in the contacts app, change all 10402be to 10402a5 in all smali file.
And make it with all global resource id in the app...
If you found a global resource link in the app what not exist in the MiniCM7 resources, you must do it:
For example you found a string, what not exist in minicm
1. copy it from the public.xml (from the 4.0.2.A.0.42 framework-res)
2. go to the last string in the public.xml (in the MiniCM7 framework-res)
3. add the copied line
4. modify the resource id to the last id in MiniCM+1 (in the unmodified MiniCM7 the last string is "symbol_picker_gt" with the id: 0x010403fe. The first added string must be: 0x010403ff, the 2nd must be 0x01040400, the 3rd must be 0x01040401, etc...)
5. Depends on resource type (attr, bool, string, etc...) YOU MUST copy the missing resource. For example if you add a missing resource id into the public.xml what is a string, must copy the line from strings.xml into the strings.xml of MiniCM.
This is the first method
In the second method add all resources with missing or different identifier in the public.xml of the contacts app with a local id (started with 7f0xyyyy), and insert the missing strings, styles, etc INTO the APP.
And finally, you must check the resource calls in the layout files. This is much easier.
In the layout file, the local resources marked with @resourcetype, the global resources marked with @android:resourcetype (example: a local drawable resource marked with @drawable, a global drawable marked with @android:drawable). In this case the resource id is not important, just copy the missing resource into the MiniCM framework-res from the original 4.0.2.A.0.42
So, this is the basic.
With a lot of patience and a little piece of human brain EVERYBODY can do it. With a minimal programming skill this method can be automated (for example use sql tables from the xml files to find the different identifiers related to the same resource, etc)
Click to expand...
Click to collapse
Will it work with phone apk from lewa roms ? I'd like to port the PIM.apk (phone/contacts/messaging apk) from lewa and i saw this, but dont know if its the best way to do it. Is there a way to make this apk work on all roms like standard aplication ?

gravian said:
Will it work with phone apk from lewa roms ? I'd like to port the PIM.apk (phone/contacts/messaging apk) from lewa and i saw this, but dont know if its the best way to do it. Is there a way to make this apk work on all roms like standard aplication ?
Click to expand...
Click to collapse
The best way to make "standard" application: check the framework base code (there you can found the standard resource ids what is equal in all rom) and insert all non-standard resources (drawables/strings/etc) into the app.
But the phone app need to trace all function calls in the code and need to check in the framework code (mostly the android.telephony and com.android.internal.telephony section).

Hy pilu!
With your second method is possible to port the stock se (2.1) launcher to 2.3 roms?
And what about SDEs keyboard?
Sent from my X8 using xda premium

levus95 said:
Hy pilu!
With your second method is possible to port the stock se (2.1) launcher to 2.3 roms?
And what about SDEs keyboard?
Sent from my X8 using xda premium
Click to expand...
Click to collapse
The answer is easy: try it
I think possible, but better if porting apps from a system what have same api, so I can suggest: use this method on 2.3 apps
Sometime this week I will make a more detailed tutorial.
EDIT: I will check the requirement of SE 2.3 keyboard. This keyboard is NOT SDE keyboard.

pilu1978 : can't waitning to taste your rom .
It will be perfect rom I think .
Sent from my X8 using Tapatalk 2

Related

[Q]how to add lines to xml

in order to get a mod to work in my theme i need to add a couple strings to my public.xml thats found in my framework-res.apk. i used ultracompare to compare 2 different xml files and i know what needs to be added to my xml file. i use notepad ++ to edit values but never added strings.
1. can i use notepad++ to add the strings to my public.xml?
2. does it matter what line they end up on?

I use Open XML Editor, but I am sure you can use whatever works best for you. Notepad would hurt my brain though.
As far as the Public.XML, I don't think you can just remove and add lines to it...
The way it was explained to me was that any extra or new pngs added to a theme will be added into the Public.xml by way of "aapt". So there is no need to add. As far as removing items... well the entries are all coded a specific way so if you remove line 100... then everything from 101 to the end will be off by 1 and cause a lot of problems. An example...
<public type="attr" name="exported" id="0x01010010" />
<public type="attr" name="process" id="0x01010011" />
<public type="attr" name="taskAffinity" id="0x01010012" />
<public type="attr" name="multiprocess" id="0x01010013" />
<public type="attr" name="finishOnTaskLaunch" id="0x01010014" />
So as you can see the id used increases and then is associated with a specific item from within your apk. So as far as I know the best way to modify something (like a theme or etc) is to work with a Public.XML that has less in it so you can add to it... or just keep all those items in there (pngs, etc) and just make them a 1x1 image. Not the best way... but from what I have seen it has been done by many a theme maker and ROM builder.
Hope that answers your question.
** edit **
I just realized that I may had confused you (not knowing your knowledge level) so... The items are added to the Public.XML when you build the APK back together after editing it. This can be done with the apktool, which uses the aapt to do it's job. At least that is how it has all been explained to me so far. I also need to modify a Public.XML for my framework-res.apk and ran into problems here.

You don't need to worry about adding pngs to the public.xml. just put the pngs in place in the decompiled apk along with the xml that's using the pngs. You can't add pngs that aren't being used, which is the only requirement.
Run 'apktool b' to rebuild the apk and the pngs should be added to the public.xml. that data will be in the resources.arsc file in the new apk if you had no errors. Copy that to your original apk and you're set.
You can decompile your recompiled apk if you want to see the newly added entries to the public xml. But that's just for fun.
Note; I found in the framework 21 for backflip that there was no more room for draw9.png images, just regular pngs.
Also, if you copy any1 else draw9.pngs from their apk make sure you copy the png from an unzipped apk and not a decompiled apk. Decompiles adds the 1 pixel ring around the image that wont go away unless recompiled. And you can't replace draw9 images to recompile or apktool will try to add it as a new draw9.png to public xml and error out. Just insert to your original apk.
That should cover all bases.

Im sorry, the second post threw me off. You said strings specifically. I would think the rule should apply the same. Use the string in an xml and the string is declared in another xml in the values folder, I think its strings xml. The compiled string resources will be in the resources.arsc file in the new apk.

djstaid said:
I use Open XML Editor, but I am sure you can use whatever works best for you. Notepad would hurt my brain though.
As far as the Public.XML, I don't think you can just remove and add lines to it...
The way it was explained to me was that any extra or new pngs added to a theme will be added into the Public.xml by way of "aapt". So there is no need to add. As far as removing items... well the entries are all coded a specific way so if you remove line 100... then everything from 101 to the end will be off by 1 and cause a lot of problems. An example...
<public type="attr" name="exported" id="0x01010010" />
<public type="attr" name="process" id="0x01010011" />
<public type="attr" name="taskAffinity" id="0x01010012" />
<public type="attr" name="multiprocess" id="0x01010013" />
<public type="attr" name="finishOnTaskLaunch" id="0x01010014" />
So as you can see the id used increases and then is associated with a specific item from within your apk. So as far as I know the best way to modify something (like a theme or etc) is to work with a Public.XML that has less in it so you can add to it... or just keep all those items in there (pngs, etc) and just make them a 1x1 image. Not the best way... but from what I have seen it has been done by many a theme maker and ROM builder.
Hope that answers your question.
** edit **
I just realized that I may had confused you (not knowing your knowledge level) so... The items are added to the Public.XML when you build the APK back together after editing it. This can be done with the apktool, which uses the aapt to do it's job. At least that is how it has all been explained to me so far. I also need to modify a Public.XML for my framework-res.apk and ran into problems here.
Click to expand...
Click to collapse
I am getting same problem as OP. You said that new PNGs or something are automatically added in public.xml right? But I am not able to see them. Actually, i added 5 more indeterminate progress bars and edited the animator xml for it too. The app compiled with apkmanager, but after decompiling the same, I don't see the new indeterminate PNGs declared in the public.xml.!! Plz. help me! I can't just flash and test immediately!! cause i don't have that phone!!

No they are not added automatically you have to add it yourself.
Only add or change lines don't remove.
For public.xml
Everything is grouped
Each group has an order
Drawable will be
0x7......00
0x7......01
................
0x7......ff
Remember they use letters also
You can add a new item
0x7.......g0
They have to be in order by resource type
String would start with ex...
0x6......00
Find the last string id that was used and add the next id.
Remember they are not always in order so actually use the text search to be sure.
Not sure if you already added the string to the strings.xml
That has to be done also.
For that open strings.xml
Copy the last line
Paste it to next line
Change string name (must match public.xml) and than value (what text is displayed)
Let me know if you need more help.
Sent from my PG86100 using Tapatalk

Here is a write up i was planning on doing for my site
decided to start it now.
Add resources to an android apk
Its just a start but should be able to do it with out problems

wes342 said:
Here is a write up i was planning on doing for my site
decided to start it now.
Add resources to an android apk
Its just a start but should be able to do it with out problems
Click to expand...
Click to collapse
Oh mahhnn!! Thanks a lot for that!! Now I don't need to depend on crappy tools for adding resources any more!!!
Once again, thanks a lot for that!!

So when i understand it right i made it like that.
I wanna add "ab_bottom_solid_dark_holo.9.png" to mms.apk.
I copy it to "drawable-xhdpi". I open "public.xml" and scroll to the end of "<public type="drawable" ". Last string is:
"<public type="drawable" name="stat_notify_sms_9" id="0x7f020254" />"
Click to expand...
Click to collapse
So i make a line under that and that would be that:
<public type="drawable" name="ab_bottom_solid_dark_holo" id="0x7f020255" />
Click to expand...
Click to collapse
In the whole xml is no other "7f020255". So that would be all? No other changes to do?

Basian Mile said:
So when i understand it right i made it like that.
I wanna add "ab_bottom_solid_dark_holo.9.png" to mms.apk.
I copy it to "drawable-xhdpi". I open "public.xml" and scroll to the end of "<public type="drawable" ". Last string is:
So i make a line under that and that would be that:
In the whole xml is no other "7f020255". So that would be all? No other changes to do?
Click to expand...
Click to collapse
Everytime I've added a drawable, or a string, to my apps, I've never had to put them into public.xml
All I do is compile and they're added automatically. The only time I need to touch public.xml is if I want to remove something.

That would be nice. iam on JellyBean on my Galaxy Nexus and use apktool cmd. And it just gave me errors.
What do u use to compile. Maybe its a nice Tool with more Functions.

X10 Mini/Mini pro Theme Reference for Newbies

This thread was opened to consolidate the information/knowledge about themes for the x10 mini/mini pro. It is basically a reference thread with key bits of information and links so that a new user can find all the necessary information in one place. It should also help us avoid the old ‘where the hell was that image…?’ and ‘where was that … thread again?’.
Please PM me or post any useful information that is missing, especially the OPs of the threads in the Themes section below. I will continually update this thread with any new information or links.
At the moment this is a work in progress. I will fill it out in the days to come. And will keep it updated so long as I have my x10 mini pro (at least another 18 months according to t-mobile ).
All useful information that is posted here will be added to this first page, so that you don't have to wade through pages of posts to try and find something. Everything after the first page should therefore either be repeated on this page somewhere or is just conversation. Please yell at me should this not be the case
Please help me out by posting information, ideas etc.
Creating Themes for the x10:
1. Getting Started
2. Using ADB
3. Creating a Theme
4. Modifying XML files and adding resources
5. Modifying Services.jar
6. Recovery tips
7. Theme collection
8. Replace Framework with Root Explorer
Credits:
_calum_
Download all your original system applications here.
**Guys If u like this tutorial thank me by donating me .**

Getting Started
Before getting started on a theme you'll need to set a few things up. Here's a list of everything you'll need:
• Root. Your phone will need to be rooted
• Java SDK (JDK). You'll need to install the JDK (and JRE) before you can start modifying the contents of your phone. Check out this video of Chewitts if you're having problems on x64 systems.
• ADB (from the Android SDK). You need ADB to push/pull files to and from your phone (see the next post)
The easiest way to make sure everything is set up properly is to install someone elses theme.
After you've done all that take a look at this.

Using ADB
There's an ADB Guide here :
Before you start need to unsecure the shell. Use the following adb commands to do this if you haven't already (to reverse it do chmod 0755... ):
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
chmod 4755 /system/bin/sh
This is all described in the links posted in the Getting Started section above
Thanks to MrRusch for making our lives easier with this tool. For those of you new to this, you should still read the guide linked above so that you know what is actually going on.
Here's a step by step for pulling the framework from your phone and pushing it back. The boot animation mod at the bottom is for 2.1 it is found in system/media/bootanimation.zip.
Step 1:
Connect phone to pc, enable usb debugging and open adb. Type:
adb pull /system/framework/framework-res.apk framework-res.apk
That will pull your framework-res.apk to whatever folder is displaying in your command line.
Step 2:
Find the framework-res.apk on your hard drive, right click and open with 7zip.
Step 3:
Use png's here or create your own and dump into the appropriate folder within framework-res.apk.
Step 4:
When you are done editing the files open up adb and type the following command:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
That will put the new framework-res.apk on your phone. It should automatically reboot (if not reboot it) and your changes should be applied!
When running the script above you can replace framework-res.apk with whatever you want. For example, Conversations.apk,Alarm.apk etc.
Remember, it is CASE sensitive I made this problem many times)
If you would like to pull an entire folder put a slash at the end of the last word. For example, adb pull /system/etc /etc"/" (no " in actual script )
Courtesy of corruptfate is the steps to modify the Boot animation
step 1: Copy bootanimation.zip to sdcard
step 2: Open CMD (Command Prompt)
step 2: type "adb shell"
step 3: type "su"
step 5: type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system"
step 5: busybox cp /sdcard/bootanimation.zip /system/media/bootanimation.zip
step 6: chmod 755 /system/media/bootanimation.zip
Click to expand...
Click to collapse

Creating a theme
So, now that we’ve got the framework-res.apk onto our hard drive, we can take a look at creating a theme. The only skill that is really required to change the appearance of the framework (this is the system file that contains the notification bar, settings etc.) is being able to edit .png image files to suit your tastes. If you can do this then it is just a matter of knowing how to extract the images, and how to update the .apk with them after editing.
.9.png's
Before we start we need to take a look at a special kind of image in android apk’s: the .9.png’s. These are recognisable, as the name suggests, by the double extension *.9.png.
.9.png's are images with a bit of extra information embedded. They contain information on how they can be stretched, and where the content can go (e.g. for a button background, which area of the background can contain the text).
This information is contained in a single pixel border (the guides) around the image and can be added using draw9patch. The catch here is that the guides must be compiled into the image before it can be used.
The Border: For the most part, you will not have to edit the border of a .9.png because, as long as you follow the guide below, the guides will already be in the image and you will not need to change them. If you do need to create your own (I’d assume you know enough not to be reading this though ), you can find more information here.
Editing the Framework
In this example we will look at editing framework-res.apk. However, the process can be used on any apk.
The method described below may seem overly complicated for those who have experience in this area, but it is (in my opinion) the easiest ‘sure-fire’ way to make sure you don’t have any problems (especially with the .9.png’s).
In rare cases, when the .apk your modifying doesn’t have any .9.png’s (e.g. the Recent Calls widget) then you can skip straight to the ‘Updating images using Drag/Drop’ section below.
Requirements:
You will need the following:
7zip apktool - this is included in the attached file themes.zip
Some people use WinRAR instead of 7zip, but apktool uses some 7zip commands internally so make sure it is installed (I think, I know this is the case for APK Manager, I still need to test this for apktool, but hey, just use 7zip, it's free and works exceptionally well).
Setting up:
In the attached zip file (themes.zip) you will find a copy of my theme creation environment. It’s not too complicated, it only contains a couple of folders so I know where everything is, three key batch files (all one-liners) and apktool.
The first thing we need to look at is install_framework.bat. This contains the following line:
Code:
java -jar apktool.jar install-framework stock\framework-res.apk
All this does is tell apktool to install the framework on your system. The resources from stock\framework-res.apk will be extracted to a default location. If you don’t do this then you will not be able to recompile other apk’s that rely on the framework (you will get a ResourceNotFound error).
The other batch files decompile and build the framework, these are the ones that need to be modified if you start working on a different apk:
Code:
decompile.bat
java -jar apktool.jar d stock\ framework-res.apk working\ framework-res
build.bat
java -jar apktool.jar b working\framework-res out\framework-res.apk
I have included the stock X10 mini pro framework. If you use on of the other frameworks out there you may find that you get a lot of errors when trying to recompile. That’s because someone got lazy with the .9.png’s
As we are modifying the framework directly we do not need to run install_framework.bat, for a different apk (e.g. Phonebook.apk) you may need to run this first to avoid errors when decompiling.
Decompiling and Building:
1. Run decompile.bat. After this you will see that the working folder is filled with the contents of the apk. The images we need to modify are in the subfolders res/drawable-ldpi and res/drawable-land-ldpi. If you look at some of the .9.png’s in there you can see the guides (see the attached image). This makes it really easy to edit them, you can just edit them like any other image (as long as you do not touch/alter the guides).
2. Edit any images that you want. For the .9.pngs I usually make a copy without the 1 pixel border so that I can edit the entire image, then I paste the copy back into the middle of the original .9.png. You don’t have to worry about the guides, they are already set correctly.
I have created a tool that takes the stock x10 mini / mini pro status bar icons, removes the background and sets them to a colour of your choice here. This was made to make my life easier by minimizing the time I spend in photoshop.
3. Run build.bat. This compiles the framework, embedding the guide information into the .9.png’s. The output framework is in the out folder. Do not push this to your phone as it is incomplete and the resources.arsc is stored incorrectly. If you do push it to your phone then you get to reflash
Now you can just drag the edited images out of the generated framework onto your hard drive and use steps 4. and 5. of the Drag/Drop method described below to update your framework.
Updating images using Drag/Drop:
1. Open the .apk in 7zip and browse to the appropriate image folder (almost always the res\drawable-hdpi folder)
2. Drag/Drop the images you want to edit to your hard drive. Leave the .apk open in 7zip
3. Edit the images in your favourite program (photoshop or similar)
4. Drag/Drop the images back into the .apk that is still open
5. Use the process described in the previous post to push the framework back to the phone
The reason that the .apk is left open in this process is that some (all?) of them are signed and updating them in this way doesn’t mess with the signature. I’ll admit to not being 100% sure about this, I’m sort of thinking now that people just had problems re-packing due to files being compressed that shouldn’t have been (see the section on editing XML files and adding resources to see what I mean). Please correct me on this one.
This also [almost] goes without saying, but: Make a backup before you start (you can look at the installer for Chewitts Dark10 theme to see how to do this).
OK, now you can start messing with the appearance of your phone, have fun
Credits
Thanks to Mr_Element for the help testing this process and making it easier to follow
Thanks to damnitpud for his post here, without which I would still have been a bit lost in draw9patch.

Modifying XML files and adding resources
First up, thanks to MrRusch for pointing out that the resources.arsc was being zipped differently. It would have taken a few more flashes to figure out how to pack it into the apk without that little nugget
The XML files in the framework-res.apk (and the other apps) are stored in a compiled form, making them impossible to edit without decompiling them. The process of decompiling them and recompiling is reasonably simple but care is required if any images/resources are added to the apk.
Modifying the xml files opens up certain things that can’t be changed by just modifying some image files. The best example is changing the battery icon in the notification bar to show a different image for each percentage instead of just 10%, 20%, 40% etc.
When you modify xml files and add resources to your apk, make sure you copy ALL the modifications made to the stock apk each time after compiling. I have noticed strange effects if I don't do this such as the wrong images being used - I am assuming that in the newly compiled resources.arsc the image references/IDs change when compiled, but I'm not really sure yet. An example of this is when I tried to add the signal strength mod mentioned above to a framework that included the battery icon mod below. This only worked if I also copied the battery mod files to the framework (even though they were already in the apk) after recompiling the signal strength mod. If I just copied the files required for the signal strength mod then the battery indicator would start showing the wrong images .
Battery Icon:
Here is a step by step for modifying the battery icon in the framework. To do this you will need to download apktool and install 7zip (other compression programs may work, but I’ve only used 7zip). I have attached some example files with 100 steps (one for each percentage) in case you just want to add them to your existing framework. Just make sure they are added as described below!
1. Decompile the framework using the following command:
Code:
java -jar apktool.jar d framework-res.apk framework-res
2.This will decompile the framework-res.apk that’s in the current command window folder into a subfolder framework-res
Find the xml files you need to modify, e.g. the battery icon xml res\drawable\stat_sys_battery.xml and edit them. This is assuming, of course that you know what needs to go in the XML file . For the battery XML it is pretty obvious, just copy/paste the existing nodes and change them so you have the necessary percentage entries, see the attachment for an example with 100 steps.
3. Add any necessary resources to the appropriate folder. For the battery icon you need to create an image for each percentage (or download one of these) and add them to the res\drawable_hdpi folder. The name is the same as the name in the xml (stat_sys_battery_*.png)
4. Rebuild the apk using the following command:
Code:
java -jar apktool.jar b framework-res out\framework-res.apk
This will create a new framework-res.apk in a subfolder out.
IMPORTANT: Do not push this apk to your phone unless you want to reflash
5. Extract the xml files and images from the newly generated apk (you can use the original images, but the xml files must be the newly compiled ones from the new apk). Add these files to the original framework-res.apk that you want to push to your phone (see the previous post).
6. Extract the resources.arsc from the root of the apk
7. Rename the original framework-res.apk from your theme to framework-res.zip
8. Right-click the extracted resources.arsc and choose the 7zip menu item ‘Add to archive’
9. In the dialog that appears set the achive field at the top to the framework-res.zip from step 7. And set the archive format to zip. Now set the Compression level to store and click OK(if you do not do this your phone will not boot). The settings are in the attached screenshot.
10. Rename framework-res.zip to framework-res.apk and double check that the compressed size or resources.arsc is the same as the original size (see screenshot)
11. Done. Push the new framework to your phone.
Status Bar Text:
The style for most (all?) UI elements can be found in res/values/styles.xml. This xml file is only available in a decompiled framework. In the compiled version everything in res/values is compiled into resoureces.arsc.
The status bar text style is named TextAppearance.StatusBar. The file is pretty large so it's best just to do a search for the name. The definition looks like this:
Code:
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_primary</item>
</style>
You can easily adjust the size or make the text bold using the textSize and textStyle elements (see here for a description of these attributes and their values). The color uses the @color/... notation. This is a reference to a color resource, these can be found in colors.xml. We could just change this to a direct color entry (see here for an example), but then we wouldn't have a resource that can be reused for other parts of the UI.
If you open colors.xml you can find this:
Code:
<color name="semc_text_color_primary">#ffffffff</color>
This sets the primary text color to white (ARGB: FFFFFFFF = White). Changing the value of this will change the color of all primary text throughout the phone (settings menu etc.). If we just want to change the notification bar then it's best to add a new color. To do this just duplicate the above color definition and change the name and color:
Code:
<color name="semc_text_color_primary">#ffffffff</color>
<color name="semc_text_color_custom">#9900ff00</color>
And then adjust the style to use this new color resource:
Code:
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_custom</item>
</style>
Now recompile and copy resources.arsc to your framework as described above and push the framework to your phone for semi-transparent green text in your status bar

Modifying Services.jar
To modify services.jar we need to decompile the classes.dex file contained within. We can do this with baksmali:
1. Open services.jar (found in system/framework) with 7zip
2. Extract classes.dex from the archive
3. Open a command window and use the following to decompile:
Code:
java -jar baksmali-1.2.5.jar -o out\services classes.dex
4. You will now have a subfolder out\services with the decompiled .dex classes (smali files)
These sort of modifications will not be necessary very often. Two things that have been looked at so far are changing the text color on the status bar clock (just the clock, not the notification text) and changing the signal strength to show dBm instead of just the bars. The text color of the clock is relatively simple and is described below. The signal strength mod was done by MrRusch and requires a bit more code.
I have attached a converter MrRusch has put together to convert java to smali. This is really helpful when trying to figure out how to modify the smali or event just trying to figure out what a piece of smali code does.
You can find a reference for all the smali ops here. This one is more complete but I prefer the first purely because it's a bit more compact and it has most of what I need anyway. Thanks to untemensch and JesusFreke for the links.
Status Bar Clock Color:
I have since figured out how to do this without changing any code, just by changing some xml in res/layout, but I will keep this here as I think it is a nice, easy to follow example to start out with.
This section describes how to modify the color of the clock in the status bar without changing the color of the notification text (changing all of the status bar text is described in the xml section above).
First we need to have a look at the smali file com\android\server\status\StatusBarIcon.smali to see how the color of the clock text is set. I use Visual Studio to view/edit the smali files, but you can use any text editor - I have seen PSPad recommended a few times.
If we look at the init method we can see the following piece of smali code:
Code:
.line 44
.local v15, textColor:I
const/4 v13, -0x1
.line 50
.local v13, styleIndex:I
const v18, 0x1030079
:try_start_1f
sget-object v19, Lcom/android/internal/R$styleable;->TextAppearance:[I
move-object/from16 v0, p1
move/from16 v1, v18
move-object/from16 v2, v19
invoke-virtual {v0, v1, v2}, Landroid/content/Context;->obtainStyledAttributes(I[I)Landroid/content/res/TypedArray;
move-result-object v5
.line 53
.local v5, a:Landroid/content/res/TypedArray;
const/16 v18, 0x0
move-object v0, v5
move/from16 v1, v18
move/from16 v2, v16
invoke-virtual {v0, v1, v2}, Landroid/content/res/TypedArray;->getDimension(IF)F
move-result v16
.line 54
const/16 v18, 0x3
move-object v0, v5
move/from16 v1, v18
move v2, v15
invoke-virtual {v0, v1, v2}, Landroid/content/res/TypedArray;->getColor(II)I
move-result v15
Here's a run-down:
I'm pretty sure the lines that start with a '.' are comments from the decompiler.
The .line 4 entries are just a reference to the line number in java source-code. And I think the .local v15, textColor:I entry just notes the v15 variable name and type (I = integer).
The first bit of interest is the line invoke-virtual {v0, v1, v2}, Landroid/content/Context;->obtainStyledAttributes(I[I). The obtainStyledAttributes method definition can be found here. There are a few overloads, but the call is to the method that accepts an integer and an integer array as parameters - hence the (I[I), I and [I. The three variables in braces at the start denote the object that the method is being called on (the Context object) and the two parameters respectively. The first parameter (v1) is a resource ID and a few lines up the v18 variable is copied to this (move/from16 v1, v18 - this means move the value from v18 to the v1 variable). v18 was declared a few lines above again with the value 0x1030079. This ID can be found in the framework xml-file res/values/public.xml and the value is the name of a style (TextAppearance.StatusBar) that can be found in res/valus/styles.xml (see the xml section above).
The result of obtainStyledAttributes is copied to v5 (move-result-object v5) which (in .line 54) is copied to v0 which is then used to call Landroid/content/res/TypedArray;->getColor with the two integer parameters v18 (0x3) and v15 (0x100 - this is the color black). The first parameter is the index of the color in the style array (index 3 in v5) and the second is the default value (black).
The result of getColor() is then copied to v15 and reused later when setting up the text view for the clock:
Code:
.line 61
.local v14, t:Landroid/widget/TextView;
move-object v0, v14
move-object/from16 v1, p0
iput-object v0, v1, Lcom/android/server/status/StatusBarIcon;->mTextView:Landroid/widget/TextView;
.line 62
new-instance v11, Landroid/widget/LinearLayout$LayoutParams;
const/16 v18, -0x2
const/16 v19, -0x1
move-object v0, v11
move/from16 v1, v18
move/from16 v2, v19
invoke-direct {v0, v1, v2}, Landroid/widget/LinearLayout$LayoutParams;-><init>(II)V
.line 65
.local v11, layoutParams:Landroid/widget/LinearLayout$LayoutParams;
const/16 v18, 0x0
move-object v0, v14
move/from16 v1, v18
move/from16 v2, v16
invoke-virtual {v0, v1, v2}, Landroid/widget/TextView;->setTextSize(IF)V
.line 66
invoke-virtual {v14, v15}, Landroid/widget/TextView;->setTextColor(I)V
All this means that to change the color of the clock text only, we need to declare a new style and use the ID of this style in the call to obtainStyledAttributes. When adding the style to styles.xml I keep it in the same place as the other status bar styles:
Code:
...
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_primary</item>
</style>
<style name="TextAppearance.StatusBar.Clock" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_clock</item>
</style>
...
The name of the style can be anything, what is important is the ID reference in public.xml, and that a color semc_text_color_clock is declared in colors.xml (see the xml section above).
The style reference in public.xml must have an ID that starts with 0x0103****. This is the ID range for styles, strings and other resources have a different ID range. I always add the new style at the bottom of the style group so that I can easily see which is the next free ID:
Code:
....
<public type="style" name="SEMCTheme.Dialog.Alert.Vanilla" id="0x01030139" />
<public type="style" name="TextAppearance.StatusBar.Clock" id="0x0103013a" />
....
Now that we have added a new style we just need to adjust the smali code to use it. Change the code above from:
Code:
.line 50
.local v13, styleIndex:I
const v18, 0x1030079
to:
Code:
.line 50
.local v13, styleIndex:I
const v18, 0x103013a
Now our new style is used for the call to obtainStyledAttributes. We then need to recompile the smali to a classes.dex file and update the services.jar:
Run the following command to recompile the smali:
Code:
java -jar smali-1.2.5.jar -o out\classes.dex out\services
The output file may be a slightly different size than the original classes.dex but as long as you don't get any errors it will be OK.
Now open services.jar with 7zip and update it with the new classes.dex (drag/drop).
Done Push the services.jar to your phone with adb and reboot (make sure you have updated framework-res.apk with the new xml resources first, otherwise our new ID will point to a non-existant resource)

Possible reasons your phone won't boot after modifications:
images anren't stored properly, right format, right size etc.
unpacked apk improperly, use 7zip, it doesn't mess anything up
you signed the package before pushing it- unless you know what you're doing follow the directions to a tee and you should be fine
pushed the package to the wrong directory, /system/framework-res.apk XX, /system/framework/framework-res.apk
I'm sure many other reasons, these were the only ones I encountered
How to get past boot screen:
Use backup framework-res.apk and push that one to your phone. Remember to place that one where the modified one is.
To see if adb sees your phone type adb devices, if a serial number pops up try pushing your original, if not...
Flash your phone again from scratch . Sorry, I don't know any better way yet.
from bitter personal experience :
If anyone does mess their phone up so much that not even the SE logo shows up (just a black, maybe flickering, screen) and a reflash/seus repair doesn't help. Then what sorted me out was a reflash to Generic Nordic 1.6 using this guide the same one I used to get the 2.1 update early - then boot the phone, shut down again and run seus for the 2.1 update and bin4ry flash tool.
Not directly related, but here's a tip from XperiaX10iUser:
To reverse chmod use 0755 instead of 4755.
Click to expand...
Click to collapse
Link to All The System Apps Mini : Download

Themes:
Black Android Theme 1.6 & 2.1 (by draco_ag)
*-=ShArP sUtEr=-* Theme Design For 2.1 (by Shiven Juneja)
Black HTC Theme For x10 mini & x8 (by pulpoff)
Suavesque x10 mini pro 2.1 theme
custom framework-res for 2.1 (By Mooozer)
Black theme + original android emotions For 1.6
[WIP] X10 Mini grey theme For 1.6
Iridium Carbon for 2.1 (by Dark_dog)
~THeMe~ Simplistic v1 Port for X10 Mini/Pro (By Manny-)
~THeMe~ Gingerbread Theme for X10 Mini/Pro
[Theme]Stock Android (Nexus One)
[Theme]Gingerbread Nexus S Edition [with Android 2.3 icons]

Root Explorer
@vippie
Maybe it's a known way, but I didn't find it yet . It works great for me. Your device has to be rooted.
Zocker Tko mentioned in his thread a black theme on a german forum. There's a little tutorial on that site on howto replace the framework-res.apk using Root Explorer:
* make a backup of the original file
* Copy framework-res.apk to the SD card
* Mount /system in RootExplorer as "rw"
* Copy framework-res.apk to /system
* Set permissions for framework-res.apk to 644. See screenshot:
* Move framework-res.apk to /system/framework and replace the existing file (reported to be safer than copy).
* Reboot your phone.
Ofcourse all credits goes to Bueffel the original poster.
Click to expand...
Click to collapse
Nice Guide for installing via root explorer by DarK_dOg:
Installation procedure:
Step 1:
Copy android.policy.jar, framework.jar, framework-
res.apk files into your (/sdcard).
Step 2:
Launch Root Explorer and browse to the location of the theme
pack files. Press menu and then "Multiselect". Then
select the files and press "copy".
Step 3:
Browse to /system. Press Mount R/W tab. Then press
paste.
Step 4:
You're in /system. Select android.policy.jar file.
From the pop-up menu, choose permissions and set them
according to the screenshot:
Step 5:
We follow the exact same procedure to set the permissions for
the framework.jar and framework-res.apk files.
CAUTION:It is very important to set
proper permissions (as shown on the screenshot) to all of the three
files, or else you will end up with a bricked phone
Step 6:
Once we set the permissions, our files are ready to move on /system framework. Press menu and then "
multiselect" (we are on /system).
For once again choose android.policy.jar, framework.jar
, framework-res.apk and press move.
Step 7:
Go to /system/framework and press
paste.
Click to expand...
Click to collapse

reserved.....

Great post. Thank you!
Quick question: Unsecuring the shell, if the phone stucks at boot, will I be able to replace framework-res as long as adb recognizes the phone? No need to su?
I ask this because I recently re-flashed my phone because I couldn't replace the framework I made by the stock one, but adb was recognizing the phone, just didn't let me su...
Thanks again.
Regards

ya u r write u can replace the framework with su
Steps:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk

shivenjuneja said:
ya u r write u can replace the framework with su
Steps:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
Click to expand...
Click to collapse
Couldn't make this work.
My adb is still asking for su to root. Doesn't allow me to mount without root (su command after ad shell) even after chmod 4755.
This way if something goes wrong, I'll definitively will have to reflash... And that's... You know...
Any idea?
I would be much more comfortable to start playing around with this 'safety net' working...
Thanks again!
Regards
Thanks

Originally Posted by pulpoff >
If your phone gets stuck on booting after playing with framework or some other stuff, I've found a way to repair it without reflash :
restart phone, connect it to usb
in adb shell run rootshell command again to gain root (wise to keep it after rooting), the "su" won't work cause it depends on gfx libs and they are not started yet..
mount sdcard with this command : mount -t vfat /dev/block/mmcblk0p1 /sdcard
and put your backed files where they belong.
Good luck!
Click to expand...
Click to collapse
try this method....

shivenjuneja said:
try this method....
Click to expand...
Click to collapse
Sorry to bother...
Code:
D:\>adb shell
$ rootshell
rootshell
rootshell: permission denied
$ mount -t vfat /dev/block/mmcblk0p1 /sdcard
mount -t vfat /dev/block/mmcblk0p1 /sdcard
mount: Operation not permitted
$
Not sure I managed the 'rootshell' command well.
This is what I get.
My phone is rooted, obviously. I can do the 'su' with no problems.
I'm just trying to be safe before starting to mess around with framework...
Thanks you once again.
Regards

if the adb thing is not working thn you can do 1 thing. download droid explorer from this site http://de.codeplex.com/releases/view/50997 thn when you dont have access to your phone you can open droid explorer move your backup framework to your system framework framework-res.apk and you can also use this tool to do the further things...
http://forum.xda-developers.com/showthread.php?t=850340

I have droid explorer and android commander installed.
I know for experience that none of them work if phone gets stuck.
No 'su', no root, no permission to mount, no permission to write...
Feel free to delete this posts if you want the thread clean.
If we manage a solution, we can post it directly instead of 10 posts aroud the same thing.
Regards and thank you!

bro seus is the last option.... bt can u plz tell me where i wrote that we can do mofications without having su permissions in the thread??

shivenjuneja said:
bro seus is the last option.... bt can u plz tell me where i wrote that we can do mofications without having su permissions in the thread??
Click to expand...
Click to collapse
No, you didn't. I'm not saying that.
What I was looking for was a way to replace framework-res.apk in case something goes wrong and phone gets stuck in 'Sony Ericsson' black screen before bootanimation. In that case, 'su' is not allowed.
That's what happened to me last time I played around with it. And in that case I were not able to put the good framework-res.apk back in place, so I had to re-flash.
Having shell unsecured, I believe I can avoid re-flashing even if something goes wrong. I think I finally got a way to have this safety through SuperOneClick although I'm not so sure it will work in a worst case scenario, once the 'shell root' gained is always temporary until next reboot...
As I told you before, none of the ways you posted here to get 'shell root' or 'shell unsecured' worked for me, that's only what I was looking for.
Thank you again for all your work and patience.
Best regards!

Welll...
Playing aroud and I'm a small step to re.flash the phone.
I have my phone stuck in the 'Sony Ericsson' black screen.
Can't get root, rootshell, adb root or su after adb shell to work.
I need at least to change the permissions of my framework-res.apk file in /system/framework
Any idea on how to do this and avoid the re-flash?
Thanks

[Q] hack aapt to create max id for each layout

Hi.
I'm trying to hack aapt to generate for each layout named xxx_layout.xml an extra num in R named R.id.xxx_layout_max_id which will contain the max id for that layout (since each id is an in num and each layout has several id's in it i assume one of them is the biggest).
I need it for adding custom components dynamically in runtime but for layouts like RelativeLayout which requires ID's.
Did anyone hacked appt before to know which file in aapt directory contains the code to genereate ids ?
10x.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

PUBLIC.XML and smali file chaos.

Hi guys, pretty new to playing with android, I'm trying to edit some apk (really simple app), I removed an image
from the res/ folder and removed the entry from the value xml file, which then COMPLETELY jumbled up the resource codes of public.xml when it compiled with APKTool (deleted original public.xml because it was giving compile errors), which broke the application because the resource IDs do not match to the 'smali' codes in the source.
I've googled and searched around for AGES and people are saying smali files ARE rebuilt upon recompiling which didn't
in my case. How do I fix this issue?
THANK YOU!

bump!!
please help me!

[Q] How can i regenerate public.xml after decompiling apk with apktool?

Hi,
I want to decompile Huawei Ascend Mate's settings.apk file and add some decompiled activities and classes from Samsung I9082 settings.apk (it is about dual sim functionality) and do the same with Mms.apk, Phone.apk and TelephonyProvider.apk. (With APKTOOL)
But the only problem is "public.xml"! because when an apk file is compiling from source, all of string names and plurals and etc. will convert to hexadecimal IDs that they are placed in public.xml and the keys of values in Java source will be replaced with hex IDs.
I need to regenerate "public.xml" to add new values with new IDs, but if I change IDs, I have to open all SMALI files and replace old value with new!
May somebody help me?

Better Mobile App

welcome