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

    Navigating (enabling developer mode) with broken screen (oneplus 3t)

    Scheduled Pinned Locked Moved Unsolved Support
    29 Posts 5 Posters 6.9k Views 3 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.
      • ToadtoadT Offline
        Toadtoad @doniks
        last edited by

        @doniks
        Ah, I didn't add sbin, /usr/bin, and /usr/sbin to PATH. passwd was in /usr/bin. I changed the password, so I think I'm able to get in. But, it seems like adb isn't even supported on the OP3T, so it seems like a moot point. @joe since you were able to help me navigate to developer mode, do you think you can tell me how to open the terminal with a keyboard, so I could try to setup SSH?

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          joe @Toadtoad
          last edited by

          @Toadtoad
          Once you can be sure that you are past the lock screen:
          UPDATE on this for me for some reason:

          • Hold superkey, and press a number to open any app . e.g. settings, which will prompt for password if locked.
          • Enter password ** For me I now have to press TAB to make the cursor go to the password field.

          You can reach the terminal or any app by pressing:

          • Superkey (this will open the dash)
          • Type in "terminal" , which should search for the app. Then press Enter.
          • You should be in terminal now, and it asks for your password again. Type that in and press Enter.
          • Now will be in the command line
          ToadtoadT 1 Reply Last reply Reply Quote 0
          • ToadtoadT Offline
            Toadtoad @joe
            last edited by Toadtoad

            @joe Okay, I think nearly everything is setup for SSH. The one thing I can confirm isn't working yet is wifi. My network runs on wpa-psk, and I need some way to bring the credentials to the phone. Is this possible through adb shell?

            EDIT: Also, do I need to TAB when opening the terminal before entering my password? Thanks.

            J 1 Reply Last reply Reply Quote 0
            • J Offline
              joe @Toadtoad
              last edited by

              @Toadtoad
              Refer to my first post for the wifi part.
              Under

              [wifi-security]
              auth-alg=open
              group=
              key-mgmt=wpa-psk
              pairwise=
              proto=
              psk=
              

              psk = [your wifi password]

              I think you can copy the settings from another ubuntu machine under
              /etc/NetworkManager/system-connections

              You don't need to TAB for the password in terminal. Also it might vary for the one on the lock screen 😛

              ToadtoadT 1 Reply Last reply Reply Quote 0
              • ToadtoadT Offline
                Toadtoad @joe
                last edited by

                @joe I tried copying the file from my Manjaro machine, replacing the permissions and adding the password, but it didn't seem to work, as I couldn't detect my phone on nmap from another computer on the LAN. I even tried to get into the terminal to use nmcli to connect (https://docs.ubuntu.com/core/en/stacks/network/network-manager/docs/configure-wifi-connections) but it didn't seem to work, either. How can i get my internet connected, and is there any way to verify I'm actually in the terminal? Sorry for how complicated this is getting, and thanks for the help.

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  joe @Toadtoad
                  last edited by

                  @Toadtoad
                  You are setting up via ADB through TWRP?
                  Permissions should be:
                  -rw------- 1 root root
                  And the profile in /data/system-data/etc/NetworkManager/system-connections is the exact name of the wifi SSID.

                  Not sure how you would know if you are in the terminal or not. One way would be to assume you are, then create a file e.g. "touch testfile" . Then go back to TWRP-adb and see if that file exists.

                  ToadtoadT 1 Reply Last reply Reply Quote 0
                  • ToadtoadT Offline
                    Toadtoad @joe
                    last edited by

                    @joe The permissions were -rwxrwxrwx 1 root root, but that should work as well (albeit it could be more secure). The profile has the same name as the SSID.

                    After testing, I don't think I was in the terminal. Should I try reinstalling UBPorts from scratch, and is there an initial setup page that I haven't bypassed that I may be hitting? I'm trying to figure out why I didn't access the terminal. I believe I followed the instructions exactly.

                    C 1 Reply Last reply Reply Quote 0
                    • C Offline
                      Capsia @Toadtoad
                      last edited by

                      @Toadtoad Hi,
                      You can test if you are in the terminal by connecting your headphones,
                      then type:

                      pactl load-module module-loopback
                      

                      Now you should hear your voice from the microphone to the headphones.
                      If it works, make sure to unload the module before unplugging the headphones:

                      pactl unload-module module-loopback
                      

                      If everything worked, you've successfully opened the terminal.
                      (If you run the commands without plugged headphones, your phone will generate strange, loud sounds)

                      ToadtoadT 1 Reply Last reply Reply Quote 1
                      • ToadtoadT Offline
                        Toadtoad @Capsia
                        last edited by

                        @Capsia Okay, based off of that, it seems like I am not in the terminal, unfortunately. Is there anything else I could try?

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