You'd end up with a brick? I understand that init.d determines what starts and stops in a Linux kernel based OS, e.g. Android. You delete it, nothing would start probably.
BTW I've done many ROMs recently and not had to touch anything low-level and essential like init.d.
If a ROM includes a kernel that supports init.d scripts, then it will overwrite any existing instance with its own contents.
Unless you know exactly what you're doing, it's best to leave init.d well alone. Back in my Galaxy S2 days I spent many an hour testing and tweaking scripts to optimise the performance for my needs. I know what can happen if you make even a minor error.
Assuming the question was in response to my post previous to it... several times I ended up with a device that either wouldn't boot, or that locked up hard when it did.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.