[Beta] Pixel 2 installer config
-
@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_root
could 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_root
could 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
-
@agates Oh and I forgot one important step, download vbmeta and dtbo image from here: http://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc
and then flash it with:
fastboot flash dtbo dtbo.img fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Thats to ensure you have no error from verity during boot.
-
@flohack Hmmm, well now I'm in a boot loop. At least it's something different :). After the google logo I get a temporary black screen before it reboots.
And I still can't telnet
Both system and data are empty:
root@walleye:/ # ls -alh /data total 0 drwxr-xr-x 2 root root 0 1970-01-01 00:00 . drwxr-xr-x 24 root root 0 1972-09-20 23:41 .. root@walleye:/ # ls -alh /system_root total 0 drwxr-xr-x 2 root root 0 1970-01-01 00:00 . drwxr-xr-x 24 root root 0 1972-09-20 23:41 ..
-
@flohack Oh also, same
usb 3-2
dmesg entries as before. -
@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
-
@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/
, eitherMaybe I'm pressing Volume Up at the wrong time?
-
@agates ok bootloader is wrong, try Vol-Down
-
@flohack Volume down just goes into the bootloader without the error
-
@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.
-
@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.
-
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.
-
@i2097i Oh thats a pity. Yes, some carriers are mega-stupid, and Google happily jumped onto that. It should be forbidden by law.
-
@Flohack agree entirely. Hopefully it's a remnant of the past.
-
@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?
-
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!