No way to use the UBPorts installer on a Nexus 4

lool_lauris · 28 Jan 2021, 22:11

Hi,

I'm desperately trying to install UT on a Nexus 4 but the installation doesn't succeed, see this post => https://github.com/ubports/ubports-installer/issues/1716
At the end of the failed installation, I stay stuck on the recovery screen.

In November 2019, I also had problems installing via the UBPorts installer. I had managed to get out of it by going through a manual installation => https://forums.ubports.com/topic/3340/solved-nexus-4-impossible-to-install-ut-via-the-ubports-installer-tool/3
At this time it was possible, the images were made available. It's a pity that this manual installation is no longer possible!

I specify that the phone is not bricked, since I installed a TRWP recovery and /e/.

Keneda · 29 Jan 2021, 01:46

@lool_lauris

"Error: [...] No space left on device"

lool_lauris · 29 Jan 2021, 15:21

@keneda
Yes, I saw that, but what should we do?
As I explained, on this phone after trying unsuccessfully to install UT, I installed a TRWP recovery and the rom /e/ and this without any problem, so there is space to install it.
Why can't the installer manage to take the space that exists?

flohack · 29 Jan 2021, 16:21

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

e installer manage to take the space that exists?

The installer cannot repartition your device. It expects to have space in the userdata partition (/data mountpoint) but also in the cache partition (normally mounted in /cache)... You can check that by going into a an adb shell: adb shell on the cmdline of your host. Please report here the output of df.

Keneda · 29 Jan 2021, 17:32

@lool_lauris like explained by @Flohack better than i could ever do, he's dev after all, it's a partition size issue, i guessed that.

Depending on the output the command Flo asked you to enter in an adb shell, you'll have to resize or format some partitions (or maybe unlock something?).

lool_lauris · 29 Jan 2021, 17:53

@flohack
here after the return of df

lool@lool-W510:~$ adb shell
mako:/ $ df -h
Filesystem                                    Size  Used Avail Use% Mounted on
tmpfs                                         914M  476K  913M   1% /dev
tmpfs                                         914M     0  914M   0% /mnt
/dev/block/platform/msm_sdcc.1/by-name/system 828M  797M   31M  97% /system
/dev/block/mmcblk0p22                          35M  4.1M   31M  12% /cache
/dev/block/mmcblk0p23                          13G  460M   12G   4% /data
/dev/block/mmcblk0p1                           64M   44M   20M  70% /firmware
tmpfs                                         914M     0  914M   0% /storage
/dev/fuse                                      13G  460M   12G   4% /storage/emulated
mako:/ $

And also :

mako:/ $ df -a                                                                                              
Filesystem                                    1K-blocks   Used Available Use% Mounted on
rootfs                                                0      0         0   0% /
tmpfs                                            935748    476    935272   1% /dev
devpts                                                0      0         0   0% /dev/pts
proc                                                  0      0         0   0% /proc
sysfs                                                 0      0         0   0% /sys
selinuxfs                                             0      0         0   0% /sys/fs/selinux
debugfs                                               0      0         0   0% /sys/kernel/debug
none                                                  0      0         0   0% /acct
tmpfs                                            935748      0    935748   0% /mnt
none                                                  0      0         0   0% /dev/cpuctl
none                                                  0      0         0   0% /dev/bfqio
/dev/block/platform/msm_sdcc.1/by-name/system    847656 816388     31268  97% /system
/dev/block/mmcblk0p22                             35976   4248     31728  12% /cache
/dev/block/mmcblk0p23                          13549392 471104  13078288   4% /data
/dev/block/mmcblk0p1                              65488  45504     19984  70% /firmware
tmpfs                                            935748      0    935748   0% /storage
/dev/fuse                                      13549392 471104  13078288   4% /storage/emulated
mako:/ $

flohack · 29 Jan 2021, 19:27

@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.

lool_lauris · 29 Jan 2021, 21:19

@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:

Lakotaubp · 30 Jan 2021, 11:16

@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.

Rondarius · 30 Jan 2021, 11:55

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.

libremax · 30 Jan 2021, 12:14

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

lool_lauris · 30 Jan 2021, 15:33

@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?

flohack · 3 Feb 2021, 10:18

@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

lool_lauris · 3 Feb 2021, 10:18

@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.

flohack · 3 Feb 2021, 10:20

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...

lool_lauris · 3 Feb 2021, 11:04

@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...