Database Develop

Desperately Need Help - Samsung SM-N960F/DS + T-mobile PUK and other issues.....

Hi. I am a complete noob when it comes to rooting Android.
**************************UPDATE************************************************
THIS ISSUE HAS BEEN SOLVED. PLEASE SCROLL TO POST #89 ON PAGE 9 TO SEE THE SOLUTION.
https://forum.xda-developers.com/showpost.php?p=77950935&postcount=89
***************************************************************************************************
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".​
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.

orsonwells456 said:
Hi. I am a complete noob when it comes to rooting Android.
I bought an *unlocked* Samsung Note 9 N960F/DS (Exynos 9810) international phone from a seller on ebay brand new and sealed. Received the phone yesterday (10/19/2018) and popped my working existing sim card from my iphone 6 with T-mobile into the new phone and it *worked*.........except no wifi calling.
Since my house has terrible reception I really do need wifi calling in order to receive calls (I use Skype for outbound). I decided to root and install Detonator (tekhd) even though I've never done this before. Somewhere along the line I messed up and installed the latest LUX ROM because I misred Tekhd's guide on Detonator (my fault).
Here's where I stand now: I found a stock ROM for this model (N960F/DS) and reinstalled it using Odin3 v3.13.1.
After a successful flash when I insert my working T-mobile sim I get "SIM network PIN blocked. Enter SIM network PUK."
Here the Service Provider SW shows XEU/XEU,XEU/MYM
I get the *same* message when I insert a spare T-mobile sim I happened to have that was confirmed as available with T-mobile customer service. If I take the working sim out and put it back into the other phone it works without a problem. I think that rules out the sim cards having issues.
Earlier when I had the phone rooted and Detonator installed (and working), I got a different message when I inserted the SIM:
Network Lock: This device can be remotely unlocked if eligible.
Please use the "Device Unlock" application to unlock the device.
Make sure the device has an internet connectivity to use the "Device Unlock application".
Here the Service Provider SW showed TMB/TMB/MYM.
I tried looking for a T-mobile Unlock App apk to download but could not find a recent one. I would get a "Device not supported" error. It seems T-mobile has taken it off the Playstore.
Now, I can't install a stock USA ROM from T-mobile because those ROMS are only for the Snapdragon versions and I have the Exynos chip. I was given two unlock codes over the phone with T-mobile customer service to try and unlock the Pin lock but they both did not work.
Do you think an unlock service will be able to provide me with a valid "Sim Network PUK" code? I'm happy to pay for the service if I can just get the damn phone working. I've spent almost $770 on this phone and in hindsight should just have gotten the T-mobile branded phone for $100 more. I'm really at a loss as to what I can do to rectify this situation.
Also in hindsight I should have done more research before purchasing the phone and also should have backed up my partition in TWRP........You live and you learn.
The irony here is that I had an unlocked phone.....and now it has somehow gotten locked.........by the carrier whose SIM card is working perfectly fine......in a different phone. The device was paid in full btw.
Any help is greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.

bober10113 said:
this is a first. I always though once the region lock was lifted it couldn't be relocked( to me it seems to be a region lock issue, which if it is you need to make a 5 min call on region soil... good luck)
anyways check on your box there is a sticker with model and serial . find what carrier or region its from and grab that firmware and flash it. might want to factory wipe everything (including cache) in the recovery before booting it up indownlaod mode to do Odin flash.
also remove sim before wiping/ flashing, let it boot and do the initial setup then insert sim.
Click to expand...
Click to collapse
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.

orsonwells456 said:
I did wipe and reinstall the stock rom with the sim removed. The strange thing is..........I get the same message if I insert an old, blank, unused t-mobile sim into the device. Plus the working sim works fine in my old phone. So how could it be that the sim is locked?
There is nothing on the box that says anything about a carrier. This was advertised and sold as a factory unlocked phone which by all indications it does seem to be. The only thing on the box that says anything about country is that it was manufactured in vietnam.
Click to expand...
Click to collapse
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker

bober10113 said:
no sticker with device model or anything? not even in the back of the phone when it was new? a white sticker
Click to expand...
Click to collapse
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.

orsonwells456 said:
Yes there are stickers. But it is not associated with a carrier, specific region, or country. I just see IMEI info on the sticker on the back of the phone and S/N.
Click to expand...
Click to collapse
nothing like
SM-N960FOYAU1MYM or something?

bober10113 said:
nothing like
SM-N960FOYAMYM or something?
Click to expand...
Click to collapse
Ah ok. SM-N960FZBDMYM

bober10113 said:
nothing like
SM-N960FOYAU1MYM or something?
Click to expand...
Click to collapse
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it

bober10113 said:
btw I think detonator zip backup efs partition. did your issues arise before it after flashing it? if after try to find the backup and refresh it
Click to expand...
Click to collapse
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.

I went to a site with all "official" downloads and I don't see anything for ZBDMYM........

orsonwells456 said:
I was a dumbass and did not backup. I had zero issues other than no wifi-calling before trying to root and flash detonator...... Thank you for your help.
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
you can also download it using samfirm tool
enter 960F and MYM in settings it should also be a faster download then the web links

bober10113 said:
https://samsung-firmware.org/model/SM-N960F/region/MYM/
did you flash one of these?
these should be the original firmware U1 and the lates U2 which if you flash wint be able to downgrade bootloader but shouldn't be causing rhe sim lock issue.
flash U1 first and see if it fixes your issue. then try the October U2 just for fun
Click to expand...
Click to collapse
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.

orsonwells456 said:
My baseband version currently shows N960FXXU2ARH7 and Service Provider SW Ver. shows XEU/XEU, XEU/MYM. I will try loading U1 first and see what happens.
Click to expand...
Click to collapse
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
and in Odin fill in all slots and for csc use CSC but not HOME csc file.
good luck

bober10113 said:
ok so it's too late for U1 . ure phone is already on U2 latest bootloader. so flash the October build
but be sure to wipe all with no sim before flashing
Click to expand...
Click to collapse
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.

orsonwells456 said:
Should I take out sim, use TWRP to wipe, then go into download mode, Odin3=> flash rom? Thanks.
Click to expand...
Click to collapse
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
check for a folder called .backup and or for a file like:
efs_backup.img.gz
efs_backup.img
or anything similar

bober10113 said:
yeah might as well use tarp. and erase all. but before, did you sift through internal s or ext s for an efs backup that detonator might have made automatically?
Click to expand...
Click to collapse
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......

orsonwells456 said:
No, but I did download Dr. Ketan's tool to make an efs backup. But that was way later in the process....so it wasn't the original efs directory......It was after I flashed my current "stock" rom. I'm going to try and find another site to download since that one will take 2 days on slow speed......
Btw what does the ZBD mean? MYM I figured is Myanmar......
Click to expand...
Click to collapse
probably a date code of some sort. Samsung mashes a bunch if letters to come up with country,date code. just Google it.
but try samfirm 3.6 tool to dl
https://1drv.ms/f/s!AhXVLDDj8g3AgdJZClzJmsN17YL2CQ

I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4

If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......

orsonwells456 said:
I am using Samfirm and found this;
Model: N960F
Region: MYM
File: N960FXXU2ARJ1/N960FOXM2ARJ1/N960FXXU2ARJ1/N960FXXU2ARJ1
Verions: N960F_1_20181001162540_w0h1lv73k8_fac.zip.enc4
Click to expand...
Click to collapse
yeah looks good. its October 1st build
---------- Post added at 07:45 PM ---------- Previous post was at 07:44 PM ----------
orsonwells456 said:
If Install this ROM, does this mean my phone will be region locked to MYM again? I'm definitely confused on this......
Click to expand...
Click to collapse
well ure screwed either way. the goal is to restore everything back to stock and see if you can get a line working
btw was there a seal on the box that you had to break in order to open the box when you first got it?

Samsung Galaxy SM-N950F/DS stucked in boot loop, possibly wrong firmware installed

Hello dears,
One of my clients called me related to a problem with their Note 8 device. At first it sounded like a typically bricked device problem but after taking a closer look on some of the screenshots they've sent me with the device it really got me confused as to what had happened to the device. I don't have the device with me at the moment so the screenshots is all I have until the client arrives but I'm posting this thread in hopes to find out if there is any possibility of fixing the device so that I put the client on the road for nothing.
From what I understood the client tried rooting the phone and it got into a boot loop afterwards (I don't know the exact process of rooting that they've tried, that's all they said to me), they also said that they've been with the device to someone else afterwards and they've tried a few times to resoft the device with some ROM variants on the phone but they've "failed"to fix the device in the end and my client got bored of waiting for them to keep trying.
I thought the phone may be soft bricked and I asked them for some screenshots with the device so that I can see what firmware they were running and also a screenshot with the phone model details on the back and so they sent the screenshots to me and a few extra more.
Now, the first thing that I see is that the phone strangely runs or has ran a DIFFERENT firmware version for a DIFFERENT MODEL. If you look at the screenshots posted bellow, you will see that the phone is a SM-N950F/DS but runs an N9500 Firmware/ROM (Chinese I guess). I am confused, I haven't see that before. Is it possible that the guys working at the phone before managed to install a wrong firmware and hard brick the phone even more?
I see that the ROM that is currently shown on the phone is indeed an official/stock one from Samsung so I also wonder if that's how the phone actually came out on the shelf since the client told me that they've bought it from around that region. But still, the rom is clearly made for another model from the one written on the back of the phone so I don't really know what to say I haven't met with this issue before.
Also, judging by the screenshots offered what would be the steps you guys would make to fix the phone (if possible) and what exact rom version should I flash via Odin if anyone has an idea.
Should I flash the stock N950F/DS firmware or the N9500 CHC/TWN stock firmware? What would be the steps to bring this device back to life ? I appreciate your patience and I hope that the phone can still be revived.
Here are the screenshots (I apologise for the quality but this is what the client has sent at the moment).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.

stonedpsycho said:
He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.
Click to expand...
Click to collapse
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.

BrainwashedUser said:
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.
Click to expand...
Click to collapse
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...

stonedpsycho said:
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...
Click to expand...
Click to collapse
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.

BrainwashedUser said:
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.
Click to expand...
Click to collapse
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".

StevePritchard said:
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".
Click to expand...
Click to collapse
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?

BrainwashedUser said:
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?
Click to expand...
Click to collapse
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.

BrainwashedUser said:
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.
Click to expand...
Click to collapse
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?

BrainwashedUser said:
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?
Click to expand...
Click to collapse
I am unsure with all the errors but try using Odin 13.3.1.

Similar Issue
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.

awetsm said:
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.
Click to expand...
Click to collapse
Looks like you have a refurbished note 8 korean model N950N with replaced body and faked software N950F .
The motherboard is Korean so don't try flash N950F software on it will fail in odin it won't work.
Only N950N firmware will work only on your phone and you can flash android 9 pie but be careful if you flash N950N firmware you will lose N950F software and also dual sim will no longer will work too because possibly your dual sim also converted by software not Hardware. Because there's no N950N Exists with dual sim model.

Verizon G977U - Removed Carrier Bloat, Question about CSC

Hello, I have the Galaxy S10 5G on Verizon, SM-G977U. I'm currently running the latest Android 10 update: G977UVRS3YSL6. I moved away from Verizon and switched to T-Mobile, however I wanted to remove the carrier bloat, and potentially switch the CSC to XAA or TMO from VZW. I was able to remove all Verizon bloat by doing the following:
YOU MUST REMOVE YOUR GOOGLE ACCOUNT PRIOR TO THIS. YOU WILL TRIGGER GOOGLE FRP LOCK.
Opened the dialer and used the code *#272*IMEI-NUMBER#.
Saw two CSC codes, VZW - the active one, and a second one, GCF.
Switched to GCF, and the phone did a factory reset.
After the factory reset underneath Service provider SW ver. it listed GCF/GCF/VZW and all verizon carrier bloatware did not get installed.
So while that's nice to have removed the Verizon bloat, I wonder if I can take it one step further and switch the CSC to XAA or TMO. I'm lead to believe that I can change the CSC to one of those, because it appears since switching to GCF, also underneath Service provider SW ver. it lists the following: SAOMC_SM-G975U_OYN_GCF_PP_0009. This appears to be a Galaxy S10+ CSC code, would it then be possible to flash the SM-G975U or SM-G975U1 CSC codes onto the SM-G977U? And thus be able to change to XAA or TMO or any of the options of a unlocked firmware?

On doing your change from VZW to GCF, does that prevent OTA updates from Verizon?

psygnosi said:
On doing your change from VZW to GCF, does that prevent OTA updates from Verizon?
Click to expand...
Click to collapse
I believe if you have VZW as your current carrier, as long as you still get service, you will continue to get OTA updates.

Thanks.

furby_ said:
Hello, I have the Galaxy S10 5G on Verizon, SM-G977U. I'm currently running the latest Android 10 update: G977UVRS3YSL6. I moved away from Verizon and switched to T-Mobile, however I wanted to remove the carrier bloat, and potentially switch the CSC to XAA or TMO from VZW. I was able to remove all Verizon bloat by doing the following:
Opened the dialer and used the code *#272*IMEI-NUMBER#.
Switched to GCF, and the phone did a factory reset.
After the factory reset underneath Service provider SW ver. it listed GCF/GCF/VZW and all verizon carrier bloatware did not get installed.
So while that's nice to have removed the Verizon bloat, I wonder if I can take it one step further and switch the CSC to XAA or TMO. I'm lead to believe that I can change the CSC to one of those, because it appears since switching to GCF, also underneath Service provider SW ver. it lists the following: SAOMC_SM-G975U_OYN_GCF_PP_0009. This appears to be a Galaxy S10+ CSC code, would it then be possible to flash the SM-G975U or SM-G975U1 CSC codes onto the SM-G977U? And thus be able to change to XAA or TMO or any of the options of a unlocked firmware?
Click to expand...
Click to collapse
Also don't forget to remove your Google account from phone prior to this. It will reset and erase everything. You will trigger Google frp lock.

Unaccessible S10 5g
psygnosi said:
Also don't forget to remove your Google account from phone prior to this. It will reset and erase everything. You will trigger Google frp lock.
Click to expand...
Click to collapse
Hey, bud!
So I did the exact same process as OP in a Verizon s10 5G.
However, I made the mistake of not removing my Google account, when I start the phone I go through the process of select lenguage, blah blah, then choose wifi and click next it just loads and says I need to start the setup process again because I didn't log in to my Google account. However I'm not even able to type in anything, it just skips the whole typing process. I'm just stuck at setting up the phone... Can't do anything else. Do you know anything about this or how I can fix it? TIA

You'll have to Odin flash AT&T Firmware then back to Verizon I believe, or flash CSC. I don't quite remember.
I'm pretty certain it was flashing AT&T and then back to Verizon though, the reason for flashing the AT&T firmware is to force the CSC code to change, as VZW and GCF don't exist on the AT&T firmware.
Don't fret though, I did the same thing as you on my first attempt

Miguel1. said:
Hey, bud!
So I did the exact same process as OP in a Verizon s10 5G.
However, I made the mistake of not removing my Google account, when I start the phone I go through the process of select lenguage, blah blah, then choose wifi and click next it just loads and says I need to start the setup process again because I didn't log in to my Google account. However I'm not even able to type in anything, it just skips the whole typing process. I'm just stuck at setting up the phone... Can't do anything else. Do you know anything about this or how I can fix it? TIA
Click to expand...
Click to collapse
The way i got around this issue was to flash back to android 9. Once there you can log into your google account. Then remove your account and flash android 10. Now you can log in to android 10.

psygnosi said:
The way i got around this issue was to flash back to android 9. Once there you can log into your google account. Then remove your account and flash android 10. Now you can log in to android 10.
Click to expand...
Click to collapse
Did you flash with Odin or which program?
Where did you download update 9?

Miguel1. said:
Did you flash with Odin or which program?
Where did you download update 9?
Click to expand...
Click to collapse
Yes used odin. Got android 9 from sammobile.

psygnosi said:
Yes used odin. Got android 9 from sammobile.
Click to expand...
Click to collapse
Really appreciate your help bud. Will give it a try.

Miguel1. said:
Hey, bud!
So I did the exact same process as OP in a Verizon s10 5G.
However, I made the mistake of not removing my Google account, when I start the phone I go through the process of select lenguage, blah blah, then choose wifi and click next it just loads and says I need to start the setup process again because I didn't log in to my Google account. However I'm not even able to type in anything, it just skips the whole typing process. I'm just stuck at setting up the phone... Can't do anything else. Do you know anything about this or how I can fix it? TIA
Click to expand...
Click to collapse
i can help you. inbox me

furby_ said:
Hello, I have the Galaxy S10 5G on Verizon, SM-G977U. I'm currently running the latest Android 10 update: G977UVRS3YSL6. I moved away from Verizon and switched to T-Mobile, however I wanted to remove the carrier bloat, and potentially switch the CSC to XAA or TMO from VZW. I was able to remove all Verizon bloat by doing the following:
YOU MUST REMOVE YOUR GOOGLE ACCOUNT PRIOR TO THIS. YOU WILL TRIGGER GOOGLE FRP LOCK.
Opened the dialer and used the code *#272*IMEI-NUMBER#.
Saw two CSC codes, VZW - the active one, and a second one, GCF.
Switched to GCF, and the phone did a factory reset.
After the factory reset underneath Service provider SW ver. it listed GCF/GCF/VZW and all verizon carrier bloatware did not get installed.
So while that's nice to have removed the Verizon bloat, I wonder if I can take it one step further and switch the CSC to XAA or TMO. I'm lead to believe that I can change the CSC to one of those, because it appears since switching to GCF, also underneath Service provider SW ver. it lists the following: SAOMC_SM-G975U_OYN_GCF_PP_0009. This appears to be a Galaxy S10+ CSC code, would it then be possible to flash the SM-G975U or SM-G975U1 CSC codes onto the SM-G977U? And thus be able to change to XAA or TMO or any of the options of a unlocked firmware?
Click to expand...
Click to collapse
When you changed to GCF, did this remove the Verizon boot logo?
How to remove that?

Hi there!
First of all, thank you for the explanation! Everything went perfectly and no bricking occured.
Nevertheless, there's something that doesn't seem to be working. Since the wiping, the Setup Wizard can't finish the process. It keeps crashing and on a loop. There's a notification I can't even remove.
Did you encounter this problem too?
I'm attaching screenshots of the error message I'm getting.
By the way, do you know if this process is reversible if your current carrier is not American? If yes, how could I do so?
Thanks a lot!

I also have the same situation. have you solved this problem yet. Can you show me
I also have the same situation. have you solved this problem yet. Can you show me

For anyone who might still be wanting to do this, if you run the command you will be prompted with 3 choices. Network and Sales change, just network, and dev.
If you want to remove all Verizon bloat, you have to select network and sales change, however you will run into the issue above. Where the set up wizard will fail and crash but you can still add google/samsung/etc accounts and full set up the phone. The notification doesn't go away and if you try and run it again, it will just keep crashing.
The 2nd choice that won't cause that issue is just the network change. Pretty much will enable all bands/sets phone into global mode for network settings. BUT it keeps the Verizon bloat. (personally went from 1 bar to 4 in my house with tmobile sim in Verizon software phone)
I personally settled with the 2nd and just disabled what I could. So I didn't have any constant notifications and wasn't limited to Verizon's bands after getting the device unlocked.
Just something to keep in mind for those who are planning on or have switched to ATT software, you only have the DEV option.

Note 8 N950U1 stuck on 7.1.1 & Odin won't flash - Suggestions?

Specs:
Unlocked Samsung Galaxy Note 8 - N950U1
Product code: VZM
Baseband version: N950USQU3BRA5
Build number: NMF26X.N950U1UEU3BRA5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
Screenshots from About Phone and SamMobile app:
https://imgur.com/a/pcnbZZF
Been following guides on XDA and SamMobile to attempt flashing Odin the past 4 days with no success. It's an unlocked refurbished Verizon I got off eBay, but I've been using it on T-Mobile the past 2.5 years. Have tried both the Verizon and and T-Mobile firmware files (meant for N950U1) just trying to get to Android 9. At the moment I keep getting the message "All threads completed. [Succeed 0/Fail 1]" soon after pressing START. Do you have suggestions for what I can try next or what might be wrong?
It's also been brought to my attention that there's conflicting elements on the phone between N950U and N950U1 firmware and build. Not sure if this the source of all the trouble and if there's a way to fix it
Troubleshooting I've tried:
-Using various Odin builds (including patched)
-Making sure Smart Switch processes aren't running on computer during Odin flashing
-Waiting until the blue COM box shows in Odin
-2 factory resets of phone
-Updating through Smart Switch
-Buying a Verizon SIM to try initiating update
-Trying both N950U and N950U1 firmware

mountaineermh said:
Specs:
Unlocked Samsung Galaxy Note 8 - N950U1
Product code: VZM
Baseband version: N950USQU3BRA5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
Been following guides on XDA and SamMobile to attempt flashing Odin the past 4 days with no success. It's an unlocked Verizon I got off eBay, but I've been using it on T-Mobile the past 2.5 years. Have tried both the Verizon and and T-Mobile firmware files (meant for N950U1) just trying to get to Android 9. At the moment I keep getting the message "All threads completed. [Succeed 0/Fail 1]" soon after pressing START. Do you have suggestions for what I can try next or what might be wrong?
Troubleshooting I've tried:
-Using various Odin builds (including patched)
-Making sure Smart Switch processes aren't running on computer during Odin flashing
-Waiting until the blue COM box shows in Odin
-2 factory resets of phone
-Updating through Smart Switch
-Buying a Verizon SIM to try initiating update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
That's because you're trying to go from N950USQU3BRA5 which is N950U to N950U1 and I think Samsung eventually blocked going from N950U to N950U1 (someone else may know for sure) .. If you try downloading the N950U firmware instead it'll probably work.

MrMike2182 said:
That's because you're trying to go from N950USQU3BRA5 which is N950U to N950U1 and I think Samsung eventually blocked going from N950U to N950U1 (someone else may know for sure) .. If you try downloading the N950U firmware instead it'll probably work.
Click to expand...
Click to collapse
Thanks for getting back to me. An admin at SamMobile pointed out that my firmware and baseband don't match (my phone states that it's a N950U1 even though the baseband is N950USQU3BRA5). I don't know how this could be, as it's not something I did, but it's why I've been attempting the N950U1 firmware. In your opinion, is there a chance I'd mess something up even more by trying to flash the N950U firmware when the phone explicitly states in the "About Device" section it's an N950U1?

mountaineermh said:
Thanks for getting back to me. An admin at SamMobile pointed out that my firmware and baseband don't match (my phone states that it's a N950U1 even though the baseband is N950USQU3BRA5). I don't know how this could be, as it's not something I did, but it's why I've been attempting the N950U1 firmware. In your opinion, is there a chance I'd mess something up even more by trying to flash the N950U firmware when the phone explicitly states in the "About Device" section it's an N950U1?
Click to expand...
Click to collapse
What does it say in the About Phone section for build number? If they're all different versions that means your phone is a repaired device and they used different phone parts to get it to work and if you try flashing it it doesn't work and something could go through and then render the phone useless.

MrMike2182 said:
What does it say in the About Phone section for build number? If they're all different versions that means your phone is a repaired device and they used different phone parts to get it to work and if you try flashing it it doesn't work and something could go through and then render the phone useless.
Click to expand...
Click to collapse
Build number is NMF26X.N950U1UEU3BRA5
Baseband is N950USQU3BRA5
Here are screenshots:
https://imgur.com/a/pcnbZZF

If at anytime you are going from U1 to U or U to U1 you need to make sure and do a factory reset first. What I would do is download Phone Info app from playstore and use the app to do a refurbishment check. MrMike could be right with what he said. But you should not have any problems bouncing between U1 and U firmware. I do it all the time. You just have to make sure the bootloader is the same. Make sure you are using correct version of odin
Sent from my SM-N960U using Tapatalk

butchieboy said:
If at anytime you are going from U1 to U or U to U1 you need to make sure and do a factory reset first. What I would do is download Phone Info app from playstore and use the app to do a refurbishment check. MrMike could be right with what he said. But you should not have any problems bouncing between U1 and U firmware. I do it all the time. You just have to make sure the bootloader is the same. Make sure you are using correct version of odin
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I'm curious as to why his phone says N950USQU3BRA5 and also N950U1UEU3BRA5.. That's throwing me off. Haven't seen that before.

That is odd for sure. I'm wondering if its refurbished. There has been a lot of this exact same thing with devices bought off ebay.
Sent from my SM-N960U using Tapatalk

butchieboy said:
That is odd for sure. I'm wondering if its refurbished. There has been a lot of this exact same thing with devices bought off ebay.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
It was a refurbished phone from eBay, so I guess it all fits. I'm about to attempt flashing N950U firmware using the latest Odin, so hopefully that'll iron everything out

Just tried flashing the N950U firmware and it gave me the same fail message after trying to setup the connection. I used the official 3.14.4 build, the 3B Patched build, and the 3.12 PrinceComsy build.
I'm at a loss for what to do/try

Try finding user data for whatever carrier your flashing
Sent from my SM-N975U using Tapatalk

Question EUX CSC, HELP!

Hello, just got my S21 Ultra Exynos, and my CSC is EUX, no way to change it in ITV, flashed with odin with or without sim, but nothing. So samsung pay doesn't work, and i can't receive official update. What can i do?

Download Google Phone dialer from Google Play
*#*#27262826#*#* enter code
CSC list will open, Select CSC and install
WILL WIPE DEVICE

Just tried, but it doesn't work...

so, at last you can try to buy credits via ebay SamKEY CSC Change , using samkey.org program

nowy57 said:
so, at last you can try to buy credits via ebay SamKEY CSC Change , using samkey.org program
Click to expand...
Click to collapse
S21 Ultra in not supported

renton82 said:
Just tried, but it doesn't work...
Click to expand...
Click to collapse
Try flashing the first firmware ATLF and it might work, I noticed that I can't do it anymore on my S20 ultra with Januarys CUA update anymore so it might work if you flash back

Darbar1701 said:
Try flashing the first firmware ATLF and it might work, I noticed that I can't do it anymore on my S20 ultra with Januarys CUA update anymore so it might work if you flash back
Click to expand...
Click to collapse
Where i can find atlf firmware?

renton82 said:
Where i can find atlf firmware?
Click to expand...
Click to collapse
On Sam mobile or samfw , let me know how you get on,, look for BTU firmware, I think mine will be EUX too so I hope I does work

i just bought s21 ultra (998b) brand vodafone, i can't debrand it to install thai firmware, i tried flash with Odin with different firmware downloaded but nothing. I also tried to go back with firm vodafone. please help me find a solution

renton82 said:
Hello, just got my S21 Ultra Exynos, and my CSC is EUX, no way to change it in ITV, flashed with odin with or without sim, but nothing. So samsung pay doesn't work, and i can't receive official update. What can i do?
Click to expand...
Click to collapse
Did you by any chance set it up without a sim in - I did that with my s20 ultra and it went to EUX no matter how hard I tried factory reset with sim in I couldn’t get it to go to BTU
I ended up sending it back to Samsung as they said EUX gets updates but it doesn’t
try a factory reset with a uk sim in fingers crossed it trips theBTU but I think the only thing is to return it to Samsung and swap it

I'm also in this position! Received s21 ultra from Samsung UK, in the UK, UK sim but stuck with eux csc. Unable to change no matter what I've tried including factory reset. Unable to use samsing pay and no access to UK updates. Anyone have any solutions other than returning the phone? Also what would be the best way to get samsungs attention regarding this?

Did you set your phone up with a uk sim ? It’s a massive issue if it’s doing it with a uk sim
Only way is to email them as even though the phone is multi csc once it’s ok EUX you can’t access any of the others
just Out of curiosity which sim did you use

There is a thread on Samsung support
No Samsung Pay, no updates, stuck with EUX European CSC
I just received my S21 Ultra today and found that Samsung Pay displayed messages in German and would not work. Upon investigation it appears to be locked on the EUX CSC instead of BTU and as a result I also don't receive firmware updates. Reading around, it appears Italy had a similar issue...
eu.community.samsung.com

I found the following solution on samsung support
Turn off WiFi.
Remove SIM.
Power Off (not reboot).
Insert SIM.
Power On.
Enter Pin Code
It worked for me, so relieved

A new software update has been released yesterday and fixes this. You should receive it on your phones automatically, or check for the update.

It won’t update if not on BTU surely I am on XEU and it says no update available I am well and truly miffed now

I am returning the handset I am not paying over £1300 for a handset which is not fit for purpose I am so angry

mancuk010972 said:
I am returning the handset I am not paying over £1300 for a handset which is not fit for purpose I am so angry
Click to expand...
Click to collapse
I had the same issue (stuck on EUX on a Dec patch) booked a return and reset phone. Read this thread. Turned it back on, put a SIM card in and 900MB odd update was available with a Jan security patch. Will try it again now for a day, else this is going back.

Is this happening because you have to setup your phone on WiFi with the aim inserted or is it doing it anyway?

vnenwani said:
I had the same issue (stuck on EUX on a Dec patch) booked a return and reset phone. Read this thread. Turned it back on, put a SIM card in and 900MB odd update was available with a Jan security patch. Will try it again now for a day, else this is going back.
Click to expand...
Click to collapse
Weird. I've also tried that too but it doesn't work. It's like the Carrier update isn't being triggered?