On Tue, 23 Dec 2014 14:21:37 +0100, dattaz wrote: > update.zip are sign because they go on differente hardward, build for > open c FR have a different signature of a open c EU build > But you right only gecko and gaia are include
Sure, I understand that the hardware is slightly different, but then the hardware for the Flame is much more different than the Open C versions, yet http://paulrouget.com/e/openc/ tells me that the Open C is compatible with the Flame (at least as long as the Flame's Gecko and Gaia builds were based on Jellybean). So I just don't understand why there is this need for separate EU and FR builds of Gecko and Gaia. > Communauty build are based on root build from ZTE, if you can install it > on other build good for you, but you can have bug and brick maybe (some > people how install EU build on a FR phone have this problem) I am using the latest non-root base system from ZTE (which is a bit more up-to-date than the root build), but wouldn't expect there to be any major differences. > I don't thing installation of update from network will work, if you > don't have good build (zte root build, + update.zip after) Yes, but probably only because the update will abort because the build id doesn't match... Christof -- http://cmeerw.org sip:cmeerw at cmeerw.org mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
