• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
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 13.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 20 Aug 2021, 00:57

      @flohack Unfortunately, I'm getting the same behavior (stuck at white google boot logo).

      Will try to get logs again to see if there's something new.

      F 1 Reply Last reply 20 Aug 2021, 11:24 Reply Quote 0
      • F Offline
        flohack @agates
        last edited by 20 Aug 2021, 11:24

        @agates Can you try to connect with either telnet 192.168.2.15 or ssh phablet@10.15.19.82 when its stuck?

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

        A 1 Reply Last reply 21 Aug 2021, 19:39 Reply Quote 0
        • A Offline
          agates @flohack
          last edited by 21 Aug 2021, 19:39

          @flohack Both fail with network unreachable πŸ˜•

          F 1 Reply Last reply 21 Aug 2021, 19:51 Reply Quote 0
          • F Offline
            flohack @agates
            last edited by 21 Aug 2021, 19:51

            @agates damnit its getting personal. So lets try this:

            • Can you flash TWRP recovery to boot
            • Then, run fastboot boot halium-boot_walleye.img and let it get stuck for lets say 5mins
            • Then, Long-press power to reboot into recovery
            • finally, when TWRP has booted can you enter adb shell and then try to see if that file exists: /sys/fs/pstore/console_ramoops ?

            Thanks!

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

            A 1 Reply Last reply 21 Aug 2021, 21:19 Reply Quote 0
            • A Offline
              agates @flohack
              last edited by agates 21 Aug 2021, 21:19

              @flohack Okay so to be clear, I:

              1. Flashed TWRP to the boot partition:
                fastboot flash boot twrp-3.3.0-0-walleye.img
              2. Booted into the halium boot image directly:
                fastboot boot halium-boot_walleye.img
              3. Waited 10 minutes
              4. Force-rebooted the device, it booted into TWRP
              5. Opened adb shell checking for /sys/fs/pstore/console_ramoops.

              Unfortunately that file isn't there... the pstore directory is empty.

              Here are the images used with sha256sum:
              twrp-3.3.0-0-walleye.img: e7edcfb553b5c9b7ed717b3439c465075ee17b0eb938bafdce511bbea1cc3cd6
              halium-boot_walleye.img: ed82425569e229863e58c17e636a2e341374d796520a478598580cbf9878127c

              F 1 Reply Last reply 21 Aug 2021, 21:44 Reply Quote 0
              • F Offline
                flohack @agates
                last edited by 21 Aug 2021, 21:44

                @agates Alright can you try the same with wiping data partition first? I have a suspicion... Wipe data, and then try telnet 192.168.2.15 again one time, and if this does not come up, try to boot into that recovery again and see for a pstore... πŸ™‚

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

                A 1 Reply Last reply 22 Aug 2021, 04:53 Reply Quote 0
                • A Offline
                  agates @flohack
                  last edited by 22 Aug 2021, 04:53

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

                  F 1 Reply Last reply 22 Aug 2021, 20:02 Reply Quote 0
                  • F Offline
                    flohack @agates
                    last edited by 22 Aug 2021, 20:02

                    @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 27 Aug 2021, 09:52

                      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.

                      F 1 Reply Last reply 29 Aug 2021, 21:41 Reply Quote 0
                      • F Offline
                        flohack @Contonice
                        last edited by 29 Aug 2021, 21:41

                        @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 29 Aug 2021, 22:43 Reply Quote 0
                        • A Offline
                          agates @flohack
                          last edited by agates 29 Aug 2021, 22:43

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

                          F 1 Reply Last reply 30 Aug 2021, 09:16 Reply Quote 0
                          • F Offline
                            flohack @agates
                            last edited by 30 Aug 2021, 09:16

                            @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
                            • F Offline
                              flohack
                              last edited by 8 Nov 2021, 08:33

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

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

                              C 1 Reply Last reply 8 Nov 2021, 18:20 Reply Quote 0
                              • C Offline
                                cliffcoggin @flohack
                                last edited by 8 Nov 2021, 18:20

                                @flohack Which version of the installer please?

                                F 1 Reply Last reply 9 Nov 2021, 12:46 Reply Quote 0
                                • F Offline
                                  flohack @cliffcoggin
                                  last edited by 9 Nov 2021, 12:46

                                  @cliffcoggin 0.8.8 πŸ˜‰

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

                                  B 1 Reply Last reply 13 Nov 2021, 17:01 Reply Quote 0
                                  • B Offline
                                    BifPowers @flohack
                                    last edited by 13 Nov 2021, 17:01

                                    @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
                                    • First post
                                      Last post