I am working with the sierra FX30 module, and during some tests to put new image on the module, I entered in the fastboot for the module be recognized like an android device to flash a new image. However, I erased the original kernel and the rootfs and tried to flash a new one, so now when the module is rebooted it boots as an android device and is not listed in the USB/serial list tty/USBx.
Looking for some solutions on documentation, I see that I could do this using the TP1 pin, but I am not finding if this pin is avaiable on FX30 module.
Has anyone had this problem or a right way to recover FX30?
I just did the procedure on a Windows machine, looking at the device manager the FX30 appears as an Android bootloader interface, even putting the TP1 to low. The device manager looks like this:
Hi Gustavo,
What version of software did you load onto the FX30 that caused this issue to occur? Did you build your own kernel image or did you download it from the Source, FX30 or WP8548 section?
Yes, swiflash won’t work. Sorry, I suggested that before I knew the Android Bootloader Interface was coming up. I’m still trying to determine how to resolve this internally.
The problem was solved, an engineer from Sierra in Brazil sent me a rootfs and kernel file that he generated in his machine. So I used fastboot to write these two files and the FX30 restarted successfully and now is working like before.