Database Info

Init.d scripts not working correctly

I am currently working on a custom rom but I can't get the init.d start up scripts to rewrite the values of certain files and do the thing I want them to do. Anyone have any ideas why?
Sent from my SGH-T839 using XDA Premium App

Busybox? Ask dev.

Depending on which files you are trying to overwrite, it may be writing them before the system sets their values.

if this is the problem any ideas on how i can overwrite the system values AFTER the system sets the values?

i'm currently using the 01insert_file_name_here - 98insert_file_name_here
method and i have it set to 98 so that means that the system should be writing those values last which should mean the values would be overwritten like i wanted but yet NONE of the init.d scripts are running.
hmmm.....

Which kernel are you using?

your kernel from glorious overdose that you said i could use haha
i even also tried switching to a kg2 stock deodex base and doing the same mods and the same result happened.....
i thought that the #filename method in the system/etc/init.d folder was the method used for running startup scripts.....i also gave the ect/init.d folder rwx-rwx-rwx permissions (0777) in the updater-script yet nothing.....

it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.

sduvick said:
it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.
Click to expand...
Click to collapse
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s

-x]Trunks[x- said:
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s
Click to expand...
Click to collapse
it seems galaxy s phones need the script to start with "S" followed by a number between 01-98 then a file name.....so the 2nd option I posted is correct.
but yet even with using your kernel i can't get the script to set the values i'd like it to for the rom i'm working on.....here's the script i have made (don't worry those who have work that is contributed to that file will be credited when i post the rom w/ this working script)
i've been trying for almost a week with different people's "solutions" yet none work
rom base: kj2 deodex w/ root
modem: kj2
kernel: glorious overdose 2 kernel
hopefully you can figure out the problem

[MOD/TUT]CRT Off Animation & SIP Over LTE/HSPA

I know there is already a CRT Off Animation flashable zip in this section, but if you already have a themed framework then it can be a pain in the a$$ trying to flash it over whatever you have. As for SIP over LTE/HSPA, I've seen a lot of requests from people on how to enable it, so here it is. I'm also making this kind of for myself, since I always search for tutorials on how to change things, but always just end up finding .zip files, which can get quite annoying if I only want to change one thing. In any case, here we go...
Prerequisites
Superuser (Duh)
Apk Manager by Daneshm90
ADB + Understanding How To Pull/Push Files (Need help? Read this!)
Patience
A Good Texteditor (I recommend Notepad++)
Know why "sudo rm -rf /" is always a bad idea
Steps To Follow
Pull your framework-res.apk file from your system folder
Place said framework-res.apk file into the "place-here-for-modding" folder included in the Apk-Manager Folder
Run the Script.bat file also included in the Apk-Manager Folder.
Run option 9 in the newly opened window (Don't use the dependency option)
Go back into the Apk-Manager Folder; there should now be a folder dubbed "projects".
Head into that folder and open framework-res/res/values/bools.xml with that good texteditor you're supposed to have if you read the prerequisites.
Don't be intimidated by some of the code you see. Ignore everything else in the file and head straight for/search "config_animateScreenLights". This controls the state of the CRT Off Animation.
This step may sound a little counter-intuitive, but in order to get the CRT Off to activate correctly, you need to set the boolean to "False".
Now that CRT Off Animation taken care off, we can move on to enabling SIP over HSPA/LTE. Go to/search for "config_sip_wifi_only" and set this boolean to false as well.
There are actually other things you can enable/disable in the bools.xml file, although I would not recommend poking around unless you know what you're doing. Example: Enable Menu Unlock by setting that specific bool (not entirely sure of its name) to true.
Save the bools.xml file, and return back to the main menu of Apk Manager.
Select option 11 and say y (system app) and then n (no need to retain anything)
If you head back to your "place-apk-here-for-modding" folder, there should be a new file named unsignedframwork-res.apk. Open this (DO NOT EXTRACT THE FILES) using a tool such as winrar or 7zip, and delete both the META-INF folder and the AndroidManifest.xml
Copy the META-INF and the AndroidManifest.xml from the original framework-res.apk and place it in the new unsignedframework-res.apk. Remember to not extract the files, just copy/paste.
Rename unsignedframework-res.apk to framework-res.apk and push that back to the system folder on your phone.
Reboot
Enjoy Your CRT Off Animation + SIP Over HSPA/LTE!
FAQ
What is SIP? SIP stands for Session Initiation Protocol, and is used for controlling communications such as Voice over Internet Protocol, or Video over Internet Protocol. It's used in a lot of applications on the market, a big one being Skype. If you want to learn more, go here, here, or here.
Why would I need SIP over HSPA/LTE? Because I told you so. No, but seriously, this will allow you to use all kinds of SIP applications found on the market not only on wifi networks, but also on the go.
Can you haz build me a flashable zip? The whole point of this thing is to teach people how to mod their own already modded files without having to replace everything. But yeah, if you PM me I'll probably do it.
IAQ
Why is jomeister15 so amazing? Sorry, this question is not infrequently asked.

nice tutorial, it took me a while to find this information a few days ago, good to know someone has gathered it and made it easy to find.

very nice i know i did that while back ago and i was like ughhh ** also there is a post for crt animation on you should include that too. i know id like to get it on my theme but im working through it and it blows my head into 2 .. but moderator please pin this thread or make it a sticky right @ top with cherry.

Awesome tutorial! Been wanting to add the CRT off animation to my ROM for a while now, just haven't gotten around to it. And I will definitely be following your guide. However, can someone please explain to me what SIP is? I've seen a couple of threads about it but none of them have actually explained what it is. Thanks!
Sent from my SAMSUNG-SGH-I727 using XDA App

plwalsh88 said:
Awesome tutorial! Been wanting to add the CRT off animation to my ROM for a while now, just haven't gotten around to it. And I will definitely be following your guide. However, can someone please explain to me what SIP is? I've seen a couple of threads about it but none of them have actually explained what it is. Thanks!
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Just updated OP with FAQ section that includes explanation of SIP if you want to take a look.

i am getting FC. Not working. After changing the file size reduced to around 5mb which before it is 7mb.

gkrananth said:
i am getting FC. Not working. After changing the file size reduced to around 5mb which before it is 7mb.
Click to expand...
Click to collapse
What app in specific are you getting FC with? It may just be in issue with fixing permissions. Try that first, and if that doesn't work, re-try the procedure but do not carry the android manifest and meta-inf over. May I also ask what rom you're on? Every dev's framework is different.

oh CRT
hay i did it.. no FC no ERRORS or no CRT off animation.. phone is working normally .. (i made a zip also)
im using samsung skyrocket with embryo 6.1 plz help me to fix this(as above mentioned my framework-res also decreased like 2mb)

sakunakia said:
hay i did it.. no FC no ERRORS or no CRT off animation.. phone is working normally .. (i made a zip also)
im using samsung skyrocket with embryo 6.1 plz help me to fix this(as above mentioned my framework-res also decreased like 2mb)
Click to expand...
Click to collapse
Dude you just necro'd a thread that's almost a year since last post and half these guys aren't even around anymore.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Originally Posted by sakunakia
hay i did it.. no FC no ERRORS or no CRT off animation.. phone is working normally .. (i made a zip also)
im using samsung skyrocket with embryo 6.1 plz help me to fix this(as above mentioned my framework-res also decreased like 2mb)
Click to expand...
Click to collapse
Dude you just necro'd a thread that's almost a year since last post and half these guys aren't even around anymore.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
omg this
Sent from my SGH-T999 using xda premium

[HELP]Aroma scripts error.[THREAD CAN BE CLOSED]

Hi guys.I tried adding Aroma Installer to BlazR but i get Syntax Error:Aroma-Config on line 207 col (when i want to flash the rom)..I what tried to resolve this bug:
»Shearched on the internet&xda but nothing found
»Checked the 207th line using notepad++ but the scripts seem correct.
Any help is wellcome.
PS:Here is the link of the aroma config http://www.multiupload.nl/L17MB983GI .

Try This
Code:
menubox(
"<~installationtype.title>",
"<~installationtype.desc>",
"icons/install",
"type.prop",
"<~installationtype.typical>","<~typical.desc>","icons/default",
"<~installationtype.custom>","<~custom.desc>", "icons/customize"
);
But why do you want to make a Rom with AROMA, when there is already Crybernation and MoonRom? And obvisously your script is a copy and paste job of mine with some things deleted (like it was almost the same with MoonRom)

crybert said:
Try This
Code:
menubox(
"<~installationtype.title>",
"<~installationtype.desc>",
"icons/install",
"type.prop",
"<~installationtype.typical>","<~typical.desc>","icons/default",
"<~installationtype.custom>","<~custom.desc>", "icons/customize"
);
But why do you want to make a Rom with AROMA, when there is already Crybernation and MoonRom? And obvisously your script is a copy and paste job of mine with some things deleted (like it was almost the same with MoonRom)
Click to expand...
Click to collapse
Sorry for that.If you don't agree i will remove the Aroma installer.I don't have the ammount of time needed to learn all script.I'm busy with the school.
I need aroma because i want to let people choose their kernel&apps easy.
Sorry again and thanks for help.
PS:Can i continue modifying your script ?I will learn faster if i will continue it.But as i said if you don't agree with that i will stop and continue on my own .
EDIT:In fact i combined yours and moonROM's.Tweaked a lil' and this is the result..

I would suggest you to use my script as a draft and make your own script. I think this will help you more than just deleting the entries you don't need.
I saw also some entries in your script which you don't need because you deleted these functions.
It took me really a lot of time and a lot of research to write this but I don't want that my work will be copied. So use it as a draft or let it be please.

crybert said:
I would suggest you to use my script as a draft and make your own script. I think this will help you more than just deleting the entries you don't need.
I saw also some entries in your script which you don't need because you deleted these functions.
It took me really a lot of time and a lot of research to write this but I don't want that my work will be copied. So use it as a draft or let it be please.
Click to expand...
Click to collapse
Ok.I will use it as a draft.Tnx for help.
EDIT:Thread can be closed now!

Thread closed upon OP's request

[HowTo] Odex FRAMEWORK, all Android versions may apply.

Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
This method should work on all Android devices.
------------------------------------------------------------------------------------------------------------
First of all, what is odex? Something you should know about classes.dex.
Odex stands for Optimized dex. I'm not gonna explain a lot because I'm not sure if I'm right. First of all, in typical apk files, when you open it with WinRAR or something like that, you can find a file called "classes.dex"(this type of apk is deodexed). This file is the key. It contains the core codes of the apk. However the other type of apk comes with an *.odex file and doesn't have classes.dex inside the apk file. This is odexed apk. There are 2 types of ROMs here, odexed and deodexed. Odexed ROMs' classes.dex are already out of the apk files, while deodexed ROMs' classes.dex are still in the apks. When Android executes an apk, it has to extract the classes.dex out and execute it. So when you flash an deodexed ROM, the first boot takes a long long time since the Android system needs to extract all the classes.dex into dalvik-cache(it shows "Optimizing apks" on the screen for 4.0 ROMs, shows boot animation on screen for 2.3 or below ROMs). However for the odexed ROMs, because the classes.dex are already out there, the system just grabs them and use them, without wasting time and storage space extracting classes.dex out.
Why odex framework?
It can boost your device a little by odexing your framework. Your phone can run more efficiently. Although it's a complicated process, but trust me, it's worth it.
What is so special about odexing framework files? What's the difference?
Odexing an app is very easy, and I believe everyone knows how to do it. But odexing framework is really annoying. Why? Because apps and more like stand-alone things, they are not a part of system. You delete it, nothing bad happens, your phone still boots, you just get endless FC if you delete the wrong one, or missing status bar, that's all. But framework files you cannot mess around. They are parts of the system. They have to match the system's codes precisely, without any error, even the order of files(keep this in mind, very important). So for every ROM, the framework initialize codes are different(same RUU or other ROM based ROMs count as its base ROM), and you must modify the odexing binary to make it odex for you properly, or you can sit and watch the beautiful bootloop.
What's the relationship between odexing apps and odexing framework?
Simple, but important. If you odexed apps, you cannot touch the framework. Framework always goes in the first place. If you wanna odex both, you must odex framework first. Or... "The Tragedy of App and Framework"...
So what do we have to keep in mind before we start?
Keep your mind clear, prepare a bag of ice in case you feel dizzy with the codes, and MAKE ENOUGH SPACE FOR FRAMEWORK ODEXING. I would prefer you remove a few useless apks in /system/app first to make more room in system partition. Failing odexing may brick your device forever! Nah just kidding it will only cause you to bootloop. No big deal. Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
What tools do you need?
Notepad++ and a magical rar that contains all you need to success.
Let's get started.
------------------------------------------------------------------------------------------------------------
1. Use your file manager to find init.rc at the very root directory of your phone and copy it to SDCard for later code editing, or you simply adb pull it out and skip the coping step. (If you know how to compile boot.img it is even easier, just unpack boot in Android Kitchen, look for line "export BOOTClassPATH". I'm not gonna introduce that method since most people can't. Silly me, didn't I just intoduced that? XD)
2. Connect USB, set mode as disk drive so you can access your SDCard. Copy init.rc into your computer. Open it with notepad, and find where it says "export BOOTClassPATH", create a new file and copy line "export BOOTClassPATH" into the new file. For example:
Code:
export BOOTCLASSPATH/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
3. Open dexopter in the rar you downloaded with Notepad++. Find the lines that show the similar contents to the things after "export BOOTClassPATH". It is Line 21 to Line 35 on my laptop. Edit them according to the things you just copied out of init.rc. For example, if the first file is "X.jar", then you will have to edit the line into "dexopt-wrapper/system/framework/X.jar /system/framework/X.odex". Then repeat until you finish with all the files that are listed in the long list you copied out of init.rc. File order DOES MATTER. Use the bag of ice I told you to prepare eariler to make you sober if you feel dizzy with the codes. The lines may be more or less after you edited them, doesn't matter.
4. Copy "dexopter" and "dexopt-wrapper" into /system/bin and set the correct permissions. Make sure they have enough permission to change your system files. Restart your phone.
5. Go to CMD and lead it to where adb.exe is(included in the rar). Type these in order:
Code:
adb shell
su
cd system/framework
dexopter fr
Then the codes will run crazy in your cmd window... The odex process has begun!
6. If the odex process completed without error, you are half way there! Well it doesn't mean you have to stare at your screen during the process. It's about time we figure it out! The phone will automatically reboot once it's finished. If it doesn't and you are sure all are done, reboot manually.
7. If you can't boot properly, go back and check everything carefully. If you can, then open your file manager and copy the entire framework directory into your SDCard. You can still adb pull and skip the next coping step.
8. Mount SDCard. Go into framework directory on your computer. Open every file that has an odex file with it, delete the classes.dex inside. WinRAR is okay. The files may seem ridiculously small after you delete the classes.dex, but don't worry since classes.dex are already pulled out and turned into odex files.
9. Copy the whole framework folder into the folder where adb is at. Use adb to push all the files back into /system/framework.
Code:
adb root
adb remount
adb push framework /system/framework
adb shell
su
chmod /system/framework xxx (xxx is a permission code, depends on your ROM. They should be the same as the old deodexed framework files. Use Google to find out how to use the permission codes.)
10. After all the files are pushed in, reboot your phone.
11. If it still boots into the system, congratulations! You've successfully odexed your framework! If it doesn't, then go back and read everything carefully. The most common error occurs when you are editing the dexopter code. You will have to redo everything again.
Done! Everything is ready to go!
You can directly grab the files you've odexed and put it in your custom ROM(must be the same base), just don't forget the odex files.
------------------------------------------------------------------------------------------------------------
Okay, hmm, what to say now? Still, I would be glad if you donated me, but if you don't it's okay, just reply and hit thanks .
Oh almost forgot, the magical rar: http://d-h.st/tYi
------------------------------------------------------------------------------------------------------------
Big thanks to Scott, see him in #3. He explained why some files aren't odexed and provided a easier method(but they all get you dizzy )
Big thanks to JSLEnterprises, see him in #4. He provided a newer busybox for Scott's method.

If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2

BreatheHT said:
Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
Click to expand...
Click to collapse
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott

If anyone finds this to be too much work... dont worry... it only unpacks the classes.dex once. It will only need to unpack a dex if original file has changed (changed entries need to propogate). That's why all the consecutive boots are back to a 'normal' span of time.
re-odexing your roms IS recommended if either A) you're anal-retentive/have OCD or B) propogation ("Android is Upgrading...") happens every time you reboot your device (it happens sometimes)
If you're going to use the tool scrosler linked to, replace the busybox binary with the one inside the attatched zip (this is busybox 1.20.1). The one that come with the tool is pretty dated.
:good:
Update: Busybox 1.20.2 has been released (though not compiled for android use yet)

Great stuff guys.

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
hehe yep I know the adb pull command, I thought about it and I didn't put it in...

theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You confused bro?

Thanks. Even though I won't ever be doing this, it's good to know what's going on.

This is awesome. Thanks so much for this. I wanted to know how to odex and deodex roms.
Sent from my HTC One XL using xda app-developers app

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yep Android Kitchen can do it.

Hopefully this will help to see more odex ROMs

This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Most official ROMs are odexed.

BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2

superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Nah carrier doesn't matter.

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions

BreatheHT said:
hehe yep I know the adb pull command, I thought about it and I didn't put it in...
Click to expand...
Click to collapse
Yeah, I like to do it better that way. Dont have to move my hands from the keyboard and mouse. Makes you more efficient :good:
BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
I think all?
superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Carrier is irrelevant. Most people dont know how to work with ODEX files so they go with de-odex. Its mroe challanging but provides a better experience.
techlogik said:
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..
Click to expand...
Click to collapse
No he is asking to go the other way from odex to de-odex.
BreatheHT said:
Yep Android Kitchen can do it.
Click to expand...
Click to collapse
JSLEnterprises said:
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, I love that script. I was the one that sent him the mnt point file for the HOX :highfive:
I am going to talk to him about bringing in "official" support for the Asus TF300T. I got the boot.img fiugred out this morning! Woot. **** is about to get real with the Asus!

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
its a good final touch when cook done with smali tweaks.
another benefit is sorta kang-protection

[Q] Updater script and build.prop

Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.

Zadeis said:
Hello all!
I am looking to automate a couple things I do when I flash a new build of Cyanogen mod. Namely my couple edits of the build.prop.
Yes I do understand that some will disagree with me editing the build.prop, and some may say it's dangerous. I'm not here to discuss those matters.
What I do want to discuss is that I want to create a flashable zip that contains an updater script that will essentially add my changes for me before I even start Cyanogen mod and save me time and effort. I am very unfamiliar with such things and was hoping someone could give me a hand and point me in the right direction. That way I can do my own thing and ask less questions in the future.
P.S. Do note I do prefer to be taught than just handed a script with everything I want in it.
Click to expand...
Click to collapse
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.

elesbb said:
Same here my friend same here.
But what i do to my ROMs when i have edits i wanna make is i extract the build.prop from the zip and edit what i want using Notepad++ then drag the build.prop back to the 7zip window to add it back to the zip and i flash. Simple as that
Now, if you really wanna get fancy, you could create an sh script that will read the build.prop AFTER flashing the ROM. It will read the build.prop, then change the things you want for you.. I dont really recommend this method as its not very simple and quite frankly im too lazy to create the sh script for myself. But i do believe it is possible.
Click to expand...
Click to collapse
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.

Zadeis said:
Interesting... I have tried the modify then drop the build.prop back into the zip, using 7-zip even, and it refuses to do so. hence me trying to do it in the manner of an updater script.
Click to expand...
Click to collapse
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.

elesbb said:
You could always make a second zip containing your modded build.prop. I remember having to do this with one of my edits on my S2 cause the ROM wouldnt set itself up with the changed Build.prop.
Click to expand...
Click to collapse
Hmm maybe. I'll try using winrar to see if it makes any difference using the same drag and drop new build.prop method just to satisfy my curiosity.

Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up

Reilly1812 said:
Could it be an MD5 issue since you are "modifying" the zip?
Still Charged Up
Click to expand...
Click to collapse
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.

Zadeis said:
Actually winrar worked. 7-zip can delete files from a CM archive but not add for some reason when winrar can do both. Not sure why but I still prefer 7-zip myself for everything else.
Though while this method does work I still wouldn't mind knowing how to add my changes via build.prop to streamline the entire process of updating CM.
Click to expand...
Click to collapse
7zip works for me without any issues..
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2