Le 22/01/2014 12:26, Julien Wajsberg a écrit : > Le 21/01/2014 21:00, Brion Vibber a écrit : >> On Tue, Jan 21, 2014 at 11:47 AM, Jan Keromnes <jkerom...@mozilla.com>wrote: >> >>> Same thing bit me, I flashed B2G nightly configured as "inari" on ZTE Open >>> 1.1.0b02 (previously 1.0 upgraded over SD) and the phone is bricked. It >>> boots into a blue "Firefox OS" screen, doesn't respond to fastboot or adb, >>> and the SD upgrade doesn't work anymore... >> >> I'm trying to recover from this same thing currently. >> >> It appears to allow me to do the SD-card upgrade with the 1.1.0B2 "for >> V1.1" build -- not the 1.1.0B2 "for V1.0" build which I originally used to >> update to the official 1.1. >> >> http://www.ztedevices.com/support/smart_phone/b5a2981a-1714-4ac7-89e1-630e93e220f8.html >> >> Since I couldn't get adb working, I had to swap the SD card into a working >> Android phone to copy the file over. >> >> Anyway, I'm now successfully booting back into 1.1 so...I think I'll just >> avoid doing custom builds for a while and work with apps. :) >> > > > If you can do adb, probably it's possible and safer to push only gecko > and gaia (that's what we do internally). > > From the B2G directory, this is "./flash.sh gecko && ./flash.sh gaia". > > That said, maybe some blobs that are in 1.1 are not completely > compatible with the 1.2 code, especially in the graphic subsystem, but I > don't know much more.
I'd emphasize on this adb point, since if you have adb access, you should be able to: (1) block b2g start (2) gather logcat of the reboot loop For (1): adb wait-for-device && adb shell stop b2g For (2): adb wait-for-device && adb logcat | tee reboot.log > > > > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
