New One UI 7.0 update- error "SIM 1 NOT ALLOWED"

[Members_TCNM154]

The recent update Version: One UI 7.0 SUCKS. Immediately after the install and reboot I get the error "MM SIM 1 not allowed" But it worked fine literally right before the update. 

And apparently, there's no way to revert it. So my phone is F'ed. Can someone more knowledgeable tell me how to remove this update. I am ready to throw it out the window and smash every Samsung device I have.

I've been on the phone with support, they were no help. 

Multiple Apps are now crashing and my battery is draining super fast. I've reset to factory settings. The update is still there and so is the error and all the other bugs.

My carrier says nothing is wrong with my account and the sim card worked perfectly right before this update. And the SIM works fine if I put it in my other phone. How does an update F'up so badly?

At this point the phone is useless to me so I don't care if I have to root it to get rid of this **bleep**ty update, but I'd like to try something else first...that I haven't already tried. 

(Samsung Galaxy S24+)

[NPC1]

If you have tried everything and still nothing works and you keep getting the Sim message Maybe having your carrier assign an eSim might work? 🤷‍:male_sign:

[Members_TCNM154]

I can use the sim in my old Nokia, so it's not the sim that's the problem. Also, it's more that just the sim card error. After the update, random apps just completely crash, and my battery life has gone to **bleep** literally in a few hours. My phone is basically trash now, and I'm pretty tired of trying to fix something that wasn't broken, until this update. But thanks for your suggestion.

[realaud]

There is no way to revert the update.  I second the opinion to use the e-SIM, or have your provider try a brand new SIM card. 

[erdidd]

I'm having the same problem. My SIM card works on another phone, another SIM card from another operator, works on my phone. I bought a new SIM card and I keep having the same problem. I think there's a samsung one ui 7.0 optimization problem with the operator I'm using 

[realaud]

Have you run diagnostics on the SIM? Since the carriers tweak the updates and roll them out, I assume the would test compatibility. In any case, have your carrier try an e-sim. If that doesn't work, you are probably right, there's some interference between oneui7 and your carrier. But that is an issue for your carrier and Samsung to duke out. More so an issue for your carrier to solve.

[Members_TCNM154]

I'm not sure what you mean by "diagnostics on the SIM." The SIM works fine in my Nokia, and worked fine before this update. At this point, I assume it is because I am in Colombia and this phone is not even available for sale here. My carrier had a difficult time registering the IMEI number when I first arrived here, for that same reason. Additionally, this update is only available for the "Galaxy S2 series, Galaxy Z Fold6, and Galaxy Z Flip6" here in Colombia, but I guess since my phone is from the US, I was forced into the update, even though it basically **bleep** my phone's compatibility with the network here, or something else.  I find it frustrating that my phone and SIM card worked fine until this update, and it updated by itself. And now I'm basically without a working phone, while I'm here, because of this update.  I'm giving up on it, and Samsung. The phone is useless now, and I'll never buy another Samsung product again. So, there's that. 

[realaud]

The SIM obviously does not work fine in *your* phone.  Your phone has a diagnostic tool kit to determine if there are any errors with the hardware.  The diagnostics are located in the device care settings on your phone and in the support tab of the Members app.  Once again, have your carrier go with an e-SIM option and see if that helps.  U.S. model phones should work and be compatible anywhere. Issues occur when people try to connect international phones to U.S. networks.  Perhaps your Columbian carrier has not had a chance to tweak the update for your model phone.  Updates are sent to carriers, who then tweak the updates to work with their networks.  If it was not your phone's turn in Columbia to get the update and you updated here, in the U.S., that could very well be the issue.  This is not Samsung's fault.  However, that being said, if you had updated in the U.S. and traveled to Columbia, your phone should still be usable.  The issue may be the Columbian carrier's SIM not being compatible yet.  You might have to temporarily switch carriers to a U.S. carrier. T-Mobile is good for that.  It does not require a contract and you can just stay on board until your Columbian carrier catches up.  Or buy a pre-paid U.S. SIM.

[Members_TCNM154]

Thank you for the advice. I'm going to run the diagnostics now. Unfortunately, I can't switch to a US carrier while I am in Colombia, they don't work here unless you connect to a US tower first. T-mobile sucks, I would never give them a penny. But thanks for the suggestion. My US phone number was ported long ago, so I have no need for anything else from the US and I don't ever plan on returning, so there's that. I've already paid for the year for my Colombian number and I use it for everything in my life, so it's kind of important to me here. I'd rather switch back to my Nokia and save myself the trouble of trying to make my Samsung work again. Whether or not this is Samsung's fault, it has definitely soured my thoughts on ever purchasing a Samsung device again. I paid a lot of money (for me) to have a device that just suddenly stopped working, over night, for no reason whatsoever, other than Samsung thought everyone needed to have an "upgrade" and forced it on me.

[IHateOneUI7dot0]

👏 I completely agree with your thoughts. I **HATE** 7.0, and I didn't ask for it. It's like yesterday I drove a Ferrari, and this morning, it's a Ford Pinto. The look and feel, and operability of most apps is beyond *awful.* Did I mention I **HATE** 7.0? That hatred is beginning to extend to Samsung as well. Like being suddenly stabbed in the back by a trusted friend. One of the worst rollouts I've seen in many years.