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.
      • flohackF Offline
        flohack
        last edited by

        We know there is a problem with Pixel 2, only Pixel 2 XL seems to work at this time. I will take down the config for walleye. And yes, I need debug assistances, it would involve using telnet adb and ssh, to see where we are in the boot process, also using boots with the volumen and power buttons multiple times, using fastboot boot to temporarily boot a kernel etc.
        If some of you can help with this I can give some instructions maybe

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

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

          @flohack I have experience with ssh and adb. Telnet would be new to me. I don't have much experience beyond flashing Android ROMs, but I would like to help where I can.

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

            @bifpowers Ok in which timezone you are in?

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

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

              @flohack I'm in Eastern Time. I should have some time tomorrow evening to troubleshoot.

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

                @bifpowers Ok I will write up some explanations for you later πŸ™‚

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

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

                  Alright here are some generic steps to see where we are:

                  1. Check that kernel actually boots correctly:
                  • On your host, enter dmesg -w and then power up the device
                  • connect your USB cable. See if the host sees a new USB device
                  • IF there are any messages about RNDIS coming up, try to ping 192.168.2.15 or 10.15.19.82 and eventually try either telnet on 192.168.2.15 or ssh (with user phablet) on 10.15.19.82

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

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

                    @flohack Unfortunately I'm not getting anything from any of those steps. I'm on Windows 10 currently, and tried with both PowerShell and WSL Ubuntu.

                    1 Reply Last reply Reply Quote 0
                    • J Offline
                      Jay Ajit Mate
                      last edited by Jay Ajit Mate

                      I'm on arch linux and using the appimage installer. It gets stuck on "preparing system image/mounting partitions'
                      tried using an ubuntu vm -same problem

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

                        HOLY CRAP!
                        I did not see that this devicetree uses 2 kernel configs for each device. I only patched the one for XL. I push now some changes to add also muskie.

                        Can someone in roughly 24hrs from now try again to install Pixel 2? I bet its working then πŸ˜‰

                        BR Florian

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

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

                          @flohack best email I've gotten all week! Will give it a shot.

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

                            Here is the instruction how to flash:

                            • Download https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fwalleye-taimen/job/main/lastSuccessfulBuild/artifact/halium-boot_walleye.img and flash this with fastboot flash boot halium-boot_walleye.img

                            Good Luck!

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

                            1 Reply Last reply Reply Quote 0
                            • I Offline
                              i2097i
                              last edited by i2097i

                              @flohack

                              I am unable to get past the recovery step. Everything seems to work, I reboot to recovery and I can interact with the UBports recovery mode interface but it never continues from that point. Any ideas?

                              Update: It seems to hang on the

                              Preparing system image
                              Mounting partitions...
                              

                              section after the reboot to recovery (screenshot attached).

                              It could be that I am not giving it enough time so I am going to leave it throughout the night. Here is the verbose output of my UBPorts session:

                              ...
                              info: Downloading 8 files
                              info: Downloaded file 1 of 8
                              info: Downloaded file 2 of 8
                              info: Downloaded file 3 of 8
                              info: Downloaded file 4 of 8
                              info: Downloaded file 5 of 8
                              info: Downloaded file 6 of 8
                              info: Downloaded file 7 of 8
                              info: Downloaded file 8 of 8
                              verbose: running core action write
                              verbose: running adb action wait
                              verbose: running adb action preparesystemimage
                              
                              

                              Thanks!

                              Screenshot from 2021-09-02 23-45-23.png

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

                                Pixel 2 does not boot into UI anyways, I would ask you to wait a bit until we can get this sorted out finally. If you like, you can help debugging it maybe, if you are ok with using adb and fastboot directly.

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

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

                                  Ok guys lets try a different approach. Can you please enter fastboot, flash that image into boot: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc with fastboot flash boot boot.img - so far so old.
                                  Now: DO NOT reboot, but select Boot to recovery. Does this bring up our UT recovery screen?

                                  Thanks!

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

                                  I 1 Reply Last reply Reply Quote 0
                                  • I Offline
                                    i2097i @flohack
                                    last edited by

                                    @flohack

                                    • Booted to fastboot

                                    • ran fastboot flash boot boot.img with this img

                                    I am not sure what is meant by DO NOT reboot, but select Boot to recovery. After running the fastboot command should I just use volume up/down to make the recovery reboot option be visible? Not sure if it is supposed to do something at that point.

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

                                      @i2097i Yes exactly, select manually the recovery option.

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

                                      I 1 Reply Last reply Reply Quote 0
                                      • I Offline
                                        i2097i @flohack
                                        last edited by i2097i

                                        @Flohack
                                        yes, if I press the power button on recovery, it boots to UBPorts Recovery.

                                        I also wanted to mention that I let this run all night and it was still on the verbose: running adb action preparesystemimage when I woke up this morning.

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

                                          @i2097i Oh yes please dont do that, to not damage your display if its not turned off by recovery πŸ˜‰ - the install will not take longer than a few minutes, otherwise its broken πŸ™‚
                                          Ok but good to hear, we have a working recovery...

                                          So actually the kernel is fine. Can you do the following then:

                                          • Boot into recovery
                                          • Check with adb devices that you can see the device
                                          • use adb shell to gain shell access into the recovery
                                          • Issue a mount data that should get userdata online
                                          • Do a ls -la /data and paste the result here

                                          Thanks!

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

                                          I 1 Reply Last reply Reply Quote 1
                                          • I Offline
                                            i2097i @flohack
                                            last edited by

                                            @Flohack The screen does turn off after a certain amount of time so my display is all good!

                                            Here is the output:

                                            : adb shell
                                            root@walleye:/ # ^C                                                                                                                                                                          
                                            130|root@walleye:/ # pwd
                                            /
                                            root@walleye:/ # ls -la /data
                                            total 0
                                            drwxr-xr-x  2 root root 0 1970-01-01 00:00 .
                                            drwxr-xr-x 24 root root 0 1973-04-20 00:54 ..
                                            root@walleye:/ # 
                                            

                                            /data is empty it seems.

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

                                              @i2097i Did you mount data? can you check with simply typing mount ? Its unlikely that it is fully empty

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

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