UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    adb - no permissions

    Scheduled Pinned Locked Moved Support
    11 Posts 4 Posters 1.3k Views 1 Watching
    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.
      • G Offline
        gmelchett
        last edited by

        Without development mode enabled, "adb devices" does not list any devices.
        When enabling development mode, I'm lacking permissions:

        $ adb devices
        List of devices attached
        06axxxxxxxxx        no permissions;
        

        How do I get permissions? On Android there is this pop-up box, but I've not seen anything like that on ubuntu ports. I'm running 16.04(2018-w39) on a Nexus 5, recently flashed image from the anbox testing thread: https://forums.ubports.com/topic/1676/development-testers-for-anbox

        advocatuxA LakotaubpL S 3 Replies Last reply Reply Quote 0
        • advocatuxA Offline
          advocatux @gmelchett
          last edited by

          @gmelchett hi, I don't know why you're experiencing an issue but the normal behaviour is that the first time you run adb with your device plugged, a pop-up to allow or deny adb shows.

          1 Reply Last reply Reply Quote 1
          • LakotaubpL Offline
            Lakotaubp @gmelchett
            last edited by

            @gmelchett You could try re installing 16.04 with the installer I think that picks up the adb permission for you. So you would be all set to try anbox again remembering it not daily driver ready yet.

            1 Reply Last reply Reply Quote 0
            • G Offline
              gmelchett
              last edited by

              Thanks for your suggestions!
              @advocatux Maybe I did deny adb when trying out something weeks ago..
              @Lakotaubp Hmm.. The installer does "adb -P 5038 shell echo 1" in the background and it looks like you have to have adb working in order to install anything. At least that how it looks to me.

              Would be a bit sad if I had to reflash android first and then ubuntu again, just to be able to enable adb.

              advocatuxA LakotaubpL 2 Replies Last reply Reply Quote 0
              • advocatuxA Offline
                advocatux @gmelchett
                last edited by advocatux

                @gmelchett probably the easier way is to delete the adb keys in your device so you can do that process fresh from the start. You'll find them at /data/misc/adb/adb_keys

                G 1 Reply Last reply Reply Quote 0
                • LakotaubpL Offline
                  Lakotaubp @gmelchett
                  last edited by

                  @gmelchett I ment just run it through the installer again. No need to reinstall android first, but try what @advocatux said first is the best idea.

                  1 Reply Last reply Reply Quote 0
                  • G Offline
                    gmelchett @advocatux
                    last edited by

                    @advocatux Sadly, /data/misc/adb/ is empty

                    advocatuxA 1 Reply Last reply Reply Quote 0
                    • advocatuxA Offline
                      advocatux @gmelchett
                      last edited by

                      @gmelchett if it's empty, that means there aren't keys so shouldn't have any trouble running adb from scratch. Set developer mode on, and while your device screen is unlocked, plug it to your computer.

                      Run adb devices, that will start the adb server and trigger the auth pop-up in your device.

                      Using a good usb cable is also very important. Good luck!

                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        Stefano @gmelchett
                        last edited by

                        @gmelchett type in terminal:

                        sudo adb kill-server

                        Unlpug the phone from PC, then type in terminal

                        sudo adb start-server

                        Plug in the phone.

                        G 1 Reply Last reply Reply Quote 1
                        • G Offline
                          gmelchett @Stefano
                          last edited by

                          @stefano Thanks! running adb with sudo did the trick! Strangely, I've not had to do that with android phones.

                          S 1 Reply Last reply Reply Quote 1
                          • S Offline
                            Stefano @gmelchett
                            last edited by

                            @gmelchett I was having the same issues 🙂

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post