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

Bootloader unlocking for suzu: Back up TA partition, accept unlock code, flash OEM binaries for AOSP #1305

Closed
vasyugan opened this issue May 19, 2020 · 9 comments
Assignees
Labels
bug a bug in the software itself

Comments

@vasyugan
Copy link

vasyugan commented May 19, 2020

At the moment, the installer is dysfunctional for suzu:

  • It cannot back up the TA partition, which must be done before unlocking the boatloader, or you can never revert to factory state (happened to me)
  • I doesn't hint at the need to obtain an unlock code from sony and provides no opportunity for entering it.
  • It doesn't flash or hint at the need to flash the OEM binaries for AOSP BEFORE proceeding with the installation, so that the Ubuntu recovery installed ends up in a boot loop, and thus, installation doesn't get completed

I think that therefore when the installer detects a locked bootloader it should stop and provide a link to the instructions, I have written them down here and I would think they should be on the device page, because that's obviously the place where you look first.

@Flohack74 Flohack74 transferred this issue from ubports/installer-configs Jul 28, 2020
@Flohack74
Copy link
Member

@fredldotme what do you think, what would be a good UX for that?

@NeoTheThird NeoTheThird added needs confirmation a bug that has not yet been confirmed or reproduced bug a bug in the software itself and removed needs confirmation a bug that has not yet been confirmed or reproduced labels Sep 23, 2020
@NeoTheThird
Copy link
Member

Here's how this looks in the wild #1071

@fredldotme
Copy link

Aargghh, if I just didn't miss the notifications. Alright, so the device unlock UX I'm not sure we can do easily without implementing a lot of things in the installer, so I would recommend hinting on the requirement in the device config, let that surface to the user in the installer UI and link them to a new forum thread I could set up specifically to guide the user.

@NeoTheThird
Copy link
Member

I'm always a fan of automating as much as possible, if it's just a matter of passing the key for the oem-unlock, i'm happy to implement a UI for that. If you have ideas on how a note could look, could you send a PR to the config?

@fredldotme
Copy link

I noticed we already have a guide for TA backup, unlocking etc. on suzu's devices.ubuntu-touch.io page, we could show that one after showing the hint about the Android 8 requirement.

@NeoTheThird
Copy link
Member

Manual downloads for flashing the oem partition are included in 0.5.6-beta. If someone wants to add it to the config files where it's needed, i'd be very appreciative. See the notes for developers on the release for usage documentation.

@NeoTheThird NeoTheThird added the help wanted help from community contributors would be appreciated label Oct 25, 2020
@NeoTheThird
Copy link
Member

Opened #1479 to track those new-fangled unlock requirements. For the rest, i'll update the config accordingly.

NeoTheThird added a commit to ubports/installer-configs that referenced this issue Oct 28, 2020
@NeoTheThird NeoTheThird removed the help wanted help from community contributors would be appreciated label Oct 28, 2020
@NeoTheThird NeoTheThird self-assigned this Oct 28, 2020
NeoTheThird added a commit to ubports/installer-configs that referenced this issue Oct 28, 2020
@robiwan1
Copy link

the easiest way to add unlock code to the "fastboot oem unlock..." command is to ask in the UI and/or add an option in the config file, because there is already an option in the ubports-installer to view/edit the selected config file...

@NeoTheThird
Copy link
Member

@robiwan1 we're going to have an ui, that's being tracked in #1479

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug a bug in the software itself
Projects
None yet
Development

No branches or pull requests

5 participants