I want to add a zipalign script to my rooted odex stock rom KK2, I've got the script that most custom roms seem to use 'S70zipalign'.
Am hoping I don't get shot down in flames for this but is it just a matter of having busy box installed and putting the script in the following folder path system/etc/init.d to get it to zipalign my apps on boot
Related
Zipalign apks of Stock Roms by using following steps:
Thanks to Senab for the Zip file
Steps:
1. Download the zip file from the following post
http://forum.xda-developers.com/showthread.php?t=594615
2. Extract the file
3. Rename "zipalign_apks" file as "zipalign_apks.sh" and past it into your "/system" folder using root explorer
4. Then put Zipalign file to "/system/bin" folder using root explorer
5. Get the Scripmanager from Market and navigate to "/system" folder, run the zipalign_apks.sh file as root
6.Done
7. My log shows AIME.apk is zipaligned rest all other apps are already zipaligned
knzo's init.d script with zipalign binary is a lot simpler IMO.
Using ROM toolbox does the same thing...
Agreed, one advantage I found here is we can edit the script to zipalign "/system/app" folder applications, once zipaligned then we can remove all these files and save useful memory. It is not required to run zipalign on every boot. Also now new market apps have already been zipaligned hence it is a one time process IMO.
i believe most if not all apps are zipaligned.
anyway i run the steps as in OP
and pretty surprise to see below apps are not yet zip-aligned...
com.tf.thinkdroid.amarket-1.apk
com.mactiontech.X5EA-1.apk
com.cootek.smartinputv5-1.apk
com.cootek.smartinputv5.language.chs-1.apk
sweetpotatoz said:
i believe most if not all apps are zipaligned.
anyway i run the steps as in OP
and pretty surprise to see below apps are not yet zip-aligned...
com.tf.thinkdroid.amarket-1.apk
com.mactiontech.X5EA-1.apk
com.cootek.smartinputv5-1.apk
com.cootek.smartinputv5.language.chs-1.apk
Click to expand...
Click to collapse
1. Can You please post the log file in the "/data" folder.
2. Also, in the script change the "/data/app" to "system/app" and run the script again, you will find that now system files are being zip aligned.
3. I will try this on my P500 and get back to you with my findings.Thanks
i have some questions guys:
1) how do i know if all work?(now i'm a little problem with setcpu but i do not knovw if it's a problem of script..sometimes setcpu open itself in 15-20 seconds..)
2)how can darky_zipalign zipalign if in my phone i`ve not zipalign binari?
3)i see that in the set of my phone
94tweaks
95touch
96vm_management
97internet tweaks
do not set anything ... I checked the files modified with echo, and no
respects the values of tweaks
any idea?
ive got raphael kernel i don t know how script work
in init.d if they work with busybox in /sbin or /system
/xbin or in other way ive symlinked all applet in /system/xbin
but not in /sbin with the busybox of kernel...
if someone tell me how script work i can understend
what is the problem
Hi i just created this zip to install init.d on our phone (G530H)
For those who dont know what is the "init.d" its just a folder on the system where you can put some scripts and will run everytime you start the phone, its usefull to clean some cache, get better performance, zipalign etc. theres a lot of scripts on the web but i dont have time to test all of them so, heres a zip to install this folder, it includes the zipalign binary, tested and fully working, you can also google some scripts, test them and share the results with us
Flash it on cwm or twrp and enjoy
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Humberto.Ortega said:
To run init.d scripts you need a custom kernel that support it or enable it on stock kernel. Without these changes , you will just have a new folder in your system...
Click to expand...
Click to collapse
then... How do this worked?
Dam7lc said:
then... How do this worked?
Click to expand...
Click to collapse
I think this flashable zip has already enabled init.d support in stock kernel. I searched how to enable this support and I found we have to install the file "install-recovery.sh" in system/etc. I download your zip file and I saw that this file is present...
So this zip file doesn´t contains only script, but enable the init.d support for the stock kernel :highfive:
We can check this in /data/local/tmp...there should be a txt file there named "init.d_log_test.txt"
Sorry my mistake
I'll flash it and report later....
Thanks man!!
PLEASE MAKE ONE FOR G530P to enable gsm
To my speculations it seems the g530p is no different from the g530 variants p/h/t/t1 and the others as they all have the same qualcomm baseband but as the cdma feature is enable and the others are lock can you gather a team and make this possible to create a baseband or modem that edit these fields and enable gsm/umts or any other bands to work globally as well as the init.rd
thanks
Finally got to rooting my S7, it seems MM only supports systemless root (since CF, SuperSU, only roots in systemless mode, i dont mind)
i have several questions i would like help with
firstly, su/su.d folder i presume holds scripts that are to run on boot, i cant seem to get these to work, ive created a su.d folder in /system and the scripts would work, is there any reason why su/su.d scripts dont work?
secondly, where should i install my busybox? i see su/bin, su/xbin, system/bin and system/xbin are all viable options, is there an advantage over another?
thirdly, when i get system/su.d scripts working and install xposed, they stop working on boot, so im left with no boot up scripts.
any help would be greatly appreciated :good:
For a working init.d support by this method you have to be rooted with latest SuperSU by Chainfire...
This will work any KitKat device that is rooted with latest SuperSU....
After flashing the below and reboot, you will see a file in /data/initd_test.log confirming that init.d scripts are being executed on boot...
This does not require any busybox..
This will not modify any file but add a folder and a file /system/su.d/init.sh ......
In my opinion this is safe method since it does not modifies any important files...
All scripts in init.d will set to chmod 755 on every boot
Thanks
http://su.chainfire.eu/#updates-sud
https://topjohnwu.github.io/Magisk/guides.html#boot-scripts
Thanks for this! :good: