I've searched the internet/XDA far and wide for an answer but can't seem to find a solution that fits my exact issue. I'm trying to mod my android keyboard to have red text color instead of white. I decompiled LatinIME.apk and edited styles.xml found in the Values folder. I only changed TWO lines which contain the hex color code for white- "#ffffffff". I changed them to the corresponding hex code for red which looks like #fff44444. I recompiled using ApkMultiTool. I deleted the resources file using the keep folder method and everything compiles fine. I then pushed the app to system/app making the correct adjustments to the permissions. I reboot the phone and keep getting the error message of, "unfortunately, Android Keyboard has stopped." When I go into my sms app and try to open the keyboard to send a text the message pops up again, however in the background my keyboard pops up and it DOES have the red text color I was looking for. So my modifications worked but I can't get the apk to run correctly. The ONLY file I made any modifications to was styles.xml.
I tried to wipe data for the android keyboard as well as my user dictionary but to no avail. I'm using a t-mobile G2X running Eaglesblood 4.0.4 AOSP.
Edit- LogCats In post 3!
bump...
Anyone? After more research I figured it might a signature issue. I swapped out the META-INF and AndroidManifest.XML from the original un-modded apk to my modded APK....Still not luck. I went ahead and also just tried signing the apk (I know you're not supposed to sign system apps but I ran out of ideas!) with SignApk for windows and STILL nothing. I have no idea what is making this app force close =(
These are 3 LogCats that I took immediately after I pushed the modified LatinIME.apk to system/app and did a reboot. After rebooting is when I start getting the errors. After the error message came up I opened Alogcat (application) and took these three. All of them were taken after the error message came up.
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.
I've seen it asked quite a few times now, so I thought I would share how I've been creating my own themes for the Nook. This is a quick and dirty guide as I've almost got it down to a science for quick, keyboard shortcut, theming.
Things you'll need
Photoshop or The Gimp for editing files
Android SDK so you can push and pull files to/from the Nook.
draw9patch app in the Android SDK /tools folder for creating 9.png files
APK Manager (http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1)
Notepad++ or some other text editor for editing XML files. After using Notepad++ on this, I'd highly recommend it though
An attention span
Some restraint
This is a rather good guide that helped me get started. My only complaint is that it is almost to complicated and includes more information than what is needed for a basic theme.
http://forum.xda-developers.com/showthread.php?t=916814
Getting Started:
Download the Android SDK and get it installed.
Download APK Manager
ADB pull /system/framework/framework-res.apk
Make a copy of the framework-res.apk files as a back-up in case you need to revert
Copy the framework-res.apk file to the /place-apk-here-for-modding folder under the APK Manager folder
Launch the APK Manager Script.bat file
Type in 22 to select the default project
Type in the number next to framework-res.apk in the list to select it as your project
Select 1 to extract the files
Select 9 to decompile (this is what makes the XML files readable)
Go to the /projects/framework-res/res folder under the APK Manager folder to view all the files from the theme
Images are located in the /drawable-mdpi folder. XML files are located throughout, but the files specific to layout are under the /layout folder. To change global settings, such as color codes and strings, edit the XML files under the /values folder.
Creating custom PNG files: If you are using Photoshop, use the Save For Web feature when saving. Save the image as PNG-24. Select None under the Matte option. Select None under Metadata.
A word on 9.png files: 9.png files are files that can be stretched by the OS. There is a 1 pixel border all the way around the image. In that 1 pixel border, you'll notice solid black lines here and there. The black pixels indicate which portions of the image are to be stretched. You can add this border and the black pixels in Gimp or Photoshop, or you can open the file the draw9patch app under the Android SDK /tools folder. The draw9patch app will actually display how the image will look when stretched as you add the black pixels around the border, so it can come in handy and it's what I prefer to use. You can open and edit .9.png files in draw9patch and edit the border even after you save the file.
Once you have all your files edited, recompile the APK package with APK Manager
Option 11
y
y
It will tell you to delete the files under the /keep folder that you have edited. Delete any images and XML files, from the /keep folder, you edited under the /projects folder. If you edited XML files, delete the /keep/res/resources.arsc file as well
Press any key to continue and let the script finish
In a separate command line window, mount your Nook's /system folder (adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system)
back in APK Manager, select 8
/system/framework/framework-res.apk
Reboot your Nook
Boot Loop: If you messed something up and are stuck in a boot loop, most of the time you can still mount your Nook, push the original framework-res.apk to it and reboot. Or, you can use an unedited version of the CWM flashable zip file from the link below.
NOTE: it is not smart to push your framework-res.apk file to the Nook. I've learned the hard way that you can only do this about 10 times before you run out of memory and can no longer boot your Nook until you reflash Froyo again.
I'd recommend only a few flashes on a bare bones copy of Froyo until you feel comfortable with working on the framework theme. After that, I'm attaching a base, flashable zip for you to use in CWM so you can flash the theme instead of pushing. This will prevent you from getting stuck in a boot loop (unless you do something wrong yourself).
To add your framework-res.apk file to the zip, just open the zip and replace the /system/framework/framework-res.apk file (I'd recommend 7zip).
A Few Goodies
I'm including all of the PSD files I use to edit and create themes. If you want to create your own, custom theme, these will get you started. The only downside to these PSD files is that they are at the MDPI scale. If you want to create an HDPI theme, you'll need to increase the sizes.
Link to PSD files for creating your own theme, plus the flashable CWM zip file:
http://jjis.me/android-theme-templates
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
PMDColeslaw said:
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
Click to expand...
Click to collapse
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
wretchedlocket said:
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
Click to expand...
Click to collapse
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment updater-script.zip
PMDColeslaw said:
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment 546902
Click to expand...
Click to collapse
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
PMDColeslaw said:
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. I had too many things to do with the family yesterday.
If you haven't got this working yet, I'd suggest trying to start with removing just the /system/app/Vendind.apk file via the updater-script. If it works, then go back in and add each additional line until you run into problems again. At that point, you'll know what your problem is.
Since everything else (framework-res.apk, services.jar, etc.) gets replaced successfully, leave those lines alone. I'd just start with the basics of replacing the Vending.apk first and then work your way back up from there.
Im trying to teach myself here and actually reading unlike others at times, but What my GOAL: is to remove the GPS icon in my ROM when it is not active. I may be wrong so please correct me if I am...
I started with "APKtool" to decompile my "systemUI.apk" I then edited "HtcCdmaStatusBar.smali" located in "com/android/systemui/statusbar/policy"
I ran into a problem with compiling it back together with errors (after trying for hours to find my mistake) I moved on to...
"APK-Manager"
Again following instructions I decompiled "systemUI.apk" using "com.htc.resources.apk" as well since its a system file..
It seems to have worked, it said to delete whatever I modified in the "keep" folder well the ".smali" files don't appear only XML and system images but I went ahead and tried to take that "SystemUI.apk" that I recompiled with the edited files and dropped it in my phone via root manager
(well yea that didnt seem to work)
I moved on to this link http://forum.xda-developers.com/showthread.php?t=549309
I used it as a reference to edit the files I wanted to and not the the ones that were on the guide. well I had no errors and I and did everthing correctly, as i thought and the finally step I pushed the "SystemUI.apk" via adb and then rebooted
That resulted in a force close on my "status bar" i believe it said when I booted it up, after i cleared the force close my phone worked fine except the fact I had NO TASKBAR what so ever...
I am running "Showdown 1.0'
http://forum.xda-developers.com/showthread.php?t=1209777
Like always, Thanks for any help or ideas in advanced....
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Where did the thread go? Dont see it in Q &A forum??? Having the same problem
I was JUST having a very similar issue.. I was trying to decompile and recompile rosie but it kept giving me errors. Someone said try apkmanager 4.9 (I was using 5) and my problems went away. Also I noticed if you are using a file that has already been modified apkmanager didnt seem to like that. I had to take a stock one, make the xml changes, build it then replace whatever images I had replaced in the original
and now I cant get the ***** to build right. I'm not trying to mod it so the pull down notification bar is semi-transparent but it wont build correctly
pastebin of my apkmanager log file http://pastebin.com/uZ8JacJL
I'm trying to do some editing to the status_bar.xml, but anything I do causes force closes and no status bar.
I'm pulling SystemUI.apk via ADB, decompiling with APK Multi-Tool, making a change in the status_bar.xml as small as changing the background color of it, compiling with APK Multi-Tools, and pushing with ADB. Every time, it just disappears and starts spam force closing.
Any ideas?
EDIT: Changing ANYTHING from SystemUI.apk seems to cause force closes.
Muffunz said:
I'm trying to do some editing to the status_bar.xml, but anything I do causes force closes and no status bar.
I'm pulling SystemUI.apk via ADB, decompiling with APK Multi-Tool, making a change in the status_bar.xml as small as changing the background color of it, compiling with APK Multi-Tools, and pushing with ADB. Every time, it just disappears and starts spam force closing.
Any ideas?
EDIT: Changing ANYTHING from SystemUI.apk seems to cause force closes.
Click to expand...
Click to collapse
What rom are you running? How are you installing the modded apk? What exactly are you trying to change? Are you making multiple mods at once? If you're modding any xml within the apk and it fc's when you install it, it's either not compiling properly or the changes you made aren't kosher. Try using apk manager with the latest apk tool to decompile and compile and see if that helps.
Also, if all you wanna do is change the status bar background color, just decompile the systemui.apk, edit statusbar_background.9.png (without breaking the pixel guides) recompile the apk, and instead of flashing the recompiled apk, extract that .png and drop it into the stock apk and flash that.
10tonhammr said:
What rom are you running? How are you installing the modded apk? What exactly are you trying to change? Are you making multiple mods at once? If you're modding any xml within the apk and it fc's when you install it, it's either not compiling properly or the changes you made aren't kosher. Try using apk manager with the latest apk tool to decompile and compile and see if that helps.
Also, if all you wanna do is change the status bar background color, just decompile the systemui.apk, edit statusbar_background.9.png (without breaking the pixel guides) recompile the apk, and instead of flashing the recompiled apk, extract that .png and drop it into the stock apk and flash that.
Click to expand...
Click to collapse
I'm on UnNamed, and I'm pushing the APKs via ADB in command prompt. I'm trying to change the color of the status bar right now, but I'd also like to change the icons. I did what you suggested, but it didn't change anything. Bar is still there and no force closes, but it's still the same color even though the 9.png file is a different color.
Muffunz said:
I'm on UnNamed, and I'm pushing the APKs via ADB in command prompt. I'm trying to change the color of the status bar right now, but I'd also like to change the icons. I did what you suggested, but it didn't change anything. Bar is still there and no force closes, but it's still the same color even though the 9.png file is a different color.
Click to expand...
Click to collapse
Do this, the compiled systemui that's giving you fc open it and the unmodified version. Drag nine patch image you edited to the unedited systemui
Sent from my SGH-I777 using Tapatalk
10tonhammr said:
What rom are you running? How are you installing the modded apk? What exactly are you trying to change? Are you making multiple mods at once? If you're modding any xml within the apk and it fc's when you install it, it's either not compiling properly or the changes you made aren't kosher. Try using apk manager with the latest apk tool to decompile and compile and see if that helps.
Also, if all you wanna do is change the status bar background color, just decompile the systemui.apk, edit statusbar_background.9.png (without breaking the pixel guides) recompile the apk, and instead of flashing the recompiled apk, extract that .png and drop it into the stock apk and flash that.
Click to expand...
Click to collapse
jivy26 said:
Do this, the compiled systemui that's giving you fc open it and the unmodified version. Drag nine patch image you edited to the unedited systemui
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
I tried that. Nothing happened, the status bar didn't change.
Muffunz said:
I tried that. Nothing happened, the status bar didn't change.
Click to expand...
Click to collapse
Don't adb push it. Just flash it. Download winrar (google it). Download one of my themes (or any theme) for unnamed, delete all the the folders except "system" and "Meta". Open system folder and delete eveything except "apps" folder. Open apps folder and delete everything. Add your modded systemui.apk to the apps folder and flash in cwm.
Its MUCH MUCH easier to use APK Manager and have it push it as an unsigned system app. After you push it, run an "adb shell killall system_server" <-- does a quick system reset, and you can test it out.
I'm not sure what changed but I finally got APK Manager set up to be able to push things itself, and I finally got a change to go through! Thanks for the help guys.
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