The /e/OS install on my new Fairphone Gen 6 did not go as well as hoped.
I did a factory data reset to start over, but I am not allowed to reinstall the eSIM. Murena Helpdesk says it could be 5 days before they respond to a ticket. Is there any way to preserve a downloaded eSIM so I don’t have to ask for a new QR code every time I attempt to complete initial provisioning? If it takes a week each attempt, it could be months before I get a chance to try out my new phone.
Hi @Carlb welcome to the /e/ users forum.
Is it useful to share the install problem? Perhaps we can help you avoid more Factory resets. (The correct install is generally successful in one go, unless a Google account is left on the phone triggering frp.)
As I understand it eSIM reinstatement following Factory reset is somewhat dependant on the supplier / carrier. One needs a connection to the carrier to ensure they maintain what is effectively the account backup (reinstated, as you say, often by QR code).
Maybe some carriers offer backup direct off the device, idk, will depend on carrier.
For clarity are you asking about a Murena eSIM?
Yes, I was provisioning a new phone with /e/OS/ and porting my old number to the new phone,
Murena had emailed a QR code with very little instructions and NO mention of it being single-use.
During OS install, it never offered to transfer data from the old phone, and the ASHA protocol did not work at all. I recently installed Android on a Samsung phone (with a physical SIM chip), and had problems with ASHA (hearing aid support), but after 3 or 4 factory data reset and reinstall, it finally worked. Since the QR code made no mention of single use, I tried the same on the new Fairphone Gen 6. 
Apparently ASHA in the new phone is non-functional so I will have to return it. I’m still waiting to hear from Morena how we can handle porting my phone number to an alternative carrier or parking it somewhere until I can get a phone that works.
It’s a shame, since I was really looking forward to trying /e/OS/ on the Fairphone.
Carl
Regarding ASHA there is one issue on Gitlab
Sadly it is reported closed due to lack of activity despite (also closed) 🔊 Call to Action: Help us test ASHA protocol for Hearing Aids!