User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET CLR 1.1.4322; .NET4.0E; BRI/2; rv:11.0) like Gecko Steps to reproduce: I am not sure if this bug is filed under the correct category. I've flashed my Keon Geeksphone with the v123 base image. Actual results: The device became unresponsive. I tried to recover the Keon by removing the battery for ± 30 seconds, reinserting the battery and pressing the volume up and power buttons at the same time. Expected results: The system recovery menu should appear however, the device remained switched off without displaying the recovery menu. Kindly assist.
If I understand correctly, you flashed your Keon with a Flame v123 base image. This is more of a support issue, unless it's an enhancement requests to make the Flame base image builds recognize they're not flashing a flame device. Relevant resources are: - GeeksPhone forums https://forum.geeksphone.com/index.php?board=45.0 - support.mozilla.org: https://support.mozilla.org/, specifically https://support.mozilla.org/en-US/products/firefox-os/fix-problems I think the short answer is that if the device isn't listed in "fastboot devices" when you boot it into fastboot mode (volume down and power button), then the device may be permanently bricked. Do make sure that your system recognizes the USB id of 18d1:d00d first! If it shows up from fastboot, then most existing flash scripts for keon should work fine. Whenever any script invokes "adb reboot bootloader" the device ends up in fastboot mode. I do hope you are able to recover the keon! It's a good little device!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
And note that when I boot my keon into fastboot mode, the screen is black and nothing shows up. Which is different from recovery mode! recovery mode is "volume up and power" and results in an orange screen that has a bunch of options.
Thanks Andrew. I'll let you know should I be able to recover the device.
You need to log in before you can comment on or make changes to this bug.