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

installation of /e/OS on Fairphone 2 doesn't work #137

Open
Commown-team opened this issue Apr 3, 2023 · 9 comments
Open

installation of /e/OS on Fairphone 2 doesn't work #137

Commown-team opened this issue Apr 3, 2023 · 9 comments
Labels
bug Something isn't working device Request to add or improve a specific device.

Comments

@Commown-team
Copy link

Commown-team commented Apr 3, 2023

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:

  1. Enable USB debugging and OEM unlocking
  2. The Fairphone 2 is detected by OpenAndroidInstaller, click on "continue"
  3. The requirements are verified
  4. Zip file of /e/OS for Fairphone 2 and twrp recovery file (.img) are uploaded
  5. Click on Continue
  6. Click on "Confirm and run" : the Fairphone 2 reboots into the bootloader
  7. Click on Continue
  8. Click on "Confirm and run" : the Fairphone 2 stays in fastboot mode and openandroidinstaller loads for an indefinite time... The button "Continue" is not clickable and the procedure can't be continued

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):

  • OS: Ubunu
  • Version : 20.04

Smartphone (please complete the following information):

  • Device: Fairphone 2
  • OS: (to be verified)
  • Version (to be verified)

openandroidinstaller.log

@tsterbak tsterbak added bug Something isn't working device Request to add or improve a specific device. labels Apr 3, 2023
@tsterbak tsterbak added this to the Release Beta 0.4.3 milestone Apr 3, 2023
@tsterbak
Copy link
Member

tsterbak commented Apr 3, 2023

@Commown-team Thank you for your interest in the project! :)
This should not happen. Sorry about that.

Can you please attach the log file so I can investigate the issue? You can find it in the same directory as the executable.

@Commown-team
Copy link
Author

Thank you for your reactivity. I've attached the log file. Hope it helps to understand this issue !

@tsterbak
Copy link
Member

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.

@tsterbak tsterbak removed this from the Release Beta 0.4.3 milestone May 1, 2023
@tsterbak
Copy link
Member

tsterbak commented Oct 7, 2023

Hi @Commown-team,
we now had a few releases in the meantime and this issue should be fixed. Can you possibly retry if you have the device still available? :)

@Gredin67
Copy link
Contributor

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

@tsterbak
Copy link
Member

Hi @Gredin67, thanks for reporting this issue!
It looks like a different issue to me as far as I can tell. Could you attach the log file of this trial? It seems like the ROM and/or twrp image could not be validated properly. Thank you 🙂

@Gredin67
Copy link
Contributor

Sorry I don't, it was not my phone and we switched to manual install cause no time.
Can you explain how and why you validate the ROM and TWRP files ? Just by checking the filename ? Or a checksum ?

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.

@Gredin67
Copy link
Contributor

I'm pretty sure @Commown-team could try again on a FP3 and send the logs.

@tsterbak
Copy link
Member

tsterbak commented Dec 1, 2023

Can you explain how and why you validate the ROM and TWRP files ? Just by checking the filename ? Or a checksum ?

They are validated as basic measures to prevent people from breaking their devices with random files.

  • Twrp is only validated by checking the filename.
  • for the ROM we check, if the pre-image field in the file /META-INF/com/android/ of the ROM actually contains the device code of the device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working device Request to add or improve a specific device.
Projects
None yet
Development

No branches or pull requests

3 participants