[Beta] Pixel 2 installer config
-
@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 devicesthat you can see the device - use
adb shellto gain shell access into the recovery - Issue a
mount datathat should get userdata online - Do a
ls -la /dataand paste the result here
Thanks!
-
@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:/ #/datais empty it seems. -
@i2097i Did you mount data? can you check with simply typing
mount? Its unlikely that it is fully empty -
My bad - I did not run
mount data. Nowadb shellis just hanging. Is there some where that I can see logging for this? -
@i2097i No, adb is a very quiet protocol - try unplug/replug and reconnect
-
@i2097i Or do you mean the mount command does not finish?
-
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
adbcommands to run on the device itself (adb devicesworks) -
@i2097i Just try to get adb shell working to get an interactive shell
-
@Flohack same issue - I'm going to factory restore this device and try again. I'll post my findings asap.
-
@i2097i a simple
adb shellshould never get stuck, yes do that plz. And use an Android 9 image maybe to flash a few system partitions with the right version -
@Flohack Yeah, the hanging of
adb shellis 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. -
@i2097i I agree thats the one I would have taken too
My languages: 🇦🇹 🇩🇪 🇬🇧 🇺🇸
-
@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) -
@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.15after lets say 20 secs on the Google logo? Thanks! -
@flohack No change in behavior
-
@agates ok can you check on your host what dmesg gives you, any mention of an RNDIS adapter coming up when booted normally?
-
Oh and please see again in recovery if you can also mount system partition (
mount /system_rootcould do it). And whats inside there... -
@flohack said in [Beta] Pixel 2 installer config:
@agates ok can you check on your host what dmesg gives you, any mention of an RNDIS adapter coming up when booted normally?
Here's the dmesg log, from recovery (first disconnect) -> normal reboot -> force reboot into bootloader
agates@risa ~> sudo dmesg --follow-new [73050.471900] usb 3-2: USB disconnect, device number 6 [73182.441061] usb 3-2: new high-speed USB device number 7 using xhci_hcd [73182.589728] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00 [73182.589735] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [73182.589738] usb 3-2: Product: Android [73182.589739] usb 3-2: Manufacturer: Google [73182.589741] usb 3-2: SerialNumber: FA79F1A09215 [73186.703138] usb 3-2: USB disconnect, device number 7 [73212.553220] usb 3-2: new high-speed USB device number 8 using xhci_hcd [73212.702787] usb 3-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.04 [73212.702794] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [73212.702796] usb 3-2: Product: Pixel 2 [73212.702798] usb 3-2: Manufacturer: Google [73212.702799] usb 3-2: SerialNumber: FA79F1A09215 -
@flohack said in [Beta] Pixel 2 installer config:
Oh and please see again in recovery if you can also mount system partition (
mount /system_rootcould do it). And whats inside there...root@walleye:/ # mount /system_root root@walleye:/ # ls -alh /system_root total 58K drwxrwxr-x 24 audio camera 4.0K 2021-08-26 08:03 . drwxr-xr-x 24 root root 0 1972-09-19 23:20 .. drwxr-xr-x 2 root root 4.0K 2021-08-29 06:04 android lrwxrwxrwx 1 root root 13 1972-09-14 01:28 apex -> /android/apex drwxr-xr-x 2 root root 4.0K 1972-09-14 01:28 bin drwxr-xr-x 2 root root 4.0K 2016-04-12 20:14 boot lrwxrwxrwx 1 root root 14 1972-09-14 01:28 cache -> /android/cache lrwxrwxrwx 1 root root 13 1972-09-14 01:28 data -> /android/data drwxr-xr-x 3 root root 4.0K 1972-09-14 01:28 debian drwxr-xr-x 4 root root 4.0K 1972-09-14 01:28 dev drwxr-xr-x 115 root root 4.0K 1972-09-14 01:29 etc lrwxrwxrwx 1 root root 16 1972-09-14 01:28 factory -> /android/factory lrwxrwxrwx 1 root root 17 1972-09-14 01:28 firmware -> /android/firmware drwxr-xr-x 3 root root 4.0K 1972-09-14 01:28 home -rwxr-xr-x 1 root root 9.4K 2021-04-13 21:11 init drwxr-xr-x 20 root root 4.0K 1972-09-14 01:28 lib drwx------ 2 root root 16K 1972-09-14 01:27 lost+found drwxr-xr-x 2 root root 4.0K 2021-08-26 22:22 media lrwxrwxrwx 1 root root 17 1972-09-14 01:28 metadata -> /android/metadata drwxr-xr-x 3 root root 4.0K 1972-09-14 01:28 mnt lrwxrwxrwx 1 root root 12 1972-09-14 01:28 odm -> /android/odm drwxr-xr-x 3 root root 4.0K 1972-09-14 01:28 opt lrwxrwxrwx 1 root root 16 1972-09-14 01:28 persist -> /android/persist drwxr-xr-x 2 root root 4.0K 2016-04-12 20:14 proc lrwxrwxrwx 1 root root 16 1972-09-14 01:28 product -> /android/product drwx------ 2 root root 4.0K 1972-09-14 01:28 root drwxr-xr-x 12 root root 4.0K 1972-09-14 01:28 run drwxr-xr-x 2 root root 4.0K 1972-09-14 01:28 sbin drwxr-xr-x 2 root root 4.0K 2021-08-26 22:22 srv drwxr-xr-x 2 root root 4.0K 2016-02-05 09:48 sys lrwxrwxrwx 1 root root 15 1972-09-14 01:28 system -> /android/system drwxrwxrwt 2 root root 4.0K 2021-08-26 22:32 tmp drwxr-xr-x 2 root root 4.0K 2021-08-29 06:04 userdata drwxr-xr-x 10 root root 4.0K 1972-09-14 01:28 usr drwxrwxr-x 11 audio camera 4.0K 2021-08-26 08:03 var lrwxrwxrwx 1 root root 15 1972-09-14 01:28 vendor -> /android/vendor -
@agates Okay so you got already some potential UT data in your system partition. Please wipe that too, so that data nd system are clean, then the boot should drop into a telnet session on 192.168.2.15
