On Thu, 17 Oct 2013 01:28:10 -0700 (PDT) Eduardo González <[email protected]> wrote:
> Hi! I'm author of adapted boot image, and is correct is not > recommended use files from third party as file hosted by me, but the > issue about create own boot.img is not so easy. Before talk about > boot.img, is necessary remember that flashing the zte open > using ./flash.sh require fastboot full supported. If you get problems > using flash.sh (as exact messages posted by Sven) then you have a > device without fastboot full supported. In order to enable fastboot > you must update using DEV images from ztedevices.com, for example the > images of UK American Standard or European Standard. Check > https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN > > Next step is use boot image adapted by me as explained on > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > By default, b2g tree do not create boot.img. You must define on > device tree (<b2g_dir>/device) the elements required so kernels is > compiled and generate boot.img. Additionally stock boot.img contain a > kernel using particular modules (zte blobs) not included into b2g > kernel source _______________________________________________ dev-b2g > mailing list [email protected] > https://lists.mozilla.org/listinfo/dev-b2g If the owners of ZTE Opens had a nice easy way to get the latest stable and testing images for their devices (like the geeksphone users have at http://downloads.geeksphone.com/) none of this would be an issue. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
