Re: OTA Updates not working
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 !
@keneda if I can steal your phone I can get all the data off your device, thats why a wide-open bootloader is a problem. If you are fine with that, ok
@flohack I think kenedas answer was at least as ironic as yours.
Keneda last edited by Keneda
@keneda oh, ok
@keneda No unfortunately not, an unlocked bootloader allows to flash any open recovery, from which you can just pull all data. Note also that stock Android bootlaoders will wipe the data partition when unlocking to preven this to be too easy.
But for UT locking the bootloader would make it impossible to rescue your data off your device, since we do not use a huge cloud service like Android devices, and people would be very worried if they cannot get access to their data.
Also, in case UT fails for you, the open bootloader is the only way to reinstall without data loss with the installer. its a delicate question. Last, on some devices a locked bootloader will not boot an unsigned OS like UT, comparing that to a builtin certificate, and thats basically a good thing since it would provide a guard against tampering with the OS. But we cannot use that since we cannot sign our images as the vendor does
Keneda last edited by Keneda
What would be the solution? Encrypted partition/device like talked in this thread https://forums.ubports.com/topic/1012/one-method-to-encrypt-home-phablet/33 ?
@keneda Basically we only need to encrypt 2 folders, not whole partitions, that makes booting easier. Yes, that would help, but with a bit of a different concept to make it "UT-compatible".
Keneda last edited by
Ok, thanks for the whole explaination, i'll stick with my wide opened phone untill you (devs) have not better to do than implement encryption ^^
Not a big deal for me.
Thank you very much for bringing UT to FP3. I have been long awaiting for this.
I have downloaded the latest image and successfully flashed to UT.
As soon as I boot to UT, the OTA update starts to download. I tried a few version and the results are as follows:
Version 207: when the phone started to reboot, it showed the failed message and could never be boot to UT again.
Version 208: when the phone started to reboot, it showed that the OTA update was successful. However, it then kept rebooting to fastboot.
Version 211: same result as Version 208
All these sizes were >500MB. Hope these information can help. Thank you.