Database Users

Help with compiling apk for framework-res

I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??

Rockstar52 said:
I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??
Click to expand...
Click to collapse
You have to sign it with 12

Lenn said:
You have to sign it with 12
Click to expand...
Click to collapse
Tried it, still boot loops at the Archos screen. I then have to do a complete format & wipe reinstalling the SDK, firmware, and the root files. I don't get it.

Lenn said:
You have to sign it with 12
Click to expand...
Click to collapse
Do not sign frameworks! How many time do I have to say this! System apps do not get signed...
Now, as far as the framework, there's two things to check. First, what XMLs have you edited? Second, instead of using root explorer to copy the framework, connect to a pc and use adb to perform these commands:
Code:
su
stop
cp /system/framework/framework-res.apk /system/framework/framework-res.old
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
start
If it continues boot-looping, you will still be connected through adb, so you just
Code:
stop
cp /system/framework/framework-res.old /system/framework/framework-res.apk
sync
start
and it will come back up without having to reformat or anything.
If it's bootlooping even when you use the adb method to copy, then your XMLs must be reencoding incorrectly. Post a list of all XMLs you have changed.

msticninja said:
Do not sign frameworks! How many time do I have to say this! System apps do not get signed...
Now, as far as the framework, there's two things to check. First, what XMLs have you edited? Second, instead of using root explorer to copy the framework, connect to a pc and use adb to perform these commands:
Code:
su
stop
cp /system/framework/framework-res.apk /system/framework/framework-res.old
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
start
If it continues boot-looping, you will still be connected through adb, so you just
Code:
stop
cp /system/framework/framework-res.old /system/framework/framework-res.apk
sync
start
and it will come back up without having to reformat or anything.
If it's bootlooping even when you use the adb method to copy, then your XMLs must be reencoding incorrectly. Post a list of all XMLs you have changed.
Click to expand...
Click to collapse
I do have my system set up for adb, but for some reason it don't read my A101, it works fine for my phone. The device manager shows my A101 listed as a Gen8 ADB Device, but it don't show up when i use the command: adb devices.
With your help I did manage to replace all of the stock .png's. I also found that I don't need to edit the .xml files to do what I want to. Thanks, for so much of your help! Although I would like to replace the .9.png's also and I understand that you must de-compile the .apk in order to do so. this way I could build a custom theme.

Rockstar52 said:
I do have my system set up for adb, but for some reason it don't read my A101, it works fine for my phone. The device manager shows my A101 listed as a Gen8 ADB Device, but it don't show up when i use the command: adb devices.
With your help I did manage to replace all of the stock .png's. I also found that I don't need to edit the .xml files to do what I want to. Thanks, for so much of your help! Although I would like to replace the .9.png's also and I understand that you must de-compile the .apk in order to do so. this way I could build a custom theme.
Click to expand...
Click to collapse
Have you done this yet(from the archos support site):
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
And disabled/reenabled debugging on the tablet?

msticninja said:
Have you done this yet(from the archos support site):
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
And disabled/reenabled debugging on the tablet?
Click to expand...
Click to collapse
No but I will give it a try and report back.

None of my changes are taking effect??!

Still not working, just a question. I am running Win7 64bit could this be the problem?? Do I need to be on a 32bit system to do the decompiling, compiling?
Tried on my wife's 32bit system still the same. For some reason it's not compiling the .apk right.

Rockstar52 said:
I am trying to create a custom theme, by modifying the framework-res.apk. I have been successful in porting some really cool .png files, but my problems start with the de-compiling & recompiling the .apk so I can modify the .xml & .9.png files. It seems every time I recompile my .apk it sends me in to a boot loop. I have used both APKTool and APK Manager with no luck. Here are my steps:
APK Manager:
1. Use a root explorer to copy the framework-res.apk.
2. Paste the file on my sd card.
3. Copy the file and paste it in the "place-apk-here-for-modding" folder.
4. Choose option 9 for compile.
5. Open the .xml file with Notepad++.
6. Recompile .apk using option 11.
7. Yes to "is this a system file?"
8. Yes to "keep original files & signatures"
9. Delete the files I modified from the "keep" folder and the resources.ascr file.
10. Finish the build of the .apk.
11. Copy & paste the modified .apk back to my sd card.
12. Rename the file from unsigned-framework-res.apk to framework-res.apk.
13. Use root explorer to cut & paste the modified to my /system/framework folder.
14. Reboot.
I now end up in a boot loop what am I doing wrong??
Click to expand...
Click to collapse
With ApkManager did you delete the 'public.xml' folder in ..\res\values ?

waterpolo said:
With ApkManager did you delete the 'public.xml' folder in ..\res\values ?
Click to expand...
Click to collapse
No, I did not. Was I supposed to?
EDIT: Ok I did some digging and what I have found is that the file size of the original framework-res.apk is 9.32mb. Once I rebuild it whether I modified anything or not the rebuilt .apk is only 7.34mb. Upon further inspection it seems to leave out all of the "value" named folders from the newly built .apk, and it does this whether I use APKTool or APK Manager(even though I say keep files). Has anyone else had this problem?

IM having the same problem,no solution though ! i edited bools.xml but after recompiling its not there ! Anyone solution ?

[Q] Icons

Say I like the icons on one CM9 ROM and want to use them on another, any way I could locate them and save them to the SD? If so where are they located? I've been looking through my root files, and haven't found them. Thanks.

One way to retrieve the icon, is to pull the apk for which ever program icon you want and using 7-Zip (or zip program of your choice, to open apk in another zip program you must rename from .apk to .zip. 7-zip automatically recognizes apk files as an archive, which is nice. ) , open the apk and look in /res/drawable-mdpi and find the icon and copy it to your device.

daggy1985 said:
One way to retrieve the icon, is to pull the apk for which ever program icon you want and using 7-Zip (or zip program of your choice, to open apk in another zip program you must rename from .apk to .zip. 7-zip automatically recognizes apk files as an archive, which is nice. ) , open the apk and look in /res/drawable-mdpi and find the icon and copy it to your device.
Click to expand...
Click to collapse
Thank you very much.

help me how to install

my rom is stock odex i used universal deodexer and deodexed my.system/app and system/framework folders in my pc . now my question.how can i install that app and framework folders to my phone ??(i tried replace with root explorer but it does not .(how can i make thats to a flashable zip?

but
my problem is not that . i can make a flashable zip . its working fine but after i flashed old .odex files doesnt delete. how can i add it to meta inf for when flashing delete app and replace new app and same for framework

You just need to put in a simple delete line into the update script
for example
Code:
delete("/system/app/Vending.apk");
will delete the Vending.apk from the folder system/app
remember if you are manually pushing files with a root browser you need root permissions and you need to set the correct file permissions - for most apps in the app folder it will be rw-r-r

thnx
thanx i learned if i want to delete folde i will use delete_recursive

help
look .
delete(system app systemui.odex
this is working succesfully but after i flashed my zip system ui is lost . it doesnt show . i looked system app its deodexed permissions is rw--r-r its true but doesnt show . what's can i do ?

denizarca said:
look .
delete(system app systemui.odex
this is working succesfully but after i flashed my zip system ui is lost . it doesnt show . i looked system app its deodexed permissions is rw--r-r its true but doesnt show . what's can i do ?
Click to expand...
Click to collapse
most likely if the status bar just doesn't show but does not display a force closed message its because the SystemUI.apk is not correctly signed
as long as the file name is correct and it is correctly compiled with no errors the only thing left is the signing
You can sign an apk easily with zipsigner (playstore)
just copy the apk to any folder on your sd card
start zip signer
select your apk as the input
select the name you want to call it for the output (make it different from the input - you can change the name later)
select platform key as the key you wish to sign (this is for system apps for user apps use a test key)
sign the apk
once done the apk will be outputted as a zip file
change the name of this zip to the name of your apk and don't forget to change the .zip extension back to .apk
put in a flashable and flash in cwm with system mounted
you can check any errors with the SystemUI.apk by doing a logcat via adb as the phone is starting up
By searching the logcat for SystemUI you will be able to see any errors in it and why its not starting - eg Signature mismatch skipping loading

CM12 superuser mod without computer

Since Serajr 'one click' superuser mod only works on stock ROM, you have to use apktool to achieve the same on CM. Here's how you can do it on your phone. Only tested on official CM12 on Xperia Z1c, with a clean flash of /system, (unmodified), but probably can be applied elsewhere, maybe with some adjustment.
1. Follow steps 1 and 2 in this post, (except for the part about copying theme files) - http://forum.xda-developers.com/sony-xperia-z1-compact/general/tweak-theme-computer-t3279649 Note that the /system/framework/SemcGenericUxpRes/SemcGenericUx file is not present in CM ROM, so instead you would copy /system/framework/org.cyanogenmod.platform-res.apk. Also copy /system/framework/services.jar to the same directory.
2. Import the first 2 files as framework, according to step 3 in the link above, then tap on services.jar, and 'decompile all'. You will end up with a folder called 'services-src'.
3. Using a root browser and capable text editor, (I used Mixplorer and Jota+), follow instructions to mod PackageManagerService.smali file here - http://forum.xda-developers.com/showpost.php?p=62909773&postcount=4
Notes on this step: This file is over 60,000 lines long, which is why I specified 'capable' above. Many text editing programs won't handle it very well. Even if they can display it OK, you're going to need something that has a good search function, and copy/paste ability or it will be a big headache trying to do this on a phone. I found the first line to edit somewhere around line 8,700, by searching for 'compareSignatures'. The tutorial recommends using the word 'cannot' to help find the second one, but that didn't work for me. I used 'compareSignature' for that also, and just used the arrows to jump ahead through the search results until I found it.
4. Once the mods are made, save and exit. Then go back to apktool, and tap on 'services-src' folder and choose 'recompile'. You will end up with a file called 'services.apk'. All that is in the 'apk' is a classes.dex file. Use Mixplorer or RTB to extract the classes.dex from the apk. Then, with Mixplorer, go into your original services.jar, (that you copied into apktool folder), and delete the classes.dex file in there. Then go back to your new classes.dex, that you extracted from services.apk, and copy it into the services.jar. Using Mixplorer, you don't have to unzip/rezip or extract anything. Just long-press your new classes.dex, choose copy, then go into the jar just by tapping it, and then paste.
5. Move the new services.jar to /system/framework and reboot, (of course back up your original just in case).
The only way I know to test su mod is to attempt to use something that claims to require it, so I tested it with this - http://forum.xda-developers.com/cro...t-xperia-z5-systemui-particle-effect-t3206206 (the same thread as above). See screenshots for success verification.

very nice

Snapdragon camera v2 help

​Hi. I flashed snapdragon camera v2. But it stops.
Then i want to remove the android icon with the text com.android.cameralauncher. But i cannot find. It. I tryed flashing the uninstal. And searched with a rooted file explorer. But i still have not located the file. Who can help me?

This is also me something went wrong with my account.

60nine said:
ok... i did it this way (using ES file explorer)
1. extract the zip to sd card somewhere
2. under "system/priv-app" > create a folder called "SnapdragonCamera"
3. give the folder "drwxr-xr-x" permissions
4. copy "SnapdragonCamera2.apk" to that folder and give it "-rw-r--r--" permissions
5. copy the "lib" folder (from the zip you've extracted) to "SnapdragonCamera" folder and give it the same permissions as the parent folder has ("drwxr-xr-x")
6. inside the "lib" folder there is also "arm" folder (give it the same "drwxr-xr-x" permissions)
7. inside that "arm" folder there are two ".so" files - give them "-rw-r--r--" permissions
8. reboot
i have to say it's a nice camera and i've used quite a few camera apps so far...
at the first glance - photo quality is the same as with the xdabbeb camera, but i like the UI better...
my device details:
- LG G2 (d802) running somboons stock 30f lollipop rom
- dorimanx kernel (v5.9.2 latest)
- xdabbeb camera and advanced drivers installed
Click to expand...
Click to collapse
Yep this was also the solution for my problem