Context: I have a Verizon branded Note 10+, trying to use a Mint mobile connection. Wi-fi calling doesn't work, connection speed is atrocious, but everything works swimmingly out of the box when I put the same SIM in my unlocked Pixel. I am quite sure my Note 10+ is unlocked because it is fully paid off and well past the 60 day period, and more importantly because the Mint SIM DOES work in it, just very poorly.
So it's quite evident that I have to flash TMB firmware to get a serviceable reception.
Trying to follow the steps outlined here - https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648
Based on what I understand I have to flash unbranded firmware first and then my desired carrier firmware which is T-Mobile. Can someone please help me understand what firmware I should be looking for?
My current baseband version N975USQU3CTE7.
My question is when downloading through Frija, should I be looking for SM-N975U1 (VZW) firmware or SM-N975U1 (XAA) firmware for the first step? Or can I use either?
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
TheXev said:
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
Click to expand...
Click to collapse
To anyone reading this in future, I followed this guide to the letter and worked flawlessly for me..every feature that I wanted now works without any additional configuration..signal quality has improved drastically..
Thanks for taking the time to write this..took me a couple of days to set everything up and prepare..I am glad I didn't rush it
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.
Hello everyone, I have had my G960F/DS for over a month and I just discovered the Canadian CSC package from @_alexndr from his DevBase thread: "https://forum.xda-developers.com/showthread.php?p=76516024&postcount=497", but have an issue I hope can be resolved. When I do a clean flash of the CSC package followed by DevBase, I keep getting a new sim detected message which prompts to reset my phone to use it. If I agree to reset and restart, it gives me two service providers "Rogers" and no matter which one I choose, the phone reboots and displays the same message.
I believe the issue could be that since I have to install TWRP to install the CSC and the ROM package, that it can't provide the proper reset process so it just loops. I know people mentioned since the Canadian G960W is a Snapdragon processor that the CSC is not compatible, but the CSC actually works as I get the same signal strength as I did with my S7 on LTE, it just the phone wants to always reset to install the CSC bloatware and it can't do that at the moment.
I thought to open this thread as it is a question and not necessary an issue with the DevBase ROM, so any help would be great!
I posted on the Devbase thread the following to hopefully help anyone else having this issue. I did find a workaround though. I basically flashed the OMX Multi-CSC and I opened up the Canadian Zip file provided and pasted all the files in the '/odm/omc' folder besides the two sales_code and CSC_Version files. I then opened up the mps_code file in '/efs/imei' and changed the code to RWC and my phone booted with RWC active and no prompts to reset it. I did realize though that Rogers doesn't allow WiFi calling or VoLTE on non-Rogers IMEI devices so it was kind of a waste of time. At least my Signal Strength is where it should be lol.
There may be a better solution and even though I have flashed many ROMs and been on XDA for a few years, this issue was new for me and hopefully this helps for anyone. Of course do a backup of your EFS and ROM before doing anything like this to be sure.
Andrw0830 said:
I posted on the Devbase thread the following to hopefully help anyone else having this issue. I did find a workaround though. I basically flashed the OMX Multi-CSC and I opened up the Canadian Zip file provided and pasted all the files in the '/odm/omc' folder besides the two sales_code and CSC_Version files. I then opened up the mps_code file in '/efs/imei' and changed the code to RWC and my phone booted with RWC active and no prompts to reset it. I did realize though that Rogers doesn't allow WiFi calling or VoLTE on non-Rogers IMEI devices so it was kind of a waste of time. At least my Signal Strength is where it should be lol.
There may be a better solution and even though I have flashed many ROMs and been on XDA for a few years, this issue was new for me and hopefully this helps for anyone. Of course do a backup of your EFS and ROM before doing anything like this to be sure.
Click to expand...
Click to collapse
I'm so glad I came across this because I am in an identical situation: I came from an exynos rooted S7 and now just got a G960F and I want to flash a Canadian CSC (XAC or KDO) so that my signal strength is better. I'm finding that my LTE speeds are way slower and I'm only getting one bar of 4G+ with my koodo sim card.
I will give this a try and see what happens. I'm thinking maybe I should have gone with a (I think) rootable G9600 and flashed a W firmware on it but we'll see how this works.
Hi @Andrw0830, was there really any benefit of the RWC CSC? I have the same model as you on Rogers and haven't noticed any particular problems with signal strength. I was considering modifying mine so Samsung Experience/Pay/etc recognizes I'm in Canada.
moo113 said:
Hi @Andrw0830, was there really any benefit of the RWC CSC? I have the same model as you on Rogers and haven't noticed any particular problems with signal strength. I was considering modifying mine so Samsung Experience/Pay/etc recognizes I'm in Canada.
Click to expand...
Click to collapse
Mainly the signal icon I noticed either shows low signal even if I am in the same area I know is good or the signal icon won't change so that is mainly a cosmetic fix. You do have the options of WiFi and VoLTE, but I found out afterwards that Rogers doesn't allow you to activate them when you purchase the phone elsewhere so not much advantage. Really the only thing might be the Reverse number lookup feature allows you to turn on when using the Rogers CSC.
I just flashed the TMobile firmware through Odin and it looks identical to the unlocked firmware. The LTE did not change and I'm not getting video calling. Any suggestions?
stu5797 said:
I just flashed the TMobile firmware through Odin and it looks identical to the unlocked firmware. The LTE did not change and I'm not getting video calling. Any suggestions?
Click to expand...
Click to collapse
What is your firmware now? It sounds like it didn't update.
Sent from my SM-N975U1 using Tapatalk
Thanks for the response. Here is a pic of the firmware and the files I flashed from sammobile
stu5797 said:
I just flashed the TMobile firmware through Odin and it looks identical to the unlocked firmware. The LTE did not change and I'm not getting video calling. Any suggestions?
Click to expand...
Click to collapse
You first need to flash the unlocked firmware (U1), then boot up with your Tmobile sim installed. You'll see something about carrier settings being applied, and then you can go flash the U firmware
Read carefully through the steps from this thread: https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648
I am seeing the same thing as stu5797.
I purchased a Note 10+ Unlocked (blue, 256Gb), since the Unlocked had better trade-in value on my old phone.
Went to https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648 for flashing the T-Mo software, so I could get the carrier specific things.
Since I already had the U1 (as it was purchased unlocked), I did not re-flash the U1 package.
I installed my SIM card, booted the phone. Waited for it to say it was rebooting to apply carrier settings. Completed reboot. Shut down. Started in Download mode. Installed the USERDATA_TMB_N975USQU1ASGO_CL16450385_QB24967230_REV00_user_low_ship_MULTI_CERT.tar.md5 from the "U firmware" link. Booted after the install, and proceeded to set up my phone.
After I had done some significant setup, my phone informed me that there was a firmware update ready to go. I let it install, and it upgraded from SGO to SH4. Downloaded Phone Info to compare against Stu, and found everything identical, with the exception of a single character. My product code is SM-N975UZBATMB.
I do not see an option for video calling, no T-Mo boot animation, and no LTE+ indicator. Not sure what else might be missing/different.
I hope this description is helpful in figuring out where Stu and I went wrong. More, I hope there is a fix that doesn't require wiping the phone, as I've probably invested 8+ hours in setup on this one so far.
Thank you for any assistance.
I figured it out and you wont lose any data. Install this in Odin in the CSC spot HOME_CSC_OMC_OYN_N975UOYN1ASH4_CL16618444_QB25286449_REV00_user_low_ship_MULTI_CERT
from the "U firmware."
This wont wipe data and will give you all the Tmobile features like HD calling, 4g LTE, tmobile splash screen etc.
Hope this will help!
stu5797 said:
I figured it out and you wont lose any data. Install this in Odin in the CSC spot HOME_CSC_OMC_OYN_N975UOYN1ASH4_CL16618444_QB25286449_REV00_user_low_ship_MULTI_CERT
from the "U firmware."
This wont wipe data and will give you all the Tmobile features like HD calling, 4g LTE, tmobile splash screen etc.
Hope this will help!
Click to expand...
Click to collapse
If we flash this only we will lose OTA support yeah?
Sent from my SM-N970U1 using Tapatalk
stu5797 said:
I figured it out and you wont lose any data. Install this in Odin in the CSC spot HOME_CSC_OMC_OYN_N975UOYN1ASH4_CL16618444_QB25286449_REV00_user_low_ship_MULTI_CERT
from the "U firmware."
This wont wipe data and will give you all the Tmobile features like HD calling, 4g LTE, tmobile splash screen etc.
Hope this will help!
Click to expand...
Click to collapse
Yup, that did it!
Turns out, I had misunderstood the instructions to flash the U firmware alongside the Userdata file. The last time I fiddled with my firmware, it was all one file.
So I downloaded the TMB SH4 firmware, flashed the BL/AP/CP/HOME_CSC, and it looks to be working like a champ. Got the TMB splash on startup, 4G LTE icon, video call showing up in the dialer...
Thanks!
---------- Post added at 12:40 AM ---------- Previous post was at 12:36 AM ----------
EggNogg421 said:
If we flash this only we will lose OTA support yeah?
Sent from my SM-N970U1 using Tapatalk
Click to expand...
Click to collapse
I do not expect that this will cost you OTA support. I started with the SGO U1 software, flashed just the TMB USERDATA (didn't actually get any of the other files in there, because I misunderstood the instructions), and still got an OTA to SH4.
Ford thanks so much for the nice gesture but I could not accept. You are a very generous person. The reason why I can't accept is I am not an expert on this subject and should buy you a coffee. I only flashed that home_csc TMobile file and everything seems perfect but I don't get otas( not a big deal to me)
When you flashed Ford, did you also flash that TMobile userdata file with the TMobile home csc and the other TMobile files? Thanks buddy
This is all still quite confusing. I wish there was an updated thread with a set of instructions on exactly how to change the stock Unlocked phone to a T-Mobile or other carrier model with pictures or even a video with step by step.
I should be getting my backordered Note10+ Unlocked from Sammy in the next few weeks and this is the first thing I am going to do is make it a T-Mobile device will all the apps and boot animations. I'd like to have all my ducts in a row with everything downloaded and instructions in hand so I can hit the ground running on day 1.
BigMosley said:
This is all still quite confusing. I wish there was an updated thread with a set of instructions on exactly how to change the stock Unlocked phone to a T-Mobile or other carrier model with pictures or even a video with step by step.
I should be getting my backordered Note10+ Unlocked from Sammy in the next few weeks and this is the first thing I am going to do is make it a T-Mobile device will all the apps and boot animations. I'd like to have all my ducts in a row with everything downloaded and instructions in hand so I can hit the ground running on day 1.
Click to expand...
Click to collapse
It will work the same as the previous models. When you get your device, out your TMO SIM card in and let it provision for TMO.
Download the TMobile firmware. You'll get five files. BL, AP, CP, CSC, HOME_CSC, and USERDATA.
I'm assuming you have ADB, FASTBOOT, and Samsung drivers all set up on your computer.
Use ODIN 3.13.1_3B to flash the new firmware. Just place the files in the appropriate spots. Use CSC and ignore HIME_CSC.
Put your phone in download mode. I believe this year you shut it off, then while holding both volume up and down, insert the USB cable.
Then hit start on ODIN.
Mr. Orange 645 said:
It will work the same as the previous models. When you get your device, out your TMO SIM card in and let it provision for TMO.
Download the TMobile firmware. You'll get five files. BL, AP, CP, CSC, HOME_CSC, and USERDATA.
I'm assuming you have ADB, FASTBOOT, and Samsung drivers all set up on your computer.
Use ODIN 3.13.1_3B to flash the new firmware. Just place the files in the appropriate spots. Use CSC and ignore HIME_CSC.
Put your phone in download mode. I believe this year you shut it off, then while holding both volume up and down, insert the USB cable.
Then hit start on ODIN.
Click to expand...
Click to collapse
Should I completely boot up the Unlocked model and install the day one update first?
BigMosley said:
Should I completely boot up the Unlocked model and install the day one update first?
Click to expand...
Click to collapse
There's no reason to
stu5797 said:
I only flashed that home_csc TMobile file and everything seems perfect but I don't get otas( not a big deal to me)
When you flashed Ford, did you also flash that TMobile userdata file with the TMobile home csc and the other TMobile files? Thanks buddy
Click to expand...
Click to collapse
I thought about it a little more, and it is possible that we will lose the OTAs. When I flashed the USERDATA, I wasn't properly fully on the TMB SGO. It is possible that the OTA was the one intended for the U1, and that is what I got updated. I will keep an eye out for when TMB releases an OTA after SH4, and see if I get it then.
I would expect it to work properly, given that the hardware is identical, and, at that point, will be entirely on the TMB firmware.
The order I did things in was:
U1 boot with TMB SIM card inserted
Waited for "Reboot to provision carrier data" or something like that (very shortly after booting, did not set anything up)
Waited for reboots to complete
Booted into Download Mode, installed TMB USERDATA (SGO) with Odin
Thought I was properly on TMB firmware because I saw WiFi Calling in my settings, so proceeded to restore from Samsung Cloud backups / copy data with SmartSwitch
Several hours into this, received notification of OTA update to SH4
Allowed update to complete, continued working with phone
Next day, realized I was missing TMB boot animation, noticed this thread
Read through, provided my experiences
Saw your post on the fix
Went back to original flashing post, saw my mistake
Didn't see the SH4 firmware in the "U Firmware" link, so tried to get it another way
Got annoyed with SamMobile, found and downloaded Frija, installed the framework files necessary
Used Frija to download SM-N975U/TMB SH4 firmware
Extracted files from .zip
Flashed BL / AP / CP / HOME_CSC. Did not flash the non-HOME CSC, nor the USERDATA, as either would result in a wipe of the setup I had done so far
Rebooted, got TMB boot animation, waited a while for update (sat at boot animation for maybe a minute, give or take, looked frozen, was not)
Checked the phone, found LTE icon now read "4G LTE", contacts now had Video Calling as an option.
Phone Info now shows "Phone Model" as SM-N975U (pretty sure it was showing as a U1 before)
As far as I can tell, everything thinks I have a N975U/TMB as this point, so I expect things to work as though it were.
Oh, also, the other versions from Phone Info no longer match what you had posted earlier, stu. Attaching the Firmware page screenshot.
Edit:
On further review, the "Available CSC Codes" has also changed.
Was: ACG, AIO, ATT, BST, CCT, CHA, GCF, LRA, SPR, TFN, TMB, TMK, USC, VMU, VZW, XAA, XAG, XAR, XAS
Now: BST, SPR, TMB, VMU, XAS, ATT, CCT, CHA, GCF, USC, VZW, XAA
I flashed to TMobile (flashed all files but userdata) from unlocked, no wipe. When I got into updates I get the following:
I get that as well pcriz. I am assuming to get TMobile otas you have to flash all files including USERDATA. Flashing userdata will erase data so you should use the regular csc when flashing if you want true otas.
stu5797 said:
I get that as well pcriz. I am assuming to get TMobile otas you have to flash all files including USERDATA. Flashing userdata will erase data so you should use the regular csc when flashing if you want true otas.
Click to expand...
Click to collapse
Nothing I enjoy more than setting up my phone when I should be sleeping.
I'll give it a try, maybe that will bring back visual voicemail in the dialer
guys can you confirm that FM Radio tuner is not more enabled ?
wolfgart said:
guys can you confirm that FM Radio tuner is not more enabled ?
Click to expand...
Click to collapse
The app fails to connect. Could be disabled. Could be gone
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.
This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?
MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.
I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.
Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.
I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.
Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.
I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?
I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.
All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?