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

    Nexus 5 frozen on Google unlock screen

    Scheduled Pinned Locked Moved Support
    5 Posts 2 Posters 378 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.
      • P Offline
        pelican9000
        last edited by

        Have Xubuntu Xenial 16.04 installed on laptop. Downloaded ubports .deb file with dependencies and installed. Have Nexus 5 phone with no personal data on it. Went into developer mode. Got as far as "reboot phone by pressing power and volume". Now the installer does not see the phone. Have tried 3x to manually install. Rebooted 4x. Phone is frozen on BSOD black screen with Google name and open padlock. Tried 2 USB cables. All the installer does is sit at "Waiting for Device." ubports installer ver. 0.8.8 beta. Help!

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

          @pelican9000 First thing I would check is that ADB and Fastboot see the device correctly. If they are ok then we can look elsewhere. One other thing is that if the device was not on stock android the install may fail due to the partitions having being altered.

          P 2 Replies Last reply Reply Quote 0
          • P Offline
            pelican9000 @Lakotaubp
            last edited by

            @lakotaubp The phone is not showing up in Ubuntu as a block device. On Thunar or even in gparted. The device is invisible to the installer and all I get is a black screen with the word Google and an open padlock. Booting and rebooting and restarting the installer have no effect. There is no other screen and how do I get to the fastboot screen or any other screen? Or do I have a brick?

            1 Reply Last reply Reply Quote 0
            • P Offline
              pelican9000 @Lakotaubp
              last edited by

              @lakotaubp forgot to mention the obvious. adb devices in the terminal brings up zilch

              1 Reply Last reply Reply Quote 0
              • P Offline
                pelican9000
                last edited by

                Finally was able to reboot about 20 more times to get to the Android screen and install 2 of the Ubuntu Touch downloaded files. After 6 "Yikes" screens I was able to finally do an update of the parially installed system. Now works fine. This experience wasn't OS/2 but BSD might be easier!

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • First post
                  Last post