Re: OTA Updates not working
After cleaning up a bit, there is only one branch (master) left on Gitlab, which already includes the anbox patches (for the case, it gets available for arm64 some time).
This is the latest bootimage, where I confirmed myself, that OTA updates work again:
Thats look good.
Linux ubuntu-phablet 4.9.112-perf+ #1 SMP PREEMPT Mon Jan 18 19:48:19 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
I didnt know that via OTA I will not get a new kernel. I'm sorry for that.
In my case, after UT reboot to finish the lastest OTA update, my phone don't want boot to UT again. My FP3 reboot always on fastboot mode.
@purplecroc89 did you change the release channel in update settings?
@luksus i'm still on default channel "developpement". Do i have to change for "candidate" channel ?
@purplecroc89 No, you don't have to and should not change. Channel-Switch is causing a full-update, which currently results in an unbootable device, that is why I was asking.
Did prior OTA-Updates work for you?
Can you boot manually into the recovery?
If you don't want to investigate this further, just try to flash the latest (master) boot and system image from gitlab again:
And give the OTA update another try.
@luksus I don't now if prior OTA updates works, it's the first time i install UT on my FP3 since OTA updates works. I have try to boot manually on recovery mode but dosn't work. I have the message "error!" with android logo. After UT installation if i lock bootloader, i can't boot on the OS. Do you now if it's normal ?
@purplecroc89 uhhh, I never relocked my bootloader, because I wan't to be able to flash the device again, in case something went wrong.
And without a working android, we are not able to unlock the bootloader again, as far as I know... Please corect me if I am wrong.
So I would not recommend to lock the bootloader to you either.
So if you got the time:
Please unlock it again.
Flash the images I linked above.
Do not lock the bootloader.
Try an OTA update.
And if that works, perhaps try to lock the bootaloader again and give the OTA another try...
Keneda last edited by
Why would anyone want to lock bootloader?
Let it wide opened...
@keneda you have to consider the context.
We are in a development environment and afaik there is no way to lock/unlock it without wiping the data partition.
I am even not sure if one needs to do the oem unlock with some code again. Where would you enter the code on ubports?
But I also have to clarify, that I did not experiment a lot with locking and unlocking the bootloader.
So I would be more than happy, If another person could do this for me .
I also think, that this is a general ubports/halium(?) issue/discussion.
@luksus I think you don't need to have Android to unlock bootloader. Without Android you can unlock bootloader with this adb command : "fastboot flashing unlock" and to lock fastboot "fastboot flashing lock".
@luksus Ok, so i try again to install UT with images you give me in link.
I can boot on recovery manually. Just after installation i download and install lastest OTA update and after reboot, boot on UT again is impossible.
i don't know if i'm doing something wrong
@purplecroc89 Does not sound wrong to me.
What exactly is happening?
Does it automatically reboot to the recovery, when you hit "reboot & install" and do you see the the ubports mascot with a text "installing update"?
Or does it immediately fail to install the update?
What is displayed on the screen?
@luksus When i hit reboot After OTA update download is finish, device reboot automatically on recovery and UBports logo appears with the message "installing update". After that device reboot and it reboot automatically on bootloader again and again.
@purplecroc89 ok, that sounds like the error I encountered, when doing a full update.
What is happening here, is that the updater script formats the system partition and then reinstalls ubports on it. But that formatting somehow breaks something on the partition so, that the next reboot in the current slot fails, and the phone immediately reboots to the other slot, hoping there would be a bootable os...
Can you tell me, which size the downloaded update has? If it is something abourt 500MB it is a full update.
If it is lower, 100-250MB, it is an incremental update.
Perhaps there is triggered a fullupdate even without channel-switch.
@Purplecroc89 I rebuild the system image, that you can flash the current ubports dev version:
Then you could try another OTA Update tomorrow.
If you want to keep a working OS on your phone, just flash both slots:
fastboot flash system_a system.img
fastboot flash system_b system.img
- do the same for the bootimage
Then on a failed OTA, the system should boot after automatically switching to the other slot.
And for Reference:
Switching the active slot:
Checking, which slot is active:
fastboot getvar slot-active:a
@luksus The downloaded update size something like 560Mb.
@purplecroc89 Ok, then it is a full update and currently expected not to work until I solved this issue:
@luksus Ok, so, with yours steps and with dev system image version, latest OTA update work and i can use my phone normally. Thank a lot for your time and your help !