Closed Bug 1053446 Opened 12 years ago Closed 8 years ago

Can't upgrade/downgrade nightly on Flame

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ivan.enderlin, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:34.0) Gecko/20100101 Firefox/34.0 (Beta/Release) Build ID: 20140813030201 Steps to reproduce: I have installed Firefox OS nightly few days ago on a Flame, the 5th August, commit number d85bbae2, channel “default” but it should print “nightly” I suppose, ID of the version is 20140805160201. I am trying to update the software. Actual results: When looking for a new update, I got a message saying no new update available, while there is (http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame/). Expected results: Updating :-).
Also, as I said in https://bugzilla.mozilla.org/show_bug.cgi?id=908560, I have tried to downgrade by flashing to v123. However it seems to not work. I have: $ ./flash.sh * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached f03f4181 device Partition table... < waiting for device > and nothing happens. Thanks!
I have the same issue with a brand new Flame, I'm stuck to the "partition table" step... nothing happens. I run Debian Jessie. @Ivan Enderlin, do you finally found a solution since two month ?
Had the same issue (getting stuck at `< waiting for device >`) when trying to flash base image v188, on Ubuntu 14.10. Running the script with `sudo` did the trick.
(In reply to contact from comment #3) > Had the same issue (getting stuck at `< waiting for device >`) when trying > to flash base image v188, on Ubuntu 14.10. > > Running the script with `sudo` did the trick. Maybe this should be made public on MDN. On MDN it is written, NOT to use sudo. But in such a way the upgrade or downgrade won't work.
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.