Ok I'm trying to make Mods to the Rosie.apk. But everytime I load my Rosie.apk I continued FC on htc.sense.com, Even if I make no changes to the rosie it still does this...What I'm doing is.....
1) apktool d Rosie.apk
2) I make no changes and just recompile it
apktool b
I get no errors so It seems to build just fine
3)Then I sign the apk
java -jar signapk.jar testkey.x509.pem testkey.pk8 Rosie.apk Rosie2.apk
4)I put it in a flashable zip file(I know this isnt't the problem)
flash it and everything loads fine then nonstop FC
I am running Ubuntu if that makes a difference........ANyone got any Ideas
I know i was having issues similar to this, I think it depends on the rom you pulled rosie.apk from and it's dependancy's when you recompile? Virtuous is giving me fits in this area even without modding anything just decompile and recompile..
My issue is with com.htc.resources
Or is rosie.apk not a system app and dont need signing? I dont think you sign system apps
I do you have the right resources for apktool and I even tried flashing an unsigned version as well with no luck
Related
Wasssup fellas! Ok so I'm no themer but I've started to delve into your world a little bit. I'm looking to draw on the experience of any of you that have successfully modified the Rosie. So here's my set up
I've got Apktool set up in Ubuntu before you ask I downloaded 1.3.1 not 1.3.2
I have all the dependencies in place
I've installed the framework (apktool if com.htc.resources.apk)
Rosie.apk decompiles with no errors (apktool d Rosie.apk out)
I've modified /res/value/colors.xml to add transparency to the app drawer? (This may be my issue)
Compiled (cd out/ .......apktool b) compiles with no errors
I've tried this signing Rosie.apk, Not signing it, Copying out the "Res" and "Resource" file and going into the original Rosie.apk with Ark Manager without extracting the archive and dropped in the "Res and "Resource" files.
Same result each time when I push the file via ADB or put it in a flashable zip the phone boots goes through the animation capacitive keys light up then the phone gets stuck on the last frame of the boot animation and just hangs there forever no boot loops just hangs there?
Any help would be more than appreciated, thanks guys!
Lou
gtalk @ RedemptionRom
email: [email protected]
Rosie in my sky raider theme is working great. And I modified the png's inside it. Didn't need to do all of the things you did. I just themed the png's, zipped it up in an update.zip and then flashed it through recovery.
But I did not edit the colors.xml like you did. I left that alone.
[¦] mobile [¦]
Be sure to use the same com.htc.resources.apk and framework-res.apk from the ROM you took Rosie from.
HeyItsLou said:
Wasssup fellas! Ok so I'm no themer but I've started to delve into your world a little bit. I'm looking to draw on the experience of any of you that have successfully modified the Rosie. So here's my set up
I've got Apktool set up in Ubuntu before you ask I downloaded 1.3.1 not 1.3.2
I have all the dependencies in place
I've installed the framework (apktool if com.htc.resources.apk)
Rosie.apk decompiles with no errors (apktool d Rosie.apk out)
I've modified /res/value/colors.xml to add transparency to the app drawer? (This may be my issue)
Compiled (cd out/ .......apktool b) compiles with no errors
I've tried this signing Rosie.apk, Not signing it, Copying out the "Res" and "Resource" file and going into the original Rosie.apk with Ark Manager without extracting the archive and dropped in the "Res and "Resource" files.
Same result each time when I push the file via ADB or put it in a flashable zip the phone boots goes through the animation capacitive keys light up then the phone gets stuck on the last frame of the boot animation and just hangs there forever no boot loops just hangs there?
Any help would be more than appreciated, thanks guys!
Lou
gtalk @ RedemptionRom
email: [email protected]
Click to expand...
Click to collapse
This means sense failed to load. The phone booted but sense does not work. If you have a back up launcher it would have defaulted to that. Good way to test is to install lp or launcher 2 so next time it will still load in.
synisterwolf said:
This means sense failed to load. The phone booted but sense does not work. If you have a back up launcher it would have defaulted to that. Good way to test is to install lp or launcher 2 so next time it will still load in.
Click to expand...
Click to collapse
Great idea!!! Doing that makes testing much easier fairly obvious don't know how I missed that one.
Berzerker7 said:
Be sure to use the same com.htc.resources.apk and framework-res.apk from the ROM you took Rosie from.
Click to expand...
Click to collapse
The Rosie is part of the theme I'm using which comes with both the Framework-res.apk and com.htc.resources.apk. Am I correct in using this set of framework files or should I be using the Rom's original framework?
What exactly are you trying to modify in rosie? Is it just the app drawer background? I can tell you that rosie has little to do with framework-res. The app drawer background colors are located in launcher.xml and allappsgridview.xml.
deficitism said:
What exactly are you trying to modify in rosie? Is it just the app drawer background? I can tell you that rosie has little to do with framework-res. The app drawer background colors are located in launcher.xml and allappsgridview.xml.
Click to expand...
Click to collapse
I mentioned the framework because apktool requires you to install it to decompile rosie.apk. I will check those xml's out. The failed boot may be because I edited the /res/values/colors.xml file. I don't have my virtual machine fired up but I did edit one of the all_apps strings in there from #ff000000 to #80000000 on the advice of a themer. This may be what f'd me up.
HeyItsLou said:
I mentioned the framework because apktool requires you to install it to decompile rosie.apk. I will check those xml's out. The failed boot may be because I edited the /res/values/colors.xml file. I don't have my virtual machine fired up but I did edit one of the all_apps strings in there from #ff000000 to #80000000 on the advice of a themer. This may be what f'd me up.
Click to expand...
Click to collapse
Yeah don't worry about the colors.xml. just those 2 xmls I mentioned.
deficitism said:
Yeah don't worry about the colors.xml. just those 2 xmls I mentioned.
Click to expand...
Click to collapse
Will do, thanks man.
deficitism said:
Yeah don't worry about the colors.xml. just those 2 xmls I mentioned.
Click to expand...
Click to collapse
What changes should I make to the XML's for transparency? Also after I compile Rosie what do you recommend for a process in getting the new changes implemented? To clarify, should I rip the resources file and classes.dex out of the new compiled version and replace the ones in the stock Rosie? Ive tried about 20 different methods and I get force closes each time...thanks man!
Sent from my ADR6300 using XDA App
If it compiled correctly you should be able to push the compiled version to /system/app with no trouble. There are 2 possibilities:
1) The apk got signed with whatever tool you are using and system apk's can't be signed this way. I think APKManager signed with the test cert automatically.
2) The changes in the xml's may not be correct for which we need to wait for deficitism to verify what was changed. Typically changing color attribs won't cause an FC though.
One thing you can try is to just extract the res folder, where the changes are, in the new Rosie to your PC and open the original with 7zip and drag that folder to the 7zip window. Then push that.
NilsP said:
If it compiled correctly you should be able to push the compiled version to /system/app with no trouble. There are 2 possibilities:
1) The apk got signed with whatever tool you are using and system apk's can't be signed this way. I think APKManager signed with the test cert automatically.
2) The changes in the xml's may not be correct for which we need to wait for deficitism to verify what was changed. Typically changing color attribs won't cause an FC though.
One thing you can try is to just extract the res folder, where the changes are, in the new Rosie to your PC and open the original with 7zip and drag that folder to the 7zip window. Then push that.
Click to expand...
Click to collapse
Thanks dude, I actually figured it out no more help needed.
HeyItsLou said:
Thanks dude, I actually figured it out no more help needed.
Click to expand...
Click to collapse
Cool, glad you got it working.
So what was the cure?
Alright, so I decompiled the apk, edited the XML files I needed to. And now it won't compile. Keeps throwing java errors. Would someone be so kind to compile this for me?
This is a System APK so it needs to be compiled and signed. If you're curious or it needs extra files pulled from somewhere, it's the SystemUI.apk in the CM7 Droid nightly build 88.
Thanks!!
Here's what I need compiled:
http://mikelierman.com/SystemUI.apk.zip
0vermind said:
Alright, so I decompiled the apk, edited the XML files I needed to. And now it won't compile. Keeps throwing java errors. Would someone be so kind to compile this for me?
This is a System APK so it needs to be compiled and signed. If you're curious or it needs extra files pulled from somewhere, it's the SystemUI.apk in the CM7 Droid nightly build 88.
Thanks!!
Here's what I need compiled:
http://mikelierman.com/SystemUI.apk.zip
Click to expand...
Click to collapse
What did you use to decompile it? APK Manager from this thread?
http://forum.xda-developers.com/showthread.php?t=695701
Oh and once you compile it, you don't have to sign it because is a system app and not a regular app.
0vermind said:
Alright, so I decompiled the apk, edited the XML files I needed to. And now it won't compile. Keeps throwing java errors. Would someone be so kind to compile this for me?
This is a System APK so it needs to be compiled and signed. If you're curious or it needs extra files pulled from somewhere, it's the SystemUI.apk in the CM7 Droid nightly build 88.
Click to expand...
Click to collapse
What errors are you getting from apktool? It's going to be hard for someone else to compile an apk that has not been decoded by them and not knowing what files have been changed. Letting us know at least what .png or .xml files were modified would be a start but will work best if we could just figure out why you aren't able to build with your modifications.
The first thing I noticed from the zip you attached is that it's missing the apktool.yml file that should get created a package is decoded. Second, make sure to pull /system/framework/framework-res.apk so resources can be decoded/built properly. If you are using APK Manager, use option 10 to decode with framework-res.apk. If you are just using apktool run the command "apktool if framework-res.apk" before decoding.
mazdarider23 said:
Oh and once you compile it, you don't have to sign it because is a system app and not a regular app.
Click to expand...
Click to collapse
SystemUI.apk actually does get signed using the platform key. The easiest way to do so in my opinion is to use ZipSigner 2 on your phone. Also, once you've placed the modified SystemUI.apk into /system/app make sure it's permissions are rw-r--r--(chmod 644 /system/app/SystemUI.apk) and it's owner:group is root:root(chown 0:0 /system/app/SystemUI.apk). Next reboot to recovery, wipe dalvik-cache and cache, then reboot.
MongooseHelix said:
What errors are you getting from apktool? It's going to be hard for someone else to compile an apk that has not been decoded by them and not knowing what files have been changed. Letting us know at least what .png or .xml files were modified would be a start but will work best if we could just figure out why you aren't able to build with your modifications.
The first thing I noticed from the zip you attached is that it's missing the apktool.yml file that should get created a package is decoded. Second, make sure to pull /system/framework/framework-res.apk so resources can be decoded/built properly. If you are using APK Manager, use option 10 to decode with framework-res.apk. If you are just using apktool run the command "apktool if framework-res.apk" before decoding.
SystemUI.apk actually does get signed using the platform key. The easiest way to do so in my opinion is to use ZipSigner 2 on your phone. Also, once you've placed the modified SystemUI.apk into /system/app make sure it's permissions are rw-r--r--(chmod 644 /system/app/SystemUI.apk) and it's owner:group is root:root(chown 0:0 /system/app/SystemUI.apk). Next reboot to recovery, wipe dalvik-cache and cache, then reboot.
Click to expand...
Click to collapse
Well I'm glad you told me because little old me has been modifying system apps since the days of the nexus one and I've yet to sign one....I think is all depends on who's doing the modification...hahahaha....Good luck 0vermind on finding someone to compiling your systemui.apk!
mazdarider23 said:
Well I'm glad you told me because little old me has been modifying system apps since the days of the nexus one and I've yet to sign one....I think is all depends on who's doing the modification...hahahaha....Good luck 0vermind on finding someone to compiling your systemui.apk!
Click to expand...
Click to collapse
I'm not quite sure what to make of that comment...I certainly wasn't trying to step on your toes so I apologize if it came across that way. Just wanted to help avoid and rule out any issues that might come up. With APK Manager or by using 7zip, you can move the manifest and/or META-INF folder containing the signature from the original but to imply that system apps are not signed is incorrect.
I also think it is important that those messing with system apps understand that there are different keys used to sign apps. For anybody reading this that wants to figure out how certain packages are signed, here's a bit of an explanation. If we extract SystemUI.apk, we see a directory called META-INF. This holds the key/signature info. The key's serial number can be determined with the following command:
Code:
keytool -printcert -v -file SystemUI/META-INF/CERT.RSA | grep SerialNumber
You can check other apks/jars and noticing which have matching serial numbers, meaning they are signed with the same key...
platform key - SystemUI.apk, Settings.apk, Phone.apk, etc
shared key - Contacts.apk, UserDictionaryProvider.apk, etc
test key - Calendar.apk, DeskClock.apk, etc
google proprietary key - Vending.apk, Talk.apk, etc (including some market user apps like Maps, VoiceSearch, Docs)
MongooseHelix said:
I'm not quite sure what to make of that comment...I certainly wasn't trying to step on your toes so I apologize if it came across that way. Just wanted to help avoid and rule out any issues that might come up. With APK Manager or by using 7zip, you can move the manifest and/or META-INF folder containing the signature from the original but to imply that system apps are not signed is incorrect.
I also think it is important that those messing with system apps understand that there are different keys used to sign apps. For anybody reading this that wants to figure out how certain packages are signed, here's a bit of an explanation. If we extract SystemUI.apk, we see a directory called META-INF. This holds the key/signature info. The key's serial number can be determined with the following command:
Code:
keytool -printcert -v -file SystemUI/META-INF/CERT.RSA | grep SerialNumber
You can check other apks/jars and noticing which have matching serial numbers, meaning they are signed with the same key...
platform key - SystemUI.apk, Settings.apk, Phone.apk, etc
shared key - Contacts.apk, UserDictionaryProvider.apk, etc
test key - Calendar.apk, DeskClock.apk, etc
google proprietary key - Vending.apk, Talk.apk, etc (including some market user apps like Maps, VoiceSearch, Docs)
Click to expand...
Click to collapse
Thanks, I didn't know this! I'm glad there's people like you and mazdarider23 on this forum that know **** like this!!!
So I want to make a 4x5 Rosie for CleanROM V / Sense 4.1 using the tut from this site. I have apktool and have done this successfully in the past for CR 4.5 and Sense 4.0.4. For some reason it is not working for me for Sense 4.1 and I need some feedback whether I am doing the right thing:
First I pull the relevant APKs
Code:
adb pull /system/app/Rosie.apk
adb pull /system/framework/framework-res.apk
adb pull /system/framework/com.htc.resources.apk
I then install the framekwork
Code:
apktool if /system/framework/framework-res.apk
apktool if /system/framework/com.htc.resources.apk
I then decompile and recompile the Rosie.apk "for fun"
Code:
apktool d Rosie.apk
apktool b Rosie Rosie_new.apk
I get a bunch of warning messages in the process but not errors. However, when I compare the sizes of Rosie.apk and Rosie_new.apk, I get large differences - 2159 KB (original) bs. 516 KB (new). If I try to flash the new Rosie.apk back to the phone in recovery I get an infinite startup loop.
i can't figure out what I am doing wrong, but I seem to recall that Sense is rather picky about which adbtool it will work with. Any advice?
Anyone?
GroovyGeek said:
Anyone?
Click to expand...
Click to collapse
try installing SystemUI.apk via apktool if.
I'm getting this issue:
I got Settings.apk and framework.apk from a rom, then i opened apktool and
1) imported fw: apktool if framework.apk
2) decompiled apk: apktool d Settings.apk
3)edited a string in a xml
4) rebuilt all: apktool b Settings Settings.apk
5)pushed it into system/app
6) fix permissions and reboot.
Settings now should work, but it doesnt. Can somebody tell me where i do a mistake?
Thank you
(I used win8, but i could use macos or ubuntu as well)
sign it first
ej8989 said:
sign it first
Click to expand...
Click to collapse
I did it. same result. maybe the application I used is not good (Auto-Sign v0.65). what application i've to use?
I didnt write it before, however the rom is on 4.2.1 (cyanogen 10.1)
put your re-complied apk to your phone's sd card and use zipsigner2 from playstore to sign it.
ej8989 said:
put your re-complied apk to your phone's sd card and use zipsigner2 from playstore to sign it.
Click to expand...
Click to collapse
Nothing. Maybe this is not good for 4.2.1? (I've used it lots of times with 4.1)
Well, apktool is using smali/baksmali to compile/decompile classes.dex/apk_name.odex file.
The problem can occur when you use different baksmali version when you decompile and also not the right version to compile (as the system expects it to be). You can also experience issues if the apk is not zipaligned properly (check down who to do that)
apktool has the smali/baksmali code inside it so you will need to get the newest version for it for JB for example.
You can check why the status bar is not there when you monitor the logcat and look for DEX related logs in the beginning.
You can also use smali/baksmali on your own: http://code.google.com/p/smali/wiki/DeodexInstructions
and just place the generated classes.dex in the apk
then zipalign -f 4 filein.apk fileout.apk (http://developer.android.com/tools/help/zipalign.html)
then push back fileout.apk (sytemui.apk in your case)
Sent from my Galaxy Nexus using xda premium
So I asked this question a long while ago, never got an answer, so I am trying again. I am interested in creating a 4x5 Rosie for JB Sense with mikeyxda's tut. I had done so previously for ICS Rosie, but can't seem to get anything going with JB Rosie. I get stuck at the very first step - decompiling Rosie.apk
1) I installed the framework from com.htc.resources.apk, framework-htc-res.apk, and framework-res.apk
2) Decompiled Rosie.apk
3) Without doing anything I attempt to recompile Rosie.apk
When I compare the original (step #2) to the recompiled one (step #3) I see a huge size mismatch - 1868 KB vs. 788 KB. If I flash the recompiled Rosie back to the phone it crashes immediately and does not work. I have tried this with both apktool 1.5.2 as well as VTS, with the same result in both cases.
Any suggestions?
EDIT: after comparing the recompiled and original APK, I am seeing the following differences:
assets\ is stored with zero compression in the original but "deflated" in the recompiled app
META-INF is present in the original but absent in the recompiled app
resources.arsc is a slightly different size and a newer version
Not sure whether any of this is significant or what to do about it. Heeeeeelp
When you decompile Rosie.apk do you get any errors?
Only asking due to the fact that MIUI has a ToolBox mod that was made by a dev, he made a special smali.jar and baksmali.jar for it. He had made the file names of the two main smali files for toolbox too long so the "commercial" smali/baksmali couldn't decompile those files.
Sent from my HTC One X using xda premium
Myrder said:
When you decompile Rosie.apk do you get any errors?
Only asking due to the fact that MIUI has a ToolBox mod that was made by a dev, he made a special smali.jar and baksmali.jar for it. He had made the file names of the two main smali files for toolbox too long so the "commercial" smali/baksmali couldn't decompile those files.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No errors only warnings