So there is this PinyinMe keyboard which looks the most like an iphone keyboard which I like as my phone is an iPhone Replica.
1. So the things I want to do is change the APK to a normal APK but I only know the way by TitaniumBackup but this app aint installed so it doesnt work.
2. The next thing I want to do is edit the APK xml files so I can remove all the chinese signs in it and change it to normal letters (mainly english).
- I already tried this but the APK wont install
3. If this is all working, I would like to make a second version of it which has AZERTY keyboard instead of QWERTY.
Please, I would really apreciate it and others too.
bOyka8 said:
So there is this PinyinMe keyboard which looks the most like an iphone keyboard which I like as my phone is an iPhone Replica.
1. So the things I want to do is change the APK to a normal APK but I only know the way by TitaniumBackup but this app aint installed so it doesnt work.
2. The next thing I want to do is edit the APK xml files so I can remove all the chinese signs in it and change it to normal letters (mainly english).
- I already tried this but the APK wont install
3. If this is all working, I would like to make a second version of it which has AZERTY keyboard instead of QWERTY.
Please, I would really apreciate it and others too.
Click to expand...
Click to collapse
Here's the APK and OBEX which I forgot to add
http://www.mediafire.com/?216cm8rcgi2z5m8
I really hope someone can help me out with this !
Ok so in this ZIP file is the original APK that you can just install and use. Also the one I edited which gives App not installed.
Can anyone look into this please??
http://www.mediafire.com/?216cm8rcgi2z5m8
bOyka8 said:
Ok so in this ZIP file is the original APK that you can just install and use. Also the one I edited which gives App not installed.
Can anyone look into this please??
http://www.mediafire.com/?216cm8rcgi2z5m8
Click to expand...
Click to collapse
You have two files in the zip. One is an .apk and the other is an .odex file.
I saw this thread as I was browsing around and came across your GooApple thread.
I am not sure what your level of expertise is, but basically, an apk from a manufacturer comes in two parts (.apk and .odex). If you want to edit the app, you must either edit both the .apk and .odex files, or you can 'deodex' the file which basically takes the contents of the .odex file and places it inside the .apk file.
If you have deodexed an apk file (removed the need for the .odex), you no longer need the .odex file. In this way, you get 'deodexed' ROMs with no .odex files inside. These are much easier to edit and work with.
There are lots of tutorials to find out more about this and about deodexing and editing .apk files if you search.
Here is a good starting point
If you are already aware of this, I apologise
nobnut said:
You have two files in the zip. One is an .apk and the other is an .odex file.
I saw this thread as I was browsing around and came across your GooApple thread.
I am not sure what your level of expertise is, but basically, an apk from a manufacturer comes in two parts (.apk and .odex). If you want to edit the app, you must either edit both the .apk and .odex files, or you can 'deodex' the file which basically takes the contents of the .odex file and places it inside the .apk file.
If you have deodexed an apk file (removed the need for the .odex), you no longer need the .odex file. In this way, you get 'deodexed' ROMs with no .odex files inside. These are much easier to edit and work with.
There are lots of tutorials to find out more about this and about deodexing and editing .apk files if you search.
Here is a good starting point
If you are already aware of this, I apologise
Click to expand...
Click to collapse
Hey man, thanks for giving me this information.
I did read about deodexing but havent had the time to look it up. And I think TBP does the deodex (I could be wrong) when changing the system app to a user app.
Anyways, I have been able to edit the xml & png's, but whenever I try to install the newly created APK, I get the error : App not installed.
Maybe this deodexing can do the trick, I'll test it out once I find 30min of free time ^^
Titanium backup doesn't deodex the .apk. That is why you are having the issue. You can swap pngs etc without decompiling, but to edit smali and some xmls etc you have to decompile... it is much easier if you have first deodexed your apk to remove the .odex file.
nobnut said:
Titanium backup doesn't deodex the .apk. That is why you are having the issue. You can swap pngs etc without decompiling, but to edit smali and some xmls etc you have to decompile... it is much easier if you have first deodexed your apk to remove the .odex file.
Click to expand...
Click to collapse
I did recompile a working APK, but when I put it all back together and try as a system/normal app and do zipalign or no zipalign, I always get an error or just a crash. But probably deodexing will do the trick.
Hopefully I'll get some time this week for doing it cause its like:
Wake up - Eat - Job - Eat - Sleep - Eat - Soccer - Eat - Sleep
The life of a mailman
Related
Hello!
I'm trying to make my own Rom right now. With dsixda's Kitchen it isn't very hard to do so I thought I'd just give it a try. I'm taking a rooted official Update (Version: 2.10.405.2) as my base. Adding busybox runparts, the /data/app functionality, a2sd+, the custom bootanimation functionality etc. isn't a problem. Removing some apps like Maps, Facebook, Teeter (and so on) and adding some like Rom Manager, Neocore or Quadrant isn't a problem, too. But if I want to implement a theme like the Carbon Espresso Mod or a theme I made with the UOT Kitchen I'm getting bootloops at booting the phone. Here's what I do: I unzip the folder (for example a theme made with the UOT Kitchen) and I copy over the framework-res.apk from the unzipped folder to my Working Folder of the Kitchen (to system/framework) and I overwrite the original framework-res.apk.
And NO: I didn't choose a battery mod or a bootanimation in the UOT Kitchen....
Hope you guys can help me
I might be wrong but doesn't the new file have to be signed? I know there is a signing option in the kitchen.
Sent from my PC36100 using Tapatalk
It's a system .apk so it doesn't have to be signed.
I can't shed any light on the subject, but here's a bump.
Are you replacing the whole "framework-res.apk" file? If so then you will need to resign your entire ROM. Why? When you change a system file ("framework-res.apk", "com.htc.framework.apk", "twframework-res", "rosie.apk", etc.) it no longer has a matching "signature" for all the files it serves images to. Plug your phone into your computer and open up "ddms" in your android_sdk > tools folder to watch what happens when the phone boots up.
A workaround (The way I do it, it's more fun IMHO) is to open up your .apk files in 7zip (or if you're on a mac BetterZip) and add the images from the themed .apk to your stock .apk. This way makes it so your original .apk has the same signature as your other system files yet has the new images from the other files that you wanted. I've had a lot of luck with this method. I don't know if it will still work if you change any .xml files as I have not messed with those yet.
I've subscribed to this thread so if you have any questions post back here or you can PM me if you want. I'm on XDA all day, every day so I'll try to help as much as I can.
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
DomiKamp said:
Thanks for all the answers! Especially to you, mbobino. Is there a way to sign the whole Rom new? When I make my Rom at the End, the Kitchen signs it automatically, doesn't it? The idea with the images is very good, but if I want to implement a theme like Carbon Espresso it isn't that easy, 'cause Carbon Espresso isn't just a few images. There are several .xml's etc.
Click to expand...
Click to collapse
The kitchen signs the .zip that you flash when you build it. It does not sign any .apks for you on its own. However, there is an option to sign .apks within the kitchen.
In my opinion, taking all of the images and figuring out how it all works is fun. I feel like I've already learned quite a bit from just digging around and moving files around.
As for the .xml files, you can decompile the .apk and edit them and then recompile the .apk. I'm actually looking into this today. It sounds like some work but hopefully I'll get it figured out.
Sounds like fun indeed So, I'll just have to try it. Where can I find the "Settings" for the Notification Bar? Thanks
The variois status*.xml files in the res/layout folder of the framework-res.apk and the status*.smali files in the services.jar.
What? If I want to implement a Theme made with the UOT Kitchen (without battery) I should just copy over those files to my existing res-framework.apk OR copy over the whole res-framework.apk (the new one) and sign it?
EDIT: Just tried it with a theme from the UOT Kitchen and it worked perfectly. I've just signed the res-framework.apk and the htc.com.resources.apk (or whatever) in the Kitchen, flashed it on my Phone and it just worked like a Charm. But I have got a 50% Transparent Notification Bar and all the system icons (Battery and time/date) are still black and not transparent! Has anyone got a idea where to change this? (.xml or whatever)...And does anyone know where I can find the HTC Wallpapers? I want to change them a little bit
HeyItsLou said:
The reason you boot loop is mis matched resource ID's in the public.xml file. If you decompile the framework using apktool after adding your images using an archiver then recompile apktool will update the public file for you which saves you from pulling ID''s for every image. I have a video tutorial of how to set up apktool and decompile framework in my Rom thread. Changing images in app apk's won't cause you to boot loop just messing with the framework will.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
HeyItsLou, I looked up your ROM thread but couldn't locate the video tutorial.... do you mind providing the url? Specifically, I am trying to add to the list of wallpapers in a ROM. (I have setup apktool but not sure where/which folder to add my wallpapers in Framework-res.apk Launcher.apk before recompiling/signing). Thanks.
You COULD use the Theme Porter by daneshm90. It will only port the PNG s for it so things like clock colour n stuff will be lost, but it will get you alot closer...
http://forum.xda-developers.com/showthread.php?t=737526
Sent from my HTC Hero using XDA App
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
DomiKamp said:
Thanks! But like I've written before in my Edit, I made it. The bigger theme (Carbon Espresso) wasn't a problem, too. I just had to sign the .apk's in system/app and system/framework (the kitchen doesn't do it by itself. You have to choose the option to sign a single .apk and then look, where the system/framework .apk's are...). Works great now!
Click to expand...
Click to collapse
Isnt that what I said in the 2nd post -.- lol jk. Glad you got it working!
Yes! And that's why I tried it. And it worked! Thanks Husker and, of course, everybody else!
Glad you got it working. Welcome to the development side of android!
Sent from my PC36100 using XDA App
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
bestialbub said:
I don't sign system files or apps and apkmanager among other threads I've read say not to. Im on a rooted backflip. I find I only have to sign third party apps to install.
Why do you have to sign YOUR files?
Click to expand...
Click to collapse
I was curious about this too. I always edit the framework-res of any ROM I flash using a custom set of images I have and have never signed the apk afterwards and it has always worked. Maybe cause I'm only replacing images? I usually do this with framework-res and twframework-res and they both can sometimes grow by 1MB or more. Just my experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
DomiKamp said:
Sorry for answering that late. Had a few things to do, so I wasn't online very often
If you want to cook an App into your Rom (NeoCore for example), then you don't have to sign it. You can just copy it into data/app. But if you want to change the whole framework-res.apk of the Rom, you have to sign it. 'Cause if you don't sign it, you'll get a Bootloop. The framework-res.apk is a very important part of the Rom, so it has to "fit" to the others. There are some ID's which have to match. Otherwise it won't work. That's how I understood it
Another Question: Has anybody got an Idea where to change the things that are coming, when you first start the phone with a new Rom (the "installation" of the Rom)? I wan't to write: "Welcome to DomiKamp's Rom!" Or something like that...
Click to expand...
Click to collapse
I think that in order to do the "welcome to" thing you'll have to edit the update-script file. I'm not 100% on it though. Look at a cm Rom and see what all is in there.
Sent from my HTC Evo 4G using XDA App
Hey all, Well i know we could not wait for a Honeycomb theme, i know i cannot, but heres my conundrum.
I have made a honeycomb keyboard, but cannot get it to install for the life of me, ive used the testkeys, shared, platform, etc (all using Signapktic from Stericson. Does anyone have any clue as to why it will not install?
A few questions that i know you might ask, answered ...
No, there is no other keyboard, other than swype, and samsung keypad..
I made it off of the GB keyboard...
Yes, I have made many of themes, many of changes to Frameworks, and have had sucess installing, and running my custom roms....
My question basically is this, IF POSSIBLE, CAN ANYONE SIGN THE FILES I HAVE TO MAKE THIS WORK? PM ME AND I SHALL SEND THE FILES. CREDIT WILL BE GIVIN, I AM ON THE OTHER HAND GOING TO NEED SOME SORT OF PROOF YOU KNOW WHAT YOUR DOING, I WORKED REAL HARD ON THIS, SO FOR RIGHT NOW ITS PRIVATE, HENSE THE PM.
THANKS AGAIN IN ADVANCE. REMEMBER .. LETS GET THIS HONEYTCOMB GOING
I know that most of the keyboards dont work simply by installing but rather need to be pushed to the data\app or data\app_s folder depending on which rom you are running. You can accomplish this using adb or using a file explorer like RootExplorer.
Thanks
Thank you man, this helps a whole lot. Now do i need to re-sign each apk inside the rom folder? or can i just re-sign the .zip?
georgegreco86 said:
Thank you man, this helps a whole lot. Now do i need to re-sign each apk inside the rom folder? or can i just re-sign the .zip?
Click to expand...
Click to collapse
I'm not sure what .zip you're refering to other than a CWM recovery flashable .zip for you keyboard. If this is what you mean, then use the same signiture (key) you'd find in any of the flashable .zips on the forums. In other words, just copy over the META-INF folder from some other .zip to yours. Of course, you'll want to make sure the update-script in this folder is pointing at the proper directories for installation.
For your apk, you should only need to sign it if you changed the AndroidManifest.xml. Otherwise, just keep the META-INF folder from them original apk.
Sorry for all the questions lately, even though I'll probably have more.
I'm working on the SystemUI.apk from IE20 and my method of compiling consists of using the keep folder method and deleting all the files I changed with apk manager 4.9.
Now I can change the Status_bar.xml and status_bar_tracking.xml without a hitch, however if I delete status_bar_expanded.xml from the keep folder (whether I change anything in it or not) I get force closes when I get it loaded onto my phone.
There's no error in the log so I'm pretty lost...So I was wondering if there's something else I have to do that anyone knows of?
Thanks if you can help!
The only thing that should be deleted are images that you edited (if you didn't edit any images just leave the folder). But if you edited ANY xml ONLY delete the resourses.arc from the keep folder. But don't delete any individual xml's from keep. And yes the size will change because of the compression used in apk mgr.
good day.
chopper the dog said:
The only thing that should be deleted are images that you edited (if you didn't edit any images just leave the folder). But if you edited ANY xml ONLY delete the resourses.arc from the keep folder. But don't delete any individual xml's from keep. And yes the size will change because of the compression used in apk mgr.
good day.
Click to expand...
Click to collapse
Thanks for the response,
However, by not deleting the xmls I edited in the keep folder it seems it just replaces them with the stock files.
Soo...This stopped the force closes, but none of my edits took.
Maybe it's time to to switch to a linux build environment...I'm frustrated to say the least. Google'd every possible problem and nothing...
EDIT: But before I do that could someone possibly try to compile this SystemUI.apk with a color edit in the res/layout/status_bar_expanded file?
Would highly appreciate this ^^^
Can anyone tell me if its possible to add the 1% battery mod to a stock odex ics rom? I have a moto razr maxx. Is there a way i can mod this myself? I tried uot kitchen but it only shows increments of 10% on my phone.
Thanks!
Yes, it can be done. My phone's ROM is the stock odexed ROM and I have 1% battery increments. You need to edit framework-res.apk, you can use apktool or APK Multi Tool or whatever to unpack the APK, and rebuild it afterwards. To get 1% battery, you need to edit/replace some XMLs.
I'll try find a link to show how the XMLs should be and some commonly used icons.
EDIT: Here: http://forum.xda-developers.com/showthread.php?t=724778
Find a style you like, download it and copy the two folders from inside into the "res" folder in your unpacked APK, overwriting any existing files (you may need to rename the drawable-hdpi-v4 folder depending on your phones resolution)
But UOT should work. Make sure in the "battery" section you changed at the top from "Custom battery" to "SCB with %" and then selected the style you want.
SifJar said:
Yes, it can be done. My phone's ROM is the stock odexed ROM and I have 1% battery increments. You need to edit framework-res.apk, you can use apktool or APK Multi Tool or whatever to unpack the APK, and rebuild it afterwards. To get 1% battery, you need to edit/replace some XMLs.
I'll try find a link to show how the XMLs should be and some commonly used icons.
EDIT: Here: http://forum.xda-developers.com/showthread.php?t=724778
Find a style you like, download it and copy the two folders from inside into the "res" folder in your unpacked APK, overwriting any existing files (you may need to rename the drawable-hdpi-v4 folder depending on your phones resolution)
But UOT should work. Make sure in the "battery" section you changed at the top from "Custom battery" to "SCB with %" and then selected the style you want.
Click to expand...
Click to collapse
what phone do you have? i already tried the uot and it will not work. from what im understanding you would need to edit the systemUI.odex file to allow for battery % but i have no clue how to do it.
fix-this! said:
what phone do you have? i already tried the uot and it will not work. from what im understanding you would need to edit the systemUI.odex file to allow for battery % but i have no clue how to do it.
Click to expand...
Click to collapse
I have an HTC Explorer. But I believe the battery icon is stored in framework-res.apk, and not SystemUI.apk, so SystemUI.odex shouldn't be a problem (SystemUI.odex is the odex file of SystemUI.apk - you can't edit odexed apps, you would have to deodex SystemUI.apk first; this means combining the SystemUI.odex and SystemUI.apk files into one, deodexed SystemUI.apk, which can then be edited).
Although UOT may require you to upload a deodexed SystemUI.apk along with framework-res.apk, because some theme mods required SystemUI.apk. So you might need to get a deodexed SystemUI.apk. There's a guide to deodexing here: http://forum.xda-developers.com/showthread.php?t=1208320
It is a slightly complicated process, but it's not impossible to figure out I don't know for sure if this is what you need to do to make it work though. Make sure you have a nandroid backup before you flash the theme
i guess ill wait for a dev to deodex the stock rom then. the uot kitchen states it can work on odex roms but in my case it does not.
fix-this! said:
Can anyone tell me if its possible to add the 1% battery mod to a stock odex ics rom? I have a moto razr maxx. Is there a way i can mod this myself? I tried uot kitchen but it only shows increments of 10% on my phone.
Thanks!
Click to expand...
Click to collapse
Anything's possible... See HERE, HERE, and a mini re-odex tutorial HERE.
And, I believe there were some major framework/system changes in the transition from GB to ICS - so, the battery files may have moved to SystemUI from framework-res..
alteredlikeness said:
Anything's possible... See HERE, HERE, and a mini re-odex tutorial HERE.
And, I believe there were some major framework/system changes in the transition from GB to ICS - so, the battery files may have moved to SystemUI from framework-res..
Click to expand...
Click to collapse
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
fix-this! said:
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
Click to expand...
Click to collapse
You'd also need to upload all the .jar and .odex files from /system/framework I think to make it possible to deodex systemUI.apk.
EDIT: If you do that, I should probably be able to deodex it for you. (Assuming that process hasn't changed for ICS, which I don't think it has). Once you have this file deodexed, you should be able to use UOT, it supports ICS battery mods.
EDIT: If you need an easy way to copy those files off the phone, you can try this: http://androidcommander.com/
fix-this! said:
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
Click to expand...
Click to collapse
Sorry, but I'm not too familiar with ICS yet... eagerly waiting Q3 for my phone.
Plus, I ported the battery from a deodexed set so I don't know all of the smali/xml edits involved if I were to do it from scratch...
You could still upload a whole system dump or cwm backup for me to look at ...if you wanted to. It'll let me get familiar with Moto's ICS..
SifJar said:
You'd also need to upload all the .jar and .odex files from /system/framework I think to make it possible to deodex systemUI.apk.
EDIT: If you do that, I should probably be able to deodex it for you. (Assuming that process hasn't changed for ICS, which I don't think it has). Once you have this file deodexed, you should be able to use UOT, it supports ICS battery mods.
EDIT: If you need an easy way to copy those files off the phone, you can try this: http://androidcommander.com/
Click to expand...
Click to collapse
im uploading now if someone can do this for me, i cannot figure it out. the razr devs do not seem interested in doing this on a ics leak.
http://www.mediafire.com/?m1i08symjcalvy4
uploaded system/framework & app
fix-this! said:
http://www.mediafire.com/?m1i08symjcalvy4
uploaded system/framework & app
Click to expand...
Click to collapse
Downloading now, provided it works I should have it up in 15 - 20 mins
EDIT: Appears it's a bit different, trying another approach now which will take a bit longer, but seems to be working for now at least (doing it this way means deodexing all the files).
EDIT: I'll try and get SystemUI.apk uploaded tonight, the rest will have to wait to tomorrow if you want them.
EDIT: There is a possibility I will need "init.rc" from the root of your device (i.e. not inside any folders like "system" or "data") to properly deodex all the files. A few seem to be giving errors and stuff.
Here's the (hopefully) deodexed SystemUI.apk [well, it IS deodexed, the "hopefully" refers to hopefully it's done right]. Try this with UOT (along with framework-res.apk, which isn't odexed in the first place), and as I said before, be sure to make a nandroid backup before hand.
You may also need to delete the SystemUI.odex file from your phone after applying the theme, I am not completely sure. If after applying the theme it has not worked, try doing so - worst case scenario you should be able to restore your nandroid backup if deleting the .odex file breaks something.
SifJar said:
Downloading now, provided it works I should have it up in 15 - 20 mins
EDIT: Appears it's a bit different, trying another approach now which will take a bit longer, but seems to be working for now at least (doing it this way means deodexing all the files).
EDIT: I'll try and get SystemUI.apk uploaded tonight, the rest will have to wait to tomorrow if you want them.
EDIT: There is a possibility I will need "init.rc" from the root of your device (i.e. not inside any folders like "system" or "data") to properly deodex all the files. A few seem to be giving errors and stuff.
Click to expand...
Click to collapse
heres the file you need to deodex.
fix-this! said:
heres the file you need to deodex.
Click to expand...
Click to collapse
Thanks. I can try deodex all the jars and apks with that tomorrow if you want. For now, SystemUI.apk seems to have deodexed fine without it, so you can grab it above and try UOT with it (that's the only file UOT needs other than framework-res.apk which isn't odexed anyway). Let me know if it works
SifJar said:
Thanks. I can try deodex all the jars and apks with that tomorrow if you want. For now, SystemUI.apk seems to have deodexed fine without it, so you can grab it above and try UOT with it (that's the only file UOT needs other than framework-res.apk which isn't odexed anyway). Let me know if it works
Click to expand...
Click to collapse
ill try it but if you think you could deodex everything that would be great.
used uot with the modded systemUI and it didn't work, still only getting 10% increments. i think the entire system/app & framework needs to be deodexed.
fix-this! said:
used uot with the modded systemUI and it didn't work, still only getting 10% increments. i think the entire system/app & framework needs to be deodexed.
Click to expand...
Click to collapse
Just found this HERE - looks like a good 1% battery tutorial...
But, from the look of your system, you have battery files (images/xmls) in BOTH the SystemUI.apk and framework-res.apk - how's that?
I don't think I'll be able to upload the deodexed files. It'd be a large file, and I don't really want to waste the bandwidth I'm afraid.
It's not a hard process for you to do though. There are two main options. Either buy Titanium Backup Pro for your phone, and then load it up and press menu, then "more" and then "Undo sys Dalvik integration..." which will deodex everything in /system/app (but not /system/framework), or else download this: http://forum.xda-developers.com/attachment.php?attachmentid=972719&d=1333088601 (I'd strongly recommend this second method)
Extract the ZIP, and place everything from /system/app in "_app" and everything from /system/framework in "_framework". Run AutoDEOToolMain.bat. Select option 2, then paste in this as the custom BootClassPath:
Code:
core.jar:core-junit.jar:bouncycastle.jar:ext.jar:framework.jar:framework-ext.jar:android.policy.jar:services.jar:apache-xml.jar:filterfw.jar:com.motorola.android.frameworks.jar:com.motorola.android.widget.jar:com.motorola.frameworks.core.addon.jar
Let it run, and all the deodexed files will be in the deodexed folders. Any files that weren't deodexed will be in the original folders.
This is really quite an easy process, so I'm sure you could achieve it yourself.
EDIT: There still seem to be a couple of errors with the above BootClassPath, the following two JARs seem to be missing: /system/framework/kafdex.jar and /system/framework/com.motorola.orange.simauth.jar (I removed them from the BootClassPath because the JARs were missing, if you can find these two JARs add :kafdex.jar:com.motorola.orange.simauth.jar to the end of the above BootClassPath and put the two JARs in "_framework". Then I think you will be able to deodex every JAR and APK. Without them, most still seem to work though. (A number of the APKs in /system/app do not deodex properly. A little googling has shown me that motorola often neglect to include com.motorola.orange.simauth.jar on their phones [probably to try and stop deodexing] and this is the main problem)
EDIT: Try using this tool to mod your battery: http://forum.xda-developers.com/showthread.php?t=1434061
Use the deodexed SystemUI.apk along with the standard framework-res.apk, and download one of the 1% battery mods from that thread. I really don't think the rest of the system apps being odexed should cause an issue.
Hi guys,
my father recently bought a so-called China phone (Doogee X5max) that comes with several malwares right out of the box.
Most of the are quite easy to remove, two of them give me the creeps.
I am no pro when it comes to Android and so I stumbled across several problems.
First of all I managed to remove the malware from Settings.apk and SystemUI.apk by decompiling, editing and odexing the files and compiling them again. Easy going...
So far so good.
Now for the hard part.
How to get those files back into the ROM? Since those files need to be resigned with the same certificate that was used signing all the other system files I am kind of stuck here. Resigning the files with Zipsigner (using all possible types, "platform", etc.) did not work which leads me to the conclusion that Doogee did not use the AOSP certificates to sign their ROM. Am I right?
The only possible solution seems to be creating a custom ROM out of the Doogee X5max stock ROM. Is this correct?
I googled a lot but have not found up-to-date or understandable manuals/instructions on how to do this.
Can someone please help me or give me a hint at least?
Thanks in andvance
deomaki
deomaki said:
Hi guys,
my father recently bought a so-called China phone (Doogee X5max) that comes with several malwares right out of the box.
Most of the are quite easy to remove, two of them give me the creeps.
I am no pro when it comes to Android and so I stumbled across several problems.
First of all I managed to remove the malware from Settings.apk and SystemUI.apk by decompiling, editing and odexing the files and compiling them again. Easy going...
So far so good.
Now for the hard part.
How to get those files back into the ROM? Since those files need to be resigned with the same certificate that was used signing all the other system files I am kind of stuck here. Resigning the files with Zipsigner (using all possible types, "platform", etc.) did not work which leads me to the conclusion that Doogee did not use the AOSP certificates to sign their ROM. Am I right?
The only possible solution seems to be creating a custom ROM out of the Doogee X5max stock ROM. Is this correct?
I googled a lot but have not found up-to-date or understandable manuals/instructions on how to do this.
Can someone please help me or give me a hint at least?
Thanks in andvance
deomaki
Click to expand...
Click to collapse
After recompiling your modded apk, unzip it and the original apk, replace everything in the original apk with what is in your modded apk except meta-inf and Android manifest. Zip back up, change it from .zip to .apk. That is what you use to replace your system apk. That only goes for system apks. You sign the others.
Tulsadiver said:
After recompiling your modded apk, unzip it and the original apk, replace everything in the original apk with what is in your modded apk except meta-inf and Android manifest. Zip back up, change it from .zip to .apk. That is what you use to replace your system apk. That only goes for system apks. You sign the others.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
Before giving this a chance, just one question: By "Android manifest" I suppose you mean manifest.ms?
Kind regards
deomaki
deomaki said:
Hi,
Thanks for your reply.
Before giving this a chance, just one question: By "Android manifest" I suppose you mean manifest.ms?
Kind regards
deomaki
Click to expand...
Click to collapse
I have never seen a manifest.ms but I suppose so if that is what is in yours.
Tulsadiver said:
I have never seen a manifest.ms but I suppose so if that is what is in yours.
Click to expand...
Click to collapse
The manifest.ms resides inside the META-INF folder...
Trying to installl the so manipulated original apk via adb results in [INSTALL_PARSE_FAILED_NO_CERTIFICATES].
Am I supposed to uninstall the original settings.apk from the device first (which I did) or just replace the original apk on the device with the newly created one and delete the odex in oat/arm?
Thanks in advance
deomaki
deomaki said:
The manifest.ms resides inside the META-INF folder...
Trying to installl the so manipulated original apk via adb results in [INSTALL_PARSE_FAILED_NO_CERTIFICATES].
Am I supposed to uninstall the original settings.apk from the device first (which I did) or just replace the original apk on the device with the newly created one and delete the odex in oat/arm?
Thanks in advance
deomaki
Click to expand...
Click to collapse
You leave the original meta-inf like I said. You use the original apk replacing everything in it with the modded stuff, res, resource.arsc if any and any classes.dexs. Don't worry about any oat folders.
Tulsadiver said:
You leave the original meta-inf like I said. You use the original apk replacing everything in it with the modded stuff, res, resource.arsc if any and any classes.dexs. Don't worry about any oat folders.
Click to expand...
Click to collapse
Hi Tulsadiver,
I followed your advice and replaced everything except the menta-inf folder from the original apk. Then I copied over my modded apk and restarted the device (just to be sure).
After rebooting the Settings icon was gone from my homescreen and the app drawer, leaving me unable to start the settings.
Tapping the seetings.apk using a file browser left me with the error, that there was an error while parsing...
Regards
deomaki
deomaki said:
Hi Tulsadiver,
I followed your advice and replaced everything except the menta-inf folder from the original apk. Then I copied over my modded apk and restarted the device (just to be sure).
After rebooting the Settings icon was gone from my homescreen and the app drawer, leaving me unable to start the settings.
Tapping the seetings.apk using a file browser left me with the error, that there was an error while parsing...
Regards
deomaki
Click to expand...
Click to collapse
I actually said, everything but the original meta-inf folder and original Android manifest....
Steps
Decompile apk.
Edit your apk
Recompile apk.
Unzip both modded and original apk
Delete everything in the original apk except meta-inf and Android manifest.
Copy everything from modded apk over to original apk except for the meta-inf and Android manifest.
Zip it back up, change it from .zip to .apk.
Copy this apk to the root of your phone.
Change permission to 0644
Copy/Move to replace the existing apk.
Reboot
Tulsadiver said:
I actually said, everything but the original meta-inf folder and original Android manifest....
Steps
Decompile apk.
Edit your apk
Recompile apk.
Unzip both modded and original apk
Delete everything in the original apk except meta-inf and Android manifest.
Copy everything from modded apk over to original apk except for the meta-inf and Android manifest.
Zip it back up, change it from .zip to .apk.
Copy this apk to the root of your phone.
Change permission to 0644
Copy/Move to replace the existing apk.
Reboot
Click to expand...
Click to collapse
Hi again,
thanks for your efforts by the way
That's exactly what I did except taking the original androidmanifest.xml since I had to change some things in it...
Will the whole process be not applicable then?
Regards
deomaki
deomaki said:
Hi again,
thanks for your efforts by the way
That's exactly what I did except taking the original androidmanifest.xml since I had to change some things in it...
Will the whole process be not applicable then?
Regards
deomaki
Click to expand...
Click to collapse
Unclear. I've seen some doogee posts on here. Maybe try one of those?
Tulsadiver said:
Unclear. I've seen some doogee posts on here. Maybe try one of those?
Click to expand...
Click to collapse
mmmh, maybe if will have to find out all system apks that use the same certificate framework-res.apk does and resign them with a new cert including the modded system.apk.
I was trying to find a way around that, but maybe I have to go the hard way...
I think that should solve my problem, what do you think?
Regards
deomaki