ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    "weird" error response trying to QDL VOLX2 (unbricking)

    VOXL 2
    1
    2
    65
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      brianaustin
      last edited by

      Hello,

      I have tried the web based interface for unbricking my VOXL2 device but no success. It fails on CDT flashing.

      Device shows up in QDL mode
      Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

      I am familiar with using QDL so tried my own install I use for my work devices and this is the output of flashing which I find very strange

      LOG: INFO: benchmark
      LOG: INFO: emmc
      LOG: INFO: ufs
      LOG: INFO: fixgpt
      LOG: INFO: getsha256digest
      LOG: INFO: End of supported functions 15
      LOG: INFO: Calling handler for configure
      LOG: INFO: Storage type set to value UFS
      LOG: INFO: Calling handler for program
      LOG: ERROR: Failed to open the UFS Device slot 0 partition 3
      LOG: ERROR: Failed to open the device:3 slot:0 partition:3 error:0
      LOG: ERROR: OPEN handle NULL and no error, weird 344481268
      LOG: ERROR: Failed to open device, type:UFS, slot:0, lun:3 error:3
      [PROGRAM] failed to setup programming
      
      

      I have never seen this "weird" error before. I get this trying to run the same commands that the python scripts do in the web interface.
      Are there any suggestions on how to proceed to unbrick this unit?

      Thanks,
      Brian

      1 Reply Last reply Reply Quote 0
      • B
        brianaustin
        last edited by

        After trying the web interface as well as command line I am still not able to successfully flash the image. I keep getting the same error above. Regardless of what position the switch is on the device only shows up in QDL mode.

        If there is no other method for force flashing the device (There does not appear to be any physical switch or button other then the one) do I need to submit an RMA?

        This device worked fine and was finally able to get the cameras and everything working and it just stopped allowing adb and not showing up on my Linux PC. bummer

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Powered by NodeBB | Contributors