Database Develop

[Tool] Inject Apps to ROM for Installation

If you're like me, you probably have installed a new ROM at least once a week. I usually use Titanium Backup to restore all my Apps, but it takes quite a long time since I use a lot of Apps. Also, if you don't have the Pro version of Titanium Backup, you will need to click through the Install button for every App you want to install.
This program is a simple way to fix that. What it does is it injects you Apps as part of the ROM when you install a new ROM. This way, as soon as you install your ROM, your Apps will already be installed as part of the ROM.
I have only tried this with the latest Team Whiskey Onyx ROM, but it should work with most, if not all ROMs.
Also, not all Apps can be installed this way, especially if you try to include the data. YMMV.
INSTRUCTIONS
Prepare your computer
1. Install Java JRE and SDK.
2. Install 7-Zip. It can be found here: http://www.7-zip.org/
3. Download Testsign.jar. It can be found here: http://www.robmcghee.com/android/creating-an-android-update-zip-package/. Download the file "Testsign.zip" and extract it. Testsign.jar should be in there. You will need this later.
4. Set up your windows Path Environment.
a. Go to your Control Panel and open "System."
b. For Windows 7, you will need to click on "Advanced System Settings."
c. Go to the "Advanced" tab.
d. Click on the "Environment Variables" button.
e. Under "System Variables" find "Path." Select it and click on the "Edit" button.
f. A window should pop up a field for "Variable value." In there, you will want to add your 7-Zip and Java SDK bin path. At the end of "Variable value," add (without the quotes)
";C:\Program Files (x86)\Java\jre6\bin;C:\Program Files\7-Zip"
It might be slightly different for you if you're not using a 64-bit Windows. Basically, this step is to allow you to run the Java and 7-Zip command-line tools from anywhere in your system.
5. Reboot your computer.
6. Test to make sure you can run the Java tools and 7-Zip tools. Do this by running "cmd." A command-line prompt should appear. In there, type "java" and hit enter. The usage info for running java should appear. Now type "7z" and hit enter. The usage info for 7-Zip should appear. Your computer is now set up to run my batch file.
Prepare your Apps
WARNING: Not all Apps work using this method, and not all data can be restored using this method. If it doesn't work, you can restore it using Titanium Backup and it should work fine. Once you find that a certain App doesn't work, you should probably remove it from your App/Data folder (read below) so it doesn't install next time using this method.
1. Get all your APKs and data. The easiest way I know how to do this is by using Titanium Backup to make a backup of all my Apps.
2. Use Titanium Backup and back up your Apps.
3. Inside your SD Card, you should have a TitaniumBackup folder. All your Apps and data are in here. Every App you have backed up in Titanium should have 3 files. A .properties file, a apk.gz file, and a tar.gz file. The apk.gz file will contain your APK. The tar.gz file will contain your data. You can extract these files using something like WinRAR.
4. Extract your APKs and put them in a folder called "data\app". Extract your App's data and put them in a folder called "data\data". Your "data\data" should look something like this "data\data\com.appname".
5. Once this is complete, you can use this APK/data set for any future ROMs.
Create your ROM with your Apps
1. Put AppToROM.bat, testsign.jar, your data folder, and your ROM's zip into the same folder.
2. Drag your ROM's zip onto AppToROM.bat.
3. The batch file will now start creating your new ROM for you. It will do the following steps:
a. Extract your ROM.
b. Copy your data to the extracted ROM folder.
c. Zip everything back up.
d. Sign the new Zip.
4. When everything is done, you should have a "NewROM.zip" file. Use this new Zip file to install your ROM like you normally would.
Disclaimer:
I take no responsibility for any harm that this may do to your device. All of the tools here, except the bat file, I did not write. I just created a bat file that puts all the tools together to make it easier to install your Apps after installing a new ROM.

or you could just open your update.zip and place your apks in system/app re-zip and flash. Done this multiple times and it works. just need to keep a copy of your apks on your computer. ill try this method tonight. thanks

If you put it into "system/app" it will install it as a System app, and I believe you can't uninstall it regularly (kind of like how you can't install the bloatware). You will need to use Titanium Backup to uninstall it.
Also, I remember reading that some people were not able to install the ROMs after zipping it up because it's not signed.
This script is very simple. It basically just unzips the ROM, copies over your apps, zips back the ROM, and then signs it. Once you have your Windows set up, you can just drag and drop the ROM to the .bat file and it'll do all that for you.
Is this useless? Maybe. But, the same could be said for something like RyanZA's OCLF. You can sit there, type in all the commands to convert to EXT2, wait for it to convert, and reboot, or you can just run OCLF (which is basically just running a script for the conversion, to put it simply).

blackerwater said:
or you could just open your update.zip and place your apks in system/app re-zip and flash.
Click to expand...
Click to collapse
Why not just put them into data/app instead?

or you could just...
Or you could just download a pro version of titanium backup so that it can restore all your apps without you needing to click. There are plenty to be found online. The latest version, the better, as it would be more stable with froyo

So doing things this way... since it will be signed, i can also take other things out form other roms that i like and toss them in this rom??

I have titanium paid version. Just run it and it does everything
Sent from my SGH-T959 using XDA App

Dude it's called WinRAR. Open up the zip. Drop your apps into the data/app folder.
Then flash it. Simple.
Want certain apps to stay even after hard resetting? put them in system/app
This tool is completely unnecessary.

That's really a good idea. I like the method very much, it give me more free time to do some other things when flashing...Thanks !

Anderdroid said:
Dude it's called WinRAR. Open up the zip. Drop your apps into the data/app folder.
Then flash it. Simple.
Want certain apps to stay even after hard resetting? put them in system/app
This tool is completely unnecessary.
Click to expand...
Click to collapse
Ditto. This seems way more complicated then the method I've been using. You say it's simple that there are like 20 steps.

yeah and CWM has the option to toggle signature verification.. so you can flash unsigned apps on the vibrant.. but if you use 7zip it doesnt mess with the sig...

epakrat75 said:
Why not just put them into data/app instead?
Click to expand...
Click to collapse
Or that should work. And as for signing problems I us ubuntu and ive never had that happen but I guess with windows anything is possible.
Sent from my vibrant

Etrnaly said:
If you put it into "system/app" it will install it as a System app, and I believe you can't uninstall it regularly (kind of like how you can't install the bloatware). You will need to use Titanium Backup to uninstall it.
Click to expand...
Click to collapse
$adb shell
$su
#rm /system/app/CrappyBloatwareAppOfChoice.apk
Done.
No need for titanium.

Sorry for the noob question
Anderdroid said:
Dude it's called WinRAR. Open up the zip. Drop your apps into the data/app folder.
Then flash it. Simple.
Want certain apps to stay even after hard resetting? put them in system/app
This tool is completely unnecessary.
Click to expand...
Click to collapse
When you say your apps do you mean your .apks thanks

without odex

I am using the GT540 with 2.1 rom
i want delete in the system/app-> odex files
but when i delete any odex files
app does not work
examples
delete system/app-> music.odex... music does not work
There are some applications run with odex
some applications run without odex (example lgecamera.apk)
I would like in working without odex every app on 2.1
how do I
please help
Thank you for answers
I'm sorry for my English

I think first you need to understand the concept of ODEXing. In stock LG roms the system applications are Odexed. "ODEX" stands for Optimized DEX - Classes.dex is usually a file that stands inside the apk file of any application. When a program is odexed the file is extracted from the apk, optimized, and saved alongside the application in the odex format. However, since the apk no longer contains its (albeit optimized) classes, deleting the odex file leaves the application broken and unusable, until you reinstall it again. Now, I can think of only one way to deodex right now, but I really don't think it's a good idea(The rom i'm using was deodexed, yet I odexed it intentionally). What you need to do is:
1. Make a backup of your phone using clockworkmod recovery
2. From that backup take system.img and boot.img
3. You will need to download and run Android Kitchen. Since it's a Linux program, you'll need that as well. Look into it.
4. Insert the 'boot' and 'system' img files into the kitchen, and use the deodex option, then export the rom as update.zip
5. Put the file in your sdcard, boot into recovery, and format system
6. Choose 'install update.zip', and install the one you've created
7. From 'Advanced' menu clean Dalvik-Cache, and see if the phone works now.
While this *should* work *in theory*, as far as I know using a backup to modify it in the kitchen doesn't always work. Also, since I imagine some of your system apps are now broken, what I told you to do should be done after first reinstalling the rom in some way, in order to get your apps straight.
Well, I hope I've been helpful. Good luck.

if I'm not wrong there should be a script somewhere i the forum

bs828 said:
if I'm not wrong there should be a script somewhere i the forum
Click to expand...
Click to collapse
For deodexing? There's one for odexing, but I'm not sure about the opposite one. I'll do a search. Besides, some of his system apps are already screwed up, so I doubt that will help.

This kitchen can run on Cygwin (author mentioned it)

nutterbg said:
I think first you need to understand the concept of ODEXing. In stock LG roms the system applications are Odexed. "ODEX" stands for Optimized DEX - Classes.dex is usually a file that stands inside the apk file of any application. When a program is odexed the file is extracted from the apk, optimized, and saved alongside the application in the odex format. However, since the apk no longer contains its (albeit optimized) classes, deleting the odex file leaves the application broken and unusable, until you reinstall it again. Now, I can think of only one way to deodex right now, but I really don't think it's a good idea(The rom i'm using was deodexed, yet I odexed it intentionally). What you need to do is:
1. Make a backup of your phone using clockworkmod recovery
2. From that backup take system.img and boot.img
3. You will need to download and run Android Kitchen. Since it's a Linux program, you'll need that as well. Look into it.
4. Insert the 'boot' and 'system' img files into the kitchen, and use the deodex option, then export the rom as update.zip
5. Put the file in your sdcard, boot into recovery, and format system
6. Choose 'install update.zip', and install the one you've created
7. From 'Advanced' menu clean Dalvik-Cache, and see if the phone works now.
While this *should* work *in theory*, as far as I know using a backup to modify it in the kitchen doesn't always work. Also, since I imagine some of your system apps are now broken, what I told you to do should be done after first reinstalling the rom in some way, in order to get your apps straight.
Well, I hope I've been helpful. Good luck.
Click to expand...
Click to collapse
Thank you for your excellent explanation
definitely going to try them
but where do I find Android kitchen for the GT540
and the running xp or win7?
Can you give the web address?
thanks a lot.

Here you are
http://forum.xda-developers.com/showthread.php?t=633246
You can use kitchen on Windows thanks to Cygwin .
Wystukane z mojego Swifta przy użyciu Tapatalk.

[Q] CWM Recovery: patching backups; updating CM

Some simple (I hope) questions. Let's say I do a full CWM backup and copy the complete backup directory to my desktop. If I now want to change something inside this backup can I simply change the relevant .tar.a file(s), write their new checksums into nandroid.md5, copy everything back to the sd card and expect the whole thing to work?
No 2: I have just let the HD+ update itself to cm-10.1.3-ovation (final) and all went swimmingly. However, I saw that the update is not done incrementally, instead the whole zip is downloaded and the /system tree simply overwritten with its contents. I had put some bits and pieces into /system/app and /system/bin and modified a few files inside of /system, all of which changes were of course gone. So a better update strategy might be to download any new version from the CM website to a desktop machine, patch the .zip file there and then have CWM install it. Can CWM install such an update file like any other .zip or is the update.zip route the correct way?
Or perhaps the best way to update in such a scenario is to download the .zip, sync it with an existing CWM backup (as in the first question) and restore the backup?!

If you get the md5 sum right editing the tar should work.
You can edit the downloaded zip before you flash it and it will still install. But editing after install is about the same amount of work.
What I used to do on the Nook Color was to modify the gapps zip to add the /system changes I wanted and then reflashed the gapps every time I flashed a new ROM. That way gapps were refreshed and the new changes were inserted in /system. Or, you could make your own zip to flash only your changes. The easiest way to make one is to edit the gapps zip to put your changes in and then delete the gapps files from the zip.
Do these zip changes with archive software without totally unzipping and rezipping.
Edit: Since some of my changes were modifications to build.prop, I developed a script to edit the new ROM's build.prop on the fly as part of the zip. That way build date, etc stayed right. If you want, I can use PM to send you a copy of my old edited gapps for you to study. However, since you are on CM10.1 stable, you will probably not be updating again.
Sent from my Nook HD+ running CM10.1 on emmc.

> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.

TooMuchSloeGin said:
> If you get the md5 sum right editing the tar should work.
Okay, thanks for the confirmation.
> You can edit the downloaded zip before you flash it and it will still install.
But how do I trigger that install, once in CWM? That was my 2nd question.
> But editing after install is about the same amount of work.
Not in my case as I have a) no MTP and b) can easily auto-sync huge directory trees with a powerful command line tool.
I think the best way forward is to ignore the installing of new install .zips via CWM, however this is done. Instead I'll produce a nandroid-compatible backup directory and "restore" that.
Thanks again for your help.
Click to expand...
Click to collapse
You don't trigger it, you manually boot to CWM and manually install it. Go to install zip from SD and choose where you put it.
And by editing after install, I meant editing /system once it is installed on the Nook.
Sent from my Nook HD+ running CM10.1 on emmc.

Error status 7

Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..

Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.

-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.

pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!

[Q] CWM not writing image.zip on 4.2.2

Hi,
Tried creating an 'image.zip' with CWM 6. There is a successful confirmation message that the file was written to /sdcard/clockworkmod/image.zip. But I can't find the file and there is no change in the available space after supposedly having written the file. I think the file was not saved.
I'm using trickdroid 7.5.0 / android 4.2.2.
Any ideas what's wrong?
Thanks

joeycyq said:
Hi,
Tried creating an 'image.zip' with CWM 6. There is a successful confirmation message that the file was written to /sdcard/clockworkmod/image.zip. But I can't find the file and there is no change in the available space after supposedly having written the file. I think the file was not saved.
I'm using trickdroid 7.5.0 / android 4.2.2.
Any ideas what's wrong?
Thanks
Click to expand...
Click to collapse
Did you try TWRP.. anything above and including v2.6.3.3.. unfortunately me being a noob cannot post the link to it.. you will have plenty links here on the forum

Use TWRP CWM has been buggy for a few years now.

joeycyq said:
Hi,
Tried creating an 'image.zip' with CWM 6. There is a successful confirmation message that the file was written to /sdcard/clockworkmod/image.zip. But I can't find the file and there is no change in the available space after supposedly having written the file. I think the file was not saved.
I'm using trickdroid 7.5.0 / android 4.2.2.
Any ideas what's wrong?
Thanks
Click to expand...
Click to collapse
I have the same issue. I am on 4.4.4 and I installed CWM only to create this zip file. I only see it within CWM but can't find it in Explorer in the same folder. I generally use TWRP.

DanRo80 said:
I have the same issue. I am on 4.4.4 and I installed CWM only to create this zip file. I only see it within CWM but can't find it in Explorer in the same folder. I generally use TWRP.
Click to expand...
Click to collapse
CWM stores backups in /data/media/clockworkmod (old 4.1.2 filesystem), now sdcard goes to /data/media/0/....
you'll need to use a root-enabled file explorer to get to /data/media/

nkk71 said:
CWM stores backups in /data/media/clockworkmod (old 4.1.2 filesystem), now sdcard goes to /data/media/0/....
you'll need to use a root-enabled file explorer to get to /data/media/
Click to expand...
Click to collapse
AWESOME! I found it. Thank You