Unable to update to 20.04 OTA-4 stable from 20.04 OTA-3 stable

dln949

I have 20.04 OTA-3 stable running just fine - as far as I know - on a Pixel 3A.

I decided to immediately, manually update to OTA-4. But it refuses to update, I always end up with the message, "Already up-to-date".

Why is it refusing to update? What should I do?

Here is terminal output:

phablet@ubuntu-phablet:~$ sudo system-image-cli -v -p 0 --progress dots
[systemimage] Jan 30 22:28:09 2024 (6376) running state machine [20.04/arm64/android9plus/stable/sargo]
[systemimage] Jan 30 22:28:09 2024 (6376) Looking for blacklist: https://system-image.ubports.com/gpg/blacklist.tar.xz
[systemimage] Jan 30 22:28:09 2024 (6376) [0x78c049eb20] Requesting group download:
	https://system-image.ubports.com/gpg/blacklist.tar.xz -> /var/lib/system-image/keyring.tar.xz
	https://system-image.ubports.com/gpg/blacklist.tar.xz.asc -> /var/lib/system-image/keyring.tar.xz.asc

[systemimage] Jan 30 22:28:09 2024 (6376) Allow GSM? No
[systemimage] Jan 30 22:28:09 2024 (6376) [/com/lomiri/applications/download/39e2c564a13b49be82f75804ff8cfe33] Running group download reactor
[systemimage] Jan 30 22:28:09 2024 (6376) self: <LDMDownloadManager at 0x78c049eb20>, self._iface: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0x78c04c0590> :1.129 /com/lomiri/applications/download/39e2c564a13b49be82f75804ff8cfe33 at 0x78c03b4190> implementing 'com.lomiri.applications.GroupDownload' at 0x78c03b4370>
[systemimage] Jan 30 22:28:10 2024 (6376) [/com/lomiri/applications/download/39e2c564a13b49be82f75804ff8cfe33] Group download reactor done
[systemimage] Jan 30 22:28:10 2024 (6376) Local blacklist file: /var/lib/system-image/blacklist.tar.xz
[systemimage] Jan 30 22:28:10 2024 (6376) Looking for: https://system-image.ubports.com/channels.json
[systemimage] Jan 30 22:28:10 2024 (6376) [0x78c04b84c0] Requesting group download:
	https://system-image.ubports.com/channels.json -> /tmp/system-image-_jyctn7e/channels.json
	https://system-image.ubports.com/channels.json.asc -> /tmp/system-image-_jyctn7e/channels.json.asc

[systemimage] Jan 30 22:28:10 2024 (6376) Allow GSM? No
[systemimage] Jan 30 22:28:10 2024 (6376) [/com/lomiri/applications/download/ebce2ebe7ec14b3184b73df60d231358] Running group download reactor
[systemimage] Jan 30 22:28:10 2024 (6376) self: <LDMDownloadManager at 0x78c04b84c0>, self._iface: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0x78c04c0590> :1.129 /com/lomiri/applications/download/ebce2ebe7ec14b3184b73df60d231358 at 0x78c03a2b20> implementing 'com.lomiri.applications.GroupDownload' at 0x78c049e040>
...
.
.
[systemimage] Jan 30 22:28:11 2024 (6376) [/com/lomiri/applications/download/ebce2ebe7ec14b3184b73df60d231358] Group download reactor done
[systemimage] Jan 30 22:28:11 2024 (6376) Local channels file: /tmp/system-image-_jyctn7e/channels.json
[systemimage] Jan 30 22:28:11 2024 (6376) got channel: 20.04/arm64/android9plus/stable
[systemimage] Jan 30 22:28:11 2024 (6376) found channel/device entry: 20.04/arm64/android9plus/stable/sargo
[systemimage] Jan 30 22:28:11 2024 (6376) [0x78c04b84c0] Requesting group download:
	https://system-image.ubports.com/20.04/arm64/android9plus/stable/sargo/index.json -> /tmp/system-image-_jyctn7e/index.json
	https://system-image.ubports.com/20.04/arm64/android9plus/stable/sargo/index.json.asc -> /tmp/system-image-_jyctn7e/index.json.asc

[systemimage] Jan 30 22:28:11 2024 (6376) Allow GSM? No
[systemimage] Jan 30 22:28:11 2024 (6376) [/com/lomiri/applications/download/d40d6ceba5684d1f9cba44d89c12fcfa] Running group download reactor
[systemimage] Jan 30 22:28:11 2024 (6376) self: <LDMDownloadManager at 0x78c04b84c0>, self._iface: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0x78c04c0590> :1.129 /com/lomiri/applications/download/d40d6ceba5684d1f9cba44d89c12fcfa at 0x78c03a2b20> implementing 'com.lomiri.applications.GroupDownload' at 0x78c03a2fa0>
.
.
.
.
[systemimage] Jan 30 22:28:11 2024 (6376) [/com/lomiri/applications/download/d40d6ceba5684d1f9cba44d89c12fcfa] Group download reactor done
[systemimage] Jan 30 22:28:11 2024 (6376) Already up-to-date
[systemimage] Jan 30 22:28:11 2024 (6376) state machine finished
phablet@ubuntu-phablet:~$

Lakotaubp

@dln949 Keep trying it will arrive soon https://forums.ubports.com/topic/9783/focal-20-04-ota-4-available-now

dln949

@Lakotaubp Thanks.

I assumed that if the instructions were provided in the blog posting, that meant all was ready and available. Is that assumption incorrect?

Moem

@dln949 The blog post also said:

OTA-4 will become available for the following supported Ubuntu Touch devices over the next days

domubpkm

For those who want OTA-4 right away, the easiest way is to use the UBports installer (without wipe data) .

dln949

@Moem said in Unable to update to 20.04 OTA-4 stable from 20.04 OTA-3 stable:

@dln949 The blog post also said:

OTA-4 will become available for the following supported Ubuntu Touch devices over the next days

But, this is the part of the blog post that made me think otherwise (bold emphasis added by me):

"If however you would like to receive the update immediately, turn on ADB access and issue the following command over adb shell :

sudo system-image-cli -v -p 0 --progress dots"

But, I guess "immediately" really doesn't mean "immediately"? Sincere question, not trying to be snarky, I just want to understand, and more importantly to be sure there isn't something wrong with my device.

Moem

@dln949 said in Unable to update to 20.04 OTA-4 stable from 20.04 OTA-3 stable:

But, I guess "immediately" really doesn't mean "immediately"

Hum ho, no, you're right... that is unclear, it seems that it should not say that. Immediately normally means: right this moment.
And as far as I know, while the update is being rolled out, the only way to get it immediately is by reflashing with the installer (while making sure the 'wipe data' box is unticked).

arubislander

@dln949 said in Unable to update to 20.04 OTA-4 stable from 20.04 OTA-3 stable:

But, I guess "immediately" really doesn't mean "immediately"? Sincere question, not trying to be snarky, I just want to understand, and more importantly to be sure there isn't something wrong with my device.

You confusion is warranted. There seems to be something amiss with the way this update is being made available. Normally you should be able to immediately get it with the commands mentioned in the blog post. But for some reason this is not the case.

As suggested, and if you are eager to, try applying it through the installer, without ticking wipe. Also please report back how it goes. We will then be better able to advise others in a similar situation, until the situation can be rectified.

zubozrout

@arubislander That is interesting though because as you say that command should work. I believe it used to work to be able to skip that queue and it worked the same way as installing from the installer. Or is that not the case?

MrT10001

@zubozrout It seems to be working. I have manually updated my ASUS Zenfone from the adb shell and my Pixel 3aXL did it automatically!

And..... just done my Redmi 9 pro....

My Oneplus 5, 5T, 6 and 6T aren't updating yet, but I also cannot connect through ADB.

kugiigi

This is a second hand info but apparently, the update roll out was indeed not triggered but it is now. This is probably the reason of all this confusions
This is just a one time thing though so it's still safe to say once the blog is published, the update rollout is in effect already

MrT10001

Just done my OP5 through the installer.... It works....

OP6T done through installer... It works...

Still surprised, both devices get picked up by windows, but not ADB in terminal!

dln949

It worked today, I was able to update my phone with the command.