I want to change locales and images in system apk of CM 7.2.0 on my LG-P500. It is Contacts.apk and CMParts.apk. Decompiling and compiling passed without errors. Everything is ok! But!
When i put on phone already changed Contacts.apk upon transition to a tab of a dialer I receive an (android.process.acore Force Close!) And
When i put on phone already changed CMParts.apk upon transition to Interface/Notification Power Widget/Widget Buttons/Brightness modes I receive an (android.process.acore Force Close!).
Help me please...! I don't know that I do not so. Thanks!
(Sorry for my English)
Did you sign the apk?
I know that some people claim you don't need to sign system apps, but there are times when signing it is the only way to make it work.
Also, did you decompile and recompile with the appropriate framework-res.apk installed (the one from the rom you are using)?
Yes. I put signed and not signed apks. All the same too most. And when I try to decompile with dependences APK Manager writes that this application not the dependent.
TroyxRUS said:
Yes. I put signed and not signed apks. All the same too most. And when I try to decompile with dependences APK Manager writes that this application not the dependent.
Click to expand...
Click to collapse
Have you tried running a logcat to see what the issues are? That's what I always do when I get errors. Usually the logcat will tell you the error in a detailed enough manner that you can go back and fix the code.
Is this by any chance a stock rom? Because if its a stock rom, I've heard of people having issues sticking modified apks into a stock rom.
I have the same problem and would like very very much to know how to solve that ...
thanks
How to install framework?
Press Thanks on getting Helped by me
Related
Modding a 2.1 Sense UI rom (Hero Based.... but more of a hybrid)
Hey, I've edited the AndroidManifest.xml of the HtcDialer.apk, repackaged, sign and first tried to adb push it to my phone - didn't work, tried adb install - parser error, so I repackaged the entire update.zip and reflashed - still didn't work.
Logcat shows this:
Package com.android.htcdialer has no signatures that match those in shared user android.uid.shared; ignoring!
Click to expand...
Click to collapse
I tried popping into recovery and running "fix apk uid errors" but it still throws the same logcat and the dialer won't open.
How do I fix this?
EDIT: I've got this problem, facebook sync and camera/video to fix, then I'll be releasing the fastest SenseUI rom you guys have EVER seen. No joke.
OK, I'm grasping at straws here - so I've also tried, through ADB, completely uninstalling it and rm'ing any traces, then I tried to adb install it and it still won't work, I get an ADB error:
INSTALL_FAILED_UPDATE_INCOMPATIBLE
But everything should be deleted! It shouldn't matter that the old and new signatures don't match, its an entirely fresh install!
I've also noticed that when I adb pu****, I get a list of the HTC apps that share that uid.shared - and at one point they all said "uid=10011" - now they all say "uid=10010". I'm trying to fix this back to he original to see if this is part of the problem, but I can't find this anywhere in the androidmanifest.xml for any off these apps (like contacts, phone, etc).
I know HTC has this shared id stuff for all of their apps, but there must be an easy way to update JUSt an androidmanifest.xml file with a single line to give it vibrate permission. Is there any way I can resign the modified .apk AS Htc?
I have a similar problem (probably the same), does anyone know anything that might help?
Take what was edited and open the original apk with 7zip just drag the edited files in the 7zip window it will ask if you want to add the files, click yes then close out 7zip now pack it up in a update.zip and sign.......Do not sign the apk leave the original signature in there.
Flash adn that should take care of it.
Hi - I need to mod arrays.xml in Values.xml - the autobrightness functionality in 2.2.2 UK retail is a joke.
What is framework-res.apk signed with? Can I get away with platform signing and pushing via ADB? Like I normally do...
PS: I tried the modded apk signed with TestKeys, but got shed loads of FCs on many of the Google Framework apps and services... had to reinstall 2.2.2 via MSU. On a cheery note, in between FCs, the autobrightness worked well!
I pushed the modded framework via ADB, btw.
Any idea welcomed.
Probably the odex nature of the ROM?
Sent from my MB525 using XDA App
In my opinion the problem has nothing to do with the way you signed the framework-res. If the signature check fails all you get is a bootloop.
FYI usually i sign the framework-res with test keys, even when i made heavy mods i had no troubles.
Maybe something wrong in the arrays.xml file?
Thanks, I have modded the xml many times before without issue. I seem to remember that pushing via ADB didn't work before, so maybe I will do it as an update.zip. I am also wondering about permissions. Will explore.
PS: Any view on the fact that /framework is odexed? I note that the apk is 1.2MB smaller when built....!
Guys,
Need your advise on this problem that I'm facing right now. I did some Mod on the Phone.apk but somehow the Phone.apk will FC. I won't see the Pin number entry and it won't detect any mobile signal. If it did pass the two processes mentioned before, it will FC when...
1. I hang up a call.
2. the screen on during the call. (proximity sensor activity)
I did a simple compilation by decompile the original Phone.apk and compile it without any changes and still can't work, even with signed and unsigned APK. Any kind soul able to give me an advise on what to look at...
FYI,
1. The original (stock) deodexed Phone.apk was working flawlessly.
2. ROM - KI4
3. Tools - APK Manager, Brut Apktool
4. Signer - Zipsigner2 (autotest & platform key), APK Manager option number 12; both did not make any difference
Thanks in advance.
Repair permissions?
This often helps. Maybe give it a try.
donalgodon said:
Repair permissions?
This often helps. Maybe give it a try.
Click to expand...
Click to collapse
You mean the file permission. Yup I already did that. Even wiping the dalvik.
Is the phone.apk dependent on other apk? Maybe I signed it incorrectly?
Go to manage application and wipe data of phone.apk
Don't delete the app just wipe data
Solved
Managed to solve it. Seems that any compiled Phone.apk did not work correctly. I had to manually compiled classes.dex and replaced it together with resources.arsc on top of the original Phone.apk
Weird but it does not FC so far.
Bugeca said:
Managed to solve it. Seems that any compiled Phone.apk did not work correctly. I had to manually compiled classes.dex and replaced it together with resources.arsc on top of the original Phone.apk
Weird but it does not FC so far.
Click to expand...
Click to collapse
old post, but i am having the same trouble as you not being able to decompile and recompile a untouch stock phone.apk. what did you do to resolved this? how did you manually compiled the classes.dex file? sorry for being a noob.
Let me start off by saying that I have a condition known as "Sausage Fingers"...I am pretty much unable to use any keyboard I've come across due to the tiny letter keys...Luckily the stock blur keyboard suits my stubby little appendages.
My question is: Is there a way to get this keyboard to work on other ROMS as I have tried and it won't work. I'm experienced in phone development and have done all the things necessary to get an installed keyboard to work...to no avail. Must the APK be modified in some way?
Maybe...
http://forum.xda-developers.com/showthread.php?p=22749340
Sent from; does anyone care?
You need a deodexed version of latinime.apk from blur and that needs to go into /system/app with the proper permissions.
Then you need libjni_latinime.so from blur and that needs to be put in /system/lib with the proper permissions.
Reboot and see if it works. Either way you need more than an apk, you need a matching lib.
thickkeys keyboard
KSmithInNY said:
You need a deodexed version of latinime.apk from blur and that needs to go into /system/app with the proper permissions.
Then you need libjni_latinime.so from blur and that needs to be put in /system/lib with the proper permissions.
Reboot and see if it works. Either way you need more than an apk, you need a matching lib.
Click to expand...
Click to collapse
I realize with a simple google search I could probably find this out but I'll ask anyhow...whats the easiest way to deodex latinime.apk myself?
I tried attaching it for you but keep getting a vbulliten error so I'll link it in a minute. Be prepared to read a logcat when/if this doesn't work. I wouldn't put it past moto to add a dependency on their custom framework but hey you never know ....
EDIT - HERES THE LINK TO DOWNLOAD LATINIME.APK DEODEXED[/URL]
EDIT - Very welcome. I killed the link because im cleaning up my Ubuntu One account. Good luck.
KSmithInNY said:
I tried attaching it for you but keep getting a vbulliten error so I'll link it in a minute. Be prepared to read a logcat when/if this doesn't work. I wouldn't put it past moto to add a dependency on their custom framework but hey you never know ....
EDIT - HERES THE LINK TO DOWNLOAD LATINIME.APK DEODEXED
Click to expand...
Click to collapse
Thanks man...i appreciate it!
I am trying to modify AndroidManifest.xml of settings.apk
But as we all know, if we modify that AndroidManifest.xml, we have to sign the apk so when I modify the AndroidManifest.xml and sign the settings.apk and push it then it doesnt get installed and I get a error in logcat saying there is a mismatch in signatures of the apk and system uid.
Then I tried restoring stock signatures but it still doesnt get installed and in log it says the apk has no signatures because I modified AndroidManifest.xml.
Do anyone have solution for this to sign system apps properly or any other workaround?
I came to know that every system apk and framework apk must be batch signed incase of editing the manifest xml.
I don't think that every apk needs to be re-signed. I've never done this, but my thought was that any apk that has an AndroidManifest.xml with the same original modified dates (you can check the dates with 7-zip) need to re-signed together. Won't it mess up some other apks that don't need to be re-signed if you were to re-sign everything? Please let me know if I am way off..
Also, note that there are other ways to invert the colors in apks besides editing the AndroidManifest... (i.e. edit the /values/styles.xml, /layout/*.xml, etc... can be a pain, but it works) - Sorry, but I guess I am assuming that that's what you are going after by editing the AndroidManifest in the Settings.apk... again, anyone feel free to correct me if I'm wrong on anything here - I am all for learning and sharing!
^^No I dont want to theme it or colorize it
I am adding new functionality for which some new permissions and activity declaration is needed in Manifest file
But if I modify Manifest and use stock signature files it doesnt install and if I resign it then it say signature mismatch with system uid.
Bump!!
I have edited the AndroidManifest.xml in the Settings.apk (for theme color change), and I did not re-sign it after compiling, I retained the originals.
And, it worked fine when I put it on my phone alone (with a flashable zip package), BUT (this is a big but), - it did not get installed when I put it in a ROM package together with all the system files. That's when the signatures become an issue... you need to then re-sign all, or nearly all apps and framework.
At least that's my experience...
Check out this thread.. http://forum.xda-developers.com/showpost.php?p=28475720&postcount=63
Sent from my phone's mind
Oh then I have to sign all system apks
Any other way?
Do you know how to sign with system key which will match system uid?
Only for AOSP ROMs you can resign and apks work. Samsung use closed source.....how could you ever match signatures? Also don't change the Manifest. Leave it. Who says you have to change it?
Note that its via the public.xml that you need to add these listings as to what the apk is now doing. No the manifest. Is it going to market? No so don't change manifest simple. If it is then it shouldn't really be a system app. Also you can disable signature checking within your ROM if that is all you are worried about. I have signed apks from the market that I have themed and then installed them to system and they work fine. Its the apks you use that have dependencies that WON'T work. I.e. apks like Samsung TWiz apks that listen for the system vold boot complete proprietary to Samsung or say an ASOP apk that is trying to chime into something that is framework related in a non-asop ROM.....this then becomes a permissions issue
---------- Post added at 05:09 AM ---------- Previous post was at 05:05 AM ----------
PS: I have edited androidmanifest anyway and apks still work fine.... upgraded the SNS apk to ensure it was fit for use above and beyond SDK 10
varun.chitre15 said:
I am trying to modify AndroidManifest.xml of settings.apk
But as we all know, if we modify that AndroidManifest.xml, we have to sign the apk so when I modify the AndroidManifest.xml and sign the settings.apk and push it then it doesnt get installed and I get a error in logcat saying there is a mismatch in signatures of the apk and system uid.
Then I tried restoring stock signatures but it still doesnt get installed and in log it says the apk has no signatures because I modified AndroidManifest.xml.
Do anyone have solution for this to sign system apps properly or any other workaround?
Click to expand...
Click to collapse
Did you figure out in the end? Still stuck with same problem as you