>> Yes, fastboot is working after holding volume down on reboot. >> But what is it good for without having any kernel image (or source) to flash >> or boot? > > Good point. Though you should be able to flash the system image this way > which might allow you to replace gecko/gaia.
Sounds good, but my main problem now is that I have two devices one of which is bricked (since I accidentally did a "fastboot flash" instead of a "fastboot boot"). So I need a way to get the boot image off the working phone, on which I don't have any permission to. >> Heck it's not even documented which kernel configuration to use in case >> alcatel would publish anything: >> flo, otoro, unagi, inari, keon, peak, leo, hamachi, helix, wasabi, fugu, >> tarako, tara, dolphin, pandaboard, vixen, flatfish, ... <-- which one? > > I don't think we have an entry for it yet. Is it a JB-based device? You > might build a working gecko using the 'flame' device (note, not the > 'flame-kk'). Naturally, if you build this way don't try to flash > anything else besides gecko/gaia. JB as in Jelly Bean? I think yes. At least the entries in /system/build.prop point to Android 4.3: ... ro.build.version.sdk=18 ro.build.version.codename=REL ro.build.version.release=4.3 ... ro.product.brand=qcom ro.product.name=msm8610 ro.product.device=msm8610 ro.product.board=MSM8610 ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ...
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
