@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.
@Flohack agree entirely. Hopefully it's a remnant of the past.
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.
@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.
@Flohack same issue - I'm going to factory restore this device and try again. I'll post my findings asap.
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)
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?
@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.
@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.
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.
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!
