Related
my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.
Its something I would like to be able to do as well. According to Haykuros twitter hes going to be making a video about android rom cooking soon so that should help
jholt0130 said:
my question is this, say for example I have my phone setup just as I like with the theme of my choosing, htc music app instead of the stock android app in the cyanogen mod. i would like to be able to create a rom from this setup that I could then just load on my phone as oppsed to loading a cm mod, then installing music player, then installing the theme. before the flaming begins, i tried the search to no avail. i am aware of how to sign the zip and all of that. just a point in the right direction would be MUCH appreciated.
Click to expand...
Click to collapse
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.
xidominicanoix said:
This should've gone in the Q&A section. Will probably get locked soon.
But in response to your question, I guess you could grab the CM rom, then grab the theme you use and overwrite the files in the rom, and then overwrite the music app with the HTC music. Resign and you got your update.zip customized how you want it.
Click to expand...
Click to collapse
Thanks for the help and my apologies for the wrong section
how do you resign it?
joey3002 said:
how do you resign it?
Click to expand...
Click to collapse
by searching.
Stericson said:
Automatic version!
Do not use this to sign APK files in Vista or windows 7! It will cause your theme to loop phones when placed on a device. Only use this to sign update files if your using those O/S's
Note, this will not work if your SDK or the path that you place this in has any spaces in the dir name!
An Example of this is c:\users\Nikki and Stephen\sdk\tools
Try to put the SDK and the contents of the zip in a dir where the names are all together and not like the one above.
I have made a batch file that will automate the entire process of setting up to use the signing tool made by JF. This batch file will set the CLASSPATH, set the PATH, install the registries, and will even allow you to sign files manually if you wish. I plan on building onto this batch file to include other things. However, for the moment, it will only include what you see here.
In order to use this you should have downloaded the sdk already. Simply extract all of the files into the tools dir of your sdk, and run autosign.bat follow the instructions and go through the options one by one, starting with 1 working through 4. You can however, put the contents of this zip anywhere on your computer and it will work. It is just better to put them into the tools dir of your SDK. Especially for the consideration of future versions.
Autosign .zip: http://www.fightforthepits.com/Androidstuff/signing.zip
Want to set up the signing tool manually?
Here is the link for the signing tool: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
FOR XP:
Right click on My Computer click properties, then choose the tab that says advanced.
Click the button that says environmental variables.
Go to system variables find the one that says CLASSPATH
double click it
go to the end of variable value.
There should be a semicolon ; at the end, type in the path to the testsign.jar located in the tools directory of your SDK
for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar
If CLASSPATH is not in your system variables then create it.
Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory.
For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
FOR VISTA:
Open a cmd prompt.
Replace THEEXACTPATHTO-TESTSIGN with the path to the dir that holds the file testsign.jar.
Type:
echo %CLASSPATH%
If it is returns %CLASSPATH%
Type the following:
set CLASSPATH=THEXACTPATHTO-TESTSIGN\testsign.jar
If it comes back with something else then
Type the following:
set CLASSPATH=%CLASSPATH%;.;THEXACTPATHTO-TESTSIGN\testsign.jar
For Example, when I type this it looks like:
set CLASSPATH=%CLASSPATH%;.;c:\Android\SDK\tools\tests ign.jar
To set the PATH
Replace THEEXACTPATHTO-SDK with the path to the tools dir of your SDK.
Now type:
set PATH=%PATH%;.;THEXACTPATHTO-SDK\tools
For example, when I type this out it looks like this:
path-%PATH%;.;c:\Android\SDK\tools
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
Signing the Files:
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
When you choose it a cmd window should open for a few seconds and then close. the file you signed will be overwritten with the new resigned file.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Click to expand...
Click to collapse
.apk's not showing up after flash in resigned .zip
Ok, so I've created a ROM to my liking. All the .apk's I normally use and got rid of the ones I don't. My problem is after I customized the ROM and flashed it none of the .apk's I added showed up. The only ones that showed up were the paid apps. I never opened the .apk's and made changes. I assume I don't need to change them to .zip resign and back to apk. Do I? I am using Windows 7 though and am able to resign no problem. Thanks to anyone who replies.
USING DSIXDA's KITCHEN TO CREATE YOUR OWN SOFT-MODs
(THIS IS MY FIRST BIG TUTORIAL, SO PLEASE CO-OPERATE AND HELP ME MAKING THIS GUIDE BETTER!!)
DsiXDA has created an excellent Kitchen for 'cooking' custom ROMs. So first THANKS goes to DsiXDA.
READ THIS BEFORE PROCEEDING:
Click to expand...
Click to collapse
For Kitchen to get working you need a Linux environment. My choice is go for Ubuntu 10.04 / 10.10 (I won't recommend 11.xx as Unity spoils the 'Cooking' experience). You should have a little bit of experience with Ubuntu. You can do it on Windows too. Install Ubuntu inside VirtualBox. I won't recommend using cygwin as it may reduce the performance.
Click to expand...
Click to collapse
GIVE CREDITS TO THE ORIGINAL DEVELOPER
I. Setup the Kitchen:
Download DsiXDA's Kitchen at https://github.com/dsixda/Android-Kitchen/archives/master. Download the 0.179 version
Get an 'original' ROM (not soft-modded). The ROM that I used in this tutorial is Pebe's CyanogenMod 7
Get JDK. It's necessary. Execute the following command in Terminal:
sudo apt-get install openjdk-7-jdk
When asked for password, enter the one which you use for logging in.
For 64-bit system, you need the ia32-libs ( sudo apt-get install ia32-libs )
Extract the contents of the dsiXDA's kitchen to a folder, say kitchen, in your Home folder (for convenience). Just inside the kitchen folder there should be the ./menu file
Open Terminal. Browse to your kitchen directory
cd ./kitchen
source ./menu
It should open up the Kitchen Menu
This is the basic setup of your Kitchen. Now move up to the next big step.
II. Actual ROM:
Copy the ROM (in my case, it is cm7_v2.zip (pebe's CM7)) and paste it in the original_update folder
Execute Kitchen (Step 5 from I). Select option '1. Setup working folder from ROM'. Another menu appears, hit ENTER. It'll show up the available ROMs list. It should display at least one ROM. In my case it was "(1) cm7_v2.zip". Enter selection number: 1. Hit ENTER. It'll prompt for changing the name, leave it, no need. Hit ENTER. It'll start extracting the ROM. In my case, it found the updater-script. It'll ask to convert the script into update-script. We want update-script at the moment, so just hit ENTER. It should say 'Finished setting the working folder!'. Hit ENTER. You'll be back to Menu.
The Menu shows various options like 'Adding Root permissions, installing busybox, etc'. You can play with them. As most of the ROMs have Root and Busybox installed, we don't need any of these features.
Now comes a bit advanced part. Select ADVANCED OPTIONS. There are various options like Deodex files, add Nano text editor, signing APKs, etc. I'll explain each of them:
Deodex: Merges ODEX and APK together. However, it's applicable for ODEXed ROMS (mostly Stock 2.1) only. Neither of GB and FroYo versions are ODEXed. So you can skip this step.
Add task killer tweak: It's a good alternative to Supercharger script. Only thing is, it isn't as versatile as Supercharger script. Leave this if you don't know anything about Task killer values like FOREGROUND APP, BACKGROUND APP, etc
Add data/app functionality: Suppose you've come across a situation that the system size reaches almost 150 MB (standard for GT540) and still you want to add some more apps, then this tweak is for you. It adds the /data/app folder. You can place apps in this folder. These apps will be directlty installed in the /data partition thus eliminating the 150MB limit.
Add Bash: Adds command-line completion in Terminal commands. Install if you want. Not needed.
Add Apps2SD: This is much primitive type of Apps2SD in which you have to create an ext partition on your SD card. Not recommended. Link2SD (app) is much better.
Add busybox run-parts: This tweak is most important one. I enables the startup scripts option, that means, scripts placed in /etc/init.d folder will get executed during the booting process. Recommended for Stock and AOSP ROMs only.
Add custom boot animation: If you want to add a custom boot animation to your ROM, then you need this. Select this option. It'll ask you to proceed, hit ENTER. A folder /data/local will be created inside the WORKING_xxxxxxx_xxxxxxx folder. Place your bootanimation.zip in that folder. Google some nice boot animations or if you want to create your own boot animations, Despotovski brothers had made a 'Boot Animation maker', check it here http://forum.xda-developers.com/showthread.php?t=1234611
Rest all tweaks are not required for now
III. Something's Cooking!
There will be a folder named something like WORKING_xxxxx_xxxxxxxx in your kitchen folder. Open it up. It contains the actual system, boot.img file, data directory etc.
The best feature of DsiXDA is that you can easily 'browse' the system.
Open the system folder. Here you can see the apps, etc, lib, usr, etc folders.
Adding / Removing Apps: Open the apps folder. You'll see APKs of all the system apps. Try removing some apps. You can remove Dev tools, pre-installed CM themes or any other app. Add your own apps. Copy-paste your apps here. If their filenames have spaces in them (like Root Explorer.apk) remove these spaces (like RootExplorer.apk). You can also use the /data folder for adding more apps.
Adding some other stuff: The /etc folder has a lot of cool stuff too. The apns-conf.xml file contains the APNs. System can auto-detect the APN according to your carrier. I got an apns-conf.xml file which contains a huge list of APNs. Just replace the existing file.
Adding Fonts: Pick your favorite font (I like Ubuntu). Grab the .ttf file of that font. Open /fonts folder. Remove the existing DroidSans.ttf file. Copy-paste your font file in it and rename it to DroidSans.ttf.
IV. Final Steps:
Open the kitchen menu. Advanced Options → Sign all APKs
Back to main menu. '9. Check update-script for errors'.
'6. Zipalign all APKs'
'99. Build ROM'. If it shows warning regarding BOOT-EXTRACTED folder exists, select y (remove BOOT-EXTRACTED).
Select a build option → 1. Interactive Mode
Would you like to Zipalign → n (we already did that before)
It'll start making update.zip.
Add updater-script to your ROM → y (We want compatibility with ClockworkMod)
Proceed with the change → y
Sign your ROM → y
Change the name → n
Once you're back to main menu, select Exit (x)
Your ROM is located in OUTPUT_ZIP folder (It'll be a zip file)
Copy this zip file on your SD card. Reboot into Recovery. Select 'Install zip from SD card', select the ZIP file.
Reboot. See if everything works properly.
I KNOW THERE MIGHT BE ZILLIONS OF ERRORS IN THIS GUIDE. IF YOU'RE STUCK AT SOME POINT OR CANNOT UNDERSTAND SOMETHING, TELL ME. I'LL TRY TO MAKE THIS GUIDE MORE EASIER TO UNDERSTAND.
THIS IS A BASIC SOFT-MODDING GUIDE. I'M DOING SOME INVESTIGATION REGARDING THEMING AND BUILD.PROP TWEAKS. I'LL BE ADDING THESE SECTIONS LATER.
WOW nice work making this TUT!!
Nice Work!
thanks!!
gonna try this out sometime
There is a search feature guys this was posted about like half a year ago
I tried the kitchen its not that great all you can do is zipalign change some options and re package
TBH androidboss you probably could do more using terminal and root explorer
Sent from my tf101 using xda premium 1.54Ghz
Guys! Before Soft-Modding please ask the Devs first. They worked and took up free time for those roms and they would like a thanks.
Danzano said:
There is a search feature guys this was posted about like half a year ago
I tried the kitchen its not that great all you can do is zipalign change some options and re package
TBH androidboss you probably could do more using terminal and root explorer
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
really i should try one day!
with credits and thanks!!
Algud if you need tips or want a hand customizn give me a shout hell if you wana use enigma and just cretic it to you're liking be my guest
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
Algud if you need tips or want a hand customizn give me a shout hell if you wana use enigma and just cretic it to you're liking be my guest
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
yeah thanx bro!!
i will try and make one during this weekend
once i get my phone fixed..
i will pm you if i need help with something about the
soft-mod!!
All good
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
All good
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
pm' ed u!!
soz its a bit long!
I'll be writing the "Theming using UOT Kitchen" tutorial tonight
tejasdj12 said:
I'll be writing the "Theming using UOT Kitchen" tutorial tonight
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=18934516#post18934516
you can base on this if u want
I first wrote this guide here on my site and thought I should put it here as well.
I am going to write this post to show how "easy", yet time-consuming, converting an RUU into a custom, de-odexed ROM can be as long as you can follow directions. I am doing this to hopefully help with development of ROMs for people who may be a bit intimidated on doing this. Before you start, you’ll need:
1. A Windows installation
2. VirtualBox installed in Windows
3. Ubuntu 10.04 (at least) installed in VirtualBox
4. dsixda’s Android Kitchen set up properly in Ubuntu
5. Java JDK installed in Ubuntu (Search openjdk in Synaptic Package Manager)
6. No fear of taking your time with this
I am suggesting the above because that’s what I’ll be using for this guide. Some devs frown at the use of kitchens but de-odexing manually can be a real pain in the ass and very time consuming.
First things first, you need to have Ubuntu up and running inside VirtualBox and you’ll need to get the Android Kitchen set up properly. To do this, extract the Android Kitchen zip file you downloaded. Rename the extracted folder to just “kitchen”. Copy that folder into your Ubuntu “home” directory. The final path will be “/home/username/kitchen”. You can test this by opening Terminal and typing:
Code:
cd kitchen
./menu
If the Android Kitchen starts, then you’re good to go. It’s that easy.
Now, going back to your Windows installation, download the RUU you want to build from. Once downloaded, you’ll need to double-click the RUU to run it. You’ll get a window that opens to allow you to continue installing the RUU. You need to not click anything there. Leaving that window open, open a Windows Explorer window. In the address bar type:
Code:
%temp%
and hit enter. This will take you into your Temp directory where the rom.zip is extracted. You can now do a search for rom.zip. Once found, copy the rom.zip to another directory (ie. Desktop). You can now close out of the RUU installer.
You’ll need to now copy your rom.zip to your Ubuntu virtual machine. How you do that is up to you. The easiest way is to set up Shared Folders in VirtualBox and copy it from within Ubuntu.
Once you have this file in Ubuntu, for simplicity, copy it to your desktop. Next, you’ll need to extract it. Simply right-click the rom.zip and select “Extract Here”.
If you now open you extracted folder, you should see a bunch of .img files. The 2 we are looking for are system.img and boot-signed.img. For now, create a new folder on your desktop, we’ll call it “custom”, and copy the boot-signed.img into that folder (I usually rename boot-signed.img to boot.img). Also create a folder called “system” in the same directory. Next we need to mount the system.img so we can extract the contents into the “system” folder you just created. Back in Terminal, type:
Code:
sudo mkdir -p /mnt/temp
sudo mount -o loop ~/Desktop/rom/system.img /mnt/temp
and then
sudo cp -r /mnt/temp/* ~/Desktop/custom/system
After several minutes, you should have a folder called “custom” on your desktop and inside of that should be “boot.img” and a “system” folder with a bunch of files and folders in it. You now need to change permissions on the folder so you can zip it up and copy it all. Back in Terminal type:
Code:
sudo chown -R username ~/Desktop/custom
Next step is to zip it all up so we can get it into the kitchen. Highlight both the “boot.img” and “system” folders, right-click them, and select “Compress”. Change the extension to .zip and click OK. Once zipped, drag (or copy) that folder into /home/username/kitchen/original_update.
Open Terminal and type:
Code:
cd ~/kitchen
./menu
Once the kitchen starts, you’ll need to set up a Working Folder, so select option “1″. If you only have 1 ROM zip in there you can just hit Enter. Follow through the prompts to rename your working folder if you want. I’m not going to guarantee that it will always work but it has worked for me in the past to select option “2″ from the main menu to “Add root permissions”. Moving on to de-odexing, select option “0 – ADVANCED OPTIONS”. Next, select option “11 – Deodex files in your ROM”. I usually do this by deodexing framework first and then system. If you’re de-odexing the ATT ROM, “PirateGhost” from xda clued me in that you need to temporarily remove the “com.att.vmm.sharedlib.jar” from /system/framework otherwise de-odexing will fail. When you get into the de-odexing option it will have you set your API level. The default is 10 which is Android 2.3.4 however, ICS can be 14 or 15. If on the latest 4.0.3, it’s API Level 15. Google can also help you here. If you’ve done everything right it will de-odex for 20 minutes or so depening on your hardware and should say “0 .odex files remain”. If you have any that remain, you can do them manually or not at all. Up to you on how you do it.
Since that’s basically all we’re discussing for right now on creating this ROM, we’ll continue on to building a flashable zip. Back at the main menu, select option “99 – Build ROM from working folder”. I recommend using the default “Interactive Mode”. Select yes to optimizing/zip-aligning all apks. When asked to add Updater-script to ROM, select yes. Here’s the thing with the updater-script that it builds. It’s only partially right. You need to fix the partition format section for the Vivid (or for whatever phone you’re building for). It’s best to look at some other’s scripts to see how it’s done. When asked by the wizard to sign your ROM, don’t do it. It’s not necessary. Feel free to rename it to whatever you want. After you’ve fixed the updater-script and I do mean AFTER, you can try flashing the ROM. And don’t forget to flash the boot.img as well.
There you have it. You now have a base ROM for you to work from. Obviously, this is just scratching the surface of what can be done but it’s a start. This is just how I do it. There are other ways to accomplish the same thing but this method has worked for me. Attached is a sample updater-script that I pulled from my AT&T stock ICS ROM. Use it only as a template and modify it to fit your needs and obviously, remove the txt extension.
Jirv311 said:
I first wrote this guide here on my site and thought I should put it here as well.
I am going to write this post to show how "easy", yet time-consuming, converting an RUU into a custom, de-odexed ROM can be as long as you can follow directions. I am doing this to hopefully help with development of ROMs for people who may be a bit intimidated on doing this. Before you start, you’ll need:
1. A Windows installation
2. VirtualBox installed in Windows
3. Ubuntu 10.04 (at least) installed in VirtualBox
4. dsixda’s Android Kitchen set up properly in Ubuntu
5. Java JDK installed in Ubuntu (Search openjdk in Synaptic Package Manager)
6. No fear of taking your time with this
I am suggesting the above because that’s what I’ll be using for this guide. Some devs frown at the use of kitchens but de-odexing manually can be a real pain in the ass and very time consuming.
First things first, you need to have Ubuntu up and running inside VirtualBox and you’ll need to get the Android Kitchen set up properly. To do this, extract the Android Kitchen zip file you downloaded. Rename the extracted folder to just “kitchen”. Copy that folder into your Ubuntu “home” directory. The final path will be “/home/username/kitchen”. You can test this by opening Terminal and typing:
Code:
cd kitchen
./menu
If the Android Kitchen starts, then you’re good to go. It’s that easy.
Now, going back to your Windows installation, download the RUU you want to build from. Once downloaded, you’ll need to double-click the RUU to run it. You’ll get a window that opens to allow you to continue installing the RUU. You need to not click anything there. Leaving that window open, open a Windows Explorer window. In the address bar type:
Code:
%temp%
and hit enter. This will take you into your Temp directory where the rom.zip is extracted. You can now do a search for rom.zip. Once found, copy the rom.zip to another directory (ie. Desktop). You can now close out of the RUU installer.
You’ll need to now copy your rom.zip to your Ubuntu virtual machine. How you do that is up to you. The easiest way is to set up Shared Folders in VirtualBox and copy it from within Ubuntu.
Once you have this file in Ubuntu, for simplicity, copy it to your desktop. Next, you’ll need to extract it. Simply right-click the rom.zip and select “Extract Here”.
If you now open you extracted folder, you should see a bunch of .img files. The 2 we are looking for are system.img and boot-signed.img. For now, create a new folder on your desktop, we’ll call it “custom”, and copy the boot-signed.img into that folder (I usually rename boot-signed.img to boot.img). Also create a folder called “system” in the same directory. Next we need to mount the system.img so we can extract the contents into the “system” folder you just created. Back in Terminal, type:
Code:
sudo mkdir -p /mnt/temp
sudo mount -o loop ~/Desktop/rom/system.img /mnt/temp
and then
sudo cp -r /mnt/temp/* ~/Desktop/custom/system
After several minutes, you should have a folder called “custom” on your desktop and inside of that should be “boot.img” and a “system” folder with a bunch of files and folders in it. You now need to change permissions on the folder so you can zip it up and copy it all. Back in Terminal type:
Code:
sudo chown -R username ~/Desktop/custom
Next step is to zip it all up so we can get it into the kitchen. Highlight both the “boot.img” and “system” folders, right-click them, and select “Compress”. Change the extension to .zip and click OK. Once zipped, drag (or copy) that folder into /home/username/kitchen/original_update.
Open Terminal and type:
Code:
cd ~/kitchen
./menu
Once the kitchen starts, you’ll need to set up a Working Folder, so select option “1″. If you only have 1 ROM zip in there you can just hit Enter. Follow through the prompts to rename your working folder if you want. I’m not going to guarantee that it will always work but it has worked for me in the past to select option “2″ from the main menu to “Add root permissions”. Moving on to de-odexing, select option “0 – ADVANCED OPTIONS”. Next, select option “11 – Deodex files in your ROM”. I usually do this by deodexing framework first and then system. If you’re de-odexing the ATT ROM, “PirateGhost” from xda clued me in that you need to temporarily remove the “com.att.vmm.sharedlib.jar” from /system/framework otherwise de-odexing will fail. When you get into the de-odexing option it will have you set your API level. The default is 10 which is Android 2.3.4 however, ICS can be 14 or 15. If on the latest 4.0.3, it’s API Level 15. Google can also help you here. If you’ve done everything right it will de-odex for 20 minutes or so depening on your hardware and should say “0 .odex files remain”. If you have any that remain, you can do them manually or not at all. Up to you on how you do it.
Since that’s basically all we’re discussing for right now on creating this ROM, we’ll continue on to building a flashable zip. Back at the main menu, select option “99 – Build ROM from working folder”. I recommend using the default “Interactive Mode”. Select yes to optimizing/zip-aligning all apks. When asked to add Updater-script to ROM, select yes. Here’s the thing with the updater-script that it builds. It’s only partially right. You need to fix the partition format section for the Vivid (or for whatever phone you’re building for). It’s best to look at some other’s scripts to see how it’s done. When asked by the wizard to sign your ROM, don’t do it. It’s not necessary. Feel free to rename it to whatever you want. After you’ve fixed the updater-script and I do mean AFTER, you can try flashing the ROM. And don’t forget to flash the boot.img as well.
There you have it. You now have a base ROM for you to work from. Obviously, this is just scratching the surface of what can be done but it’s a start. This is just how I do it. There are other ways to accomplish the same thing but this method has worked for me. Attached is a sample updater-script that I pulled from my AT&T stock ICS ROM. Use it only as a template and modify it to fit your needs and obviously, remove the txt extension.
Click to expand...
Click to collapse
Thanks, I've De-odexed ICS 4.0.3 ROM from WEE RUU. But. When I flash to Phone. The boot was successfully. And Everything works. But in the Sense Desktop. Any of ICON's Title Couldn't Display in the Sense Homescreen. It's totally naked!! including widgets. What's Problem? The others text display is work.
My Lab: Windows 7 with JDK&JRE
Cygwin+Kitchen 1.92
---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------
Should I Cooking ICS with Ubuntu?
ChunD.K said:
Thanks, I've De-odexed ICS 4.0.3 ROM from WEE RUU. But. When I flash to Phone. The boot was successfully. And Everything works. But in the Sense Desktop. Any of ICON's Title Couldn't Display in the Sense Homescreen. It's totally naked!! including widgets. What's Problem? The others text display is work.
My Lab: Windows 7 with JDK&JRE
Cygwin+Kitchen 1.92
---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------
Should I Cooking ICS with Ubuntu?
Click to expand...
Click to collapse
Can you grab a screenshot? Seems pretty strange.
I find problems out。When I tried to Extract All files form a Stock RUU。Than pack it up without any touching。flash to phone。Boot Successfully...
But IT'S JUST NAKED!!! I really confused！
RUU Version：Australian RUU-HOLIDAY-ICS-35-S-Telstra-WWE-3.25.841.4-Radio-3.02.4740.09-34.20.701040.19
Everything is fine when I Run RUU.exe to update。
Jirv311 said:
Can you grab a screenshot? Seems pretty strange.
Click to expand...
Click to collapse
Where you are? I need your Reply.
ChunD.K said:
Where you are? I need your Reply.
Click to expand...
Click to collapse
I need your screenshot.
Jirv311 said:
I need your screenshot.
Click to expand...
Click to collapse
Finally, Here is the Problem Screenshot. SO WERIED
I‘ve also use the latest Touch RECOVERY。 Problem is still。。。
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You gotta help me!
I mean i Pack them pu without any touching。
Where are you？
If I had to guess, I'd say you're using an unsupported language? I honestly am not sure.
Sent from my HTC PH39100 using xda premium
No, Itried switch to English. It jut naked.
Thanks alot for the thread! Is there anyway you could go into more detail about fixing the updater script for vivid?
bennykudos said:
Thanks alot for the thread! Is there anyway you could go into more detail about fixing the updater script for vivid?
Click to expand...
Click to collapse
I attached the updater-script to the OP. The main thing that needs fixing when your building it is putting in the correct format commands for the Vivid.
Do you know how to decompile the apks? I have expiernce with decompiling
Apks on the Samsung infuse but I can not figure out how do it for this phone...I can't even successfully install the framework...and yes I'm using an ics apktool...I've tried on both windows 7 and ubuntu 11.04
Could someone please link me to an apktool that works with this phones stock ics apks and tell me any special/extra steps I need to do to install framework and decompile apks
Sent from my HTC PH39100 using xda app-developers app
mg2195 said:
Do you know how to decompile the apks? I have expiernce with decompiling
Apks on the Samsung infuse but I can not figure out how do it for this phone...I can't even successfully install the framework...and yes I'm using an ics apktool...I've tried on both windows 7 and ubuntu 11.04
Could someone please link me to an apktool that works with this phones stock ics apks and tell me any special/extra steps I need to do to install framework and decompile apks
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
i think its called apk manager now.. sorry to revive
Hey people, I've just found it at O3D forums and I think I should share the information, as I don't have time for creating a good tutorial myself.
This way you can change colors for your own likes and make a lot kind of themes.
Before starting you should have your Apktool environment set up.
1. (only if you never saw APKTOOL in your life, otherwise, just jump it)
1· Download and install latest version of Java JDK
2· Download latest version of APK Multi-Tool as we'll be using it for un/packing APKs and push/pull them from/to our device.
3· Extract it anywhere you may like. If posible, in C:/ to avoid any kind of problems. Be sure to read README file before asking something about it.
4· Run Setup.bat, type 3 and press Enter. Close it.
5· Run Script.bat, type 0 and press Enter. Now let's type our framework's path.
6· /system/framework/framework-res.apk for basic framework file. This will be pulling it out from our phones.
7· Repeating Number 5, type /system/framework/lge-res.apk for LG's framework file.
8· Now move to X:\...\APK-Multi-Tool\place-apk-here-for-modding\ and copy both apks (framework-res + lge-res) and paste it at X:\...\APK-Multi-Tool\other\
9· Run Setup.bat again, type 2 and press Enter. Now both frameworks should be installed and we are ready to un/pack APKs from the version we're actually using (v30A/B/C/D...). Close it.
10· Back in Script.bat, type 0 again followed by Enter, then type the path of your desired APK. (/system/framework/xxxxxx.apk for frameworks & /system/app/xxxxxx.apk for apps). After pushing it, select it as your actual project.
11· Now type 9 followed by Enter. This will unpack our APK.
12· Now is the time for tunning anything you want to. Go to X:\...|APK-Multi-Tool\projects\xxxxxx.apk\ and you'll find there everything.
13· When it's done, let's re-pack it typing the option 11 followed by Enter. When repacking gets done, it will ask if you want to use any files from your original APK. Tell it Yes, otherwise your apk won't get signed.
14· When the extracting is done, move to X:\...|APK-Multi-Tool\keep\ and erase everything there BUT META-INF folder + AndroidManifest.xml. Now press anything at APK Multi-tool window and you'll get your APK ready to go.
15· Now type 8 to push it back to your phone and type the desired path. If it cames from /system/app/xxxxx.apk or /system/framework/xxxxx.apk.
If you get any error recompiling it, you should take a look at the log, typing 23 and fix it at the projects folder.
Click to expand...
Click to collapse
2.
potaturrias said:
When i maked this theme (my first theme) y used trial and error procedure.
The first step is replace or edit 9.png. pictures in drawable-hdpi folder located in framework-res.apk and lge-res.apk, you can do this quickly using this tools:
http://jgilfelt.github.com/android-actionbarstylegenerator (Check that the names of new pictures match with the old pictures)
http://android-holo-colors.com/
Many images have to edit them by hand
If you put more files than originally,for example switches in lge-res drawable-hdpi, you will get an error when try to compile.
The second step is replace xml files in drawable folder using xml files from zip file that you downloaded in the previous step.
If you don't get the desire result you have to edit styles.xml or drawable folder files or layout files to change backgrounds colors, text color,etc.
Remember there applications with lines in XML files that reference to framework or lge-res, for example:
android:textColor="@*android:color/transparent makes reference to transparent color defined in framework-res and
android:textColor="@com.lge.internal:color/transparent makes reference to transparent color defined in lge-res.
I hope that this mini guide help you, remember that you can make your theme based on this theme, will be easier i think.
Click to expand...
Click to collapse
Thanks to @potaturrias!
GUIDE ON HOW TO "DEODEX"
YOUR STOCK ROM ON PC
THIS IS FOR LG G FLEX ON JELLY BEAN 4.2.2
HAS NOT BEEN TESTED ON KITKAT 4.4
THIS IS NOT FOR ANYONE WHO IS NOT
COMFORTABLE WITH "ADB" AND ITS COMMANDS!!!
IM NOT RESPONSIBLE FOR YOUR CHOICE TO FOLLOW THIS GUIDE OR IF YOU STRAY FROM THE GUIDE AND SCREW UP YOUR DEVICE BY JAMMING FORKS IN THE USB PORT OR USING IT AS A FLOATATION DEVICE (doesnt work, i tried, sinks right to the bottom)
So with that said lets begin.
There are a few things youll need to do to get set up if you havent already implemented these. Things youll need : adb set up, android sdk, xUltimate v2.4.2, fresh stock phone (backed up), fairly descent understanding of adb and its commands, and one toothpick.
1.Download android-sdk & extract it. http://developer.android.com/sdk/index.html
2. Download xUltimate v2.4.2 & extract it. http://www.xeudoxus.com/android/xUltimate-v2.4.2.zip
3.Copy the extracted android-sdk contents to a new folder youre going to create in C:/Program Files/Android
4.Change name in this folder there is a folder named SDK change it to Android.sdk.
So that you end up with a folder inside C:/Program Files/Android named "Android.sdk" C:/Program Files/Android/Android.sdk
In that folder you should have :
build-tools
extras
platform-tools
system-images
tools
FOR THOSE OF YOU, IF YOURE LIKE ME AND HAVE HAD SDK/ADB INSTALLED FOR A WHILE ON YOUR PC YOU MAY NEED TO UPDATE TO VERSION 1.0.31 OR NEWER. I HAD TO AND THAT MADE ALL THE DIFFERENCE. JUST PULL THESE FILES OUT OF THE NEW VERSION AND PASTE WHERE YOU HAVE YOUR SDK/ADB SET UP
FILES TO COPY AND PASTE
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
THAT SHOULD HAVE YOU UP TO DATE
5. You need to flash back to stock and reroot. For this you can follow this thread to do so :
http://forum.xda-developers.com/showthread.php?t=2644083
6. I hope it goes with out saying, MAKE A BACKUP AND SAVE IT SOMEWHERE BESIDES YOU PHONE AS WELL AS ON YOUR PHONE !!!!!
7. Make sure usb debugging in enabled. If you dont no how to do this then you shouldnt be doing this and you best bet would be to go to the PLAY STORE and download GO LAUNCHER and some GO themes to make your phone "prettier" This is for themers out there to be able to have a deodexed rom (system/app folder & system/framework folder) to be able to theme and mod.
8. Connect your phone to your computer.
9. Launch Main.exe In the xultimate folder. (run as administrator)
10. Select option 1 (pull /system/app) wait till its done it will take 20+ mins
11. Select option 2 (pull /system/framework) wait till its done it will take about half as long
12. Select option 3 (Deodex /system/app) wait till its done
[If encounter any error. Find out which .odex file it is . Then remove .odex file from the origi_app in xUltimate folder]
13. Select option 4 (Deodex /system/framework) wait till its done
14. Now select EXIT.
15. Rename the folder "done_app" to "app" and the "done_frame" to "framework"
16. Copy the 2 files you just renamed to the root of your sdcard on you your LG G Flex.
17. Now youre done with the hard part and the time consuming part.
TIME TO GET THOSE FRESHLY DEODEXED FILES
PUT BACK WHERE THE BELONG
THIS IS WHERE YOULL NEED TO USE adb.
1. Again make sure you have usb debugging eneabled, connect your phone to PC and make sure its in "MTP" mode.
2. Navigate to where you put your sdk files you extracted earlier.
C:/Program Files/Android/Android.sdk
3. Now in the Android.sdk folder hold "shift" and right click inside folder then select from the drop down menu "open command prompt here"
If this is the first time youve used adb on this phone then make sure you get the supersu prompt asking for permission to use adb from this PC.
4. Enter these commands one line at a time and hit enter after each line. Some lines may take several minutes to do their thing but be patient it will give you another cursor and cmd prmt line to type on. (VERY IMPORTANT TO DO THIS EXACTLY PER INSTRUCTIONS !!!!!) !!!!!! DONT ENTER ANYTHING IN RED ITS JUST EXPLANATION !!!
adb devices should see your device
adb shell
su
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
NOW IF EVERYTHING WENT WELL YOU REBOOTED AND HAVE A DEODEXED ROM!!
6. Congradulations you have now deodexed your LG G Flex stock rom and can now begin theming. I suggest before you do anything else you reboot into recovery and make a back up so if anything gets fubared you dont have to restore to an odex rom and go thru this again.
UPDATE : THIS DOES WORK ON KITKAT 4.4
Reservered
Sent from my LG-D959 using Tapatalk
works
It works with 4.4
Thanks dude
mattwheat said:
GUIDE ON HOW TO "DEODEX"
YOUR STOCK ROM ON PC
THIS IS FOR LG G FLEX ON JELLY BEAN 4.2.2
HAS NOT BEEN TESTED ON KITKAT 4.4
THIS IS NOT FOR ANYONE WHO IS NOT
COMFORTABLE WITH "ADB" AND ITS COMMANDS!!!
IM NOT RESPONSIBLE FOR YOUR CHOICE TO FOLLOW THIS GUIDE OR IF YOU STRAY FROM THE GUIDE AND SCREW UP YOUR DEVICE BY JAMMING FORKS IN THE USB PORT OR USING IT AS A FLOATATION DEVICE (doesnt work, i tried, sinks right to the bottom)
So with that said lets begin.
There are a few things youll need to do to get set up if you havent already implemented these. Things youll need : adb set up, android sdk, xUltimate v2.4.2, fresh stock phone (backed up), fairly descent understanding of adb and its commands, and one toothpick.
1.Download android-sdk & extract it. http://developer.android.com/sdk/index.html
2. Download xUltimate v2.4.2 & extract it. http://www.xeudoxus.com/android/xUltimate-v2.4.2.zip
3.Copy the extracted android-sdk contents to a new folder youre going to create in C:/Program Files/Android
4.Change name in this folder there is a folder named SDK change it to Android.sdk.
So that you end up with a folder inside C:/Program Files/Android named "Android.sdk" C:/Program Files/Android/Android.sdk
In that folder you should have :
build-tools
extras
platform-tools
system-images
tools
FOR THOSE OF YOU, IF YOURE LIKE ME AND HAVE HAD SDK/ADB INSTALLED FOR A WHILE ON YOUR PC YOU MAY NEED TO UPDATE TO VERSION 1.0.31 OR NEWER. I HAD TO AND THAT MADE ALL THE DIFFERENCE. JUST PULL THESE FILES OUT OF THE NEW VERSION AND PASTE WHERE YOU HAVE YOUR SDK/ADB SET UP
FILES TO COPY AND PASTE
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
THAT SHOULD HAVE YOU UP TO DATE
5. You need to flash back to stock and reroot. For this you can follow this thread to do so :
http://forum.xda-developers.com/showthread.php?t=2644083
6. I hope it goes with out saying, MAKE A BACKUP AND SAVE IT SOMEWHERE BESIDES YOU PHONE AS WELL AS ON YOUR PHONE !!!!!
7. Make sure usb debugging in enabled. If you dont no how to do this then you shouldnt be doing this and you best bet would be to go to the PLAY STORE and download GO LAUNCHER and some GO themes to make your phone "prettier" This is for themers out there to be able to have a deodexed rom (system/app folder & system/framework folder) to be able to theme and mod.
8. Connect your phone to your computer.
9. Launch Main.exe In the xultimate folder. (run as administrator)
10. Select option 1 (pull /system/app) wait till its done it will take 20+ mins
11. Select option 2 (pull /system/framework) wait till its done it will take about half as long
12. Select option 3 (Deodex /system/app) wait till its done
[If encounter any error. Find out which .odex file it is . Then remove .odex file from the origi_app in xUltimate folder]
13. Select option 4 (Deodex /system/framework) wait till its done
14. Now select EXIT.
15. Rename the folder "done_app" to "app" and the "done_frame" to "framework"
16. Copy the 2 files you just renamed to the root of your sdcard on you your LG G Flex.
17. Now youre done with the hard part and the time consuming part.
TIME TO GET THOSE FRESHLY DEODEXED FILES
PUT BACK WHERE THE BELONG
THIS IS WHERE YOULL NEED TO USE adb.
1. Again make sure you have usb debugging eneabled, connect your phone to PC and make sure its in "MTP" mode.
2. Navigate to where you put your sdk files you extracted earlier.
C:/Program Files/Android/Android.sdk
3. Now in the Android.sdk folder hold "shift" and right click inside folder then select from the drop down menu "open command prompt here"
If this is the first time youve used adb on this phone then make sure you get the supersu prompt asking for permission to use adb from this PC.
4. Enter these commands one line at a time and hit enter after each line. Some lines may take several minutes to do their thing but be patient it will give you another cursor and cmd prmt line to type on. (VERY IMPORTANT TO DO THIS EXACTLY PER INSTRUCTIONS !!!!!) !!!!!! DONT ENTER ANYTHING IN RED ITS JUST EXPLANATION !!!
adb devices should see your device
adb shell
su
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
NOW IF EVERYTHING WENT WELL YOU REBOOTED AND HAVE A DEODEXED ROM!!
6. Congradulations you have now deodexed your LG G Flex stock rom and can now begin theming. I suggest before you do anything else you reboot into recovery and make a back up so if anything gets fubared you dont have to restore to an odex rom and go thru this again.
Click to expand...
Click to collapse
Dang dude I just posted this and you've already done it. Wow maybe you should have written this thread. Lmao. It took me several hours to figure out my adb being older version was why it wasn't working.
Sent from my LG-D959 using Tapatalk
mattwheat said:
GUIDE ON HOW TO "DEODEX"
YOUR STOCK ROM ON PC
THIS IS FOR LG G FLEX ON JELLY BEAN 4.2.2
HAS NOT BEEN TESTED ON KITKAT 4.4
THIS IS NOT FOR ANYONE WHO IS NOT
COMFORTABLE WITH "ADB" AND ITS COMMANDS!!!
IM NOT RESPONSIBLE FOR YOUR CHOICE TO FOLLOW THIS GUIDE OR IF YOU STRAY FROM THE GUIDE AND SCREW UP YOUR DEVICE BY JAMMING FORKS IN THE USB PORT OR USING IT AS A FLOATATION DEVICE (doesnt work, i tried, sinks right to the bottom)
So with that said lets begin.
There are a few things youll need to do to get set up if you havent already implemented these. Things youll need : adb set up, android sdk, xUltimate v2.4.2, fresh stock phone (backed up), fairly descent understanding of adb and its commands, and one toothpick.
1.Download android-sdk & extract it. http://developer.android.com/sdk/index.html
2. Download xUltimate v2.4.2 & extract it. http://www.xeudoxus.com/android/xUltimate-v2.4.2.zip
3.Copy the extracted android-sdk contents to a new folder youre going to create in C:/Program Files/Android
4.Change name in this folder there is a folder named SDK change it to Android.sdk.
So that you end up with a folder inside C:/Program Files/Android named "Android.sdk" C:/Program Files/Android/Android.sdk
In that folder you should have :
build-tools
extras
platform-tools
system-images
tools
FOR THOSE OF YOU, IF YOURE LIKE ME AND HAVE HAD SDK/ADB INSTALLED FOR A WHILE ON YOUR PC YOU MAY NEED TO UPDATE TO VERSION 1.0.31 OR NEWER. I HAD TO AND THAT MADE ALL THE DIFFERENCE. JUST PULL THESE FILES OUT OF THE NEW VERSION AND PASTE WHERE YOU HAVE YOUR SDK/ADB SET UP
FILES TO COPY AND PASTE
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
THAT SHOULD HAVE YOU UP TO DATE
5. You need to flash back to stock and reroot. For this you can follow this thread to do so :
http://forum.xda-developers.com/showthread.php?t=2644083
6. I hope it goes with out saying, MAKE A BACKUP AND SAVE IT SOMEWHERE BESIDES YOU PHONE AS WELL AS ON YOUR PHONE !!!!!
7. Make sure usb debugging in enabled. If you dont no how to do this then you shouldnt be doing this and you best bet would be to go to the PLAY STORE and download GO LAUNCHER and some GO themes to make your phone "prettier" This is for themers out there to be able to have a deodexed rom (system/app folder & system/framework folder) to be able to theme and mod.
8. Connect your phone to your computer.
9. Launch Main.exe In the xultimate folder. (run as administrator)
10. Select option 1 (pull /system/app) wait till its done it will take 20+ mins
11. Select option 2 (pull /system/framework) wait till its done it will take about half as long
12. Select option 3 (Deodex /system/app) wait till its done
[If encounter any error. Find out which .odex file it is . Then remove .odex file from the origi_app in xUltimate folder]
13. Select option 4 (Deodex /system/framework) wait till its done
14. Now select EXIT.
15. Rename the folder "done_app" to "app" and the "done_frame" to "framework"
16. Copy the 2 files you just renamed to the root of your sdcard on you your LG G Flex.
17. Now youre done with the hard part and the time consuming part.
TIME TO GET THOSE FRESHLY DEODEXED FILES
PUT BACK WHERE THE BELONG
THIS IS WHERE YOULL NEED TO USE adb.
1. Again make sure you have usb debugging eneabled, connect your phone to PC and make sure its in "MTP" mode.
2. Navigate to where you put your sdk files you extracted earlier.
C:/Program Files/Android/Android.sdk
3. Now in the Android.sdk folder hold "shift" and right click inside folder then select from the drop down menu "open command prompt here"
If this is the first time youve used adb on this phone then make sure you get the supersu prompt asking for permission to use adb from this PC.
4. Enter these commands one line at a time and hit enter after each line. Some lines may take several minutes to do their thing but be patient it will give you another cursor and cmd prmt line to type on. (VERY IMPORTANT TO DO THIS EXACTLY PER INSTRUCTIONS !!!!!) !!!!!! DONT ENTER ANYTHING IN RED ITS JUST EXPLANATION !!!
adb devices should see your device
adb shell
su
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
NOW IF EVERYTHING WENT WELL YOU REBOOTED AND HAVE A DEODEXED ROM!!
6. Congradulations you have now deodexed your LG G Flex stock rom and can now begin theming. I suggest before you do anything else you reboot into recovery and make a back up so if anything gets fubared you dont have to restore to an odex rom and go thru this again.
Click to expand...
Click to collapse
UPDATE : THIS DOES WORK ON KITKAT 4.4
Sent from my LG-D959 using Tapatalk
Wow that must be a good sign of a well explained tutorial when 80+ people read it and no questions or issues.
Sent from my LG-D959 using Tapatalk
mattwheat said:
Wow that must be a good sign of a well explained tutorial when 80+ people read it and no questions or issues.
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Is true guy, in my 6 years of xda is the device more boring i had, anybody react to our treads, neither with a simple thanks, i will try, or worked well, thanks
At least dont have people saying, how i open cmd?this will explode my device? Hehe
Enviado de meu LG-D958 usando Tapatalk
Maikeu Locatelli said:
Is true guy, in my 6 years of xda is the device more boring i had, anybody react to our treads, neither with a simple thanks, i will try, or worked well, thanks
At least dont have people saying, how i open cmd?this will explode my device? Hehe
Enviado de meu LG-D958 usando Tapatalk
Click to expand...
Click to collapse
right right I guess it could be bad and be getting bombarded with how to and dumb questions. I figured more people would want to have a deodexed ROM so that xtheme beta5 and hkthemer themed more of their system.
Sent from my LG-D959 using Tapatalk
removed odex
Ok, get ready for it here comes the dumb nOOb question: When i remove odex file in orig_app and rerun xultimate, app associated with odex is no longer in done app folder, is that how it goes down or should i be doing something differently when i run into errors?, thank you
Yes when you remove odex in orig folder then rerun some apps not necessary to have and any apps that error out that are you will have to Google them and find the deodex version. But if you used the lgflash back to stock then rerooted you shouldn't get any errors on any necessary apps. I didn't. There where 3 maybe five that I got errors on but they weren't necessary to have so I deleted them.
Sent from my LG-D959 using Tapatalk
mattwheat said:
Yes when you remove odex in orig folder then rerun some apps not necessary to have and any apps that error out that are you will have to Google them and find the deodex version. But if you used the lgflash back to stock then rerooted you shouldn't get any errors on any necessary apps. I didn't. There where 3 maybe five that I got errors on but they weren't necessary to have so I deleted them.
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
I'm not trying to hijack your thread but if anybody is interested I found another similar method specifically for KK. I have used it and it works perfectly. The only apk that it wouldn't deodex was the stock LG keyboard. If anybody would like a link I could share. It does not work real well with 4.2 so this one here is the best option for 4.2.
No problem. If there's an easier method by all means. I didn't even know when I wrote this one if it worked on kk or not. I'm still on 4.2.2 for the recovery.
http://forum.xda-developers.com/showthread.php?t=2725930
I used this as instructed and it takes a while but worked perfectly. I will save you some time and tell you to remove lg stock keyboard. Tool does deodex but for some reason will not work. Just adb push using same method as stated in op except you will have to add a step for the priv app. I take no credit or responsibility but I've used it myself and it does work.
Sent from my LG-D950 using XDA Premium 4 mobile app
Matt check your pm plz
mattwheat said:
Wow that must be a good sign of a well explained tutorial when 80+ people read it and no questions or issues.
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
This is the best explained way to deodex a ROM I've ever seen. Definitely going to try. Will be the first time I've read a how to on deodexing and feel confident enough to try it myself instead of installing someone elses deodexed ROM. But I may revisit with a question lol