Add eSIM loops forever. Please help

[Felzor]

Hello, I recently purchased an unlocked refurbished Samsung Galazy 25+ (256gb) n excellent condition. I'm excited to upgrade since I'm coming from an A36.

Unfortunately, I'm unable to transfer and/or activate my eSIM (Mint Mobile) on my new device. Scanning the QR code from Mint just locks me in an endless doom loop back to the activate eSIM screen. I dont think its a Mint problem since the QR code works fine on my A36 (unlocked, formerly Verizon).

Tried restarting, updating, resetting network settings, etc. Even did a factory reset! No luck. The seller has good reviews and he's been trying to help me over the phone. Also talked to Mint ustomer support, and they confirmed my phone's IMEI is unlocked and compatible with their service.

I would really appreciate people's advice as i would hate to return this otherwise excellent device. BTW, what's even weirder is there is still an old T-mobile esim card listed, which im also unable to remove or modify. I'm worried this problem is somehow baked into the carrier software/settings, and I wouldn't even know where to start...

[Mujibar]

It's likely that the device you bought is a carrier model (probably T-Mobile) that wasn't properly unlocked. Please share a screenshot of your about phone > software information screen (see attached pic).

[Felzor]

Thanks for the reply! I've attached a screenshot. Well, that would be ashame since the seller got good reviews and Mint even said the device was unlocked...

[Mujibar]

It looks like the phone has T-Mobile firmware as well as carrier software. Something's preventing the Mint eSIM from overwriting the carrier software, which explains why you still see the T-Mo eSIM.

Your best bet is to return the phone. You want a device that is verified as factory unlocked (model name ends in U1). That will allow you to use whichever carrier you want.

[Felzor]

Thanks for getting back! FYI, the model name does in fact end in U1. I'm not sure how that's possible with the T-Mobile firmware being there? Even stranger, my current functioning A36 is unlocked Verizon (boots up with Verizon logo and model number ends in V) and works perfectly with the Mint esim. So I feel like there's more going on here. Probably will end up returning since there's no clear solution in sight, but open to other ideas. Thanks!

[Mujibar]

You're right, everything that incorporates model number on that screen indicates a U1 device. But it's most definitely not running unlocked firmware (that would be XAA). It's very strange. If it were me, I wouldn't bother trying to figure it out any further. Good luck with the return!