Database Develop

Samsung Galaxy S6 (SM-G920T1)

I got my phone at Rent-A-Center, and got T-Mobile service on it. The phone worked fine for a while, until all of sudden I got a message:
Security Error
The phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.
Click to expand...
Click to collapse
So, I followed some instructions online, hooked my phone to the computer, and upgraded the firmware through Kies, which gave it a metroPCS ROM. I had been suspecting that someone flashed the phone before I got it from Rent-A-Center, but this really sealed it. So, I called T-Mobile, and T-Mobile tried to tell me that the phone was now locked to metroPCS and I had to call them. metroPCS said that they would not help. So, I had to do some work on it myself. I tried to find a T-Mobile compatible ROM, and before I did that I wiped the phone completely. Nothing will flash to it now, and it's in a bootloop. None of the flashes succeeded except that I was able to get a custom recovery on it. I can access TWRP and Download mode, but I can't successfully flash anything. Can I get some help?
Edit: I meant to append "Boot Looping" to the end of the title when I finished the posts body. I apologize.
Edit 2: I was finally able to get it out of the boot-loop by flashing a new bootloader, and flashing the stock ROM. However, it's back on metroPCS and still has that same message. How do I fix this?

IO.0 said:
I got my phone at Rent-A-Center, and got T-Mobile service on it. The phone worked fine for a while, until all of sudden I got a message:
So, I followed some instructions online, hooked my phone to the computer, and upgraded the firmware through Kies, which gave it a metroPCS ROM. I had been suspecting that someone flashed the phone before I got it from Rent-A-Center, but this really sealed it. So, I called T-Mobile, and T-Mobile tried to tell me that the phone was now locked to metroPCS and I had to call them. metroPCS said that they would not help. So, I had to do some work on it myself. I tried to find a T-Mobile compatible ROM, and before I did that I wiped the phone completely. Nothing will flash to it now, and it's in a bootloop. None of the flashes succeeded except that I was able to get a custom recovery on it. I can access TWRP and Download mode, but I can't successfully flash anything. Can I get some help?
Edit: I meant to append "Boot Looping" to the end of the title when I finished the posts body. I apologize.
Edit 2: I was finally able to get it out of the boot-loop by flashing a new bootloader, and flashing the stock ROM. However, it's back on metroPCS and still has that same message. How do I fix this?
Click to expand...
Click to collapse
Download Samsung Kies and try to do a firmware install by providing your model and serial number.

IO.0 said:
I got my phone at Rent-A-Center, and got T-Mobile service on it. The phone worked fine for a while, until all of sudden I got a message:
So, I followed some instructions online, hooked my phone to the computer, and upgraded the firmware through Kies, which gave it a metroPCS ROM. I had been suspecting that someone flashed the phone before I got it from Rent-A-Center, but this really sealed it. So, I called T-Mobile, and T-Mobile tried to tell me that the phone was now locked to metroPCS and I had to call them. metroPCS said that they would not help. So, I had to do some work on it myself. I tried to find a T-Mobile compatible ROM, and before I did that I wiped the phone completely. Nothing will flash to it now, and it's in a bootloop. None of the flashes succeeded except that I was able to get a custom recovery on it. I can access TWRP and Download mode, but I can't successfully flash anything. Can I get some help?
Edit: I meant to append "Boot Looping" to the end of the title when I finished the posts body. I apologize.
Edit 2: I was finally able to get it out of the boot-loop by flashing a new bootloader, and flashing the stock ROM. However, it's back on metroPCS and still has that same message. How do I fix this?
Click to expand...
Click to collapse
Flash it with the latest Metro PCS firmware, then you will have to get a unlock code from unlock base or your preferred unlocking company. After that it will work on T-Mobile and every other GSM carrier BUT you must keep the metro PCS bootloader and modem. I use a 920T with 920T1 bootloader and modem on the att network. I am running the tmobile twisted six rom + kernel with great success.

Quickvic30 said:
Flash it with the latest Metro PCS firmware, then you will have to get a unlock code from unlock base or your preferred unlocking company. After that it will work on T-Mobile and every other GSM carrier BUT you must keep the metro PCS bootloader and modem. I use a 920T with 920T1 bootloader and modem on the att network. I am running the tmobile twisted six rom + kernel with great success.
Click to expand...
Click to collapse
Flashing always fails for me.

Gthomas1216 said:
Flashing always fails for me.
Click to expand...
Click to collapse
Well metro uses that unlock app also now so I'm not sure that method even works anymore these days. Also you have to make sure the bootloader number is the same or above the metro firmware your trying to flash. Bootloader number is the fifth from the last number.

Quickvic30 said:
Well metro uses that unlock app also now so I'm not sure that method even works anymore these days. Also you have to make sure the bootloader number is the same or above the metro firmware your trying to flash. Bootloader number is the fifth from the last number.
Click to expand...
Click to collapse
I downloaded one from a tutorial and it failed on Odin then I downloaded 2 more metropcs firmwares from sammobile and they failed. I'll try to do what you said, find one similar to my bootloader.
---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------
Quickvic30 said:
Well metro uses that unlock app also now so I'm not sure that method even works anymore these days. Also you have to make sure the bootloader number is the same or above the metro firmware your trying to flash. Bootloader number is the fifth from the last number.
Click to expand...
Click to collapse
This method seemed to have took place in 2015 and I even saw posts of it working in late 2016. Do you by any chance know when metropcs started using an device unlock app?

Gthomas1216 said:
I downloaded one from a tutorial and it failed on Odin then I downloaded 2 more metropcs firmwares from sammobile and they failed. I'll try to do what you said, find one similar to my bootloader.
---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------
This method seemed to have took place in 2015 and I even saw posts of it working in late 2016. Do you by any chance know when metropcs started using an device unlock app?
Click to expand...
Click to collapse
Pretty sure they started using it when marshmallow was released.

Soft brick update custom rom to stock 6.0.1

I have a SM-G900V that was on a custom 4.4.4 ROM. I'm selling the phone and wanted to give a stock but updated phone to the guy.
I downloaded the latest for 6.0.1 for the Verzion G900V and flashed it in Odin. It got a write fail. I tried again and it went further but then got another write fail.
Now when I try to boot the phone it goes to Software update failed error. I can boot again by long holding the power button. The phone is still recognized in Odin.
The bootloader was unlocked
The emmc was 15.
The build number of the custom ROM was: Build: KTU84P- G900VRU1ANI2
I'll keep searching for a solution but the guy I'm selling the phone to is freaking out so any and all help would be much appreciated.

update
I tried flashing the same build as what was on the phone AN12 and it failed with an Auth fail error in Odin. I did some research and saw that could be a CSC problem. I tried using Kies because I read you can find the CSC code that way. I couldn't get Kies to 'talk' to the phone. It saw that a phone was connected but it wouldn't created the connection. I tried firmware recovery but I need the serial number and Samsung in its infinite wisdom doesn't put the serial number on the sticker inside the phone (at least it doesn't on US Verizon).
It's a phone from Verizon (originally bought on contract) in the US and I have been using US Verizon downloads from either updato or sammobile (for the 4.4.4)
I could realy use some help. I'd like not to bork the phone by just trying hail mary solutions.

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?

Please help! Flashing AT&T N960U firmware on N960U1 device with Android 10

Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!

You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk

butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.

butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?

Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance

abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.

Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?

Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version

robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.

I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?

Samsung SM-925A Updates and/or Custom ROM

I received a free Samsung S6 Edge from some friends. The phone had a busted battery which I fixed. The phone is still on the original 5.1.1 that the phone was released with.
When I try to do updates it says DM initialization not ready. Check network or SIM card. When I received the phone I was told it doesn't work with cell service. I checked to make sure and it definitely doesn't. There are no options for cell service in settings or the drop-down menu. This phone is missing IMEI numbers, IMEISV numbers, and baseband versions too. The only way I found out the IMEI number was it was printed on the back of the phone.
I am fairly certain the problems are software-based and not the motherboard but I don't know enough about phones to be sure. Do you guys know? I also want to remove AT&T from the phone to install a custom ROM on the device. (There is no OEM unlock in the developer options) Can I flash SM-925F firmware on the device to make it factory unlocked or will this brick the device? Will flashing the original SM-925A firmware fix the problems with the device? Please let me know if you need any more information to answer my question.

I found this: //G925A\\ Nougat 7.0.1 Latest Stock ATT Odin files G925AUCS7ERC1 | XDA Developers Forums (xda-developers.com) Should I flash this on my device? Will it fix any of the problems I had on it?

Can I flash the SM-925F firmware? Is the hardware of the factory unlocked phone and AT&T versions the same or will it brick this phone if I flash it?

Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.

skeltonh said:
Since the phone is AT&T you'll have to go through AT&T for the unlock codes before you can flash anything other than an AT&T ROM. To my knowledge there are no custom ROMS for the S6 Edge, but I could be mistaken.
Click to expand...
Click to collapse
I know this phone is old news however, I actually have the S6 and S7 edge lying around and so i got bored lol...here is my dilemma; Evidently the phone (S6 Edge G925A) had an abnormal factory reset, which is a load of BS, and now I can not get that security detail, which you know calling Samsung always ends to NO AVAIL!! I have flashed with Odin the firmware that my device is on the ERC1 firmware and still I get stuck @abnormal reset. I've searched numerous sites, different forums and still to no avail. Something told me inside that you was the man to drop a line to, any leads or info will be more than appreciated brother...Thanks for your time....
PSSS....
I got my unlock code from AT&T some time ago but the code is 16 digits long and code only takes 8 digits, and of course to hear AT&T tell it, " I simply must not putting the code in correctly"...lmao