I don't see why we should backout anything. We know that there's a
dependency on a gecko feature, and people should not expect old geckos
to provide what a newer gaia needs.
What we should do is make gaia more robust to fail gracefully though.
Fabrice
On 11/02/2015 08:57 AM, Naoki Hirata wrote:
> What's the bug number for this? We need to back this out ASAP. We
> don't have any builds since friday.
>
> On Sun, Nov 1, 2015 at 11:38 PM, Reza Akhavan <[email protected]
> <mailto:[email protected]>> wrote:
>
> Sam Foster followed up with me about this on IRC. It's most likely
> related to the l20n changes recently and requiring a newer version
> of Gecko. Sam commented about this on a related thread:
> https://groups.google.com/d/msg/mozilla.dev.fxos/HBZ35qxJCW8/BZE8wba0AQAJ
>
> The tricky thing is if you reset your profile, like I did, then
> developer tools will be disabled, thus making it hard to connect via
> adb. Here's how I got things working again.
>
> CAREFUL: I'm using a dev device and wasn't worried about losing any
> data.
>
> * Download the latest b2g aries build from TaskCluster and unpack
>
> https://tools.taskcluster.net/index/artifacts/#gecko.v2.mozilla-central.latest.b2g/gecko.v2.mozilla-central.latest.b2g.aries-ota-debug
> * Put the device into recovery mode
> o Power down completely
> o Power on and hit volume up/down a bunch of times
> o Choose the "Apply update from ADB" option
> * `$ adb reboot bootloader`
> * Change directories to ~/Downloads/aries/out/target/product/aries/
> o This directory has all the *.img files in it
> * Flash the images manually
> o `$ fastboot flash boot boot.img`
> o `$ fastboot flash userdata userdata.img`
> o `$ fastboot flash system system.img`
> o `$ fastboot flash recovery recovery.img`
> o `$ fastboot erase cache`
> o `$ fastboot reboot`
>
> Happy hacking,
> Reza
>
>
>
> On Sun, Nov 1, 2015 at 7:00 PM, Reza Akhavan <[email protected]
> <mailto:[email protected]>> wrote:
>
> Earlier today I took what's on gaia master and did a `$ make
> reset-gaia`.
>
> Now I seem to be stuck at the second step of the FTU experience
> (screen shot attached). I'm unable to get past this screen and
> since I did a reset, developer mode isn't enabled and I can't
> access the device via adb.
>
> Any suggestions or a known work around?
>
> Thanks,
> Reza
>
>
>
>
>
>
> _______________________________________________
> dev-fxos mailing list
> [email protected] <mailto:[email protected]>
> https://lists.mozilla.org/listinfo/dev-fxos
>
>
>
>
> _______________________________________________
> dev-fxos mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-fxos
>
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
