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

    [Beta] Pixel 2 installer config

    Scheduled Pinned Locked Moved Google Pixel 2/2 XL
    90 Posts 11 Posters 24.4k Views 6 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.
      • flohackF Offline
        flohack @FlashyLinux
        last edited by flohack

        @flashylinux Currently the problem is: Pixel 2 and Pixel 2 XL share the same device tree and kernel. In fact, they are almost identical. Yet we were not able to boot into UI or even telnet mode with the Pixel 2. Something gets stuck with our boot image.

        What you can do is:

        • Wipe your device with TWRP (format userdata to remove encryption, wipe all other partitions as usual)
        • Flash this boot image: https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fwalleye-taimen/job/main/lastSuccessfulBuild/artifact/halium-boot_walleye.img into the active boot slot
        • Flash dtbo and vbmeta from here: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc
        • Note: vbmeta image needs to be flashed with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
        • Reboot the device
        • Observe any activity on your USB on the host: Does any device appear after boot?
        • If not, try to flash twrp into boot, and then make a one-time boot of the boot image, thereby hopefully getting in some way a /sys/fs/pstore/console-ramoops to see whats going wrong

        I never had such troubles with booting our images as on the Pixel 2 😉

        My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

        F 3 Replies Last reply Reply Quote 0
        • F Offline
          FlashyLinux @flohack
          last edited by

          @flohack Okay I will get to work on that.

          Also I didnt mention in my first post. And I didnt see this in the thread but after the install it boots to a "installing updates" screen with the little robot. Afterwards it reboots and gets stuck at the google screen.

          I am able to get to recovery mode. Would the logs from the recovery mode be helpful? I tried to download them but unfortunately, while linux sees the phone I cant access it's file system, so I would have to provide the logs as screenshots.

          1 Reply Last reply Reply Quote 0
          • F Offline
            FlashyLinux @flohack
            last edited by

            @flohack said in [Beta] Pixel 2 installer config:

            Flash dtbo and vbmeta from here: http://twoot.bin.org.in/nextcloud/index.php/apps/files/?dir=/porting/walleye%2C taimen/walleye&fileid=8312

            When I click on this link it asks me to login to nextcloud.

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

              @flashylinux Sorry this is the right link: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc

              My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

              1 Reply Last reply Reply Quote 0
              • F Offline
                FlashyLinux @flohack
                last edited by FlashyLinux

                @flohack

                Not so good news.

                Instead of the being frozen on the boot screen. Now it boot loops.

                Try #1
                Steps
                1. Wiped everything using TWRP
                2. Flashed boot with “halium-boot_walleye.img”
                3. Flashed dtbo with “dtbo.img”
                4. Flashed vbmeta with “vbmeta.img” using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
                5. Rebooted device

                Result – Boot loops

                Try #2
                Steps
                1. Flashed boot with “twrp-3.3.0-0-walleye.img”
                2. One time booted “halium-boot_walleye.img”

                Result – This booted and then restarted and went into TWRP

                I am able to see the device when I boot into TWRP though. Not sure if this is helpful or not.

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

                  @flashylinux Ok can you check after it bootloops if there is anything in /sys/fs/pstore?

                  My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                  F 2 Replies Last reply Reply Quote 0
                  • F Offline
                    FlashyLinux @flohack
                    last edited by

                    @flohack

                    That folder is empty

                    1 Reply Last reply Reply Quote 0
                    • F Offline
                      FlashyLinux @flohack
                      last edited by FlashyLinux

                      @flohack

                      I cant edit posts I guess after so long so I am double posting but.

                      I have not been able to find any file in that directory.

                      Try #1
                      Steps

                      1. Wiped everything using TWRP
                      2. Flashed boot with “halium-boot_walleye.img”
                      3. Flashed dtbo with “dtbo.img”
                      4. Flashed vbmeta with “vbmeta.img” using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
                      5. Rebooted device
                      6. Let Boot loop 3 times
                      7. Booted into bootloader
                      8. One time booted into TWRP

                      Result – Directory empty

                      Try #2
                      Steps

                      1. Flashed boot with “twrp-3.3.0-0-walleye.img”
                      2. One time booted “halium-boot_walleye.img”

                      Result – Directory empty

                      I also noticed I was using boot slot "b" and changed it to "a" to see if that made a difference. DO NOT DO THIS. It would not allow me to boot or flash anything. It wouldn't even finish flashing a factory image. I changed it back to slot "b" and everything was back to normal.

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        RVan
                        last edited by

                        Following...

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          agates
                          last edited by agates

                          @Flohack This page at postmarketOS wiki states some issues with pstore. Is it possible we're facing the same issues?

                          https://wiki.postmarketos.org/wiki/Google_Pixel_2_XL_(google-taimen)

                          EDIT:
                          Also wondering if we need to set clk_ignore_unused=true, though I'm not sure how or if you've already configured that

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

                            @agates Ill take a look. Well idk how to set clk_ignore_unused but I will try to find out.

                            My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              agates @flohack
                              last edited by

                              @flohack Looks like clk_ignore_unused may be needed as a command line boot option, if I'm interpreting this correctly?

                              https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)

                              If there's an easy way I can test that I'd be happy to, though I realize the same chip is used in taimen and not having this issue.

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

                                Some small progress I have a Pixel 2 now in my hands and can reproduce the bootloop 🙂 Probably going to attach a UART serial cable via USB to see whats going on

                                My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

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

                                  @agates Yes indeed adding clock ignore helped. Though now the problem is, will that keep some hardware out of sleep state, and impact battery life?

                                  My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                  A 1 Reply Last reply Reply Quote 1
                                  • A Offline
                                    agates @flohack
                                    last edited by

                                    @flohack Awesome! I guess it will be hard to judge battery life since I haven't used the thing as a daily driver for over a year. I'm eager to try it, though, at least to have a phone to develop apps against.

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

                                      @agates you can try to run this installer config manually with ubports-installer -f walleye.yml - https://github.com/ubports/installer-configs/pull/150

                                      My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸

                                      A 1 Reply Last reply Reply Quote 1
                                      • A Offline
                                        agates @flohack
                                        last edited by

                                        @flohack It's working! Typing from ubports on my pixel 2 now!

                                        Thank you!

                                        KenedaK 1 Reply Last reply Reply Quote 1
                                        • KenedaK Online
                                          Keneda @agates
                                          last edited by

                                          @agates said in [Beta] Pixel 2 installer config:

                                          @flohack It's working! Typing from ubports on my pixel 2 now!

                                          Thank you!

                                          Ubuntu Touch / uTouch
                                          😉

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

                                          A 1 Reply Last reply Reply Quote 0
                                          • A Offline
                                            agates @Keneda
                                            last edited by

                                            @keneda said in [Beta] Pixel 2 installer config:

                                            @agates said in [Beta] Pixel 2 installer config:

                                            @flohack It's working! Typing from ubports on my pixel 2 now!

                                            Thank you!

                                            Ubuntu Touch / uTouch
                                            😉

                                            Ahhh yes, the behavior that drove me away from the community all those years ago: people arguing about the names of things instead of making the experience better for developers

                                            KenedaK flohackF 2 Replies Last reply Reply Quote -1
                                            • KenedaK Online
                                              Keneda @agates
                                              last edited by

                                              @agates
                                              Wow, how can someone feel so bad just because we tell him the right naming of things... ?
                                              Ubports devs themselves remind sometime people here, that ubports is the association that maintain the OS, and not the OS itself , wich is uTouch.
                                              Anyway, sorry hurting your feelings teaching something with kindness.

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

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