Thank you. I suppose I was expecting something more "official" than a file hosted on a 3rd party file locker, but if it works I'll be content.
On Tue, 15 Oct 2013 15:51:14 -0700 "平田修樹 (Naoki Hirata)" <[email protected]> wrote: > It's the second link I emailed; here is the link again, courtesy of > Eduardo : > > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > > > > On 10/15/13 1:54 PM, jezra wrote: > > Thank you. It appears that boot.img is not part of the build > > process; only ramdisk.img, userdata.img, and system.img get built. > > How/where do I find the boot.img? > > > > On Tue, 15 Oct 2013 13:36:10 -0700 > > "平田修樹 (Naoki Hirata)" <[email protected]> wrote: > > > >> This should basically do what you want if you create this as a > >> script. If you want to keep your user data, you'll want to just > >> skip/remove the userdata lines. > >> > >> #!/bin/bash > >> echo + using adb to reboot to fastboot mode && > >> adb reboot bootloader > >> > >> echo + Checking to see if we see the device using fastboot && > >> fastboot devices && > >> echo + Flashing cache && > >> fastboot flash cache ramdisk.img && > >> echo + Flashing userdata && > >> fastboot flash userdata userdata.img && > >> echo + Flashing system && > >> fastboot flash system system.img && > >> echo + Flashing boot && > >> fastboot flash boot boot.img && > >> echo + Flashing rebooting the device && > >> fastboot reboot && > >> echo + Done! > >> > >> > >> On 10/15/13 12:50 PM, jezra wrote: > >>> I am using Linux, and I have adb and fastboot installed. > >>> > >>> On Tue, 15 Oct 2013 12:45:11 -0700 > >>> "平田修樹 (Naoki Hirata)" <[email protected]> wrote: > >>> > >>>> I apologize. I wasn't aware that you had not built your own > >>>> images, that was my bad assumption. > >>>> > >>>> Have you installed the android sdk? You will need to do so in > >>>> order to flash the device. > >>>> Also which platform are you using ( Windows, Mac or linux )? > >>>> > >>>> Regards, > >>>> Naoki > >>>> On 10/15/13 12:25 PM, jezra wrote: > >>>>> Presumably, the 'flash.sh' script runs 3 or 4 commands that > >>>>> involve fastboot; and it shouldn't be necessary for beta testers > >>>>> (which is what anyone who purchased a ZTE Open is), to install > >>>>> the full build environment just to use fastboot for flashing > >>>>> images to their device. > >>>>> > >>>>> As I fall within the category of people who don't have the > >>>>> resources for a full build environment, I have downloaded > >>>>> compiled images from a fellow ZTE owner who was kind enough to > >>>>> compile Firefox OS from source. Now that I have these .img > >>>>> files, I would like to know how to use fastboot to install them > >>>>> onto my device. > >>>>> > >>>>> Any instructions for using fastboot would be greatly > >>>>> appreciated. > >>>>> > >>>>> jezra > >>>>> > >>>>> On Tue, 15 Oct 2013 11:03:59 -0700 > >>>>> "平田修樹 (Naoki Hirata)" <[email protected]> wrote: > >>>>> > >>>>>> The script flash.sh in the main repository should flash all the > >>>>>> parts including the boot.img. > >>>>>> ie: <project folder>/flash.sh > >>>>>> > >>>>>> On 10/15/13 11:03 AM, jezra wrote: > >>>>>>> Thank you for the instructions for putting the ZTE Open into > >>>>>>> fastboot mode. If possible, can you also supply the > >>>>>>> instructions for using fastboot to flash compiled B2G images > >>>>>>> onto the ZTE Open? > >>>>>>> > >>>>>>> On Tue, 15 Oct 2013 10:55:41 -0700 > >>>>>>> "平田修樹 (Naoki Hirata)" <[email protected]> wrote: > >>>>>>> > >>>>>>>> https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Hardware_Cheat_codes > >>>>>>>> FYI, Inari refers to the ZTE Open. > >>>>>>>> > >>>>>>>> Doing the vol down+up + power should put you in fastboot > >>>>>>>> mode. This means that the "fastboot" should be able to see > >>>>>>>> the device. ie: fastboot devices > >>>>>>>> > >>>>>>>> If that is the case, then you can flash partition images onto > >>>>>>>> the phone using fastboot. This is what the flash.sh script > >>>>>>>> does. It puts the device in fastboot mode and then flashes > >>>>>>>> the images per fastboot. > >>>>>>>> > >>>>>>>> Chances if you are in fastboot mode then the boot.img that > >>>>>>>> they pointed you to worked. The problem is described by > >>>>>>>> Eduardo on a separate thread: > >>>>>>>> http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html > >>>>>>>> > >>>>>>>> Once you place the boot.img in the proper location, give > >>>>>>>> flash.sh another go. If that still doesn't work please let > >>>>>>>> me know. The other thing we could potentially do is flash > >>>>>>>> just gecko/gaia on the device provided that you can reboot > >>>>>>>> the device and have adb access. This is done by : > >>>>>>>> <project folder>/flash.sh gecko > >>>>>>>> <project folder>/gaia/make reset-gaia > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> Naoki > >>>>>>>> > >>>>>>>> On 10/15/13 10:29 AM, [email protected] wrote: > >>>>>>>>> Michael: Thank you but, it took around 15 e-mails and over > >>>>>>>>> two weeks mailing around with the eBay seller until they > >>>>>>>>> actually understood my problem. They kept pointing me to > >>>>>>>>> the download already discussed in this thread over and over > >>>>>>>>> again, and I had the impression that I was talking to a > >>>>>>>>> wall. As explained, when they finally realized the actual > >>>>>>>>> problem they offered me a new phone for 80% of the initial > >>>>>>>>> price (which is a 20% discount). > >>>>>>>>> > >>>>>>>>> Again, I am not willing to throw an almost completely new > >>>>>>>>> phone (never carried around, no scratches, screen cover not > >>>>>>>>> removed yet etc.) in the trash can and buy a (discounted) > >>>>>>>>> new one just because the firmware is bricked and ZTE > >>>>>>>>> refuses to reflash it. This is the complete opposite of > >>>>>>>>> what I was expecting from a device marketed as developer > >>>>>>>>> phone - not mentioning that it's completely crazy when > >>>>>>>>> looking at it from an ecologic perspective. > >>>>>>>>> > >>>>>>>>> Vinayak: Well, this is as similar to my situation, I assume > >>>>>>>>> you can also access see the device over USB being in > >>>>>>>>> diagnostic mode when you boot it by holding both > >>>>>>>>> voldown+volup + power although the screen remains black? > >>>>>>>>> _______________________________________________ dev-b2g > >>>>>>>>> mailing list [email protected] > >>>>>>>>> https://lists.mozilla.org/listinfo/dev-b2g > >>>>>>>> _______________________________________________ > >>>>>>>> dev-b2g mailing list > >>>>>>>> [email protected] > >>>>>>>> https://lists.mozilla.org/listinfo/dev-b2g > >>>>>> _______________________________________________ > >>>>>> dev-b2g mailing list > >>>>>> [email protected] > >>>>>> https://lists.mozilla.org/listinfo/dev-b2g > >>>> _______________________________________________ > >>>> dev-b2g mailing list > >>>> [email protected] > >>>> https://lists.mozilla.org/listinfo/dev-b2g > >>> _______________________________________________ > >>> dev-b2g mailing list > >>> [email protected] > >>> https://lists.mozilla.org/listinfo/dev-b2g > >> _______________________________________________ > >> dev-b2g mailing list > >> [email protected] > >> https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
