[Motorola Droid RAZR] Silverlink34:
Hello XDA, I am currently working on a new project, porting Boot 2 Gecko (Firefox OS) to the droid razr. I have no experience in porting, only the determination to be the first person (or team of people) to accomplish this for our device.

A little about myself:

I build CM10, CNA, AOKP and AOSP from source for the droid razr so I have a little experience with such.

I use STS Dev team's android local manifest.

What I have done so far, would like advice if possible:

Read a crap ton about the Firefox OS, I believe that the only requirement it truly has is you need to at least have android 4.0 (ICS) Right now we have jellybean roms functioning on the droid razr, this isn't a problem. The only major issue I can see in this project is that the droid razr has a locked bootloader. I am hoping that SafeStrap that hashcode has developed will overcome this obstacle, but this is only possible if I have a zip to flash, I am pretty sure there isn't a way to flash a boot.img because of our bootloader being locked.

First I cloned the source B2G from mozilla's github.

Then I just took a copy of my system folder from one of my recent ics roms. Figured this was the same as just pulling it directly from the phone.Named this directory 'spyderb2g.'

I then edited the config.sh file within, (this file contains all of the repo sync commands, for each specific device. The porting guide on mozilla asks you to add in your device to this file.) I copied the pandaboard entry and renamed the title to spyder. Pandaboard seemed to be the device that was most closely related to the razr being an omap4 device. This is a possible mistake. Also, while I was in here I edited the repo sync command to have -f for force and -j2 to set the job level.

I have downloaded the pandaboard.xml from mozilla's github and added in some lines from sts's stock cm ics android_local.xml. This part I am little unsure of, I figured since the pandaboard is an omap4 device, it MIGHT get me some where. its a big 'might.' I copied over all the device specifics (local device and local vendor) Renamed the final file to default.xml.

For the device tree, I downloaded this straight from sts's github, since they have an android_device_motorola_spyder repository handy. extracted the contents of this to the same spyderb2g directory, so now this directory contains system (extracted) and the device tree all mixed together. The porting guide was not too specific on where to put this stuff.

Finally, I run this command to see if it will sync and get all the required files.

ANDROIDFS_DIR=spyderb2g ./config.sh spyder default.xml

Here's my output:

Get tmp_manifest_repo
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From tmp_manifest_repo
* [new branch] master -> origin/master
error: Cannot fetch STS-Dev-Team/android_device_motorola_edison
warn: --force-broken, continuing to sync
Fetching projects: 2% (2/95) fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

A little bit of google says that I need to add my SSH public key to github, but I have never had to do this for a build operation. Perhaps I could fork the required repos and then authenticate myself that way..but I feel there is a little more to it than that.

Any advice would be appreciated. Thanks for your time.

Since I have not built this rom yet, I am curious if other developers that have built the rom for other ported devices could inform me if the build.sh outputs a .zip file as well as an .img file.