Can not phone... Can not create APN entry point - after update to /e/ 1.1. on moto G3 osprey; Can not select manually the carrier

Just to add to your research this is the source of the APN which I expect to have gone to your device at update, the apns-config.xml prebuilt/common/etc/apns-conf.xml · v1-q · e / os / android_vendor_lineage · GitLab.

As a matter of interest I searched this list for my (supermarket, cut price) carrier. I find 3 matching lines. Interesting too that at first glance they are incorrect (out of date)! This explains why, in my case, if I format the data partition, I have to ring the carrier and ask them to push the APN to the device.

It is certainly unusual to see zero contact with the carrier airwaves! I fully see the difficulties, but I do not read that you succeeded in getting the carrier to push the APN direct to the device.

Thank you. I tested the APN with these dates another time, but after “save” the APN I wrote disappears…

Yeah, but in your case your phone also not asked you for the PIN of the SIM card and did you have “only emergency calls” also?

At the moment I phoned another time my carrier. She said, that she can not do anything, since I have no connection to the mobile network, except emergency calls. I neither can recieve SMS. She asked me, if my phone has a SIM-lock. I think that should not be in /e/ and before the upgrade my SIM worked fine.

1 Like

Does the phone not asks for the PIN if there would be a SIM-lock?

Are there possibilities of other ways to enter my SIM-PIN? Besides the “normal” “beeing asked with the field of numbers”?

Thank you for getting this confirmed, with this I think we exhausted the APN angle.

Do you feel you have a singular “SIM card not doing its job correctly” and that because of the update effective contact with the SIM had been lost? If so … you might consider

  1. Reinstall the current version

  2. Downgrade to the last working /e/ version – for either of these options, please refer to the install page Install /e/ on a Motorola Moto G 2015 - “osprey” for details and downloads. (An upgrade page exists, but note this is for OS Version upgrade.)

  3. Factory reset – the most extreme as your data will be lost, so you would have to ensure a backup first. A TWRP data backup would be useful in this case, but I always like a double backup of important stuff. Download TWRP for osprey exists but your device may have the /e/ Recovery.

Carrying out a downgrade of /e/ version should be no more risk than the update. I would expect the downgrade to fairly painless. You should not need to delete data.
I do not know if you have /e/ Recovery or TWRP.

TWRP allows you to install the /e/ image /e/ image ROM download by downloading it and put it in an accessible place on the device, internal storage or SD card. Or copy to SD card from PC. I am not certain if /e/ Recovery will do this.

Using the sideload method, in brief it would involve

On the device
Enable usb debugging, Enable USB Debugging and OEM Unlock
Boot into Recovery mode – will look and feel different comparing TWRP and /e/ Recovery.
Select the ART/Dalvic, Cache and System partitions to be wiped and then Swipe to Wipe
select Advanced, ADB Sideload …
… ensure you have connection with PC, see below …
then Swipe to begin sideload.

On the connected PC which should have adb enabled https://doc.e.foundation/pages/install-adb-window (this page is available for Windows and Linux). Do the first command below simply to ensure you have contact with the device, nothing happens other than check you have contact and gave authorisation to the PC to debug. Depending on your adb install method you might prefix the commands with ./


adb devices
adb sideload /path/to/downloaded/filename.zip

Footnote Doing any “repairs” knowing you have good backup is wise. TWRP allows you to make a backup of your data partition (see above).

1 Like

Dear aibd,

on the basis of your really nice and extensive message, what to do now I found the solution!!!

Thank you sooooo much, for your time, energy and advises. I am so glad, that my SIM works another time fine and all is working. And I did not lost much of data, only the Bliss-Starter-App-data, but this is not important.

Here what I ultimatly did:
I installed another time e OS 1.1 - nothing changed
After it I installed e OS 1.2 - nothing changed
Then I installed e OS 0.23 (as it was before the upgrade). After the reboot - I had to entry the PIN of my SIM card :)! And a bit later I got mobile net!!!:slight_smile:
BUT: The Bliss starter app had problems: “Bliss starter was closed repetdly → app informations or close the app” I opened the app informations and deleted the Cache - nothing were happen. I deleted the data. And??? Tadaaaaa: It started regularly, only my icons were different positioned in the start display.

The I tested all my apps, if they work and show their normal function - all did, except Signal messenger, messenger from e and the App Lounge - they showed the same behaviour as “Bliss starter”, so first I rebooted - did not change nothing. Than I deleted the data from these apps also, as I did for Bliss starter and they work another time. I lost little data, but in this case no problem and I have them still on a backup.

Finally I have another time e OS 0.23 and wonder if i never could update it, but that’s not my biggest problem. And I am glad, that I did not lose much data and my SIM is working as before:)!

So, thank your very much for your tips, advises and questions! It was really helpful!!!

Almalexia

2 Likes