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

    No way to use the UBPorts installer on a Nexus 4

    Scheduled Pinned Locked Moved Google Nexus 4
    16 Posts 6 Posters 1.4k Views 2 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.
      • flohackF Offline
        flohack
        last edited by

        @lool_lauris said in No way to use the UBPorts installer on a Nexus 4:

        35M 4.1M 31M 12% /cache

        I can see it already, cache is much too small: 35M 4.1M 31M 12% /cache - UBuntu Touch needs a cache partition of at least 500MB to install correctly.

        Probably one of your alternative OSes has repartitioned the sd card. You could try to restore a factory image from Google, that should bring things again in order.

        My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

        lool_laurisL 1 Reply Last reply Reply Quote 0
        • lool_laurisL Offline
          lool_lauris @flohack
          last edited by

          @flohack
          Thank you for your help Flohack.
          And do you think that flashing a stock ROM will resize the cache?
          I found this => https://androidmtk.com/download-google-nexus-stock-rom-models
          Would you know which firmware to choose between 4.4.2 (JDQ39) ... 5.1.1 (LMY48T) ?

          I'm a bit suspicious, I had a bad experience with a Nexus 5 on which I had installed several OSes (including UT) and when I handed over an official stock ROM, the phone became a brick.
          :confused_face:

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

            @lool_lauris Never used any myself but there are plenty of tools on XDA Developers for nexus 4 just had a quick look. Google should have the stock rom for your device available somewhere if your not sure of the source of others.

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

              Hi @lool_lauris
              First of all use the stock image from the official website:

              https://developers.google.com/android/images

              I do not own a N4 but I do have a N5, I guess that it is the same procedure.

              Download the latest build for your phone model.

              Download Fastboot and ADB to your pc, I am linux user and have no experience with Windows or Mac.

              Put your phone in fastboot, vol down and power button.

              Connect your phone with usb cable, and make sure that it really works, there have been alot of wonky installs because of bad usb cables.

              In terminal check if your pc detects the phone:

              fastboot devices

              On pc open Downloads.

              Right click on”occam-lmy48t-factory-c43c7cfd.zip” and click on Extract here.

              Open ”occam-lmy48t-factory-c43c7cfd” folder.

              Right click the flash-all.sh script, click on Properties, under Permission tab, tick the checkbox for:
              Make file executable
              Close this window.

              Right click on an empty spot in the folder, in the menu click ”Open terminal here” and run the flash-all.sh script. It resets the phone to default with partitions and all:

              ./flash-all.sh

              It have been a while since I did this myself on my N5 so there might be a few missing steps like recovery mode. If there is such request press vol up or vol down on phone until it says Recovery, then press Power button to change to Recovery mode.

              I guess you should be able to unbrick your N5 the same way. As long as your pc detects the phone.

              And just what @Lakotaubp wrote earlier there are great tools over at XDA developers site to help you out too.

              4 Google Pixel 3A
              1 Google Nexus 6P
              2 Google Nexus 5
              2 Pinephones
              2 Sony Xperia X

              lool_laurisL 1 Reply Last reply Reply Quote 0
              • libremaxL Offline
                libremax
                last edited by

                Google image for Nexus 4 are here : https://developers.google.com/android/images#occam

                Donate anonymously 1€/$ by year to UBports, all Ubuntu Touch users can do it ! Demonstration:
                https://forums.ubports.com/topic/1262/donate-anonymously-1-by-year-to-ubports-all-ubuntu-touch-users-can-do-it-demonstration/

                1 Reply Last reply Reply Quote 0
                • lool_laurisL Offline
                  lool_lauris @Rondarius
                  last edited by

                  @rondarius and all
                  Thank you all for your messages.

                  I must point out that I am also a confirmed Linux user and that I've been using ADB (and fastboot) for quite a while now. I'm sure, however, that I still have a lot to learn (the more I know, the more I can measure the extent of my ignorance).

                  I know these manips pretty well (those described in the Rondarius's post) because I've already practiced them quite a few times. And thanks for the link to the official stock Rom; I compared the checksum with what I've already downloaded and they are identical. But, you're right, you should always retrieve the data from the sources without going through an intermediary.

                  But my question is not about the procedure to be applied to flash the phone. What worries me is that apparently the partitioning of this Nexus 4 has been modified; and I fear possible problems when flashing the official rom stock without having made certain prior arrangements. I had a bad experience with a Nexus 5 that is currently bricked (I'm not desperate to bring it back to life...).

                  Do you think that flashing the google Rom will restore the original partitioning?

                  flohackF 1 Reply Last reply Reply Quote 0
                  • flohackF Offline
                    flohack @lool_lauris
                    last edited by

                    @lool_lauris Yes the partitions should be updated by the stock ROM, and even if not you cannot brick it, it wont just work as expected, in this case there are ways to repartition to the original layout 🙂

                    My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                    lool_laurisL 1 Reply Last reply Reply Quote 0
                    • lool_laurisL Offline
                      lool_lauris @flohack
                      last edited by

                      @flohack
                      Many thanks for your reply.

                      I put the problem on hold for now. Indeed, I lent the phone that is under /e/ to someone who needed it.
                      Thank you all for your interventions.

                      1 Reply Last reply Reply Quote 0
                      • flohackF Offline
                        flohack
                        last edited by

                        Just an update: It seems that a factory flash does indeed NOT restore partition layout. So, you would have to google how to get the original partition table back on your device. Somehow /e/ or a different ROM seems to have messed with that automatically...

                        My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                        lool_laurisL 1 Reply Last reply Reply Quote 0
                        • lool_laurisL Offline
                          lool_lauris @flohack
                          last edited by

                          @flohack
                          Thank you for this clarification; that's what I was presenting. I've already done quite a bit of research concerning a return to the original partitions. I also have this problem with a Nexus 5 that I've been trying to bring back to life for quite some time now...

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