Help from devs - extract-files.sh

[Guest RichBayliss]

Hi all,

I am very keen to start creating vanilla builds for my San Fran - but I have come up against some headaches.

After much searching, learning, breaking and more searching I am now thinking that building the entire AOSP from source would be possible for the San Fran if we had the equivilent "extract-files.sh" script that our HTC touting brothers have. For those that don't know, this script is used to extract binary modules/components from an existing device and implant them into a freshly build AOSP build.

I am not a wizard at Linux or Android, but I am learning and trying all the time - but this script has me stumped. I'm sure once we had it, that we could build fresh 2.1 Eclair builds and then as the sources start appearing maybe 2.2 or 2.3. If the current .29 kernels from kalt_kaffe work OK with 2.3 then I'm sure we could get a fresh 2.3 when the sources drop.

What I would appreciate is the help/direction of a wise ROM dev who knows what parts of the 2.1 or 2.2 ROM we need to extract and inject into an AOSP build, then we can create a Git repo to allow other people to build AOSP ROMs to start from. If I could do this myself then I would, I am not lazy, but I cannot find the resources out there to get me on a working path...

So if anyone is willing to help me out, please reply or PM me and we can start the project off - I can maintain it etc, but I just need some help to get started.

Rich

[Guest rjm2k]

This script isnt much of an issue , the rest of the vendor tree is.

[Guest fonix232]

I remember seeing somewhere a how-to-add-your-device-to-the-build-environment (huh that's long ;)) tutorial, I may even google it up again :P

[Guest RichBayliss]

I have followed the instruction on the Android Source project to create a new board/device/product in order to have a profile - but part of that profile is the device-specific binaries/kernel source/etc

This is tree I wish to create, so that others can check out the source, check out our ZTE Blade tree, configure the build env and make - resulting in the 3 images to flash to the phone.

I was under the impression from various tutorials that the "extract-files.sh" would give us all the required parts from an existing build?

[Guest Sebastian404]

I have followed the instruction on the Android Source project to create a new board/device/product in order to have a profile - but part of that profile is the device-specific binaries/kernel source/etc

This is tree I wish to create, so that others can check out the source, check out our ZTE Blade tree, configure the build env and make - resulting in the 3 images to flash to the phone.

I was under the impression from various tutorials that the "extract-files.sh" would give us all the required parts from an existing build?

Getting a AOSP build running on the SF is really easy, but getting the extra hardware to work is the tricky bit, and getting the screen the right way round.

People where working on it, including myself, but having lost my macbook air to a fat ladies drink on the way over here, I'm not going to look at it again till the new year I'm afraid.