• 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.
    • W Offline
      wilson @flohack
      last edited by 20 Mar 2021, 02:01

      @flohack Similar issue to before, after flashing and executing "adb reboot" the phone boots to the Google logo, sits there for 10-15 seconds, then enters a bootloop that eventually stops after 6-10 times in the bootloader with the message "ERROR: Slot Unbootable: Load Error".

      dmesg -w did seem to see the device, here is a sample of the last few lines of output.

      Device= 1.00
      [ 1873.652354] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [ 1873.652358] usb 1-2: Product: Android
      [ 1873.652361] usb 1-2: Manufacturer: Google
      [ 1873.652363] usb 1-2: SerialNumber: HT7B91A02053
      [ 1928.488153] usb 1-2: USB disconnect, device number 18
      [ 1934.316312] usb 1-2: new high-speed USB device number 19 using xhci_hcd
      [ 1934.466876] usb 1-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.04
      [ 1934.466882] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [ 1934.466885] usb 1-2: Product: AOSP on walleye
      [ 1934.466888] usb 1-2: Manufacturer: Google
      [ 1934.466890] usb 1-2: SerialNumber: HT7B91A02053
      [ 1988.502910] loop: module loaded
      [ 1988.556171] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
      [ 2202.191956] usb 1-2: USB disconnect, device number 19
      [ 2596.561839] usb 1-2: new high-speed USB device number 20 using xhci_hcd
      [ 2596.710679] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
      [ 2596.710686] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [ 2596.710690] usb 1-2: Product: Android
      [ 2596.710693] usb 1-2: Manufacturer: Google
      [ 2596.710695] usb 1-2: SerialNumber: HT7B91A02053
      
      
      F 1 Reply Last reply 20 Mar 2021, 13:37 Reply Quote 0
      • F Offline
        flohack @wilson
        last edited by 20 Mar 2021, 13:37

        @wilson can you please do the following: Boot recovery, rename the file /data/android-rootfs.img to smth .bak or so, and then see if it boots ? If that wont help, also rename rootfs.img to .bak and try again, we need to get to a point where the kernel at least is booted.

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

        W 2 Replies Last reply 20 Mar 2021, 19:02 Reply Quote 0
        • W Offline
          wilson @flohack
          last edited by wilson 20 Mar 2021, 19:02

          @flohack From a fresh Android install renaming the files to .bak boots into Android with no issue.

          1 Reply Last reply Reply Quote 0
          • W Offline
            wilson @flohack
            last edited by 20 Mar 2021, 19:24

            @flohack When I renamed both files to .bak and then followed the steps to flash Ubuntu Touch the phone booted, gave the Google logo for a brief second, then entered the bootloader with the message "ERROR: LoadImageAndAuth Failed: Load Error".

            F 1 Reply Last reply 20 Mar 2021, 23:41 Reply Quote 0
            • F Offline
              flohack @wilson
              last edited by 20 Mar 2021, 23:41

              @wilson Ok no idea. will think how wwe can solve that πŸ™‚

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

              1 Reply Last reply Reply Quote 1
              • A Offline
                agates
                last edited by 28 Mar 2021, 00:36

                Same issue here, can test whenever as it's not my primary device.

                1 Reply Last reply Reply Quote 0
                • F Offline
                  flohack
                  last edited by 2 Jun 2021, 18:25

                  Alright sorry took some time. As 2 XL kinda works now, I want to turn my attention to Pixel 2 again. As I do not own the device I need someone with a bit of curiosity to debug the reboot issue for me, if its still persisting. Please head over to https://forums.ubports.com/topic/6251/beta-pixel-2-installer-config and report me back any new findings.

                  I hope the reboot does not appear anymore πŸ™‚

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

                  L 1 Reply Last reply 5 Jun 2021, 03:44 Reply Quote 0
                  • L Offline
                    ljrichards1066 @flohack
                    last edited by 5 Jun 2021, 03:44

                    @flohack I dusted off my old pixel 2 and gave it a try. After reverting to android 9, I tried the installer from the command line with the new config file. That seemed to work well, going through all of the prompts. Once finished, I got the UB ports avatar and a message stating it was updating. Once finished, it rebooted and got stuck on the Google logo. I let it hang for about 10 minutes and tried two more times with fresh wipes. No luck.

                    F 1 Reply Last reply 5 Jun 2021, 20:16 Reply Quote 0
                    • F Offline
                      flohack @ljrichards1066
                      last edited by 5 Jun 2021, 20:16

                      @ljrichards1066 Alright can you please let it get stuck on the Google screen, and then try either telnet 192.168.2.15 or ssh phablet@10.15.19.82 ? THanks!

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

                      L 1 Reply Last reply 6 Jun 2021, 18:38 Reply Quote 0
                      • L Offline
                        ljrichards1066 @flohack
                        last edited by 6 Jun 2021, 18:38

                        @flohack I tried both commands. Both hang without resolution.

                        4ede7fb7-bb3a-4903-89c0-5b764f89ac8e-image.png 255c9a29-a80e-4b85-8cf3-2b25719e33f7-image.png

                        1 Reply Last reply Reply Quote 0
                        • F Offline
                          flohack
                          last edited by 6 Jun 2021, 21:46

                          Alright, I will think about a debug possibility...

                          What Android was installed before?

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

                          L 1 Reply Last reply 7 Jun 2021, 12:34 Reply Quote 0
                          • L Offline
                            ljrichards1066 @flohack
                            last edited by 7 Jun 2021, 12:34

                            @flohack I had a lineage build based on Android 9 on it. When I get off work today, I can try it from stock android 9 and see if the results are better.

                            F 1 Reply Last reply 7 Jun 2021, 18:07 Reply Quote 0
                            • F Offline
                              flohack @ljrichards1066
                              last edited by 7 Jun 2021, 18:07

                              @ljrichards1066 It should not matter actually. Are you familiar with fastboot and adb? I have some manual debug steps

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

                              L 1 Reply Last reply 7 Jun 2021, 18:38 Reply Quote 0
                              • L Offline
                                ljrichards1066 @flohack
                                last edited by 7 Jun 2021, 18:38

                                @flohack I've got a working knowledge of it from messing around with rooting and Android roms. I'd certainly be willing to try. πŸ‘

                                1 Reply Last reply Reply Quote 0
                                • A Offline
                                  agates
                                  last edited by agates 6 Jul 2021, 22:04 7 Jun 2021, 22:01

                                  @Flohack I'm able to reproduce what @ljrichards1066 is saying with getting stuck on the Google logo. On first boot I had a ubports "installing update" screen and then it rebooted into this state.

                                  Also have no network connectivity to it, but I'm comfortable with the CLI I'll assist in debugging as needed πŸ™‚

                                  EDIT: FYI I flashed build PQ3A.190801.002 for walleye first, as instructed by the installer.

                                  1 Reply Last reply Reply Quote 0
                                  • F Offline
                                    flohack
                                    last edited by 10 Jun 2021, 19:41

                                    Ok guys can you try the following:

                                    • Let it boot & fail
                                    • Long-press Vol-Down & Power to enter fastboot
                                    • select Recovery with up/down-key and power
                                    • Let it boot into recovery and execute the following command on your host: adb pull /sys/fs/pstore/console-ramoops

                                    Post this file to a pastebin and ping me back πŸ˜‰

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

                                    A 1 Reply Last reply 10 Jun 2021, 22:43 Reply Quote 0
                                    • A Offline
                                      agates @flohack
                                      last edited by 10 Jun 2021, 22:43

                                      @flohack Unfortunately, I don't have /sys/fs/pstore/console-ramoops. The pstore directory is empty πŸ˜•

                                      These were the logs I found, listed in the recovery, however:
                                      last_kmsg
                                      recovery.log
                                      system-image-upgrader.log
                                      ubuntu_updater.log

                                      In addition, rebooting into the recovery is extremely finicky. I had to re-flash the recovery to get in one time, and after the next install I rebooted into it successfully. I'll see if I can reproduce and get the error from the bootloader again.

                                      F 2 Replies Last reply 11 Jun 2021, 10:20 Reply Quote 0
                                      • F Offline
                                        flohack @agates
                                        last edited by 11 Jun 2021, 10:20

                                        @agates Wait a second how did you flash recovery? The device should not even have a recovery partition...

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

                                        A 1 Reply Last reply 11 Jun 2021, 20:10 Reply Quote 0
                                        • F Offline
                                          flohack @agates
                                          last edited by 11 Jun 2021, 10:28

                                          @agates can you boot into recovery (Is it UBports recovery at least?) and then adb shell into it. Can you:

                                          • mount /system_root
                                          • ls -la /system_root, it should have a typical Linux appearance
                                          • ls -la /system_root/var/lib/lxc/android, it should show android-rootfs.img

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

                                          A 1 Reply Last reply 11 Jun 2021, 21:36 Reply Quote 0
                                          • A Offline
                                            agates @flohack
                                            last edited by 11 Jun 2021, 20:10

                                            @flohack Apologies, I'm likely using the wrong term. I used the first part of the ubports installer to install the bootloader etc then quit.

                                            However i was able to reproduce the same behavior without having to do that, also.

                                            F 1 Reply Last reply 12 Jun 2021, 11:51 Reply Quote 0
                                            • First post
                                              Last post