I have edited then I opened both the new Settings.apk and the original Settings.apk using 7zip. then just simply drag & dropped the resource file from the new one to the original. & then I replaced that original settings.apk in my phone using root explorer and modified permission to 644. The settings is there in the drawer but when I'm tapping it ,it crashing only... Even the gear icon is also not showing,....
I didnt changed anything in the Settings.apk rather than some string values in Strings.xml file.
Please help me if..
Related
Tried everything I can find and no luck with this with Sony framwork-res.apk doing my head in, My new resources.arsc is alwyas about 200kb smaller aswell after recompiling, furthest ive got is bootanimation then restart lol. Anyone had any luck with it? All i need to change is 1 bloody line in style.xml to change bottom popup menu to black, driving me mad lol
go3asy said:
Tried everything I can find and no luck with this with Sony framwork-res.apk doing my head in, My new resources.arsc is alwyas about 200kb smaller aswell after recompiling, furthest ive got is bootanimation then restart lol. Anyone had any luck with it? All i need to change is 1 bloody line in style.xml to change bottom popup menu to black, driving me mad lol
Click to expand...
Click to collapse
Have you followed this guide to the letter?
I changed the progressbar_horizontal.xml in my framework using this guide and it worked!
yeah , changed that worked fine but the style.xml file isnt viewable unless you decompile the apk then when you recompile the folder value with style.xml is compiled into the above file resources.arsc and not had any luck with it at all lol
Try asking Mr.Rusch or Calum?
Sent from my X10a using XDA App
go3asy said:
yeah , changed that worked fine but the style.xml file isnt viewable unless you decompile the apk then when you recompile the folder value with style.xml is compiled into the above file resources.arsc and not had any luck with it at all lol
Click to expand...
Click to collapse
Hmm style.xml is not viewable but also not any other .xml is viewable or readable if you do not decompile.
So I return to My_Immortal's initial question. Have you followed calum's guide about decomipling/recompiling the resources to the letter? What about the part where you take the .asrc file from the unsigned.apk and you chose to add it to the copmressed .zip file (which is the original signed apk that you have renamed). Have you done that exactly as you should?
_calum_ said:
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
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).
Extract the resources.arsc from the root of the apk
Rename the original framework-res.apk from your theme to framework-res.zip
Right-click the extracted resources.arsc and choose the 7zip menu item ‘Add to archive’
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.
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)
Done. Push the new framework to your phone.
Click to expand...
Click to collapse
Its tge re compiling tgatsvthe problem aleays get sources not founf error in apktool. Read that it might be im not using fresh framework files tgat havent already been fiddlef eith but dont have any originnalsat the moment they all gave battery mod
Sent from my X10i using XDA App
Reading another thread I found out how to successfully get the battery icons to drop by 10% increments, but when I go into settings I can not go into settings and select battery manager. It causes the settings to force close.
I must missing something somewhere. Here are my steps I took.
1. Decompile framework-res.apk
2. Edit stat_sys_battery.xml in both /drawable a drawable-hdpi.
Added in all of the stat_sys_battery.png's
3. Recompile framework-res.apk
4. Using win-rar replace META-INF and AndroidManifest.xml from the original framew res.apk
5. Pushed the framework-res.apk to my phone
Now it seems the phone functions properly, but most of all the options in settings cause settings to force close.
Any help on this matter would be greatly appreciated.
Sent from my DROIDX using DroidForums App
Sent from my DROIDX using XDA App
I personally find it hilarious that even on 3.4.2 which is the newest release, motorola still has not fixed the battery manager force close issue... theyve had like four OTA updates now since it originally came out and still nothing
is 3.4.2 an official release from Moto and Verizon?
sent from the xda premium app for android
1. Decompile framework-res.apk (save a copy for modifications later)
2. Edit stat_sys_battery.xml in both /drawable a drawable-hdpi.
3. Added in all of the stat_sys_battery.png's
4. Recompile framework-res.apk
5. Using win-rar copy everything, with the exception of the res folder, that's changed from the newframework-res.apk to the original you saved for Modding. Your goal is to end up using the ORIGINAL .apk not the recompiled one. I think you need resource.arsc and android manifest only (not sure).
6. Replace the xmls in the original fw with the new ones and do the same with the pngs. You should have slightly more pngs (additional percentages) than before.
5. Pushed the modified OLD framework-res.apk to my phone
GL
Thank you for the response. I did get it to work correctly, my big mistake, was during the recompile. I used apk manager and it asks if you would like to keep all unchanged files from the original, them makes a keep folder and you delete what you changed. And if an xml gets edited to also delete the resources file. Then use the new apk and replace the meta and androidmanifest. Works great now. Now I just need to make new battery meter that is easier to read hout or make new battery icons as these were made for
Sent from my DROIDX using XDA App
Doh! I thought you were trying to modify a themed framework-res.apk (stock framework can be decompiled/recompiled with no issues).
Glad you got it working.
Hello,
I'm trying to change a system application on my phone using the APKMultiTool utility but am having problems. The resulting APK will crash my phone which complains about 1,000 permissions are not understood: Unknown permission android.permission...
Steps I've taken.
- Downloaded APKMultiTool
- (9) De-compiled the system framework-res.apk
- Edited the arrays.xml file
- (10) Compiled the APK
- (11) Signed the APK
- Pushed the APK back to the device
The result is an unstable system which will just crash often. Does anyone have the correct procedure for editing system apk's using the new APKMultiTool?
1.Never sign a system apk
2. Use APK manager not apk multitool
3.After compiling, open the apk using winrar and take out resources.arsc and put it back again but with compression level set to store
And then push it to phone.
you must not compiled framework-res.apk
answer Yes to both questions
delete resources.arsc in the keep folder and done
Sorry if this is a duplicate or in the wrong place, but i cant find any solutions.
I am having trouble recompiling the settings.apk. I decompile it without problems but the apk can't recompile unless I paste in the .arsc file from the stock apk (by unziping). The problem is that when I edit the xml, it needs to make a new .arsc file since I edited xml within the layout folder.
I am using apktool and have had no problems with other apk files. This is on the Samsung galaxy player 5.0 USA.
Another note, if I decompile, put in the resources.arsc file, and recompile, the new apk file is smaller. In addition, if I unzip the recompiled apk I can edit the xml w/o a problem. This is weird because when I unzip the stock settings.apk the xml files are un-readable.
Any Ideas about what I am doing wrong?
Sorry for being a noob.
tchen510 said:
Sorry if this is a duplicate or in the wrong place, but i cant find any solutions.
I am having trouble recompiling the settings.apk. I decompile it without problems but the apk can't recompile unless I paste in the .arsc file from the stock apk (by unziping). The problem is that when I edit the xml, it needs to make a new .arsc file since I edited xml within the layout folder.
I am using apktool and have had no problems with other apk files. This is on the Samsung galaxy player 5.0 USA.
Another note, if I decompile, put in the resources.arsc file, and recompile, the new apk file is smaller. In addition, if I unzip the recompiled apk I can edit the xml w/o a problem. This is weird because when I unzip the stock settings.apk the xml files are un-readable.
Any Ideas about what I am doing wrong?
Sorry for being a noob.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2251719
Hello - I am trying to add 'Reboot' option to Power Menu by modifying the following files - framework-res.apk, framework.jar, and android.policy.jar file. I was successfully able to add additional values to the xml file inside framework-res.apk and was able to merge my changes into the original .apk file and update in /system/framework without any issues. However, the smallest changes I make in framework.jar or android.policy.jar file breaks my system. It does not go into a Reboot Loop, but rather gives a message... Unfortunately, the <app name> has stopped working... or something like that... for almost all the apps and repeatedly.
I am on a Stock ROM of Micromax A110 (Mobistel T2). Do I need to DEODEX these .jar files first or do something else? I can't find the .odex files for these two jar files. I am not sure what I am doing wrong. Please help.
I can see some .odex files in my /system/app folder, but none in /system/framework. Is this normal? I am sure I didn't do any deodexing.