• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
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.3k 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.
    • A Offline
      agates @flohack
      last edited by 5 Sept 2021, 23:26

      @flohack Oh also, same usb 3-2 dmesg entries as before.

      1 Reply Last reply Reply Quote 0
      • F Offline
        flohack @agates
        last edited by 6 Sept 2021, 11:22

        @agates Ok thats good, let it bootloop once and then press Vol-Up and hopefully it boots into recovery, then we finally might be able to get hold of a /sys/fs/pstore/console-ramoops log πŸ˜‰

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

        A 1 Reply Last reply 6 Sept 2021, 17:18 Reply Quote 0
        • A Offline
          agates @flohack
          last edited by 6 Sept 2021, 17:18

          @flohack Hmm holding Volume Up during boot drops me into the bootloader with the following error message in yellow:

          ERROR: Operation Denied
          

          Nothing in /sys/fs/pstore/, either

          Maybe I'm pressing Volume Up at the wrong time?

          F 2 Replies Last reply 6 Sept 2021, 17:25 Reply Quote 0
          • F Offline
            flohack @agates
            last edited by 6 Sept 2021, 17:25

            @agates ok bootloader is wrong, try Vol-Down πŸ˜‰

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

            A 1 Reply Last reply 6 Sept 2021, 17:54 Reply Quote 0
            • A Offline
              agates @flohack
              last edited by 6 Sept 2021, 17:54

              @flohack Volume down just goes into the bootloader without the error

              1 Reply Last reply Reply Quote 0
              • F Offline
                flohack @agates
                last edited by 6 Sept 2021, 18:12

                @agates Interesting. Okay we can try the following trick:

                • Flash twrp.img to boot partition
                • Issue fastboot boot boot.img that will make a one-time boot of our bootimage, then reboot into recovery. Thats my last resort to catch this.

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

                A 2 Replies Last reply 6 Sept 2021, 20:42 Reply Quote 0
                • A Offline
                  agates @flohack
                  last edited by 6 Sept 2021, 20:42

                  @flohack OK, that didn't work. I decided to reflash android and re-flash ubports again for a fresh slate.

                  During the ubports installer while it was pushing files I decided to adb shell in and look for console-ramoops. To my surprise, it was there. No idea if it's useful or not.

                  https://pastebin.com/zYAAZGTs

                  1 Reply Last reply Reply Quote 0
                  • I Offline
                    i2097i
                    last edited by 8 Sept 2021, 19:46

                    Sorry for my absence. I currently only have a pixel 2 that is locked by the carrier and effectively useless for unlocking purposes. I was not aware that certain Pixel 2 devices had this. I will jump back in if I can get my hands on an unlock-able Pixel 2.

                    F 1 Reply Last reply 8 Sept 2021, 19:57 Reply Quote 0
                    • F Offline
                      flohack @i2097i
                      last edited by 8 Sept 2021, 19:57

                      @i2097i Oh thats a pity. Yes, some carriers are mega-stupid, and Google happily jumped onto that. It should be forbidden by law.

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

                      I 1 Reply Last reply 8 Sept 2021, 20:15 Reply Quote 1
                      • I Offline
                        i2097i @flohack
                        last edited by 8 Sept 2021, 20:15

                        @Flohack agree entirely. Hopefully it's a remnant of the past.

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          agates @flohack
                          last edited by 8 Sept 2021, 23:56

                          @flohack Any ideas how I might get past this "ERROR: Operation Denied" error? It seems that's what's preventing me from dropping into recovery after the kernel panic, right? and the bootloader erases pstore?

                          1 Reply Last reply Reply Quote 0
                          • F Offline
                            FlashyLinux
                            last edited by FlashyLinux 9 Dec 2021, 17:26 12 Sept 2021, 16:43

                            Walking in fresh to this.

                            I downgraded to Android 9.

                            On Linux Mint I opened the installer with

                            "ubports-installer --f /home/edi/Desktop/walleye.yml"

                            Install looks like it was successful, however the phone reboots to a white screen with the Google logo and an unlocked lock at the bottom.

                            Any suggestions?

                            Thanks all!

                            F 1 Reply Last reply 12 Sept 2021, 18:10 Reply Quote 0
                            • F Offline
                              flohack @FlashyLinux
                              last edited by 12 Sept 2021, 18:10

                              @flashylinux Well we took offline the installer config for walleye as it is not working currently. If you want to help testing thats fine, otherwise you will have to wait until we fix it at some point hopefully.

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

                              F 1 Reply Last reply 12 Sept 2021, 18:14 Reply Quote 0
                              • F Offline
                                flohack
                                last edited by 12 Sept 2021, 18:11

                                I removed the config now also from my first post. Sorry for the inconvenience!

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

                                1 Reply Last reply Reply Quote 0
                                • F Offline
                                  FlashyLinux @flohack
                                  last edited by 12 Sept 2021, 18:14

                                  @flohack I would love to help test! I have some experience with flashing and rooting. So I wouldn't be a complete noob haha.

                                  How can I help?

                                  F 1 Reply Last reply 12 Sept 2021, 18:20 Reply Quote 0
                                  • F Offline
                                    flohack @FlashyLinux
                                    last edited by flohack 12 Sept 2021, 18:20

                                    @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 12 Sept 2021, 18:36 Reply Quote 0
                                    • F Offline
                                      FlashyLinux @flohack
                                      last edited by 12 Sept 2021, 18:36

                                      @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 15 Sept 2021, 01:35

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

                                        F 1 Reply Last reply 15 Sept 2021, 07:09 Reply Quote 0
                                        • F Offline
                                          flohack @FlashyLinux
                                          last edited by 15 Sept 2021, 07:09

                                          @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 15 Sept 2021, 23:26

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

                                            F 1 Reply Last reply 16 Sept 2021, 08:06 Reply Quote 0
                                            52 out of 90
                                            • First post
                                              52/90
                                              Last post