Originally Posted by Robin M
Yeah, I came to the same conclusion about the init.d not being set up properly on the original (slightly modified) rom. I didn't really understand that stock phone roms are not set up to handle init.d scripts. Here is my init.rc file. Are you able to verify the problem and fix it?
Stock ROM does not have init.d support and it looks like that ROM has init.d support added differently. Normally one would include this in init.rc to support init.d
service userinit /system/xbin/busybox run-parts /system/etc/init.d
but this rom init.rc has init.d support added with
//.....A lot of code inbetween........
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Now according to my knowledge this should be ok, too and Trickster MOD CWM script would detect this and do not add another conflicting entry to run init.d. As I only have a GSM GNex, I can't test this ROM to be sure. Do you have a nandroid back up before applying my mod so we can check whether init.d works or not on that ROM? To do so you can create a file with following contents in /etc/init.d
echo "init.d works" > /data/media/checkinitd
chmod 666 /data/media/checkinitd
Then you need to set this file permission as 755 or rwxr-xr-x (same thing, just different conventions)
If after boot you see the file checkinitd with "init.d works" as content then that's my derp and I will try to fix it, otherwise it's the ROM dev's derp, and you will have to take it up to him.
Finally if all of this is over your head, just install a kernel with init.d support built in as I said in my previous post.
P.S. This init.rc you got, is it after you installed my MOD or before (you did nandroid restore)?
Originally Posted by Juiced718
Why don't I have screen and fast charge mods anymore? I flashed redemption rom and pbj kernel is that why? I don't get why that would be but if you can enlighten me I'd appreciate it
Yeah that should be why. AFAIK that kernel is nearly stock so you won't find anything fancy in it.