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

Flashing script issue with vbmeta #48

Closed
ApostolosB opened this issue Dec 18, 2019 · 5 comments
Closed

Flashing script issue with vbmeta #48

ApostolosB opened this issue Dec 18, 2019 · 5 comments

Comments

@ApostolosB
Copy link

ApostolosB commented Dec 18, 2019

sudo ./flash.sh on linux gives you:

Flashing vbmeta partition...
fastboot: error: cannot load 'vbmeta': No such file or directory

You have to run:

sudo fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

to complete the flashing.

@rinigus
Copy link
Contributor

rinigus commented Dec 19, 2019

Thanks for filing it!

@MartinX3
Copy link

@rinigus AvB2 won't be supported in SailfishOS?

@rinigus
Copy link
Contributor

rinigus commented Dec 19, 2019

@MartinX3 : to me it sounds like an extra headache coming with no real benefit to the user at SFOS. At least looking through https://android.googlesource.com/platform/external/avb/+/master/README.md, I think we have more important security considerations to fix on SFOS before. So, I don't see it happening any time soon.

But the flash script has to be fixed.

@pagism
Copy link

pagism commented Dec 21, 2019

line 214 in flash.sh should be:

$FASTBOOTCMD --disable-verity --disable-verification flash vbmeta ${SAILFISH_IMAGE_PATH}vbmeta.img

rinigus added a commit to sailfishos-sony-tama/droid-config-sony-tama-pie that referenced this issue Dec 21, 2019
@rinigus
Copy link
Contributor

rinigus commented Dec 21, 2019

@pagism: thank you very much, I can see now how this error occurred!

I will publish new images as a part of the next release (SFOS 3.2.1.20) and the updated script will be a part of it. Later I will remove images from alpha release as its probably not necessary to keep them for too long.

Closing here, reopen if it still is an issue with the next release images.

@rinigus rinigus closed this as completed Dec 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants