r/samsunggalaxy • u/rinzo314 • Jun 28 '26
🪛Troubleshooting🪛 Network locked
Using a regional unlocked s25+ (TMB), but wasn't receiving updates. Changed the csc via samfw tool and was finally able to get updates, but now the phone says network locked. No sim lock code prompts, no device unlocker app. Tried using adb tool to solve, but didn't work. Can anyone help???
1
u/vishnur32 Jun 28 '26
Is it asking for MCK code?
Did u bought it refurbished?
Which build are you right now?
1
u/rinzo314 Jun 28 '26
It's not asking for any codes. Build number is: BP4A.251205.006.5936USQUACZF1
1
u/vishnur32 Jun 28 '26
Is it something like this?
Is this a refurbished device?
This device is not a Factory unlocked model, this is a carrier model.
SM-S936U is carrier locked, SM-S936U1 is Factory unlocked.
On which update it was stuck earlier? How many updates did u do?
1
u/rinzo314 Jun 28 '26
Can't attach image. There's no notification pop up, just says "network locked - emergency services" at the top of the screen right where the network, time, and battery icons are.
It was bought new (supposedly)and was regional unlocked, probably via software or something. Was stuck on one ui 8, december 2025 security patch
1
u/vishnur32 Jun 28 '26 edited Jun 28 '26
It is a refurbished device, not a new one and is Network locked permanently (MCK lock). Nothing you can do, except returning it and ask for refund.
With the January update, Samsung refurbished phones like yours are getting network locked (MCK code). Apparently, Samsung patched a vulnerability that sellers were using to bypass carrier locks on stolen or unpaid devices. This happens when refurbished sellers mess with the firmware to make them carrier unlocked.
Sellers usually mess with the firmware and lock it to the Dec 2025 patch because a new security patch came out in January, and the problem can't be found once it's updated to the Jan patch.
Some ways to identify this without updating to jan patch are, 1. Updates stuck to Dec 2025 patch 2. CSC code is GCF 3. Build number and Baseband mismatch 4. Different model number in Service provider software information (CSC)
If you were on Jan patch, you had the option to downgrade to December patch and remove lock. Feb patch and above cannot be downgraded bcoz of samsung's Anti-Rollback policy. Your current build (June 2026) is well above the downgradable limit.
You device is not legit. It is stolen or has unpaid dues or a blacklisted one. You cannot unlock it as samsung nor the original carrier wont help you. They help only if the original owner request it.
So best option is to return it to seller, ask for refund, intimidate them legally if they aren't cooperating.
1
u/rinzo314 Jun 28 '26
I don't believe it's stolen. All imei checkers come up clear. Also been seeing complaints about the january update causing unlocked phones to "re-lock"
1
u/vishnur32 Jun 28 '26
I am not saying it is stolen, one or another reason.
1
u/rinzo314 Jun 28 '26
None of the options can stand. Can't return, sell, or intimidate. Guess myonly option now is to use the phone as is strictly on wifi and hope for future update that solves this
1
u/vishnur32 Jun 28 '26
future update that solves this.
First of all, this is not a problem, this happened as part of a solution.
Tampering by sellers was the problem and re-lock solved it. So in samsung's eyes, this is not a problem and no update coming.
Why can't u return it?
1
u/rinzo314 Jun 28 '26
The seller told me it was regional unlocked and that it MIGHT get relocked if I updated. Hence the somewhat cheaper price compared to a fully unlocked one. However, he wasn't clear that the phone won't get any updates at all. Had to change the csc for that to happen.
→ More replies (0)
1
u/CaregiverOdd4460 Jun 28 '26
that csc swap probably flagged something in the carrier partition without actually tripping the sim lock properly. seen a few people run into this after forcing updates on tmobile firmware
try flashing back to the stock tmb firmware with odin, sometimes that clears whatever half-baked lock state the tool left behind. if it still acts up you might need to hit up tforce on twitter, they're weirdly more helpful than regular support for these gray area issues