brew wants you to specify a directory, where to install
android-platform-tools. If a program doesn’t recognize what you want from it, it will print its usage pattern, to tell you what it expects from you.
Homebrew is a tool from the Mac World. It typically knows exactly where to install programs, @Stefan s guess is wrong here.
Homebrew is an easy way to install the latest android platform tools, e.g. adb and fastboot. If you use a recent Linux desktop, like Ubuntu, you can also install those programs using the apt package manager. Or you install the full android Sdk (a bit overkill).
Remove the dollar from the command.
$brew is now a variable, that is probably not defined in your shell., e.g. empty. So you where actually calling the program ‘install’, therefore the explanation from @Stefan is correct about the usage. What you want is calling the program ‘brew’ with the parameters ‘install android…’.
I managed to install ADB another way by now, but now I’m stuck with the very next step.
I give up. I don’t think it makes a lot of sense to flash a beta OS on a 500€ phone if you have never used the terminal before and need help with every single step…
If someone else however successfully flashes it (with a mac) and is willing to write down how they did it - step by step - I’ll reconsider.
I have just uploaded an updated version of the package that should contains all the necessary in order to flash the phone. I just copied the folder structure of the github of Firefox OS with the necessary scripts and files. Unfortunately, I cannot test it since I do not have a Fairphone 2 and I’m using Ubuntu GNU/linux. Can you try it on MAC OS X?
Reference https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Installing_on_a_mobile_device 1) Decompress the compressed file Fairphone2 Firefox OS xxx.7z into desktop folder (or whatever folder you want) 1) Open the terminal and enter into the build folder decompressed at previous step 2) Install ADB 2a) On OSX. If you have homebrew on OSX: brew install android-platform-tools Otherwise, download the Android Developer Tools and add the binaries to your PATH. 2b) On Ubuntu: sudo apt-get install android-tools-adb 3) Flash your phone: ./flash.sh
Moreover, some developers of Firefox OS are working on a Firefox plug in that should be able to install B2G on a supported device https://bugzilla.mozilla.org/show_bug.cgi?id=1166276. However, this plug in still requires to build the entire system, but it will be simpler than now tailored for end users.
This is the new shared folder where I can add future build without breaking any link https://mega.nz/#F!2UsjWBZY.
For license issue: send me a private message in order to get the decryption key.
Hi erotavlas and thanks for the info, I have a question about your build. Does it use the proprietary blobs as provided by Fairphone on http://code.fairphone.com ? If it does, are you aware of the licensing issues that forbid sharing custom ROMs built with these blobs ?
4 posts were merged into an existing topic: FP2: License for binary blobs
“I embraced OS X as soon as it was available and have never looked back. So a lot of In the Beginning … was the Command Line is now obsolete. I keep meaning to update it, but if I’m honest with myself, I have to say this is unlikely.” Neal Stephenson
Post #11 over there says that the bug is fixed.
I just had a chance to play around with a mac (El captain installed, not mine) & brew. Lastest brew package out of the box lets me connect to a phone with adb (shell, devices), but fastboot is hanging with similar operations. That’s all I can say for now. Not a Mac expert.
Some sites hint modifications, but I cannot try them right now. Also brew feels much cleaner. So maybe it’s best to wait a while until someone fixes this in brew? A bug report would help I guess … if other people have issues as well using fastboot.
All I used for adb/fastboot
brew install android-platform-tools
Update: The phone I was testing with was not taking
adb reboot bootloader well. I used another phone and fastboot on the mac was answering (at least while using ‘
devices or reboot’). So it looks like fastboot on the mac with brew/el captain seems to work.
We (Mozilla) have a workaround for that that we call “blob free builds”. The way it works is that the build doesn’t include any of the non-redistributable bits, but we provide a Firefox Addon (almost ready for public use, follow progress at https://bugzilla.mozilla.org/show_bug.cgi?id=1166276) that extracts the needed blobs from a device connected to the host, and rebuilds locally the images before flashing.
This process has been vetted by our legal team.
Which is exactly why I suggested to use this addon for distributing fp-osos builds as well.
.config: No such file or directory
Could not load .config. Did you run config.sh?
So load-config.sh is not working properly.
I got it running by flashing the img’s manually, however Firefox OS always crashes on me after one minute.
I flashed boot, cache, recovery, system, userdata and splash, maybe that’s not enough?
I just updated the package with a new build. Yes, I forgot the file .config in the previous package since it is an hidden file. Now it should flash correctly.
I do not know why it crashes after a minute. Maybe the cause could be the manual flash even if I do not think so. The only important files are three: boot.img, system.img, recovery.img https://developer.mozilla.org/en-US/Firefox_OS/Building_and_installing_Firefox_OS/Firefox_OS_build_process_summary
Please, try now
Is there a firefox OS build to get someware or even a tutorial how to install?
I read about the licence issue and that someone has a build but i have to PM. Just who?
And are there any known issues with it?
I don’t want to ruin the mood here, but I read somewhere today that “FirefoxOS” (will be moved) "into Tier 3 support " … it that a good or a bad thing? I assume it more or less means that they want to focus more on something else and are just using nice terms to hide it like “attempt to keep the platform working”, but I can be wrong. So please correct me
The flash script didn’t work for me (FP2 not recognized as a supported device), so I flashed the images manually again. No crashes this time, will do some more testing later!
I didn’t yet test or read the source of the flash.sh-script but does it change the partition table / bootloader of the phone? If not, I cannot imagine how you could brick a fairphone. You should always be able to reboot to the bootloader (using the vol - key) and then use fastboot to re-flash Android or something else again?
First many thanks for your work. I tryed to exactly do how described but unfortunately it gives out the same as MaartenD already sayed.
I installed on a Mac with Parallels Ubuntu 14.4LTS.
Can you “talk” to the device in any way? (
adb devices as an example? I’m not sure if Parallels will really work well with USB. Just wondering …).