What I want is to gain the system signature for a developing app. I already compiled system.img from AOSP, but it seems hard to flash it to Droid 2. Is it possible to re-sign the ROMs(or framework-res.apk) in the forum with default platform key provided by AOSP and then flash to the phone?
Related
Hi,
I'm trying to understand the limitations of applying changes to currently installed firmware in my X10.
From what I understand its possible to apply themes, but i'm more interested on changing system apps (adding values/locales, changing .dex files) and resigning them afterwards with my own key.
The problem is I get signature failures, as the bootloader? rejects packages with different key.
Is there a way I can rip off the system key & password from the firmware? and sign my applications with the correct signature?
Or is there a way to cause the system to accept my signature?
Thanks
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
HuskyHamburger said:
I want to use the android kitchen to turn our recently leaked ICS update into a rom. On Dsixda's thread, he states that we need to create a file in the kitchen's /tools/edify_defs folder with the properties of our phone, in the templates file, it is kind of unclear for me how to do this.
Can anyone help me create a file for the HTC Amaze 4G? Thanks
Click to expand...
Click to collapse
Sorry if I am reviving a not quite old thread, but it came up when I was searching for the kitchen to download on my new windows install..
If you want to create a rom you don't really need the kitchen, it can do certain things to a rom- deodex, zipalign, install superuser and busybox, etc.. but within a few days of the leak all of that is available. You can pm a developer as I did and get permission to use their files rather than recreate the wheel.
First, just run the zip file thru the kitchen, don't do anything special with it- we have a superuser zip file you can/should just unpack into the final setup.
Find the updater-script and the binaries(in the same folder), this is what tells it what to install and where, fix permissions, install the files needed for SU(look in the superuser zip files updater script for details) etc..
If you want a deodexed rom you can ask to borrow the system/app directory from a rom that already has deodexed theirs. Literally, this is the best way to do it.
What the kitchen IS better for is pulling apart the kernel, putting it back together, unpacking apks.. it has built in scripts which can be a real time saver than typing in backsmali this, smali that-- simply put a file in a folder, type a number, and magically it all happens for you.. but you won't need ANY of that until you get into the advanced stuff.
I don't know if you were still trying to figure it out or not, but at the very least this may give someone who happened across this thread SOME sort of answer-- I get sick of finding more unanswered posts or posts where people reply with "you should search".. I've searched so much I my fingers should be bleeding.
Hi all,
I'd like to modify the Gallery3D application , which is already included in my current rom (CM7 nightly), using eclipse and adb. However when trying to install the version I compiled, it fails.
There are two conflicts at least : the package name, and the providers.
I tried to freeze the ROM version with titanium backup, but it doesn't change anything.
The package name, I could change it in the source code (using sed utility, since eclipse was generating an exception with the Android tool to rename the package -_-)
But the providers, this is really annoying to have to change their names as well, it's a much more complicated operation, and I'd prefer to be able to use the source code as is.
So is there a simpler solution ?
I suppose I could try to remove Gallery3D from the ROM, but not sure how to do that. Or other possibilities ?
Ok found the solution : I simply had to remove the Gallery.apk file from /system/app
Note : I'm just sharing the work of the XDA member Ticklefish.The world-famous Tickle My Android, or TMA for short, is a command line tool for Windows that uses apktool to help you pull and decompile files from your Android phone or tablet.
Features : change the battery icon,
change the WiFi icon,
change the signal icon,
change the emoticons,
change the notification toggles,
change the softkeys,
change the transparency of the statusbar (if the rom allows it),
zipalign apk files,
sign new apk files,
sign recompiled apk files in the same way as the original,
deodex apk and jar files,
resize and change boot animations,
change fonts,
create backup-generating flashable zip files
create standard flashable zip files
..and now comes in Portuguese and French!!
To use Tickle My Android, you will need:
- a rooted Android phone or tablet with USB Debugging enabled and a recovery installed (either ClockworkMod or TWRP) ,
- any version of Android on that device,
- a Windows PC (XP or above) with the phone or tablet's drivers installed as well as Java Runtime Environment 1.6 minimum,
- a USB cable to connect your device to the PC,
- patience and a little common sense
What is Tickle My Android compatible with?
Tickle My Android's decompiler function always uses the very latest apktool files, as well as the very best aapt files, available. But, because Android is an open-source OS, there will always be some implementations of it that TMA will not be fully compatible with.
Currently, TMA is not fully compatible with some official MIUI rom's. This is because MIUI isn't open-source, unlike Android itself, and the developers aren't sharing how they construct their files.
TMA is also not fully compatible with HTC Sense 4.0+. This is because HTC have constructed their files in a different way to the Android norm and aren't letting people outside the company know how they did it.
TMA also has problems with stock Asus Transformer apk's. BUT there is a fix! Click on this post here to find out what to do. Many thanks to allan1313 for this.
Some apks come with "drawable-ldrtl" folders that apktool currently can't deal with. Unless you read from right to left, you can safely just delete those folders.
There will be some devices/roms that are unable to use the zip files TMA creates and you'll be given an error code:0. This is down to the update-binary and can be easily fixed.
Take the update-binary from a working zip file and place it in the 'user_files\UPDATEBINARY' folder. Use Option 4 in the settings menu and all future zips will use your update-binary. Easy!
How to use this : Please see this guide here.I can't copy each and every step as it is too long. http://forum.xda-developers.com/showthread.php?t=1633333
Downloads : (112.08 MB) - http://www.mediafire.com/download/z9zewr14697nj8w/TickleMyAndroid+v7.1.exe
Original Thread : http://forum.xda-developers.com/showthread.php?t=1633333
Credits ;
Ticklefish
Click to expand...
Click to collapse
What is the difference between deodex and odex roms? Sorry for the noob question but ive always been curious
Sent from my SCH-I605 using XDA Free mobile app
WHAT IS EXACTLY AN ODEX FILE ?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space The odexed file structure works well as an optimization tool. Since these .odex files contain preliminary load information about each system app, the OS knows what to expect when it’s booting up, and consequently, loads all these apps faster.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
For instance, on a non-rooted device you’ll find
system/app/Phone.apk ===> as well as ===> system/app/Phone.odex
AND NOW THE DEODEX FILE ?
It’s the process to take all the packages out from .odex file and reassemble them all together in classes.dex file which is kept inside the APK file. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
on the same device but rooted now, you’ll find this:
system/app/Phone.apk ===> but no longer the corresponding .odex file. The reassembled files become classes.dex
CONCLUSION: ADVANTAGES & DISADVANTAGES FOR BOTH SYSTEM FILES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, that’s why developers prefer it and most, if not all, of the custom ROMs come pre-deodexed.
The advantage of .odex file is the faster load time of the app and were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
And finally rooting need not necessarily mean your device is deodexed, rather that almost all stock ROMs are odexed to some extent, and usually most custom ROMs are deodexed for easy theming.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.