Open joebonrichie opened 4 years ago
We might be able to solve this by adding adb format steps like we have on the nexus 7.
Heya @NeoTheThird :wave:
I hit this issue on bacon
as well.
This device was running LineageOS 17.1
previously, and was encrypted.
Looks like it could be an issue on some other devices?
After a few attempts of using twrp
to erase/fix file permissions as mentioned in the other issues linked recently, it wasn't working.
I was able to manually flash boot-bacon.img
and recovery-bacon.img
to their respective boot
and recovery
partitions using fastboot
.
I rebooted into the UB Bootloader, ran through both the Ubuntu and Android options to wipe/erase/fix the partitions.
After that -- the ub-ports-installer
Installer was able to detect the device, download the rest of the system images, push them, flash them.
I just got to the setup screen, so let me know if any logs or anything are needed and I'll upload them. I grabbed logs from /cache/recovery/
while booted into ub-recovery
.
Related to this but I got my tabs out of order, sorry to bump the old issue.
Similarly to #895 and #609, after installing the device will bootloop if the data partition is encrypted, the wipe data option in the ubport's installer does not remedy this.
If issue was previously fixed for Nexus 5/7 could you extend the fix to the OnePlus One (and maybe for all devices) as well, thanks in advance!