Hi everyone,
I've had my Pixel 3a for about two years now and it works like a charm. I have recently changed phone carriers. I cannot download an eSIM for my new carrier while it is supposed to be compatible with the Pixel 3a. They claim this is because I still have the eSIM profile from my previous carrier. For some reason, I cannot erase this old eSIM profile manually. I get the following error message: “Can't erase SIM. This SIM can't be erased due to an error. Restart your device and try again.” Of course, I still can't erase the eSIM when I restart the phone.
I have contacted both carriers, as well as Google. They had me reset Wi-Fi, mobile & Bluetooth which didn't work. The next step they advise is a factory reset. I'd like to find another way to erase this faulty eSIM profile and I'm not completely sure that a factory reset would be “strong enough” actually.
Has anyone ever encountered a similar problem or knows a way to force the deletion of the old eSIM profile?
Were you able to delete that esim profile? I just got a "new" open box factory unlocked P3a that has the same problem. Factory reset won't kill it. Mine is definitely not new as it was half way through the A11 OTA's when I got it today. Maybe that's the reason OEM unlock is greyed out, data on. I haven't found any info yet to resolve it.
Unfortunately, I haven't been able to solve this problem. Google support told me they were escalating the issue to their developers but I haven't heard back from them in a while...
Related
I have a new sim card, it works great with my other phone,
but my oneplus One does make an issue out of it.
I just did a factory reset and it finally worked after trying every other trick (airplane mode on/off, taking out the sim card...)
I tried other sims and they do work 2/4, the sim out of my other phone didn't.
I have no idea whats wrong with my phone.
I am trying to factory reset it one last time, as I suppose it's taking my old apn setting from my google account.
I will try to go without play store for awhile if that works.
EDIT: ok, this didn't work. I didn't even connect to wifi this time, maybe the sim's dead?
But why is it still recognized by my other phone?
EDIT2: Just called the carrier, the issue is with my phone, as they do not block any models and oneplus one usually works with them.
bankshipper said:
I have a new sim card, it works great with my other phone,
but my oneplus One does make an issue out of it.
I just did a factory reset and it finally worked after trying every other trick (airplane mode on/off, taking out the sim card...)
I tried other sims and they do work 2/4, the sim out of my other phone didn't.
I have no idea whats wrong with my phone.
I am trying to factory reset it one last time, as I suppose it's taking my old apn setting from my google account.
I will try to go without play store for awhile if that works.
EDIT: ok, this didn't work. I didn't even connect to wifi this time, maybe the sim's dead?
But why is it still recognized by my other phone?
EDIT2: Just called the carrier, the issue is with my phone, as they do not block any models and oneplus one usually works with them.
Click to expand...
Click to collapse
EDIT3: did a full stock reset to stock recovery and such, somehow the sim works now.
I spent 48h to fix it...^^
So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota
My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?
[Edit: Just a quick note to let folks know, if there was anyone who cared at all, that this issue has resolved itself. I have no real understanding why, but I did a few more "Factory Resets", both with "Wipe Userdata and Personalizations" and with just "Wipe Userdata". Whatever I did just seemed to work as my wife was able to sign in afterwards. When she did I removed her account from the phone, did the multi-wipe procedure again and was able to sign in as myself. That was the goal.
Thanks very much, again, to the folks who commented on my question!]
Hey All,
I have an older device, a Moto X Pure, that I've done the factory reset/wipe all data thing via the stock Recovery. The device is on the latest update that Moto provided 3 (or is it now 4) years ago now, Android 7.1. Other than an unlocked bootloader, everything else is on the device is stock and unrooted, although it does not have a SIM card installed in it at this time. In fact, the entire reason that I'm trying to initialize it is to test a number of different mobile service providers to find the best provider for my, largely rural, common travel pathways.
However, once I enter my wifi info successfully and try to sign into this device with my Google ID/password, I cannot do it. Instead I get an error message that starts with the text that's in quotes in the post subject. The message continues with "try another account, or wait 24 hours and try again." Now, I've done the 24-hour wait thing several times, but the result is the same.
The phone was my wife's daily driver until I replaced it a couple of months ago. I've had her try to sign into it as well, but she can't do it either with the identical result.
So I'm at my wit's end. Has anyone in this sphere ever encountered this error? Were you able to overcome it? Can any other kind soul here suggest a way to circumvent this? I mean one that doesn't involve sledge hammers and concrete pads?
Thanks!
cheers,
john
My guess is problems like reported could be related to Factory Reset Protection, which happens when the previous owner of a device didn't properly remove his/her Google account from phone prior to doing a factory reset.
jwoegerbauer said:
My guess is problems like reported could be related to Factory Reset Protection, which happens when the previous owner of a device didn't properly remove his/her Google account from phone prior to doing a factory reset.
Click to expand...
Click to collapse
If his wife did a factory reset when she first got it then that's not the case.
OP, did she?
jwoegerbauer, how is the reset password handled? If you originally sign in to the device with one password but then change your Google account password, does the device authorization automatically update too?
Or do you use the original password?
Any failsafe to prevent the device owner from getting permanently locked out?
That whole embedded subsystem gives me a headache.
Thanks to both of you for the feedback on this!
jwoegerbauer said:
My guess is problems like reported could be related to Factory Reset Protection, which happens when the previous owner of a device didn't properly remove his/her Google account from phone prior to doing a factory reset.
Click to expand...
Click to collapse
Ah, yeah, that definitely happened. By that I mean that the previous owner did not properly remove their account prior to my doing the factory reset.
Now the question is: Is there any way for me to recover from this situation? I have the latest factory ROM for this device (from three or four years ago). Can I just flash that over what's on there? Or have I tripped some kind of circuit breaker and I'm just hosed?
blackhawk said:
If his wife did a factory reset when she first got it then that's not the case.
OP, did she?
Click to expand...
Click to collapse
No, and we bought it on Swappa about six months after it came out, with an unlocked bootloader no less, so we just assumed that the seller did a reset before transferring it to us, but we don't know that definitively.
blackhawk said:
jwoegerbauer, how is the reset password handled? If you originally sign in to the device with one password but then change your Google account password, does the device authorization automatically update too?
Or do you use the original password?
Any failsafe to prevent the device owner from getting permanently locked out?
That whole embedded subsystem gives me a headache.
Click to expand...
Click to collapse
Yes, same questions now that blackhawk mentions them. (Since I didn't think to ask such good ones myself!)
Thanks again to both of you for your help!
cheers,
john
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again.
Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
Click to expand...
Click to collapse
If others are experiencing the same issue after the update, then that highly suggests the problem was caused by the update.
So, unfortunately, ONLY google can fix it with another patch and you will have to wait until google gets around to fixing it.
I have similar problem though I thought it's caused by android 12 beta so I outped out it and everything was fine for few days. I restated my phone after day or two and the problem of no serivce came back. This time even factory reset didn't help.
I can't manually change preffered network type to 2g/3g and everytime I try to make a phonecall it says i need to turn off aeroplane mode off.
Felixxxxx said:
So, every since I have updated my pixel 4a to the August security patch, it starts giving me an issue with my SIM, it seems to not detect my SIM at random points of the day and I sometimes have to restart it multiple times to get it to detect again. After it gets detected, it will work fine for about 12 - 15 hours before the issue comes back again. When the issue occurs, my mobile network option in the settings will get greyed out. (see attachment below)
Went to my carrier and get a new SIM. Still, the issue persists. Even tried an E-SIM and it still doesn't work
I have contacted Google support and they told me to send my device down for repair and inspection however, even after repairing my device, the issue still persists. Factory reset does not fix it as well. Dig thru Reddit and Google forum as well, tons of others are facing the same exact issue after the August update leading me to deduce that this is not a hardware but a software issue with the update.
I saw that there was the September security update patch yesterday and I went to update it, however, the issue is still there
I then proceeded to contact Google support again and they kept telling me to send it for repair even though I already have?
Does anyone have a clue what to do?
Click to expand...
Click to collapse
Wow, unfortunate for sure. Isn't it possible to roll back to just before the update? Of course google makes the entire firmware available and I believe I've read if you remove the '-w' at the end of the script it doesn't wipe data?
At least if this was possible it would certainly indicate if it was the update or not?
cheers
So my Pixel 4a updated to the October Security Patch this night, and from there on it says "SIM not detected".
But when I go in settings it shows the network name.
I tried switching the SIMs with my Pixel 2 and everything works there, but any SIM I put in my 4a shows "SIM not detected" even though it can detect the network.
Which it probably wouldn't do if the SIM slot were defective, right?
And the timing with the update is too much of a coincidence...
I have similar issue - Pixel 3A, after update with November Security Patch, "No simcard" error appears with mandatory reboot. Tried with different SIM, there was prompt for PIN, verified and then it seems no access to simcard data. Even "emergency call" is no allowed from now. Looks like additional privilidges needed for access SIM card. No clue, how to proceed...
Galaxy S22 Ultra (SM-S908U1) USA model unlocked purchased directly from Samsung.
Running on T-Mobile. I replaced the original SIM card with eSIM several months ago so I have two different IMEI numbers.
Just updated the phone OTA to the June security update a couple of days ago when it finally became available for my phone.
Yesterday I tried to update some apps in the Galaxy Store and they wouldn't update. The screen just sort of jumped up a little, then down. After trying numerous times without success, I decided to try first signing in and out of my Samsung account which didn't work, then I tried deleting my Samsung account. When I tried to go back into Settings/Samsung account, I got an error message every time: "IMEI (or MEID) is empty". This same error message shows up when I try to sign into Samsung Pass, Accounts/Backup data, Biometrics and security/Find my phone, Galaxy Store app, pretty much anything that seems to have a tie in to my Samsung account.
I did a full factory data reset, but the problem is still there. I sort of remember updating a couple of apps in the Galaxy Store a couple of days ago and it worked fine. Could the June update process have done something to my phone, and how do I fix it?
Could be the esim that's at fault. Can you revert to sim card?
I still have the old SIM card, but it was deactivated when I had the eSIM activated.
raul6 said:
Could be the esim that's at fault. Can you revert to sim card?
Click to expand...
Click to collapse
Well, well. I decided to try your advice and inserted the old SIM card, then restarted the phone and...voila! I now have access to my Samsung account and the Samsung apps work. Thanks very much for your advice!
Missed this. Yes, if you insert ANY sim card, even a new, unused one will fix this. Once you sign in to the app successfully, you can remove that sim. Seems to be a bug introduced in the JUNE update.
That works for me until I turned the phone off in which case it lost the MEID again until I used another SIM.
if you use a non-working simcard, you will have problems with Apps & downloading. It stands to reason that this will occur. Plus ESIM is a relatively new addition and there will be bugs.