UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Install with ubports installer resulted in having a debug kernel

    Scheduled Pinned Locked Moved Fairphone 4
    19 Posts 8 Posters 1.1k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • W Offline
        wynn1212 @fubuntu
        last edited by wynn1212

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

        My devices that were powered by Ubuntu Touch
        Fairphone 4 (fp4) 8G/256G - 20.04 Development (main phone)
        Google Pixel 3a (sargo) 4G/64G - 20.04 Stable

        My devices that used Lomiri Desktop
        Surface Go 3 (8G RAM) - Ubuntu 24.04 LTS (By Ubuntu Unity)

        KenedaK Mario.CHM F 3 Replies Last reply Reply Quote 3
        • KenedaK Offline
          Keneda @wynn1212
          last edited by

          @wynn1212
          Thanks for clarifying.
          Is the same applies to FP5 ?

          2015-2023 : Meizu MX4 ☠️⚰️✝️
          2023-2024 : Nexus 5 ☠️⚰️✝️
          2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
          🇲🇫🇬🇧

          W 1 Reply Last reply Reply Quote 0
          • Mario.CHM Offline
            Mario.CH @wynn1212
            last edited by

            Hi @wynn1212,

            Wow ---- Wow => Thank you very much.

            There are very few such fundamental and logical explanations here in the forum. :clapping_hands_light_skin_tone: :thumbs_up_light_skin_tone:

            I simply had to rate you positively. :face_blowing_a_kiss:

            Thanks again.

            Greetings Mario

            📱 Oneplus Nord N100 UT20.40 (OTA5); then Xperia X (since 2020) at last UT 20.04(OTA5), now out of service due to defective camera
            🐎 When you realize you are riding a dead horse, get off!
            My languages skill: 🇨🇭🇦🇹 🇩🇪, and only orally: 🇬🇧 🇹🇭

            1 Reply Last reply Reply Quote 0
            • W Offline
              wynn1212 @Keneda
              last edited by wynn1212

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

              My devices that were powered by Ubuntu Touch
              Fairphone 4 (fp4) 8G/256G - 20.04 Development (main phone)
              Google Pixel 3a (sargo) 4G/64G - 20.04 Stable

              My devices that used Lomiri Desktop
              Surface Go 3 (8G RAM) - Ubuntu 24.04 LTS (By Ubuntu Unity)

              1 Reply Last reply Reply Quote 1
              • F Offline
                fubuntu @wynn1212
                last edited by

                @wynn1212
                Thanks! You might just have kept me from bricking my phone during the next installation attempt.

                1 Reply Last reply Reply Quote 0
                • Mario.CHM Offline
                  Mario.CH @fubuntu
                  last edited by

                  Hi @fubuntu,

                  @fubuntu said in Install with ubports installer resulted in having a debug kernel:

                  But I also read the fairphone support page, and according to it, flashing with fastboot (downgrading included) should be no issue.

                  In my opinion, the “anti-rollback function” is an additional security feature to prevent customers from installing older Android versions on their device that are no longer supplied with further security updates.
                  This would give customers a false sense of security as they would consider their device safe with a locked bootloader.

                  For developers or customers who use their device as AOSP (Android Open Source Project), however, there is still the option of a rollback or installing a different operating system and using it with an open bootloader at their own risk.

                  See also source.android: lock and unlock the bootloader.

                  But I could also misunderstand, nobody is omniscient. 🤔 :grinning_face:

                  Greetings Mario

                  📱 Oneplus Nord N100 UT20.40 (OTA5); then Xperia X (since 2020) at last UT 20.04(OTA5), now out of service due to defective camera
                  🐎 When you realize you are riding a dead horse, get off!
                  My languages skill: 🇨🇭🇦🇹 🇩🇪, and only orally: 🇬🇧 🇹🇭

                  1 Reply Last reply Reply Quote 0
                  • KenedaK Keneda referenced this topic on
                  • F Offline
                    fubuntu @arubislander
                    last edited by

                    @TheVancedGamer
                    What does the maintainer think? Any idea how that debug kernel got installed?

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      TheVancedGamer @fubuntu
                      last edited by

                      @fubuntu Some QCOM drivers seem to use trace_printk(), but honestly it's not something to bawl over, it's perfectly fine fwiw

                      KenedaK 1 Reply Last reply Reply Quote 0
                      • KenedaK Offline
                        Keneda @TheVancedGamer
                        last edited by Keneda

                        @TheVancedGamer

                        Some QCOM drivers seem to use trace_printk()

                        For clarifying, do you mean the android ROM came with this debug kernel because only on debug kernel this driver can use "trace_printk" ?

                        2015-2023 : Meizu MX4 ☠️⚰️✝️
                        2023-2024 : Nexus 5 ☠️⚰️✝️
                        2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
                        🇲🇫🇬🇧

                        1 Reply Last reply Reply Quote 0
                        • flohackF Offline
                          flohack @Keneda
                          last edited by

                          @Keneda Just a few 2 cents her:

                          • Yes for porting we often set the Android build to build a so-called userdebug image. That ensures certain behaivour, but I am unsure if we really need that. So it could be that the FP4 kernel built during our porting build is set to debug since userdebug target is being used.

                          Someone could explore this by trying to build their own port with instructions from porting group and then see which flag is being used. It would be good to finally address this, since debug kernels are potentially slower than release.

                          My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post