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:
Related
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
K, I'm rooted, with hasoon's toolkit, have Titanium Backup, I can delete system apps, back them up,..., no problem.
BUT, installing BusyBox is a no go
edit -> still having problems reinstalling busybox - i wrote a script to flash it to the system/xbin folder through cwm, which works, but i can't make the permission for busybox to execute stick after a reboot - whenever i reboot, i have to manually set it to execute in root explorer or it's useless.
Can someone help me write a cwm script to flash busybox to /system/xbin through cwm and make it permanently executable ?
bumping this - need help - anyone ?
edit -> still having problems reinstalling busybox - i wrote a script to flash it to the system/xbin folder through cwm, which works, but i can't make the permission for busybox to execute stick after a reboot - whenever i reboot, i have to manually set it to execute in root explorer or it's useless.
Can someone help me write a cwm script to flash busybox to /system/xbin through cwm and make it permanently executable ?
give this a shot
http://forum.xda-developers.com/showthread.php?t=1772338
Hello!
I use ROM toolbox pro. Today I enabled its zipalign script, but it warn me there's no zipalgn binary installed on my system. When I search on XDA, I found this thread. But it for Drod X2. So I it OK if I push that binary into /system/xbin directory? If it's not good, then how do I find a suitable binary?
Thanks!
probably will work, just don't forget set chmod 755 after pushed to xbin folder
android addicts said:
Hello!
I use ROM toolbox pro. Today I enabled its zipalign script, but it warn me there's no zipalgn binary installed on my system. When I search on XDA, I found this thread. But it for Drod X2. So I it OK if I push that binary into /system/xbin directory? If it's not good, then how do I find a suitable binary?
Thanks!
Click to expand...
Click to collapse
Don't forget to do a cwm backup.....
Sent from my ST18i
init.d zipalign Scripts are pretty much universal I've found.
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: