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.7k 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.
      • 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
                  • I Offline
                    i2097i @flohack
                    last edited by

                    @Flohack

                    My bad - I did not run mount data. Now adb shell is just hanging. Is there some where that I can see logging for this?

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

                      @i2097i No, adb is a very quiet protocol - try unplug/replug and reconnect

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

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

                        @i2097i Or do you mean the mount command does not finish?

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

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

                          @Flohack

                          this is the general gist of what I am doing:

                          adb reboot recovery && adb wait-for-recovery && adb shell "mount data" && adb shell "ls -la /data"
                          

                          I haven't been able to get any adb commands to run on the device itself (adb devices works)

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

                            @i2097i Just try to get adb shell working to get an interactive shell

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

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

                              @Flohack same issue - I'm going to factory restore this device and try again. I'll post my findings asap.

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

                                @i2097i a simple adb shell should never get stuck, yes do that plz. And use an Android 9 image maybe to flash a few system partitions with the right version πŸ˜‰

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

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

                                  @Flohack Yeah, the hanging of adb shell is likely on my end somehow. I am going to try a different cable along with rebuilding.

                                  Yeah, I'll have to get these partitions cleaned up πŸ‘ . I've been using the last Pie update PQ3A.190801.002 (5670241) to refresh.

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

                                    @i2097i I agree thats the one I would have taken too

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

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

                                      @flohack I was able to boot into that image and list the data partition:

                                      agates@risa ~/D/ubports> fastboot flash boot boot_2021-09-03.img
                                      Sending 'boot_a' (32768 KB)                        OKAY [  0.777s]
                                      Writing 'boot_a'                                   OKAY [  0.155s]
                                      Finished. Total time: 0.937s
                                      agates@risa ~/D/ubports> adb devices
                                      * daemon not running; starting now at tcp:5037
                                      * daemon started successfully
                                      List of devices attached
                                      FA79F1A09215    recovery
                                      
                                      agates@risa ~/D/ubports> adb shell
                                      root@walleye:/ # mount /data
                                      root@walleye:/ # ls -lh /data
                                      total 2.0K
                                      drwx------ 4 root root 4.0K 1972-09-14 01:27 android-data
                                      root@walleye:/ # mount
                                      rootfs on / type rootfs (rw)
                                      tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=1853348k,nr_inodes=463337,mode=755)
                                      devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
                                      proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
                                      sysfs on /sys type sysfs (rw,relatime)
                                      tmpfs on /mnt type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1853348k,nr_inodes=463337,mode=755,gid=1000)
                                      none on /acct type cgroup (rw,relatime,cpuacct)
                                      tmpfs on /tmp type tmpfs (rw,relatime,size=1853348k,nr_inodes=463337)
                                      tmpfs on /storage type tmpfs (rw,relatime,size=1853348k,nr_inodes=463337,mode=050,gid=1028)
                                      pstore on /sys/fs/pstore type pstore (rw,relatime)
                                      none on /config type configfs (rw,relatime)
                                      adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
                                      /dev/block/sda45 on /cache type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)
                                      /dev/block/sda45 on /data type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)
                                      
                                      1 Reply Last reply Reply Quote 1
                                      • flohackF Offline
                                        flohack @flohack
                                        last edited by

                                        @flohack Ok perfect so data is empty currently. Can you please just boot into normal boot, and then try to do telnet 192.168.2.15 after lets say 20 secs on the Google logo? Thanks!

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

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

                                          @flohack No change in behavior πŸ˜•

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

                                            @agates ok can you check on your host what dmesg gives you, any mention of an RNDIS adapter coming up when booted normally?

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

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

                                              Oh and please see again in recovery if you can also mount system partition (mount /system_root could do it). And whats inside there...

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

                                              A 1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post