eSIM function not working on fairphone 5

System and Apps
,
1

I have a Vodafone DE eSIM activation letter with QR code and so on that works fine on an iPhone. But once I try it on my FP5 with iodéOS 7.4 I get the below errors.

Error code: ES10B_ERROR_REASON_UNDEFINED

Last HTTP response (from server):

{

“header”: {

"functionExecutionStatus": {

  "status": "Executed-Success"

}

},

“transactionId”: “6DF5D22A8ED9408A9E8FE2933E4F5907”,

“profileMetadata”: “vyWCAwdaCpiUAiNiBjBCcleRC1ZvZGFmb25lIERFkg1Wb2RhZm9uZSBlU0lNkwEBlIICn4lQTkcNChoKAAAADUlIRFIAAAANAAAADQgGAAAAcuvkfAAAAAFzUkdCAK7OHOkAAAAEZ0FNQQAAsY8L\/GEFAAAACXBIWXMAABJ0AAASdAHeZh94AAACNElEQVQoUx1SwWoTURQ9771MkpmqtW0Smhhba5vuYhVahYpQ3BbEhZqddKdgd7rRneDGleJHiCKIpYgWqYkI4tYiKiTRpNCmNdLUthOTmTfveifvLi6cy7nnnMsT2vgEEYECsF8q4u\/rZaBYhDeYQP\/CdajxHPrzUyDHhtEaQgaAISLd+Ue1xZu0MZKkrxNjtPn8KQWM1+8\/oMrxIfoxN01+uUo+YyZgEe70\/cYCNbPjVB47QW69HkLU2m7Sl5ii1rk8NU5NUm2KiXt7ZEiT3C2V4JTeQygffY8fwhkZgQ4MDg8cRfrZC2zqGOIqhqjexPa9OzBhkF93b1Mzl6Nvs2d7CgH78tmC4Qqf13aplj9DW9OnqTqTp87uAUl7bY1P4CFxeZ47Z0TAuySECfMGsGwHXmEejsuA3ofYqENGuwYeD3ZWP\/ZIgmk8hi81iMnhs9Mn0aEOIr4F4weQ7uQo4sICalV0t\/5ASQtS8Gm5FIkeqfXpHVRcomtFoTJpyMj5i9DdXQw6fajcWuypCBFFhItYqLXyFvHiZ0QMIZodg5VMQPh8\/OrcLBLuHoK2i1YqA3W1ADubgPvmA7CyhOHRDBo\/G0i\/WsahmWmI8EKdSgXrhWsY8lswygF1fUh9ABkfgBIOGjvrSD56gqErBQTGcFLtITYxgdHVIvSFS9i3j6Cj4ujaffhtKezkUjj2cqlHYIfg38D2Ao8UhybJGRgzbhtBpcwbI7DSKUSHkz0cFKbluSH8B6+aKklyukBWAAAAAElFTkSuQmCClQECti0wK4ACBHCBJW1hbi1ndG8ucHJvZC5vbmRlbWFuZGNvbm5lY3Rpdml0eS5jb223BYADYvIg”,

“smdpSigned2”: “MBWAEG310iqO2UCKno\/ikz5PWQcBAf8=”,

“smdpSignature2”: “XzdAqprxB2NM96gidz63266ZzAQCVk1ByhLu6XCxBGbvTHKTOWsPJMwcN2EFcUI+REKQe2SSXdmQ7oSUcbzmXD7U2g==”,

“smdpCertificate”: “MIICczCCAhmgAwIBAgIQOdhk6v4KXIFiic6kGCUrXzAKBggqhkjOPQQDAjBEMRgwFgYDVQQKEw9HU00gQXNzb2NpYXRpb24xKDAmBgNVBAMTH0dTTSBBc3NvY2lhdGlvbiAtIFJTUDIgUm9vdCBDSTEwHhcNMjQwOTI2MDAwMDAwWhcNMjcwOTI1MjM1OTU5WjBaMQswCQYDVQQGEwJGUjESMBAGA1UEBwwJTGEgQ2lvdGF0MRIwEAYDVQQKDAlUSEFMRVMgU0ExDDAKBgNVBAsMA0RJUzEVMBMGA1UEAwwMVEhBTEVTIFNNRFBQMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAELtqX9HnGrfJQ5uvM\/BWP4zNuSciIZzbMRZvikfeCO92SJHc6+49Z0v269tYBC8ovB5JZoY8ymMt90\/QT+HAdTaOB1jCB0zAZBgNVHREEEjAQiA4rBgEEAYH4AgGBXGRlAjAXBgNVHSABAf8EDTALMAkGB2eBEgECAQUwTQYDVR0fBEYwRDBCoECgPoY8aHR0cDovL2dzbWEtY3JsLnN5bWF1dGguY29tL29mZmxpbmVjYS9nc21hLXJzcDItcm9vdC1jaTEuY3JsMA4GA1UdDwEB\/wQEAwIHgDAdBgNVHQ4EFgQUL4UWcTvT2CLsYeJ6hsVQTv\/oaQ8wHwYDVR0jBBgwFoAUgTcPUSXQsdQI1MOyMubSXnlb6\/swCgYIKoZIzj0EAwIDSAAwRQIgW5xDPpnEu6Q6geO1PhaFP3YBrfOJchzXlq+xDkNW4NsCIQCdaEcf1PY\/YvM8k\/yN23aJ7+g4Z\/Zd0f6hfAWp4mfDEg==”

}

Last APDU response (from SIM) is successful

Searching online I got the sense that I need to troubleshoot the OpenEUICC app. However it appears just in one place in my case: Settings → Apps → Pre-installed apps. There I can only uninstall and reinstall it. It cannot be launched, updated or interacted with any other way.

5117
51171224×2700 145 KB

After uninstalling, rebooting, installing, rebooting now I cannot even try to add an esim as tapping Add network under Settings → Network & Internet does nothing.

Seems like I need to reset the phone or reinstall iodéOS from scratch before I do anything else. In the meantime: can anyone make sense of the error log?

2

OpenEUICC is not showing in your main “App Menu”? That is the tool you want, as iodéOS removes the Google eSIM manager and relies on OpenEUICC instead, so it not being found is certainly a problem. There are some devices that don’t support OpenEUICC and still need to use Google eSIM Manager, but I don’t think (?) the Fairphone 5 is one of those?

If it really is not there, please try to “delete” from “Preinstalled Apps > Reboot” and then add again to “Preinstalled Apps > Reboot” and then see if it is found in your App Menu.

3

I don’t recall ever seeing OpenEUICC as its own app. As I already described uninstalling and reinstalling it as you describe makes no difference.

4

What are my chances a physical SIM will work? What are the requirements that I can check for in advance?

5

much better :slight_smile:

To OpenEUICC, I am seeing if maybe a config change or something happened in the last builds that may have disabled it / broken it for the FP5.

6

Since 7.5 it works. Was also able to re - lock the bootloader.

1 Like
7

Thanks for the feedback, glad to see it is working! There have been others trying to relock their bootloaders, good to have the confirmation it should work (as long as you are not “behind” the previous install).

8

I really which there was a way to find out the relevant numbers to be able to compare. Why doesn’t iodé include it in the release notes? Is there no ADB command? As it is everyone else on the forums just says to check but not how and the replies simply mention that the OP checked but not how. For me it was just trail and error after each iodé update, which seems unnecessarily cumbersome.

9

I have inquired, but the problem is it would be manually intensive to enter this in notes for each build made (for all our devices for beta and stable each month we are talking a few hundred total builds probably). The automated way (during install to compare to current install) isn’t possible, I had this discussion a few times and can’t recall but it was validly not possible. Sorry I was convinced before but the reason is not in my mind still.

Anyway, what I think we came up with as an auto way to identify vendor security update level of the iodéOS build would be to put in in the filename of the .zip. But there may be some challenge in doing that, or just not done yet.

For FP5 you can look at our commits to see what was most recently applied and compare that vendor patch name to FP’s posted name:

Our FP5 commits: Commits · v7-staging · os / public / devices / fairphone / device_fairphone_FP5 · GitLab

From there you see “FP5: Update to FP5.VT2P.C.089.20260311” on 30 March, 2026.

Then when you look at FP5 manual install instructions you see these 2 builds:

Version: FP5.VT2R.C.095
Release Date: 18 May 2026
Security Patch: 05 May 2026

Version: FP5.VT2Q.C.092
Release Date: 20 April 2026
Security Patch: 05 April 2026

So both are newer and would thus trigger ARB (and not boot iodéOS). So it must have been the LineageOS team didn’t get the April patch in before the iodéOS 7.5 build was made.