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

    Nexus 5 flash fails; Universal ADB Driver installed - 32-bit Win 7 Pro SP1

    Scheduled Pinned Locked Moved Support
    38 Posts 5 Posters 7.8k 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.
      • R Offline
        RVan
        last edited by RVan

        @Lakotaubp - I am using 64-bit Windows 7 Pro SP1..no sudo. However, I installed Ubuntu 18.04 LTS on this laptop so, it is a dual boot machine, last evening in preparation for more unanticipated issues with this. I guess it's on to Linux!

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

          @rvan use the command window and type adb devices. Soy should see a list with your device on it if not you need to install the right driver (might be the one you didn't ). This might help https://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ found this very quick so not vouching or endorsing etc. etc.

          1 Reply Last reply Reply Quote 0
          • R Offline
            RVan
            last edited by RVan

            @Lakotaubp - No. You are going too far. You must understand the constraints I am working with. I may not be explaining these well.

            The adb utility you referred me to is not installing or, executing properly. I have been trying to use v1.4.3 because, it is stated to be for Android 6+ and this is the version of Android currently on my N5. After answering "Y" to the first to questions after running the executable in Windows (Note this version of the utility only runs, it makes no attempt to install in Program Files.) I see a message stating 0 files copied. This is not correct. I attempted to install adb-setup-1.3 and this worked as desired. (4) files were copied and the installation proceeded as you see in many blogs regarding this topic. Okay. Good to go on the "15 s adb installer" yet, this should be the wrong version as Android 6+ is supposed to use v1.4.3.

            Universal ADB Driver - I navigate to this via the Start menu choice for All Programs. ClockworkMod appears here and a shortcut titled "Start ADB Server" is listed under this. I have both used this shortcut to start the server and chosen not to use it. This is because UBports installer is supposed to start this.

            With the N5 connected to a USB port I see "Android Device" in Device Manager. This says Google Nexus ADB Device beneath it.

            On to UBports installer - I launch it, connect the N5 to the USB port when instructed to do so, N5 enters USB Debugging Mode, I choose "Select device manually" because, I have been unable to locate any setting resembling OEM Unlock in the Developer Options in my N5. Next, I select Nexus 5 from the pull down list and I am ready to install. I press "Install" and then place the N5 in Bootloader mode. Bootloader screen is displayed with this information. I think lock may still be an issue despite my recent progress.

            0_1545547724128_N5BootloaderScreen.jpg

            Still, installation does not proceed. Are you suggesting I boot into Ubuntu, connect my phone to USB then execute the sudo OEM unlock then, resume trying to flash in Windows?

            Edit - I just found this reference discussing unlocking the N5 bootloader.
            https://www.androidcentral.com/unlocking-nexus-5-bootloader

            I do not know if this is correct or definitive.

            I installed SDK Tools earlier today but, I find typing "adb devices" echo's back the message, 'adb' is not recognized as an internal or external command, operable program or batch file. I have no idea how to resolve this issue but, I can tell you I have launched a command prompt window from both my "sdk-tools-windows-4333796" and "sdk-tools-windows-4333796/tools" directories and I obtain the same result.

            I need to determine what is going on with SDK Tools and the v1.4.3 of the 15s adb installer.

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

              @rvan I understand where you are and you need to unlock your device. With windows use their Command Prompt tool (terminal in linux) and with the device connected type start adb then adb devices. That will list your device. Then type fastboot devices you should see your device then fastboot OEM unlock, which should unlock your device. Lastly fastboot reboot. After that if you run fastboot unlock-info it should return true.
              Then just run the installer.
              One way to open the Command Prompt is to go to the adb folder(it will be in downloads) open it right click somewhere blank and choose the option to open here. Think I just used the search box. Good luck

              1 Reply Last reply Reply Quote 0
              • R Offline
                RVan
                last edited by

                Everything I have found indicates unlocking is best done before any other actions are taken with the N5 and requires the SDK and Platform Tools. I have these installed but, discovered they are not consistent versions. Presumably, I am okay with the "unlock the N5 right away" requirement but, I cannot confirm. I suspect this is one of the better threads regarding this subject matter:

                https://forum.xda-developers.com/google-nexus-5/general/guide-nexus-5-how-to-unlock-bootloader-t2507905

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

                  @rvan You only need bother with the Information section, number 1 Unlocking the boot loader. You've done the rest. Same as my post above really.
                  Then you can try installer again.

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    Judderman2
                    last edited by

                    If I can jump in here. I too am having problems with the installer on an N5. After much buggering about, I managed to get it to do the fastboot part, but when it reboots into UBports revovery, the installer fails to detect it. I have run "adb devices" at this point and it is quickly detected and that it is in recovery mode. I wonder if the installer is putting the "./" in the adb commands?
                    I have used three different PCs and installed Ubuntu on one, also several different cables, all to no avail. I fear the installer is the problem.

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

                      @judderman2 what ubports-installer version are you running, and for what OS?

                      Anyway, try to unplug and plug again the phone when you're stuck in that recovery step. Sometimes adb and fastboot fight too much for the same space 🙂

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        Judderman2
                        last edited by

                        Thanks for your reply. Mostly Win10 64, but also Win7 64 and Ubuntu something or other. Yes, have tried unplugging and replugging, still no joy, shame as I'm really looking forward to trying it, so fed up with Googley andwoid. Loved WebOS, it got killed, BlackBerry 10 was decent, it got killed, SailfishOS shows promise, but need to have android apps support, so not ideal; please, someone, spare us all from android

                        advocatuxA 1 Reply Last reply Reply Quote 0
                        • J Offline
                          Judderman2
                          last edited by

                          Installer version 0.1.21-beta

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

                            @judderman2 one pretty common issue with windows is that the necessary tools are not in the user's $PATH. Check that or run the installer with admin powers

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              Judderman2
                              last edited by

                              Always run installer as admin. Fastboot and ADB installed globally, but have also tried putting the path in.

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

                                @judderman2 you can try an older installer version then. This version for example https://github.com/ubports/ubports-installer/releases/download/0.1.12-beta/ubports-installer.0.1.12-beta.exe has a great success rate on windows

                                1 Reply Last reply Reply Quote 0
                                • J Offline
                                  Judderman2
                                  last edited by

                                  ok, thanks, i'll give it a go and get back to you

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

                                    @judderman2 good luck!

                                    1 Reply Last reply Reply Quote 0
                                    • J Offline
                                      Judderman2
                                      last edited by

                                      Nope, same thing, goes through fastboot stage quite quickly (after manual selection, never auto detects), reboots into UBports recovery, but installer doesn't see it. Are files available to flash with fastboot, or is it o different to android that that won't work?

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

                                        @judderman2 is there anything relevant in the installer log?

                                        1 Reply Last reply Reply Quote 0
                                        • J Offline
                                          Judderman2
                                          last edited by

                                          where would they be? Do you mean the recovery logs UBports recovery?

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

                                            @judderman2 nope. I don't really know about windows but it should be somewhere in %APPDATA% (I think).

                                            You can try https://github.com/ubports/ubports-installer/releases/download/0.1.9-beta/ubports-installer.0.1.9-beta.exe as well. That's another version with a high success rate

                                            1 Reply Last reply Reply Quote 0
                                            • J Offline
                                              Judderman2
                                              last edited by

                                              Nah, same result. Many thanks for your time, but I've taken too much up of it, especially so near to Christmas. Maybe someone in the UK would be prepared to flash it for me, for a "consideration"?

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