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

    No luck installing on my Pixel 2 (walleye)

    Scheduled Pinned Locked Moved Google Pixel 2/2 XL
    59 Posts 9 Posters 21.4k Views 4 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.
    • A Offline
      agates @flohack
      last edited by

      @flohack OK, I flashed TWRP to the boot partition, booted into TWRP, wiped the data partition, then booted into halium-boot_walleye.img directly from fastboot.

      Same result, can't telnet, no console_ramoops file.

      Wondering if I should start from android again for a clean slate?

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

        @agates No I dont think Android is the issue. The symptom seems that the kernel does not boot at all. Thats weird somehow. I will continue digging... ^^

        My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

        1 Reply Last reply Reply Quote 0
        • C Offline
          Contonice
          last edited by

          I repeated @agates's path and got the same result:
          I flashed the latest android 9 using the google site.
          Installed ubports installer on ubuntu computer.
          Downloaded the config walleye.yml for my google pixel 2 and ran the installer with it. Installation was successful. Then flashed halium-boot_walleye.img via fastboot.
          The phone won't boot and hangs on the google logo.
          The /sys/fs/pstore folder is empty.

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

            @contonice oh there is one thing I want to try, please take this boot.img instead of halium-boot: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

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

              @flohack Still no luck here, no console_ramoops found, and same behavior with stuck at google logo.

              Here's the last_kmsg if it helps.

              EDIT: I attempted with both the TWRP+boot method and the ubports installer (modifying the config with that new url for boot.img).

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

                @agates Huh the device has last_kmsg but thats from recovery only. Sad, I will try to flash the walleye kernel on taimen lets see ^^

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

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

                  Guys Pixel 2 is back in the installer, please give it a try πŸ˜‰

                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                  C 1 Reply Last reply Reply Quote 0
                  • C Offline
                    cliffcoggin @flohack
                    last edited by

                    @flohack Which version of the installer please?

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

                      @cliffcoggin 0.8.8 πŸ˜‰

                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                      B 1 Reply Last reply Reply Quote 0
                      • B Offline
                        BifPowers @flohack
                        last edited by

                        @flohack I've successfully installed the OS on the Pixel 2. I'm getting a lot of touchscreen problems though, like double or ghost touches. Shutdown seems to really power off the device though.

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better πŸ’—

                        Register Login
                        • First post
                          Last post