[Pixel C Android Development] ipdev:
I've been installing from a complete wipe of the device.

fastboot erase boot, system, vendor, recovery, cache and userdata.

Then flash twrp and boot into twrp.

Formate data and reboot into twrp.

Then sideload ROM and/or OpenGApps.

I did go back to using twrp-3.3.1-0-dragon, that seemed to fix the TWRP errors I was getting.

Something in newer ADB and/or TWRP seems to not quite work together on some devices.

If I boot twrp-3.3.1-1-dragon, mount system and then just run ls -la

mb:testing ip$ fastboot boot twrp-3.3.1-1-dragon.img
--- <SNIP> ---
mb:testing ip$ adb shell ls -la
linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
drwxrwxrwt 25 root root 1100 Sep 21 22:08 .
drwxrwxrwt 25 root root 1100 Sep 21 22:08 ..
dr-xr-xr-x 4 root root 0 Sep 21 22:08 acct
lrwxrwxrwx 1 root root 11 Jan 1 1970 bin -> /system/bin
--- <SNIP> ---
-rw-r--r-- 1 root root 65 Jan 1 1970 vndservice_contexts
mb:testing ip$
[CODE][/HIDE]
[I]Sorry for the OT about TWRP.[/I]

[QUOTE="followmsi, post: 80291955, member: 5480152"]
Tested clean install a few times .. never had to reflash boot.img to get it booting .. you may did play with magisk 19.3 ?
If you copy Rom and boot.img into your "/sdcard/Download" folder you can always flash boot.img inside TWRP - no need for cable connection and fastboot.
Only if TWRP got lost you will need to get the cable ;)
[/QUOTE]
Actually I didn't try Magisk.
I use the canary builds and since A-only SAR is now a known issue, I was waiting until there was some progress in Magisk.
[I]Since there was a new commit earlier today, I gave the unofficial (ianmacd) Magisk build a try with Beta3. - Didn't work. (Booted, no root and gave me a glitchy screen.)[/I]

Still confused about the boot.img :confused:

I dumped /dev/block/mmcblk0p1 after install and tried to fastboot boot it. Just get stuck on the android boot animation. Rebooted and fastboot flashed the boot.img from the zip file and then fastboot continue. After the damn 30 second delay, it actually booted very fast and I was in SetupWizard.

Since twrp-3.3.1-0 allows me to push, I tried installing from internal and still got booted back into twrp.

I uploaded a shell log, TWRP recovery.log and the dd dump of KERN-A.
GoogleDrive [I]dragon[/I] - [URL="https://drive.google.com/open?id=1unpdf3p_V6wegu71B1za16NqpCrVHj3x"]Link[/URL]

Could be user error.
[I]User errors and I, are old friends. ;)[/I]

As for AOSP_10.0.0_r2_BETA3
Display seems a little glitchy in AOSP vs. Lineage.
[I]Seemed quicker and smoother in LOS 17.[/I]

Outside of that not much to mention.
- Actually Bluetooth is strong. :)
[I]Well, error more likely.
When a bluetooth speaker is connected (connects right away) and testing a video in YouTube (Brave Browser) closing browser, the speaker keeps the connection to YouTube open. (Even turning off the speaker/bluetooth.) You can only kill it by rebooting.[/I]

Cheers. :cowboy: