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

    Sentinel Not connecting over adb

    Ask your questions right here!
    1
    4
    227
    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.
    • S
      SMRazaRizvi
      last edited by 18 Mar 2024, 14:45

      Hello,

      I am trying to connect to my Sentinel drone over the USB, but suddenly it doesn't connect using the adb shell.

      My laptop can see the USB device when I do run lsusb

      Bus 001 Device 016: ID 05c6:900e Qualcomm, Inc. QUSB_BULK_SN:EBC5FC33
      but when I run adb shell it says

      error: no devices/emulators found

      Please help.

      S 1 Reply Last reply 18 Mar 2024, 15:30 Reply Quote 0
      • S
        SMRazaRizvi @SMRazaRizvi
        last edited by 18 Mar 2024, 15:30

        @SMRazaRizvi I even performed the Unbricking steps as mentioned here but the issue persists.

        S 1 Reply Last reply 18 Mar 2024, 15:33 Reply Quote 0
        • S
          SMRazaRizvi @SMRazaRizvi
          last edited by 18 Mar 2024, 15:33

          @SMRazaRizvi The Unbricking, however, was successfull. Below are the last few lines from the output, and at some point inside the output I said [PROGRAM] flashed "system" successfully

          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <log value="INFO: Calling handler for patch" /></data>
          LOG: INFO: Calling handler for patch
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <response value="ACK" rawmode="false" /></data>
          FIREHOSE WRITE: <?xml version="1.0"?>
          <data><setbootablestoragedrive value="1"/></data>
          
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <log value="INFO: Calling handler for setbootablestoragedrive" /></data>
          LOG: INFO: Calling handler for setbootablestoragedrive
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <log value="INFO: Using scheme of value= 1" /></data>
          LOG: INFO: Using scheme of value= 1
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <response value="ACK" rawmode="false" /></data>
          partition 1 is now bootable
          FIREHOSE WRITE: <?xml version="1.0"?>
          <data><power value="reset"/></data>
          
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <log value="INFO: Calling handler for power" /></data>
          LOG: INFO: Calling handler for power
          FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
          <data>
          <response value="ACK" rawmode="false" /></data>
          
          S 1 Reply Last reply 18 Mar 2024, 15:59 Reply Quote 0
          • S
            SMRazaRizvi @SMRazaRizvi
            last edited by 18 Mar 2024, 15:59

            @SMRazaRizvi Issue resolved.
            I connected one of the camera ports in a wrong orientation.

            1 Reply Last reply Reply Quote 0
            1 out of 4
            • First post
              1/4
              Last post
            Powered by NodeBB | Contributors