QUOTE(pikachu01 @ Jan 31 2012, 06:56 PM)
It depends. Some APK edits need to be decompiled, most don't need to (with a simple change to a few lines). If it's an XML edit, it sometimes needs to be decompiled though.
hmm okay, thanks, tonight i try try decompile and make it work, if it works i share share here
QUOTE(antt00 @ Jan 31 2012, 07:13 PM)
To edit xml need to decompile. I am also facing errors when trying to decompile some of turkbey apk. Haven't figured out why yet.
i quote this from the droidforum link i posted, you try see can decompile not
QUOTE
"Yeah not that much to edit, but it sure is better knowing that you can decompile/recompile it... anyways I've tested and verified it to work with APKManager following what I'll explain...
OK... some guy at XDA was tinkering with apktool.jar and noted that this command helped with decompiling the SystemUI.apk... has to do with the certificate signature already in use with the framework-res.apk or to that effect, thus erroring out when trying to decompile SystemUI...
my suggestion is to copy your apktool.jar from the apkmanager 'others' folder to your C drives root directory, so you have it available in both places and much easier than typing on the full path for it when you run this command...
I also had the framework-res.apk and the SystemUi.apk in the C directory as well so that apktool sees them...
then run
java -jar apktool.jar if framework-res.apk
then
java -jar apktool.jar d SystemUI.apk decompiled
Once that's done you should be able to run APKManager as usual and it'll decompile the SystemUI.apk without errors... and it should always be able to decompile that apk from that point on, so you can get rid of the framework, SystemUI.apks, and the decompiled folder from the C directory and it will still decomp[ile in APKManager properly from that point on...