Thanks Meter 415
Join Date: Aug 2011
Location: Undisclosed Swamp Location, FL
Originally Posted by 0vermind
As far as I know, it loads 2nd-init via exec command, which init then loads and does a hijack.killall and KILLS everything in sight, and then remounts /system as whatever it's booting so recovery would become /system. I think that's how it works? It's all so confusing to me.
The implementations i have seen launch second init via a bash hijack or a mount script. The other stuff you describe is a function of second init, and not of any hijack.zip. From searching elsewhere it looks like a hijack.zip is a compressed filesystem for 2ndinit potentialy containing init scripts etc.. but i could be way off..
So this may be beating a dead horse but is there source for our specific 2ndinit?
The answer to why ours functions different has to be in there..
Got it. Research indicates the hijack.zip is cm teams answer to keeping the boot image seperate for device which need 2nd-init it is just the boot filesystem should be similar to the files i posted earlier except for a specific device. The Question i am asking is since 2ndinit is up why not parse those from elsewhere, the nameless series roms limited implementation threw them in /system/etc/rootfs why not pickup from there.. or are you intent with trying to make an official port? Does cm maintain the source for the 2ndinit on supported hardware? If so diffing those to the source for ours should put us in a solid direction as far as a cm port goes...
And for anyone that doesnt know where im coming from im a long time linux dev, but fairly new to android and this is my first android device so be nice