*I was initially reading this as an indication that the sbl3 ended up being corrupted by the OTA. Or maybe one of the other primary partitions was corrupted and not allowing it to load. However, after running “fastboot oem erase_persist” in the Bootloader, the bricked device shows the same output as the working one.

Bricked

E:\android_development\sdk\platform-tools>adb shell tail ./etc/recovery.fstab
/tz         emmc    /dev/block/platform/msm_sdcc.1/by-name/tz
/rpm        emmc    /dev/block/platform/msm_sdcc.1/by-name/rpm
/aboot      emmc    /dev/block/platform/msm_sdcc.1/by-name/aboot
/sbl2b      emmc    /dev/block/platform/msm_sdcc.1/by-name/sbl2b
/sbl3b      emmc    /dev/block/platform/msm_sdcc.1/by-name/sbl3b
/tzb        emmc    /dev/block/platform/msm_sdcc.1/by-name/tzb
/rpmb       emmc    /dev/block/platform/msm_sdcc.1/by-name/rpmb
/abootb     emmc    /dev/block/platform/msm_sdcc.1/by-name/abootb
/usb-otg    vfat    /dev/block/sda1     /dev/block/sda  flags=removable;storage;
display=USB-OTG
/persist ext4 /dev/block/platform/msm_sdcc.1/by-name/persist

Working

E:\android_development\sdk\platform-tools>adb shell tail ./etc/recovery.fstab
/sbl3       emmc    /dev/block/platform/msm_sdcc.1/by-name/sbl3
/tz         emmc    /dev/block/platform/msm_sdcc.1/by-name/tz
/rpm        emmc    /dev/block/platform/msm_sdcc.1/by-name/rpm
/aboot      emmc    /dev/block/platform/msm_sdcc.1/by-name/aboot
/sbl2b      emmc    /dev/block/platform/msm_sdcc.1/by-name/sbl2b
/sbl3b      emmc    /dev/block/platform/msm_sdcc.1/by-name/sbl3b
/tzb        emmc    /dev/block/platform/msm_sdcc.1/by-name/tzb
/rpmb       emmc    /dev/block/platform/msm_sdcc.1/by-name/rpmb
/abootb     emmc    /dev/block/platform/msm_sdcc.1/by-name/abootb
/usb-otg    vfat    /dev/block/sda1     /dev/block/sda  flags=removable;storage;
display=USB-OTG