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

    ADB devices not found on after following "boot camp" on wsl windows 10

    VOXL Flight
    3
    12
    892
    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.
    • rdjarvisR
      rdjarvis
      last edited by

      I followed all instructions in the "boot camp" section and after all updates/installs, kill-server, start-server...etc.
      No ADB devices are visible in wsl.
      VOXL is visible when running ADB Driver 2.0 on the PC, but cannot see devices in wsl.

      Suggestions?

      Thanks,
      RDJ

      tomT 1 Reply Last reply Reply Quote 0
      • tomT
        tom admin @rdjarvis
        last edited by

        @rdjarvis Our resident WSL expert says to do the following:

        In normal windows command prompt (outside of WSDL)

        adb kill-server
        
        adb start-server
        

        then check in WSL

        rdjarvisR 2 Replies Last reply Reply Quote 0
        • rdjarvisR
          rdjarvis @tom
          last edited by

          @tom Ill try that right now!

          1 Reply Last reply Reply Quote 0
          • rdjarvisR
            rdjarvis @tom
            last edited by

            @tom this is what windows command prompt tells me when running "adb kill-server"
            'adb' is not recognized as an internal or external command,
            operable program or batch file.

            tomT 1 Reply Last reply Reply Quote 0
            • tomT
              tom admin @rdjarvis
              last edited by

              @rdjarvis I was under the impression that "VOXL is visible when running ADB Driver 2.0 on the PC" meant you were able to access adb on your normal command prompt

              rdjarvisR 1 Reply Last reply Reply Quote 0
              • rdjarvisR
                rdjarvis @tom
                last edited by

                @tom sorry for the confusion. Here is a screenshot. Screenshot (5).png

                tomT 1 Reply Last reply Reply Quote 0
                • tomT
                  tom admin @rdjarvis
                  last edited by

                  @rdjarvis I'm not familiar with that tool unfortunately, I would follow the instructions here starting with the section titled "How to set up ADB on Microsoft Windows" with the Android SDK installed from https://dl.google.com/android/repository/platform-tools-latest-windows.zip

                  rdjarvisR 1 Reply Last reply Reply Quote 0
                  • rdjarvisR
                    rdjarvis @tom
                    last edited by

                    @tom thank you, I will get started

                    VinnyV 1 Reply Last reply Reply Quote 0
                    • VinnyV
                      Vinny ModalAI Team @rdjarvis
                      last edited by

                      Hi @rdjarvis ,
                      Once you have adb tools installed on your PC, I've successfully used WSL as Tom mentioned only after trying the kill and restart commands in command window/prompt. Sometimes it may take a few tries in the command prompt, but once I get Windows command prompt to see the adb device, WSL always sees it.
                      I cannot speak to other utilities, but command prompt always works for me.
                      I tried the reverse and it doesn't work, so I think some configurations require Windows to see the adb device first before it let's WSL see it.
                      Hope that helps.

                      rdjarvisR 1 Reply Last reply Reply Quote 0
                      • rdjarvisR
                        rdjarvis @Vinny
                        last edited by

                        @Vinny thanks, just got into the office and will start over. I wasnt successful with the ADB platform tools.....yet

                        1 Reply Last reply Reply Quote 0
                        • rdjarvisR
                          rdjarvis
                          last edited by

                          UPDATE
                          ADB Devices are now visible in Windows CMD after I updated the system path in environment variables.

                          Now the fun begins

                          tomT 1 Reply Last reply Reply Quote 0
                          • tomT
                            tom admin @rdjarvis
                            last edited by

                            @rdjarvis Woot! Enjoy!

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