AOSP Part 1 (A New Hope)

---

This is a think tank for making 2nd init load aosp based roms. It currently loads only init.rc. Attached below is the zip file I have made of where I currently stand with 2nd init. Please only download it if you want to help fix it. It probably doesnt work yet.

2nd init is further than the attached in this build (This is a full CM build) The script that is currently being hammered out is mot_boot_mode inside of /system/bin/ Also note that I have made the update script work in the build.

http://www.multiupload.com/4QG0NHCRG7

Hope this is what you needed:

http://www.multiupload.com/X0GM6Q60S3

Here ya go extracted boot.img from cm7-atrix nightly


rename it to .tgz as it wouldnt let me upload that lol

This is the ramdisk uncompressed did you need the kernel as well?

Nope, no need for the kernel. Checking those files now.

Edit: That was exactly what I needed, thanks!

K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.

Good luck, this community can be secretive @ times

I suspect this thread will gradually decline like the other so i if can suggest, change the title to status update. And continue to update the top post with the newest info. And a mod might wanna move it to general but i personal think it should be here as it is an active dev project.

I think in this way maybe we can start to have a public dev conversation and perhaps pool efforts from others that have similar goals. I know of a few others that are tackling the same issues for different purposes.

Seems the ways things are set up here it discourages anything but releases in the dev section. Perhaps its time for a dev q&a forum lol ...

Allot of things make our situation unique which draws allot of blank stares in the general dev forums.

EDIT:
Yay 200th post lol

Originally Posted by aceoyame

K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.

Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?

Originally Posted by mastafunk

Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?

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.

aceoyame: You might benefit from getting in touch with RevNumbers, he does nightlies for the CM 4 Droid X w/ Gingerbread Kernel, so he has a lot of experience with 2nd-init and how to make it work.

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

2nd init is maintained for supported devices. As for contacting revnumbers... I already was in contact with him lol. I worked with him on the D2G for a lot of things. Really our best contact would be to see if CVPCS can figure out what we need to do exactly. All we need to do is expand that task set but I myself am not sure how it works just yet. If you look in that shell script it calls on the task set and copies init.rc into /system/etc/rootfs. Seems like we need to make ALL of the files for our hijack zip copy into there. Right now the atrix ramdisk should be enough to boot at least. We just need to get it loaded lol. Oh and I don't think CM team actually maintains the Hijack zips, I think they pull it from a seperate repo. But it is maintained for supported devices.