-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
installation of /e/OS on Fairphone 2 doesn't work #137
Comments
@Commown-team Thank you for your interest in the project! :) Can you please attach the log file so I can investigate the issue? You can find it in the same directory as the executable. |
Thank you for your reactivity. I've attached the log file. Hope it helps to understand this issue ! |
Thank you for providing the log file! That helps a lot 🙂 It looks like you run into an issue that was fixed in the latest release 0.4.2-beta. Do you have the FP2 at hand and could try again? Let me know if the issue persists or another issue appears. |
Hi @Commown-team, |
I had a similar behaviour on a Fairphone 3. After selecting twrp and ROM file (/e/OS), continue button remains grayed out. Cannot continue the procedure. The manual procedure is working fine, see https://doc.e.foundation/devices/FP3/install |
Hi @Gredin67, thanks for reporting this issue! |
Sorry I don't, it was not my phone and we switched to manual install cause no time. If people have to download those files manually and can chose the Android ROM and TWRP version they want (provided it supports), why enforce this verification ? My suggestion would be to add a checkbox to deactivate ROM/TWRP file checking and be able to continue with the process even if the validation fails. Of course explaining the associated risks. |
I'm pretty sure @Commown-team could try again on a FP3 and send the logs. |
They are validated as basic measures to prevent people from breaking their devices with random files.
|
Describe the bug
The procedure doesn't finish and get stuck at the last step of the process "confirm and run"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
At step 8 of the description above, the expected behavior is that the button "Continue" is clickable after unlocking the bootloader
Desktop (please complete the following information):
Smartphone (please complete the following information):
openandroidinstaller.log
The text was updated successfully, but these errors were encountered: