update: found all the right tools, needed patch apktool and updated aapt.exe from sdk13 ( HC3.2)
attached at bottom of post.
has anyone managed to decompile any Honeycomb systemui.apk without any errors? I have tried a few, many diff. ways and keep getting error: mulitple resources in dimens.xml and a bunch of java code. looks like it may not have been compiled properly?? Is there a way to force decompile? or maybe someone with linux and apktool latest version 1.4.2?
anyone made a UOT Kitchen theme with honeycomb and systemui.apk yet?
thanks for the help guys.
seeing if UOT kitchen could manage.. this is the saem error I get.
Decompiling framework-res.apk UOT-11-22-22-09-2
I: Loading resource table...
I: Loaded.
I: Decoding file-resources...
I: Decoding values*/* XMLs...
I: Done.
I: Copying assets and libs...
Decompiling SystemUI.apk UOT-11-22-22-09-2
I: Framework installed to: /root/apktool/framework/1.apk
I: Baksmaling...
I: Loading resource table...
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources: spec=0x7f090009 dimen/status_bar_icon_padding, config=-port-v13at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:65)
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:58)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:196)
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:165)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:130)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:105)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:82)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:48)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibResources.java:315)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.java:50)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.java:43)
at brut.androlib.Androlib.getResTable(Androlib.java:44)
at brut.androlib.ApkDecoder.getResTable(ApkDecoder.java:148)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:98)
at brut.apktool.Main.cmdDecode(Main.java:120)
at brut.apktool.Main.main(Main.java:57)
Compiling framework-res.apk UOT-11-22-22-09-2
W: Could not find sources
I: Building resources...
I: Building apk file...
Compiling SystemUI.apk UOT-11-22-22-09-2
I: Framework installed to: /home/uot/apktool/framework/1.apk
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathNotExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:142)
at brut.androlib.Androlib.build(Androlib.java:159)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:103)
at brut.androlib.Androlib.readMetaFile(Androlib.java:138)
... 4 more
unzipped .apk and tried axmlprinter2:
It sounds a lot like the systemui.apk resources have malformed or invalid xmls, what rom source are you using exactly?
Try decompiling 506/507 to see if any of those work first, i'm guessing you're using the ones from r6.
yes r6, I though I have tried others even from a stock ROM. I wasnt able to extract system.img as I have in the past (Im on windowze) because I restored my laptop and all my tools are gone.
If you could check when you have time to try to decompile any honeycomb systemui.apk I would be grateful as I have been researching a lot, and Im sure its just a waste, as you say this is malformed or "hack" compiled Im sure.. not saying it was DJ's doing..
and rather that try to extract system .img with windows.. ( ive tried yaffs expert.apk.. no help) and cygwin.dll, with unyaffs.exe, and wunyaffs, both end up with stack trace dump. which tells me this .apk is bad news. I think it said something about a permissions error with unyaffs; My next step was going to fastboot 507/508 system.img and then pull systemui.apk, likely could screw up my ROM. I like R6 though works best for me.
thanks for the help TheManii
would you be able to unpack 506/507 system.img and just send me the .apk I will try to decompile if you are busy or just let me know if youre able to decompile one.. that would be a tremendous help.
this is definetly something we should not be seeing on an official ROM correct??
the system.img inside the 50x pkgs are ext4, not yaffs2, you'll need something that can read ext3/4 partitions to open it.
but i'm getting the same error in decompiling the systemui.apk in 506-wifi, you might want to ask brut about this, afaik the latest apktool can decompile normal HC level apks.
As an aside, I wouldnt expect r6 themes to be compatable with r7+ as r7+ are based on 507, same reason cwm isnt compatable with r6
at the least I think it should just decompile with errors and just display the multiple resources. so you're getting this on an official ROM, thats not good coding is it?
coding is serious business though. I will have to post on bruts google project page.
found this, a few people have same issue.
http://code.google.com/p/android-ap... Type Status Priority Milestone Owner Summary
huh, was it really part of api13? i figured it would have been 11/12
but one of the hc releases (i guess it was 3.2/api13) introduced dpxnn support, if you look at systemui.apk\res\layout-sw600dp or drawable-sw600dp-mdpi they overlap with the normal versions because it provides a more granular approach.
Didnt know apktool still doesnt support it. Regardless all api13+ apps should be doing it this way preferably.
more research finds this..
The "multiple resources" problem occurs when the same resource appears in two configurations in the apk (e.g. two screen sizes), which are not detected by apktool in ResConfigFlags.java. In the two cases above, the problematic resource appears in both the default config and the XLARGE config which apktool does not detect. Therefore, apktool tried to add the same resource to the default config twice rather than creating an XLARGE config space.
Ferenc Boldog's fix in https://github.com/fboldog/brut.apktool/commit/1b6d63cb355d4a36274f5edf0383a2c4e6e0f868 solves that particular problem by adding XLARGE support. Thanks Ferenc!
know how this boldog's file might work on windows?? I emailed brut.all to see if I could get a beta..
If it works without any further mods you can recompile it or wait for the next ver of apktool, i'm guessing that part/fix will be in it.
You'd need at least the jdk to compile it, and depending on file structure, linux
it seems I have found an apktool for sdk13 posted by brut on his page.. I need to get my own SDK13v aapt.exe though, updating my android sdk manager now... installing 4.0 too , this could be a while..
here is the .zip I found for sdkr13 (3.2), give it a shot if you have the latest sdk and aapt, curious if it works.
got it... woo hoo stoked! needed sdk r13 aapt.exe , didnt work with apktool 1.4.1 but did with another apktool for for 3.2
That's good news, as I'll also need to eventually recompile 3.2 apks if i ever get around to adding full langs into chimeradroid
and I got status bar clock themed for my ICS theme... cool..
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
chrisrotolo said:
got it... woo hoo stoked! needed sdk r13 aapt.exe , didnt work with apktool 1.4.1 but did with another apktool for for 3.2
Click to expand...
Click to collapse
I'm still having a ton of issues with this, could one of you walk me through it? I'm working with the Asus Transformer, but having the same issue. I can now decompile properly with apktool, but compiling just fails miserably...
I have apktool 1.4.2, but apparently the new aapt.exe is needed? Would you be able to give me a link to that?
updated first post. attached .zip of apktool and files that worked for me.
@JDV28, are you decompiling a stock .apk? or themed .apk? and what kind of changes are you making? .xml edits? .9.png's? and what a re the errors? so we can try to help.
chrisrotolo said:
updated first post. attached .zip of apktool and files that worked for me.
@JDV28, are you decompiling a stock .apk? or themed .apk? and what kind of changes are you making? .xml edits? .9.png's? and what a re the errors? so we can try to help.
Click to expand...
Click to collapse
I think I figured out my own issue, I was decompiling and recompiling a themed SystemUI.apk, and if I remember correctly, that doesnt work.
Am I right? If so, why??
Also, I am getting a 9patch error like you said in the pm, any fix for that? that's the only issue now.
Personally I would suggest making any.xml edits , recompiling then dragging .9's and any other .png's and dropping them into the new .apk arhive. You could try xultimate search for it I think its on Droid forums.
Link: http://forum.xda-developers.com/showthread.php?t=700904
There are many guides on how to patch .9 's
Related
Hi can anyone suggest an alternative tool for apktool. It just doesn't work for me. Whatever I do either gives compiling errors or just a bootloop. Thanks guys.
It's nice to know I'm not the only one. Anything past extract optimize and zip is useless for me. I have never had it actually compile an .apk without an error.
I'm having serious problems compiling the framework-res from a CM6.1 based ROM. It decompiles fine, but won't recompile I get hundreds of errors about missing referances.
I only wanna edit a few XML's :sad:
Sent from my HTC Hero using Tapatalk
l0st.prophet said:
I'm having serious problems compiling the framework-res from a CM6.1 based ROM. It decompiles fine, but won't recompile I get hundreds of errors about missing referances. I only wanna edit a few XML's :sad: Sent from my HTC Hero using Tapatalk
Click to expand...
Click to collapse
Which xmls do you want to edit, and what are you wanting to change?
dean.d said:
Which xmls do you want to edit, and what are you wanting to change?
Click to expand...
Click to collapse
Thanks for replying, but I worked it out. I had some dodgy .9.png's that were breaking the compile, so I just had to remove them before compiling.
For anyone else having trouble, check the logs after you decompile to see if there are any messages about .9.pngs. If there are, remove them from the decompiled folder, compile when you are finished, then just add the .9.png's back in afterwards with WinRAR.
I was tryna change the color of the text and the border in the bottom popup menu for my Gingerbread theme
l0st.prophet said:
Thanks for replying, but I worked it out. I had some dodgy .9.png's that were breaking the compile, so I just had to remove them before compiling.
For anyone else having trouble, check the logs after you decompile to see if there are any messages about .9.pngs. If there are, remove them from the decompiled folder, compile when you are finished, then just add the .9.png's back in afterwards with WinRAR.
I was tryna change the color of the text and the border in the bottom popup menu for my Gingerbread theme
Click to expand...
Click to collapse
The reason that happens is the original "dev" who themed the framework did not decompile/modify/recompile. He merely dragged and dropped the modified .9.png
Hence when u decompile, apktool cannot find the necessarry data within resources.arsc to decompile the .9.png and hence when u go to recompile, it complains. Ur safest bet is to always decompile an apk as close to stock as possible.
Where do you place your framework-res.apk I placed mine in the platform tools folder but apktool can not find it
Trying to create Circle Batt (no other changes) through UOT Kitchen for the Assonance 5.0 ROM.
When it finishes with the loaded Framework-res.apk file, the finished screen shows SHTF, and has an error log as follows:
+ WORKING_DIR=UOT-DW-12-15-19-37-1
+ java -Xmx64m -jar ./tools/apktool.jar d data/working_dir/UOT-DW-12-15-19-37-1/framework/framework-res.apk data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec
I: Loading resource table...
I: Decoding resources...
I: Copying assets and libs...
+ WORKING_DIR=UOT-DW-12-15-19-37-1
+ java -Xmx64m -jar ./tools/apktool.jar b data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/ data/working_dir/UOT-DW-12-15-19-37-1/framework-unsigned.apk
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'keyguard_password_attempt_count_pin_code_1' has no default translation in /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res; found: he_IL
aapt: warning: string 'permdesc_restartPackages' has no default translation in /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res; found: he_IL
aapt: warning: string 'permlab_restartPackages' has no default translation in /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res; found: he_IL
/home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res/values-hdpi-v4/drawables.xml:3: error: Resource entry stat_sys_battery_6 is already defined.
res/drawable-hdpi-v4/stat_sys_battery_6.png:0: Originally defined here.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL9068952899748163720.tmp, -x, -0, arsc, -S, /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res, -M, /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL9068952899748163720.tmp, -x, -0, arsc, -S, /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/res, -M, /home/circle/ver2b/data/working_dir/UOT-DW-12-15-19-37-1/temp/fw_dec/AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more
Click to expand...
Click to collapse
Anyone know if this file can be used? I am presuming not. But there really is no documentation on that site about this type of thing.
Is that ROM already themed? It has to be with a stock framework for that kitchen to work.
I'd say so. It says "Modified version of Gingerbread Theme".
I wonder what I need to do to get Circle Batt then. I'll ask in that thread, in the meantime if you have any thoughts, it is appreciated.
ewingr said:
I'd say so. It says "Modified version of Gingerbread Theme".
I wonder what I need to do to get Circle Batt then. I'll ask in that thread, in the meantime if you have any thoughts, it is appreciated.
Click to expand...
Click to collapse
I say use a stock framework, get the pngs for the battery from the kitchen. Open up the kitchen apk with winrar/7zip (doesnt matter if you unzip to extract them) pull all the batt icons out and drop them into the ROM framework that you want to use (do not unzip the framework, explore apk contents using winrar/7zip).
Thanks for the suggestion.
I'd say if I had the stock framework, the UOT Kitchen would have worked. Problem is, I don't have the stock framework.
I have posted a query on the thread. One person there said the UOT worked for him. I don't know if he got that same error I did or not. I'm tempted to ask for his file...but then I want to be sure. I think I'll have to reload completely again if it borks my load (at least that's all I know to do when that happens).
Getting tired of flashing lately. Hoping to settle for a while
Reefermattness said:
I say use a stock framework, get the pngs for the battery from the kitchen. Open up the kitchen apk with winrar/7zip (doesnt matter if you unzip to extract them) pull all the batt icons out and drop them into the ROM framework that you want to use (do not unzip the framework, explore apk contents using winrar/7zip).
Click to expand...
Click to collapse
+1
When making my battery mod for the Gingerbread theme, this is what I did, and it worked perfectly.
Any suggestions on where I can get the stock file?
Oh, and did you apply that to the Assonance 5.0 ROM? I see from your SIG that you are on Perception Build 3, which was not Gingerbread.
ewingr said:
Any suggestions on where I can get the stock file?
Oh, and did you apply that to the Assonance 5.0 ROM? I see from your SIG that you are on Perception Build 3, which was not Gingerbread.
Click to expand...
Click to collapse
ANY stock framework.... All you need is the pngs inside.
Sent from my SGH-T959D using Tapatalk
Reefermattness said:
ANY stock framework.... All you need is the pngs inside.
Sent from my SGH-T959D using Tapatalk
Click to expand...
Click to collapse
To be more precise, you are saying to 'replace the pngs inside', right?
My comfort zone is to use UOT Kitchen. I tried the replace once, and somehow screwed things up.
So it sounds like I can take any 2.2 framework-res.apk, and run it through the kitchen and use it.
But, then I've tried using one that worked, for example, from a Cognition 3, and use on a 4 (Maybe not those specific builds), and it didn't work.
Having been burned on this from a couple different angles, I'm just a bit skittish.
Couldn't you just get the *.png's from FightSpit's original thread for his Circle Batt Mod?
Then just put them into your framework-res.apk and re-apply using your favorite tool (ADB Push or Root File Manager).
Maybe. I was told I need the 'original' framework file. but maybe that's only if i want to use UOT, which was in fact my question. That is my preference, but I'm coming to see that it is impossible if you have a modified theme.
ewingr said:
So it sounds like I can take any 2.2 framework-res.apk, and run it through the kitchen and use it.
Click to expand...
Click to collapse
Never, ever, use a framework-res.apk that was not part of the original rom in question.
PNG files are easily replaced using any zip file editor.
Sent from my Captivate.
So just so I'm understanding correctly, if I want to customize the battery pngs manually (or any png for that matter?) I can:
Upload a stock 2.2 framework to UOT Kitchen, pull out the pngs, place them in say Perception 9's or Assonance 5's framework-res.apk? Can I also just create pngs using an image editor and drop those in?
How would I reapply using adb or Root File Manager? Do I need to use a tool of some sort to sign the apk after I change the pngs?
I'm trying to get into doing my own theming... so still learning! I'm using this guide to get started: http://forum.xda-developers.com/showthread.php?t=817998.
the kitchen seems to be having issues for me as well. no matter what framework-res i use i get errors. even stock ones.
I am trying to modify XMLs of Jelly Bean Contacts.apk. Using apktool that has been used for ICS and other Jelly Bean apks, I can decompile and then recomplie it without any error. However, the recompiled Contacts.apk would not work in cell phone, showing a message "Unfortunately, Contacts has stopped!".
To simplify the problem, I simply do decompiling and then recompiling without any modifications. I found that the size of resources.arsc has been changed from 1480 KB to 1525 KB. The new Contacts.apk causes FC!
Note: Files in smali folder can still be modified. After editing, use apktool to recompile and create a new apk. Then use WinRAR or 7zp to drag the newly created classes.dex into the original Contacts.apk. Such a "modified" Contacts.apk works properly. Note here that we did not modify resources.arsc.
This problem is only related to resources.arsc!! XMLs cannot be recompiled!!
Does anybody have the same problem? Do you know how to solve this problem? Any solutions or suggestions are appreciated.
Did anybody try this?
Are you all ok with modifying Contacts.apk?
With the current apktool jar file you can not edit any XML in the contacts apk. It has to be done in source code
Sent from the BatCave
zelendel said:
With the current apktool jar file you can not edit any XML in the contacts apk. It has to be done in source code
Sent from the BatCave
Click to expand...
Click to collapse
Thank you for your reply. The question is why we can edit XML in other apks except Contacts.apk.
Is there any magic?
framework-res.apk, Settings.apk, SystemUI.apk, Phone.apk are all ok without any problem.
iBotPeaches, the author of apktool, wrote: "Looks like we have new resource type. T9Map. Will have to code support for it. Its just loosing it on rebuild."
See discussions at: https://github.com/iBotPeaches/brut.apktool/issues/11
I know that there are already several thousand threads on forums spanning the internet involving recompiled framework-res.apk's causing bootloops, but the ones that are actually useful pretty much all say the same thing, that is to replace the meta-inf folder and AndroidManifest.xml from the newly built apk with the ones from the original file. Needless to say, that hasn't worked in my case, and neither has changing from apk-manager (wanam's latest version) to using command line apktool or from using flashable zips to adb pushing the file to /system/framework. Primary and secondary frameworks are both installed. The apk decompiles and recompiles without errors. SystemUI.apk, the only other apk I've worked on thus far, flashes without issues. I don't have a lot of experience with adb, and right now I can't remember the exact error it gave me, "protocol error" perhaps? Firmware is deodexed 9.0.1.D.0.10 / Nordic "SuperSport".
Quite probably I'm doing or not doing something really basic that will make me look and feel foolish once this is resolved, but I'm out of ideas and I just want to start modding some 9.png's. Does anyone have any suggestions?
Sv: [Q] V - Bootloops with modded framework-res.apk usual fixes not helping
Try the framework-res from here and let me know
http://forum.xda-developers.com/showthread.php?p=36503238
NuriJ said:
Try the framework-res from here and let me know
http://forum.xda-developers.com/showthread.php?p=36503238
Click to expand...
Click to collapse
Thanks, but that didn't work either. Here's exactly what I did, maybe there's something obvious I'm doing wrong:
1. Dragged the framework-res.apk from your zip to my apktool folder.
2. Decompiled with the command "apktool d framework-res.apk". Without the quotes, of course.
3. In this case I didn't modify anything, I simply recompiled with the command "apktool b framework-res". It gave me this:
C:\apktoolv3>apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'BaMmi' has no default translation in C:\apktoolv3\framewo
rk-res\res; found: ar bg ca cs da de el en_GB es es_US et fa fi fr hi hr hu in i
t iw ko lt lv ms nb nl pl pt pt_PT ro ru sk sl sr sv th tl tr uk vi zh_CN zh_TW
I: Building apk file...
4. Deleted assets, res and resources.arsc from the original framework-res.apk inside your zip. Dragged those folders/files from within the rebuilt apk in my framework-res/dist folder to the original apk.
5. Dragged the framework-res.apk from your zip to a flashable zip. I've used this zip successfully to flash modded versions of SystemUI.apk, so I don't see a reason it wouldn't work for this.
6. Booted into TWRP recovery.
7. Wiped cache and dalvik cache.
8. Flashed the zip.
9. Bootlooped.
Am I missing something? I've gotten so used to using apk-manager that I wouldn't be surprised if it's just something I'm doing wrong in apktool.
shockwaverider said:
Thanks, but that didn't work either. Here's exactly what I did, maybe there's something obvious I'm doing wrong:
1. Dragged the framework-res.apk from your zip to my apktool folder.
2. Decompiled with the command "apktool d framework-res.apk". Without the quotes, of course.
3. In this case I didn't modify anything, I simply recompiled with the command "apktool b framework-res". It gave me this:
C:\apktoolv3>apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'BaMmi' has no default translation in C:\apktoolv3\framewo
rk-res\res; found: ar bg ca cs da de el en_GB es es_US et fa fi fr hi hr hu in i
t iw ko lt lv ms nb nl pl pt pt_PT ro ru sk sl sr sv th tl tr uk vi zh_CN zh_TW
I: Building apk file...
4. Deleted assets, res and resources.arsc from the original framework-res.apk inside your zip. Dragged those folders/files from within the rebuilt apk in my framework-res/dist folder to the original apk.
5. Dragged the framework-res.apk from your zip to a flashable zip. I've used this zip successfully to flash modded versions of SystemUI.apk, so I don't see a reason it wouldn't work for this.
6. Booted into TWRP recovery.
7. Wiped cache and dalvik cache.
8. Flashed the zip.
9. Bootlooped.
Am I missing something? I've gotten so used to using apk-manager that I wouldn't be surprised if it's just something I'm doing wrong in apktool.
Click to expand...
Click to collapse
you need to install the semcgenericUPS file as well....I cant think of the exact commands now, but I will try and dig them out and post them tomorrow...
gregbradley said:
you need to install the semcgenericUPS file as well....I cant think of the exact commands now, but I will try and dig them out and post them tomorrow...
Click to expand...
Click to collapse
If you mean install it as a secondary framework in apktool, I've done that.
Sent from my LT25i using xda premium
shockwaverider said:
If you mean install it as a secondary framework in apktool, I've done that.
Sent from my LT25i using xda premium
Click to expand...
Click to collapse
ok, I think you may need to ask in the apktool thread in android hacking and develpment section
Before I go asking there I was thinking it might be worth starting over from scratch, using a completely stock firmware instead of spida_singh's modded version and flashing Nuri's deodexing package. Not that I really expect it to help, but it's worth a shot.
Sent from my LT25i using xda premium
You were right man.. I just changed the framework-res for the first time today and it didn't boot. Then i've tried without even touching anything.. Just with a clean recompile but still, it bootloops
NuriJ said:
You were right man.. I just changed the framework-res for the first time today and it didn't boot. Then i've tried without even touching anything.. Just with a clean recompile but still, it bootloops
Click to expand...
Click to collapse
Frustrating, isn't it? I haven't had much time these past few days to really follow up any more on this, like gregbradley said, we might need to ask in the apktool thread, but I've wanted to make sure I've tried absolutely everything else before I ask there. I think I'm pretty much at that point now.
shockwaverider said:
Frustrating, isn't it? I haven't had much time these past few days to really follow up any more on this, like gregbradley said, we might need to ask in the apktool thread, but I've wanted to make sure I've tried absolutely everything else before I ask there. I think I'm pretty much at that point now.
Click to expand...
Click to collapse
Yes, I think the apk tool is not compatable with ICS framework without some modifications. There are work arounds but asking the people who use it most will get you the best answers
gregbradley said:
Yes, I think the apk tool is not compatable with ICS framework without some modifications. There are work arounds but asking the people who use it most will get you the best answers
Click to expand...
Click to collapse
True. The jump from GB to ICS was a huge PITA for me, and I'm somewhat dreading upgrading to JB, as far as theming goes.
I finally just found this version of APK Manager in my DropBox, it's the one I used for months without problems but couldn't find it before because I stuck it in the wrong folder when I changed computers recently. Nuri, if you want to try it go ahead, I'm at work now and won't be able to do anything with it for at least another 12 hours, and possibly not until this weekend. I know it's a long shot, but it can't hurt to try.
EDIT: I also found this in the Xperia T/V/whatever Apps & Themes forum in the "[MOD] Reduced size onscreen buttons" thread, basically that another user (with a different device?) solved his bootloops by replacing the resources.arsc in his rebuilt apk with the original. I haven't followed that up because to be honest, that's only mildly useful for me as I tend to do a lot of modifications in /values/styles.xml as well as in other values files, so of course I need to be able to use the rebuilt resources.arsc. But for anyone not doing any edits in values, this may be enough of a workaround to get a working framework-res.
shockwaverider said:
True. The jump from GB to ICS was a huge PITA for me, and I'm somewhat dreading upgrading to JB, as far as theming goes.
I finally just found this version of APK Manager in my DropBox, it's the one I used for months without problems but couldn't find it before because I stuck it in the wrong folder when I changed computers recently. Nuri, if you want to try it go ahead, I'm at work now and won't be able to do anything with it for at least another 12 hours, and possibly not until this weekend. I know it's a long shot, but it can't hurt to try.
EDIT: I also found this in the Xperia T/V/whatever Apps & Themes forum in the "[MOD] Reduced size onscreen buttons" thread, basically that another user (with a different device?) solved his bootloops by replacing the resources.arsc in his rebuilt apk with the original. I haven't followed that up because to be honest, that's only mildly useful for me as I tend to do a lot of modifications in /values/styles.xml as well as in other values files, so of course I need to be able to use the rebuilt resources.arsc. But for anyone not doing any edits in values, this may be enough of a workaround to get a working framework-res.
Click to expand...
Click to collapse
I'll try :good:
..about that post.. He wrote that nothing changed, if he replaced the resources.arsc with stock one. Of course nothing would change then..
Hmm atleast i got the point, it's the resources.arsc file which apktool builds that's unable to boot with.
So yea maybe it's something with apktool
I'm afraid I didn't have any better luck with that version of apk-manager, either with or without replacing resources.arsc.
i find this Tutorial http://forum.xda-developers.com/showthread.php?t=1823223
ideeseng said:
i find this Tutorial http://forum.xda-developers.com/showthread.php?t=1823223
Click to expand...
Click to collapse
Good find, I'll try this out over the weekend, although I definitely hope to get an actual fix at some point.
Sent from my LT25i using xda premium
shockwaverider said:
I know that there are already several thousand threads on forums spanning the internet involving recompiled framework-res.apk's causing bootloops, but the ones that are actually useful pretty much all say the same thing, that is to replace the meta-inf folder and AndroidManifest.xml from the newly built apk with the ones from the original file. Needless to say, that hasn't worked in my case, and neither has changing from apk-manager (wanam's latest version) to using command line apktool or from using flashable zips to adb pushing the file to /system/framework. Primary and secondary frameworks are both installed. The apk decompiles and recompiles without errors. SystemUI.apk, the only other apk I've worked on thus far, flashes without issues. I don't have a lot of experience with adb, and right now I can't remember the exact error it gave me, "protocol error" perhaps? Firmware is deodexed 9.0.1.D.0.10 / Nordic "SuperSport".
Quite probably I'm doing or not doing something really basic that will make me look and feel foolish once this is resolved, but I'm out of ideas and I just want to start modding some 9.png's. Does anyone have any suggestions?
Click to expand...
Click to collapse
I suspect I know where you're going wrong..
Try Tickle My Android. Install SemcGenericUxpRes.apk before decompiling framework-res.apk. Then make your changes, recompile and use Tickle My Android's Prepare System Files For Flashing option.
If you get no luck, let me know and I can try a few things..
Sent from my SK17i using xda premium
Ticklefish said:
I suspect I know where you're going wrong..
Try Tickle My Android. Install SemcGenericUxpRes.apk before decompiling framework-res.apk. Then make your changes, recompile and use Tickle My Android's Prepare System Files For Flashing option.
If you get no luck, let me know and I can try a few things..
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
Thank you, helpful stranger!
I had a quick go of it when I got home (from a 16-hour workday no less), and so far it's been more of the same. I'll post details in your thread when I'm feeling a bit more functional, but basically I did what you said. Your tool failed on creating a flashable zip, and I once again had bootloops when I used my own zip. Regardless, I'm really impressed with TMA, and I hope with your help I can get some real use out of it!
Sv: [Q] V - Bootloops with modded framework-res.apk usual fixes not helping
Anyone tried with the new jelly bean framework?
NuriJ said:
Anyone tried with the new jelly bean framework?
Click to expand...
Click to collapse
Haven't tried yet, and tbh I haven't even had the time lately to upgrade to JB. Taking a quick look around the threads, it looks like we now have working cwm, is this right? After the bootloop problems I had with ICS, there's no way I'll try modding framework-res without recovery, lol.
btw NuriJ, is there a version of your modded shutdown menu for JB?
shockwaverider said:
Haven't tried yet, and tbh I haven't even had the time lately to upgrade to JB. Taking a quick look around the threads, it looks like we now have working cwm, is this right? After the bootloop problems I had with ICS, there's no way I'll try modding framework-res without recovery, lol.
btw NuriJ, is there a version of your modded shutdown menu for JB?
Click to expand...
Click to collapse
Yes working on that.
.. I just had time and tried to today. It doesnt boot.. just like ics, it stops at bootanimation and bootloops
btw yes see dev section vdsirotkin managed to include cwm into the stock jb kernel
Has anyone else had issues compiling sense 5 apk's using VTS? I can't nothing to compile, please leave your experiences with this issue.
Thank You
I too am having issues.
I've got VTS working and have made all my XML changes to settings.apk, with the correct linkage to the resources.apk, but when I recompile, I get a whole bunch of errors from public.xml saying the string declared here is not defined.
From what I can find by searching, this has something to do with the IDs changing, but not being updated in the public.xml file.
I'm a noob at reverse engineering APKs though. I normally compile my ROMs from source.
Hoping for some guidance.