Hum, I tried those tutorials, but I get these errors when I’m at the update phase:
adb sideload ./e-2.0-t-20240514401453-dev-beyond0lte.zip
serving: ‘./e-2.0-t-20240514401453-dev-beyond0lte.zip’ (~20%) adb: failed to read command: Success
serving: ‘./e-1.21-t-20240324389105-dev-beyond0lte.zip’ (~31%) adb: failed to read command: Success
or :
adb sideload ./e-2.0-t-20240514401453-dev-beyond0lte.zip
serving: ‘./e-2.0-t-20240514401453-dev-beyond0lte.zip’ (~20%) adb: failed to read command: Success
So, I preferred not to proceed to the update, as I thought it might be that the file was not fully transferred (I checked the md5 of both files). But maybe I was wrong.
I saw still this thread:
Is OEM locking relevant when using already e/os/ ? I can’t find the option anyway.
Note: I’m using Linux/Fedora, so no ODIN.