Related
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
live_in_the_sky06 said:
I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
Click to expand...
Click to collapse
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Yeah I did that. I'll back up my data and flash the old update, factory reset, and then see if it'll pull the latest update. Thanks. I've read where a couple of people are having issues with ota updating
I brought my Sprint Note 9 to TM. I didn't flash anything, but couldn't get OTA updates. I know I could have flashed TM, but I was lazy. I called my TM experts. They called Samsung. Samsung looked up to see where the nearest Samsung tech was. It was at a Best Buy. She was in the Geek Squad area. She evidently flashed the TM firmware. After that I was able to get the TM OTAs. There was no charge for this. I happily upgraded to the 10+ 5G when TM got it. I love it! It also came with Android 10 on it.
scottusa2008 said:
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Click to expand...
Click to collapse
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
live_in_the_sky06 said:
... In the T-Mobile app my device shows as "Unknown device".....
Click to expand...
Click to collapse
This is normal since you brought your own device and didn't purchase it from T-Mobile.
live_in_the_sky06 said:
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
Click to expand...
Click to collapse
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
scottusa2008 said:
This is normal since you brought your own device and didn't purchase it from T-Mobile.
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
Click to expand...
Click to collapse
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
live_in_the_sky06 said:
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
Click to expand...
Click to collapse
Yes
scottusa2008 said:
Yes
Click to expand...
Click to collapse
Thanks for your help
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But for some reason, AT&T doesn't allow their firmware to be publicly available (for any of their devices). I pay for a subscription to a website that gets the official releases (usually) before they hit SamFirm/Frija, and also gives me access to AT&T firmware. So I'm providing it here as a favor to anyone who would make use of it.
Manual Odin flashing in this case would be designed for those of you who:
- want to flash AT&T firmware onto a T-Mobile or Metro device that has been SIM unlocked, in order to have AT&T's customizations and enhancements
- want to manually update to a newer version on your device, either because you don't want to wait for the OTA or because OTAs aren't working on their device (usually because you're using it on a different carrier because AT&T requires an active AT&T SIM to be inserted in order for their devices to successfully check for an OTA update)
This is not a "beginner's guide to Odin flashing"-type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware, I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=305872
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you.
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data
**I do not have one of these devices and this has not been 100% verified, until someone actually tries it. Until it's been verified, you're responsible for backing up your data, taking precautions to avoid an FRP lock, etc
- From what I've seen so far, there are some builds that only AT&T will get, some that only T-Mobile and Metro will get, and some that all 3 carries will get. Since T-Mobile (use region/CSC TMB) and Metro (use region/CSC TMK) firmware can be freely downloaded by anyone at any time from SamFirm/Frija, I won't be posting their unique builds here. I also won't be posting any builds that all 3 carriers get. U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside. So that means that any U firmware version (no matter the carrier) can be flashed to any U device (no matter which carrier's firmware it's running) at any time.
So I'll only be posting AT&T-exclusive builds and even then, I won't post every single one. I don't have unlimited bandwidth on my subscription site, and it takes a lot of time and effort to download the files, extract them, create the HOME CSC, zip them all back up, and upload them to AFH. I'll try to post at least one build per month though
- Switching from one carrier's firmware to another carrier's will require use of the USERDATA file, and also a factory reset. If you just want to manually update instead of waiting for an OTA, then you only need to flash the 4 base files (use HOME CSC if you want to avoid a factory reset).
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
I recently tried to install the tmb version of n976u att but when it starts it doesn't load that version and it still continues in ATT that I'm flashing bl, ap, cp, csc, what am I doing wrong?
dr.jonirafael said:
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
Click to expand...
Click to collapse
Not possible. No unbranded firmware exists for this model
Can I put the 976(5g) on the 975U?
JapAnEEzE said:
Can I put the 976(5g) on the 975U?
Click to expand...
Click to collapse
The answer hasn't changed since you last asked it.
(in other words it is still no)
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
fncd said:
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
Click to expand...
Click to collapse
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
iBowToAndroid said:
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
Click to expand...
Click to collapse
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
fncd said:
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
Click to expand...
Click to collapse
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
iBowToAndroid said:
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
Click to expand...
Click to collapse
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
fncd said:
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
Click to expand...
Click to collapse
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
iBowToAndroid said:
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
Click to expand...
Click to collapse
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
fncd said:
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
Click to expand...
Click to collapse
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
iBowToAndroid said:
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
Click to expand...
Click to collapse
So here's the thing. The first time I ever inserted my T-mo sim, I got a message about settings, and the phone restarted. It still wasn't T-mo branded, nor did it have any of the bloat (I think that is expected, no?). No other time did it ever ask me, even after being completely wiped. However, after the subsequent installs and wipes, I always had my sim in it.
Odin never threw an error, but of course, that doesn't stop me from potentially downloading the wrong firmware for my device, correct? But in reading your first post, the firmware should all be interchangeable, so I have no idea what caused it to want to see CDMA instead of GSM. Or the super wonky IMEI issue.
I'm on the way home now and will try it again, knowing that I still have the ATT firmware saved in case something goes wrong.
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
fncd said:
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
Click to expand...
Click to collapse
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
iBowToAndroid said:
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
Click to expand...
Click to collapse
When I first got the phone, it had the ATT ringtones on it, but I never noticed the boot screen being ATT. After the flash though, those were (and are) completely gone. And when I first put my sim in there, I didn't see any ATT apps on it at all.
Edit: Should have noted that I bought it used, but did confirm with AT&T that it was paid off and unlocked by them, but is it possible that the previous owner removed the apps with the *#2xxxxxx# code change? (he did claim to have worked for Samsung recently before moving to my area to another tech company...who knows if that's true or not). Unfortunately I couldn't get that code to do anything. Shrug.
---------- Post added at 12:09 AM ---------- Previous post was at 12:01 AM ----------
Looking at your page here: https://androidfilehost.com/?w=developers&did=4128
It looks like another user posted the T-Mobile flash for January. At least I know (or believe I know) that that will be another trusted source. I'm downloading that now in the hopes that it has the userdata and such in the zip as well. I will flash that over in just a few minutes and see what shakes out.
---------- Post added at 01:01 AM ---------- Previous post was at 12:09 AM ----------
Update: So here is where things get super weird and really have me wondering what is going on with this thing. If I try to flash the latest (march) TMB firmware, the phone boots and doesn't get signal (CDMA mode). If I reset the phone and then flash the latest ATT firmware (on AFH, I think it's February), the phone works perfectly, but still no ATT customization. So. If it holds true that the 4 base files are the same, then the only thing that can be causing that is something in the newer TMB userdata / csc files, right? As those are the only differences.
All of this being said and carrier bloat aside, the phone says it's on LTE+ right now, but the download speeds (according to ookla) are over 200mb (20Mb) / sec. Which, according to Venturebeat is the speed of T-Mobile's 600Mhz 5G service, which is plastered all over my area.
Long story short - As long as I'm flashing ATT Userdata / CSC, then the phone operates normally - though I won't get updates until I can get that XAA/XAA/ATT changed to ATT/ATT/ATT. Flashing any other Userdata / CSC after December 2019 causes issues with the radio.
I do appreciate all of your help, and while my post count is non-existent, I have done my homework as best I can before posting (constant lurker)
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
change csc
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
p3r1k0 said:
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
Click to expand...
Click to collapse
Was there anything that was broken or missing on the phone, after you changed it using the code? Were there any functions that did not work?
No luck for me
dr.jonirafael said:
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
Click to expand...
Click to collapse
For most devices, Tmobile even has in their forums how to flash to a different carrier. However, their directions require you to flash the "unlocked" version of the phone (XAA) first, then the carrier specific firmware to change it over. For the Note 10+ 5G, there is no unlocked version. Samkey lists the 5G as not supported. I have tried a flashing a few different ways to move my ATT version to Tmobile, and it always boots with ATT even after Odin saying it was flashed successfully.
Hi All,
My apps are updating fine and i see that android 10 has been out for a few months now yet my Note10+ SM-N975U is not updating at all. it seems my security patches are still stuck on august 2019 and every time i try to OTA update, it says my phone us up to date. Is there anyway to bypass this. I see everyone saying to use Odin to update my phone but i am not familiar with the program and where/how to source the note 10 update
Id greatly appreciate the help as its affecting many of my apps
NYKNick1015 said:
Hi All,
My apps are updating fine and i see that android 10 has been out for a few months now yet my Note10+ SM-N975U is not updating at all. it seems my security patches are still stuck on august 2019 and every time i try to OTA update, it says my phone us up to date. Is there anyway to bypass this. I see everyone saying to use Odin to update my phone but i am not familiar with the program and where/how to source the note 10 update
Id greatly appreciate the help as its affecting many of my apps
Click to expand...
Click to collapse
+1 for me. Ive spent almost 2 years and 3 phones trying to get an answer to this. My note 8 had this problem, then my note 10+, then the replacement note 10+. At&t blames Samsung, then Samsung blames at&t, over and over and over. I even had a Samsung technician sit in on a 3 way call with an at&t technician for the better part of an hour. The last I heard was that at&t was petitioning samsung to fix something on their end because at&t shows that everything is up to date on my phone but its not. Im looking into Odin too because this is getting stupid.
At&t is horrible with OTA's. They work for some but for a lot of people it does not, and I am one of them. At&t has never been able to give me an answer as to why this happened on my Note 8..9..and 10+.
Odin is very easy. You dont have to use At&t firmware you can use any Snapdragon US firmware they are the same. Once its installed, it will provision to you sim. There are many threads that have the firmware needed or just us Frija to download the firmware. Once downloaded you need to extract the files. You will have BL..AP..CP..CSC...HOME_csc. You need to download the correct version of Odin to flash the firmware. Open Odin put device in download mode connect device. Once odin recognizes devices find where you extracted the firmware. In odin put BL in BL spot..AP in AP spot..CP in Cp spot. If you want to save data, put HOME_csc in CSC spot. If you want clean install put CSC in CSC spot as it will wipe device. Once you have everything where it should be click start and Odin will flash the firmware. Once complete Odin will say PASS at top left..boot time should take a few minutes. But remember if the firmware you flash has a higher bootloader you cant downgrade back to previous version.
Sent from my SM-N975U using Tapatalk
So I can use a verizon csc and it will work on a att branded phone? Or is a generic one better?
Edit
Basically which one do you pick. I'm leaning towards a tmobile because it sounds like the included bloatware is smaller.
I have At&t device purchased at At&t. I have used USC..Tmobile..Verizon. The device will provision to your sim. If you dont want bloat just flash U1 firmware. But I think you will lose advanced features like wifi calling if you do. I cant remember if flashing a (U) csc with U1 firmware brings back advanced features. But prob just stick with 1 firmware until you have a understanding on how to do this...Good luck.
Sent from my SM-N960U using Tapatalk
butchieboy said:
I have At&t device purchased at At&t. I have used USC..Tmobile..Verizon. The device will provision to your sim. If you dont want bloat just flash U1 firmware. But I think you will lose advanced features like wifi calling if you do. I cant remember if flashing a (U) csc with U1 firmware brings back advanced features. But prob just stick with 1 firmware until you have a understanding on how to do this...Good luck.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I actually went ahead and did this last night with the tmobile firmware and it was just as easy as you said. For whatever reason I didn't even get any bloatware. It booted up with the at&t logo and sound, and my software version says att/att/att. I put my sim card back in and there were no special notifications or anything, everything just worked. I wonder if Frija gave me the att firmware despite me putting in tmb? Either way, everything is up to day now. Thanks for the help!
Anytime my friend glad it all worked out[emoji106]
Sent from my SM-N975U using Tapatalk
US to EU Automatic Updates
Hello!
Sorry if I'm posting in a wrong place.
Will Samsung Galaxy Note 10+ US SIM FREE, getting regularly (automatic) updates in Europe.
Thank you.
butchieboy said:
At&t is horrible with OTA's. They work for some but for a lot of people it does not, and I am one of them. At&t has never been able to give me an answer as to why this happened on my Note 8..9..and 10+.
Odin is very easy. You dont have to use At&t firmware you can use any Snapdragon US firmware they are the same. Once its installed, it will provision to you sim. There are many threads that have the firmware needed or just us Frija to download the firmware. Once downloaded you need to extract the files. You will have BL..AP..CP..CSC...HOME_csc. You need to download the correct version of Odin to flash the firmware. Open Odin put device in download mode connect device. Once odin recognizes devices find where you extracted the firmware. In odin put BL in BL spot..AP in AP spot..CP in Cp spot. If you want to save data, put HOME_csc in CSC spot. If you want clean install put CSC in CSC spot as it will wipe device. Once you have everything where it should be click start and Odin will flash the firmware. Once complete Odin will say PASS at top left..boot time should take a few minutes. But remember if the firmware you flash has a higher bootloader you cant downgrade back to previous version.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Hi I have the same problem. I flashed android 10 One UI 2.0 on my Exynos Note10+ SM-N975F last December via Odin and download the firmware from Samfrew(like Sammobile).(the firmware is the German version and I bought my phone from Egypt) Since then I didn't receive any security patch updates I only have the December 2019 one. Will it be safe if I download the latest firmware from Sammobile and flash it; the file in over 5GB , can this overwrite? I never tried to flash the same software two times. Is it safe?
As long as you are using the firmware that is for your device and your region you should be fine. Although this is Snapdragon thread I would think International flashing is same. You may want to double check in your device specific thread as I don't want to be the blame if there is something different with F version.
SM-N950U Extreme Syndicate Root
---------- Post added at 06:21 AM ---------- Previous post was at 06:11 AM ----------
Also try turning off auto update date and time. Set date like 5days ahead. Then check for update. Sometimes this little trick works for OTA
SM-N950U Extreme Syndicate Root
Robiko said:
Hello!
Sorry if I'm posting in a wrong place.
Will Samsung Galaxy Note 10+ US SIM FREE, getting regularly (automatic) updates in Europe.
Thank you.
Click to expand...
Click to collapse
Yes,i have u1 version and i receive update regulary,now waiting for oneui 2.1 [emoji3]
Greetings,
I'm super new here, also a tech noob so pls be gentle.
I purchased an unlocked At&T Note 10+, and i am living in Malaysia. Little that I know At&T would never send updates to out network, and that I require an At&t SIM in order to get the updates. Currently I am stucked with Android 9, ONE UI 1.5, with no hope of getting anything higher than that.
My question is, how can i get the updates besides flashing a new firmware? I tried connecting to Smart Switch on my laptop, and all it can says is that my software is up to date on SJ8 (ATT).
Hope there's a way other than flashing. HELP.
mohdazrimny said:
I want to thank everyone for the help. I have flashed my phone with the latest XAA rom, n all is running great. I have also received OTA May security updates.
Thanks again!
Click to expand...
Click to collapse
Hi Mohd Azrimny,
Am in the same boat as you. In Malaysia and have the note 10 plus at&t version. How did you manage? I am using Odin and getting error message connection failed. Not sure what is the problem.
Can you point me from where you downloaded the firmware? I am suspecting that is the culprit.
Thanks!
mohdazrimny said:
Greetings,
I'm super new here, also a tech noob so pls be gentle.
I purchased an unlocked At&T Note 10+, and i am living in Malaysia. Little that I know At&T would never send updates to out network, and that I require an At&t SIM in order to get the updates. Currently I am stucked with Android 9, ONE UI 1.5, with no hope of getting anything higher than that.
My question is, how can i get the updates besides flashing a new firmware? I tried connecting to Smart Switch on my laptop, and all it can says is that my software is up to date on SJ8 (ATT).
Hope there's a way other than flashing. HELP.
Click to expand...
Click to collapse
I'm sorry but I don't think there's other way around, you'll need to flash another firmware.
I have an Unlocked Verizon Note10+, the first thing I did after getting it out of the box was flash the unbranded firmware (CSC: XAA).
Ever since, I've had OTA updates as quick as they're released for N975U1.
joyousfrank said:
I'm sorry but I don't think there's other way around, you'll need to flash another firmware.
I have an Unlocked Verizon Note10+, the first thing I did after getting it out of the box was flash the unbranded firmware (CSC: XAA).
Ever since, I've had OTA updates as quick as they're released for N975U1.
Click to expand...
Click to collapse
I see...tq man. Can u help me out with one last thing? As they are thousands of firmware out there, which one should i choose? Can i simply choose any unbranded firmware (N975U1) from any month security updates n just flash it? I just need a stock ROM, not the latest should be ok as the OTA will take care of the rest.
Right now i'm at nov 2019 security updates SJ8 (ATT).
Thanks in advance.
mohdazrimny said:
I see...tq man. Can u help me out with one last thing? As they are thousands of firmware out there, which one should i choose? Can i simply choose any unbranded firmware (N975U1) from any month security updates n just flash it? I just need a stock ROM, not the latest should be ok as the OTA will take care of the rest.
Right now i'm at nov 2019 security updates SJ8 (ATT).
Thanks in advance.
Click to expand...
Click to collapse
Well, unfortunately I'm not sure about previous versions, however I'm leaving attached my SW information, my CSC is XAA.
You can download it from sammobile or frija (this is way faster).
Hope this helps,
Regards.
So, knowing you are a noob is half the solution already...
I highly recommend you look for Frija on the internet. Download the tool, search for the phone you have , it is a SM-N975U , and since you want to get rid from the AT&T version, you can install the SM-N975U1 version with XAA as CSC, that Samsung themselves push updates to. Even if they will not, you can always download the next revisions..
I assume you know how to use Odin..
joyousfrank said:
Well, unfortunately I'm not sure about previous versions, however I'm leaving attached my SW information, my CSC is XAA.
You can download it from sammobile or frija (this is way faster).
Hope this helps,
Regards.
Click to expand...
Click to collapse
Thank you man! For real!
BigE said:
So, knowing you are a noob is half the solution already...
I highly recommend you look for Frija on the internet. Download the tool, search for the phone you have , it is a SM-N975U , and since you want to get rid from the AT&T version, you can install the SM-N975U1 version with XAA as CSC, that Samsung themselves push updates to. Even if they will not, you can always download the next revisions..
I assume you know how to use Odin..
Click to expand...
Click to collapse
Yes i do know how to use Odin. Just soo terrified if i'd use the wrong firmware. I've also downloaded the firmware yesterday, but still not sure of it until now. So thank you, its clear now.
mohdazrimny said:
Yes i do know how to use Odin. Just soo terrified if i'd use the wrong firmware. I've also downloaded the firmware yesterday, but still not sure of it until now. So thank you, its clear now.
Click to expand...
Click to collapse
No worries, as Odin and the phone check revisions and suitability. If not the right firmware, it should not write it.
BigE said:
No worries, as Odin and the phone check revisions and suitability. If not the right firmware, it should not write it.
Click to expand...
Click to collapse
I want to thank everyone for the help. I have flashed my phone with the latest XAA rom, n all is running great. I have also received OTA May security updates.
Thanks again!
BigE said:
So, knowing you are a noob is half the solution already...
I highly recommend you look for Frija on the internet. Download the tool, search for the phone you have , it is a SM-N975U , and since you want to get rid from the AT&T version, you can install the SM-N975U1 version with XAA as CSC, that Samsung themselves push updates to. Even if they will not, you can always download the next revisions..
I assume you know how to use Odin..
Click to expand...
Click to collapse
Thank you!!!!!!!!:good::good:
joyousfrank said:
I'm sorry but I don't think there's other way around, you'll need to flash another firmware.
I have an Unlocked Verizon Note10+, the first thing I did after getting it out of the box was flash the unbranded firmware (CSC: XAA).
Ever since, I've had OTA updates as quick as they're released for N975U1.
Click to expand...
Click to collapse
hello, i know this an old thread, and yes. im also super super green and noob on all of this.. i too have Unlocked Verizon Note10+,
and after a month or so, it cant detect my local carrier as well (maxis) and i receive a message constantly about the sim is not verizon sim
so i was hoping , flashing the firmware would eliminate this problem
what i did was :
1) download odin v3.14
2)download frija 1.4.3
3) download firmware SM-n975u1 csc XAA from frija
4)tried to flash using odin..and failed multiple time
5)tried download a patched version of odin 3.14
6)download a bunch of other firmware from USA verizon, malayisia and others
7)failed and failed and failed again
so sifu please help me?where did i go wrong? will flashing new firmware fix my carrier problem? or its a verizon issue?because it was working fine a month ago ..please help..