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

    ADB shell connects to root@m0054:/# instead of voxl2:/$

    VOXL 2
    2
    7
    441
    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
      swickliff
      last edited by 7 Mar 2024, 22:43

      When I try to ADB shell, it accesses root@m0054:/# instead of voxl2:/$
      This root interface does not have any of the voxl bash commands. For instance I couldn't use voxl-inspect-services.

      Screenshot 2024-03-06 173349.png

      I've tried killing and restarting the ADB server, but that did nothing

      lsusb is reading the device as Qualcomm, Inc. KONA-QRD _SN:3C6BFAA2

      A previous forum post had the same issue, they said it was a permissions issue.
      I am not sure what permissions I should try to change. How can I change what ADB shell connects to?

      T 1 Reply Last reply 7 Mar 2024, 23:08 Reply Quote 0
      • T
        tom admin @swickliff
        last edited by 7 Mar 2024, 23:08

        @swickliff It seems as though the voxl-suite hasn't been installed. Can you download and install the latest SDK (1.1.3) from our downloads page? downloads.modalai.com

        S 1 Reply Last reply 8 Mar 2024, 16:39 Reply Quote 0
        • S
          swickliff @tom
          last edited by 8 Mar 2024, 16:39

          @tom

          The SDK install failed to locate the voxl-suite-offline-packages. I used the 1.1.2 release because that is what we currently have on our other Voxl2 boards at the moment. If you think the 1.1.3 release will produce different results I can try that.

          Here's a screenshot of the errors:
          Screenshot 2024-03-08 112648.png

          This board was originally bricked by accident and went through the unbricking guide but had some warnings or errors pop up when the Image was re-flashed. I believe the Image reflash was attempted again but failed.

          T 1 Reply Last reply 8 Mar 2024, 17:03 Reply Quote 0
          • T
            tom admin @swickliff
            last edited by 8 Mar 2024, 17:03

            @swickliff What command did you run to generate the above failure? Are you running ./install.sh from the SDK download dir

            S 1 Reply Last reply 8 Mar 2024, 19:40 Reply Quote 0
            • S
              swickliff @tom
              last edited by 8 Mar 2024, 19:40

              @tom yes, I used ./install.sh from the voxl2_SDK_1.1.2 dir

              T 1 Reply Last reply 8 Mar 2024, 22:54 Reply Quote 0
              • T
                tom admin @swickliff
                last edited by 8 Mar 2024, 22:54

                @swickliff Can you try ./install.sh -w ? That will do a full system wipe in case a partition is corrupt

                S 1 Reply Last reply 12 Mar 2024, 15:55 Reply Quote 0
                • S
                  swickliff @tom
                  last edited by 12 Mar 2024, 15:55

                  @tom That worked! thanks for the help

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