Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn and check(?) for encryption on bacon #1032

Open
joebonrichie opened this issue Nov 15, 2019 · 2 comments
Open

Warn and check(?) for encryption on bacon #1032

joebonrichie opened this issue Nov 15, 2019 · 2 comments
Labels
help wanted help from community contributors would be appreciated needs confirmation a bug that has not yet been confirmed or reproduced

Comments

@joebonrichie
Copy link

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!

@NeoTheThird NeoTheThird added needs confirmation a bug that has not yet been confirmed or reproduced help wanted help from community contributors would be appreciated labels Nov 22, 2019
@NeoTheThird
Copy link
Member

We might be able to solve this by adding adb format steps like we have on the nexus 7.

@matrix8967
Copy link

matrix8967 commented Sep 25, 2020

Heya @NeoTheThird 👋

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted help from community contributors would be appreciated needs confirmation a bug that has not yet been confirmed or reproduced
Projects
None yet
Development

No branches or pull requests

3 participants