UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. wynn1212
    W
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 19
    • Groups 0

    wynn1212

    @wynn1212

    7
    Reputation
    3
    Profile views
    19
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    wynn1212 Unfollow Follow

    Best posts made by wynn1212

    • RE: Install with ubports installer resulted in having a debug kernel

      @fubuntu
      To Clarify
      FP4 comes with anti rollback protection and it will only trigger if your bootloader is LOCKED.
      If your bootloader is UNLOCKED, then anti rollback protection is ignored

      From what you read in the /e/OS installation instructions

      Caution: The FP4 comes with an anti-rollback feature. (...) If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.

      That is true if you try to relock your bootloader, as in the detail of /e/OS installation instructions caution section

      • Rollback protection errors trigger if you install an update whose version number is LESS than the rollback index’s value stored on device.
      • (...)
      • Rollback protection errors are FATAL when the bootloader is LOCKED.
      • Rollback protection errors are IGNORED when the bootloader is UNLOCKED.

      In short, if you unlock your bootloader and downgrad your FP4, you won’t trigger anti-rollback protection as long as you don’t relock the bootloader.

      Also, you cannot relock your bootloader with Ubuntu Touch installed anyway.

      @Keneda It's safe to downgrae FP4 to FPOS11 as long as you don't relock your bootloader. My FP4 came with FPOS13 from the factory, and I successfully downgraded to FPOS11 and install Ubuntu Touch in April 2024. Just DON'T relock your bootloader, as the FP4 will reset get_unlock_ability to 0 after the first FPOS11 boot. If you accidentally relock your bootloader with get_unlock_ability: 0, then there is no way to unlock your bootloader again.

      If you want to retain get_unlock_ability: 1 after the downgrade, just don't boot FPOS afterwards. (Source: https://forum.fairphone.com/t/how-do-i-obtain-get-unlock-ability-set-to-1-on-an-unlocked-fairphone-4/105018/4)

      posted in Fairphone 4
      W
      wynn1212
    • RE: To install Lomiri

      As of 4/25, you can now try Lomiri with Ubuntu 24.04 LTS on Ubuntu Unity
      They have testing iso for Ubuntu Lomiri 24.04 LTS and comes with installer.

      I'm now switch my Surface Go 3 tablet from Debian Sid to Ubuntu Lomiri 24.04 LTS

      posted in Lomiri (was Unity8)
      W
      wynn1212
    • RE: Install with ubports installer resulted in having a debug kernel

      @Keneda
      It should be the same as described in the /e/OS installation instructions for Fairphone FP5 (Especially in the detail of caution section) and the Manage the Bootloader guide. However, I would suggest asking others who have successfully downgraded their FP5 or conducting further research first, as only the FP4 is available in my country (Sadly the sales representative in my country does not introduce FP5), and I cannot test with the FP5.

      Regarding get_unlock_ability, I can’t confirm if the FP5 also has this issue where get_unlock_ability resets to 0. However, I would recommend checking this after the downgrade.

      posted in Fairphone 4
      W
      wynn1212

    Latest posts made by wynn1212

    • RE: Installer stuck at "Asserting unlocked bootloader variable ..."

      Which platform are you using UBPorts Installer?
      If it's on Linux, try with USB2.0 port or USB 2.0 cable.
      Or try UBPorts Installer on Windows.

      For me, I have the same problem

      stuck at "Asserting unlocked bootloader variable".

      when reflashing Ubuntu Touch on my FP4 via UBPorts Installer on Ubuntu 20.04/22.04. But I'm pretty sure it used to be working when I flashing Ubuntu Touch first time. They must to be the update (maybe kernel, android-tools or fwupd describe here: https://unix.stackexchange.com/questions/684494/fastboot-recognizes-device-but-unable-to-flash-stuck-with-no-output-on-ubuntu/747584#747584) breaks it. After pinpoint down the problem, it seems to be stuck at fastboot command. Since I have already tries different cable, usb ports, etc...

      My solution? by using windows 10/11 to flash Ubuntu Touch via UBPorts Installer. After install the driver, it works out of the box.

      posted in Fairphone 4
      W
      wynn1212
    • RE: Install with ubports installer resulted in having a debug kernel

      @Keneda
      It should be the same as described in the /e/OS installation instructions for Fairphone FP5 (Especially in the detail of caution section) and the Manage the Bootloader guide. However, I would suggest asking others who have successfully downgraded their FP5 or conducting further research first, as only the FP4 is available in my country (Sadly the sales representative in my country does not introduce FP5), and I cannot test with the FP5.

      Regarding get_unlock_ability, I can’t confirm if the FP5 also has this issue where get_unlock_ability resets to 0. However, I would recommend checking this after the downgrade.

      posted in Fairphone 4
      W
      wynn1212
    • RE: Install with ubports installer resulted in having a debug kernel

      @fubuntu
      To Clarify
      FP4 comes with anti rollback protection and it will only trigger if your bootloader is LOCKED.
      If your bootloader is UNLOCKED, then anti rollback protection is ignored

      From what you read in the /e/OS installation instructions

      Caution: The FP4 comes with an anti-rollback feature. (...) If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.

      That is true if you try to relock your bootloader, as in the detail of /e/OS installation instructions caution section

      • Rollback protection errors trigger if you install an update whose version number is LESS than the rollback index’s value stored on device.
      • (...)
      • Rollback protection errors are FATAL when the bootloader is LOCKED.
      • Rollback protection errors are IGNORED when the bootloader is UNLOCKED.

      In short, if you unlock your bootloader and downgrad your FP4, you won’t trigger anti-rollback protection as long as you don’t relock the bootloader.

      Also, you cannot relock your bootloader with Ubuntu Touch installed anyway.

      @Keneda It's safe to downgrae FP4 to FPOS11 as long as you don't relock your bootloader. My FP4 came with FPOS13 from the factory, and I successfully downgraded to FPOS11 and install Ubuntu Touch in April 2024. Just DON'T relock your bootloader, as the FP4 will reset get_unlock_ability to 0 after the first FPOS11 boot. If you accidentally relock your bootloader with get_unlock_ability: 0, then there is no way to unlock your bootloader again.

      If you want to retain get_unlock_ability: 1 after the downgrade, just don't boot FPOS afterwards. (Source: https://forum.fairphone.com/t/how-do-i-obtain-get-unlock-ability-set-to-1-on-an-unlocked-fairphone-4/105018/4)

      posted in Fairphone 4
      W
      wynn1212
    • RE: Update devel pixel3a

      @Bouleetbil said in Update devel pixel3a:

      I find this log into recovery

      Have you modify system partition before the update? (E.G. remount system partition as read-write then do some modification on system partition, install package directly to system without using libertine container)

      posted in Google Pixel 3a/3a XL
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy said in Libertine on Pixel 3a XL?:

      Is there any other workaround to get libertine working?

      As far as I know, there isn't any other workaround to get Libertine working. Your Libertine container crashed when entering the second stage (chroot to container):

      I: Base system installed successfully:
      /usr/sbin/chroot.fakechroot: line 105: 78709 Segmentation fault      env -u FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG= LD_LIBRARY_PATH="$fakechroot_chrot_paths" FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot" "${@:1:$(($fakechroot_chroot_n - 1))}" "${fakechroot_chroot_newroot#$FAKECHROOT_BASE_ORIG}" "${@:$(($fakechroot_chroot_n + 1))}"
      

      I would suggest reflashing the 20.04 stable image via ubports-installer without checking 'Wipe Userdata'. Additionally, you can always change the channel from stable to development or vice versa without losing your data.

      While this operation shouldn't erase your data, it's still recommended to back up your data before flashing. You can use TWRP 3.3.1 to back up your data partition to a USB-C drive. If you need to wipe userdata, you can restore the data partition via TWRP after a clean UT flash. I have already done this on both Fairphone 4 and Pixel 3a.

      If the problem persists after the reflash or channel change, consider restoring back to the factory Android 9.0 image PQ3B.190801.002 and then flashing UT again. After the clean flash, test immediately to see if Libertine works or not, and then decide whether to restore the data partition.

      If Libertine still doesn't work after a clean flash, there may be a bug specific to the Pixel 3a XL. In this case, consider file a bug report to UBports by following the bug reporting process.

      I hope this information helps.

      posted in Support
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy Is this your fresh 20.04 install, or have you upgrade from 16.04 before?
      If you upgraded from 16.04 before, it is recommended to start from fresh due to various changes in 20.04

      posted in Support
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy What is your UT OS Version?

      posted in Support
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy Mine is working fine on both Fairphone 4 and Pixel 3a, maybe try upgrade your UT to latest development channel?

      If problem still persist, maybe try restore back to factory Android 9.0 image PQ3B.190801.002 and flash UT again.

      Here's the result of how should it finished

      Preparing to unpack .../language-pack-gnome-en-base_1%3a20.04+20220818_all.deb ...
      Unpacking language-pack-gnome-en-base (1:20.04+20220818) ...
      Selecting previously unselected package language-pack-gnome-en.
      Preparing to unpack .../language-pack-gnome-en_1%3a20.04+20220818_all.deb ...
      Unpacking language-pack-gnome-en (1:20.04+20220818) ...
      Setting up language-pack-gnome-en (1:20.04+20220818) ...
      Setting up language-pack-gnome-en-base (1:20.04+20220818) ...
      Reading package lists...
      Building dependency tree...
      Reading state information...
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      phablet@ubuntu-phablet:~$
      
      posted in Support
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy Try this in terminal, and output the result here

      phablet@ubuntu-phablet~$ LANG=C libertine-container-manager create -i focal
      
      posted in Support
      W
      wynn1212
    • RE: Libertine on Pixel 3a XL?

      @thedeafenguy While installing container, can you click that container name, click the setting icon on the top-right corner, then click container information to see the installation detail to figure out what went wrong?
      screenshot20240429_214605228.png
      screenshot20240429_214803334.png
      screenshot20240429_214624285.png
      screenshot20240429_214626285.png

      posted in Support
      W
      wynn1212