User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 Steps to reproduce: To reproduce this problem I shallow_flashed the latest nightly to my Flame running the v18D_nightly_v4 base image. Actual results: Flashing succeeded and then the phone boots into a never-ending black screen. Expected results: Flashing should succeed and then boot up normally.

Confirming. Upgraded from Firefox OS 2.5 20150918150204, Gaia commit 3e9de022, Flame v18D_nightly_v4 base imag to <project name="platform_build" path="build" remote="b2g" revision="8d83715f08b7849f16a0dfc88f78d5c3a89c0a54"> <project name="gaia" path="gaia" remote="mozillaorg" revision="e67d319d0854e32e23210784eb9c4e1b8a025adb"/> <project name="gecko.git" path="gecko" remote="mozillaorg" revision="87995a2eae4c1cc8b099fa5725c3a8672d0b716e"/> http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/2015-09-19-15-02-05-mozilla-central-flame-kk/sources.xml See also bug 1206094 comment 5. Bug 1206092 gets stuck at a later stage (animated fox screen). Bug 1206094 also started earlier.

It's getting stuck at the same stage, when you shallow_flash over a base image you lose the animated fox screen. Where that would normally be for me there is just a black screen.

This has been fixed as of the newest update (Uploaded at 20-Sep-2015 14:04 in the UK).

One update after it was fixed, today's update bricks the Flame again.

To keep the info here updated: Every update so far since "b2g-44.0a1" has been fine. None of these have bricked the Flame.

I think we have a different issue than bricking currently. What is your current result?

The nightly update hasn't bricked my flame for a while although when master became 2.6 I switched to the 2.5 branch so I no longer get nightly updates. It's think safe to consider this fixed.

Nightly will always be on the latest version that we're currently working on so it is expected that we are switched to 2.6; if you want to stay on 2.5, that's a different channel. Thanks for your update. I'll update this bug accordingly.