Related
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
leprkon said:
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
Click to expand...
Click to collapse
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
Thanks for the prompt reply! I am downloading the file right now from sammobile. Let's hope it has everything needed! Thanks again!
Please let me know what worked, didn't. I may be doing the same very soon.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
leprkon said:
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
Click to expand...
Click to collapse
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
BlueFox721 said:
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
Click to expand...
Click to collapse
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
I failed to mention that you needed the modified Odin. I think it is normal for it to stop at 32% and then start erasing. It did the same when I went from unlocked variant to vzw. Keep us updated on your progress.
leprkon said:
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
Click to expand...
Click to collapse
The boot to bootloader is In the main recovery menu, but yeah...you need to use the modified odin
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
Support SINGLE-SKU
Supported API: 3
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
-- Installing package...
Finding update package...
opening update package...
Verifying update package...
Update package verification took 1.1 s (result 2).
Installing update...
Successfully installed package.
-- Resizing data...
E:failed to mount /data (Invalid Argument) can't mount '/data', rc = '-1'(Invalid Argument)
E:failed the resizing-data-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- amazon_symlink_vze...
-- Deleting VZW's apn file
Successfully deleted VZW's apn file
Successfully verify for dmverity hash tree.
Click to expand...
Click to collapse
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
leprkon said:
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
Click to expand...
Click to collapse
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
BlueFox721 said:
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
Click to expand...
Click to collapse
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
leprkon said:
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
Click to expand...
Click to collapse
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
BlueFox721 said:
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
Click to expand...
Click to collapse
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
leprkon said:
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
Click to expand...
Click to collapse
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
BlueFox721 said:
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
Click to expand...
Click to collapse
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
leprkon said:
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
Click to expand...
Click to collapse
Good to know....I try to use updato when available...how is that one?
BlueFox721 said:
Good to know....I try to use updato when available...how is that one?
Click to expand...
Click to collapse
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
leprkon said:
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
Click to expand...
Click to collapse
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...sorry I didn't think of it sooner...hope it helps.
Looks like we need factory binary and Canadian firmware...
BlueFox721 said:
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...
Click to expand...
Click to collapse
I've done version 3.12.7 and PC 3.12+
I'll try the carrier switching instructions again, but I couldn't get it to work properly. I'll let you know how it goes.
Edit -
It looks like those instructions require a factory binary firmware flash. Is there a way of doing it without that?
Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
quackmaster said:
Hi
I have a Note 9 which was originally purchased through Sprint. It's carrier unlocked. After moving the phone to Verizon it remains stuck in Roaming. Technicians at Verizon store clam they've never seen this problem before.
The network's shown as "Preferred System." Factory reset did not help.
I think the phone has Sprint firmware since the Sprint logo shows upon restart.
What works on phone:
Incoming / Outgoing Calls
Internet [around 60MBps]
SMS messages
What's broke:
MMS messages using default "Messaging" application
My wife's pretty upset about this problem.
I am running Linux Mint and familiar with Heimdall.
Do I need to flash Verizon firmware onto this phone?
Click to expand...
Click to collapse
Since you've already done a factory reset I would think the next logical step is to flash the Verizon or the unlocked firmware. What about the SIM card, did they try a new one?
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
quackmaster said:
They only tried one SIM.
When flashing with Heimdal do I simply need to download the Verizon firmware from SamMobile?
Click to expand...
Click to collapse
There is a thread somewhere in the guide section I recall seeing before from daillcyruz (I think was the OP). Search it and you will find instructions on how to install the VZ firmware.
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
quackmaster said:
I am getting an error with Heimdall that there's no firmware.xml.
Indeed the firmware from SamFiles does not contain any xml files.
Any idea how these can be obtained? Goggle does not seem to help.
Click to expand...
Click to collapse
Maybe try using Odin?
BladeRunner said:
Maybe try using Odin?
Click to expand...
Click to collapse
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
quackmaster said:
I do not have a Windows machine. Only Linux.
Maybe I can run a VM.
Click to expand...
Click to collapse
I ran across a thread where someone had posted a version of Odin that ran on Linux.
Here's one: https://forum.xda-developers.com/android/general/utility-odin-linux-jodin3-casual-t3777030
and another: https://forum.xda-developers.com/android/general/odin4-v1-0-linux-t3782930
None of these work. I am not able to get the PIT from device.
quackmaster said:
None of these work. I am not able to get the PIT from device.
Click to expand...
Click to collapse
you might be able to use odin in wine.. i never tried it tho.. heimdall i havent got to work either..
what firmware are you on? pie is pretty good at switchin csc based on sim inserted.. also crk3 i think it is you can access the csc.apk and change csc easily to any csc.. i havent found any other firmware it works on tho besides crk3..
if u can manage that, theres update.zips you can adb sideload but u need to b on specific firmware versions to update to certain firmwares..
i was messin around with firmwares and changed my csc to sprint.. i have vzw.. although it says roaming i am connected to verizon network so dont think its actually roaming but im not 100% sure
OK
Thanks everyone for help!
I was able to successfully flash using a Windows 10 VM running in Oracle VirtualBox VM. I used Odin v3.13_B. I did not re-partition.
I used this firmware:
https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U/VZW/download/N960USQS1ARJ9/242777/
There were no errors though after the phone rebooted it said there was an "unauthorized attempt" to install software.
It then tells me to connect to Wifi in order to verify my identity.
I cannot skip this process.
The Sprint firmware still seems to be present as I see Sprint applications. I am still roaming on Verizon though the port request was completed at least that's what they said at the store.
Interestingly the Sprint logo does not appear upon booting phone. Only the Samsung logo.
To remove Sprint firmware do I need to flash to the non-carrier firmware first before trying Verizon?
I sounds like someone else had the same problem with the SM-N960U.
The solution in that thread seems to be using the SM-N960U1 firmware.
Can anyone confirm this would be a safe fix to try?
SamMobile is a horrible website
I paid the 8 euro fee and the download for https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/VZW/download/N960U1UES1ARJ9/244757/ still takes like an hour.
It seems there's some Google phone protection targeted to deter thieves. That could be why it requires me to sign into the previous Google account after flashing.
I am removing my Google account from the phone, doing factory reset, then will try to flash Verizon firmware.
After flashing again it looks like some software called "Sprint OMDAM" still present on the phone. This loads after flashing. When I try to activate on network it comes up while the phone remains in roaming. Again Sprint unlocked the phone.
Should I re-partition?
OK
I wiped the cache partition and did factory reset.
I will yet again try another flash.
The Sprint logo is gone but Sprint apps still remain.
Should I try to re-partition the phone? I don't understand why Sprint applications are showing up when I flash Verizon firmware using Odin.
Make sure you have a Verizon SIM card in the phone.
1. Remove your accounts (Google and Samsung) under settings.
2. Factory reset under settings.
3. Download the U1 firmware using the SamFirm tool
4. Using modded ODIN 3.13.1B flash all four files (use CSC_OYN not the HOME_CSC file).
Optional, if you want WiFi calling and VoLTE:
Download the VZW N960U firmware using the SamFirm tool and flash it the same way using modded ODIN, but this time include the USERDATA file as well.
I think now on Verizon network after using U1 firmware!
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
ww007 said:
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
bober10113 said:
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
Click to expand...
Click to collapse
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
ww007 said:
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
Click to expand...
Click to collapse
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
bober10113 said:
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
Click to expand...
Click to collapse
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
ww007 said:
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
Click to expand...
Click to collapse
just use samfirm tool or frija to dl firmware.
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?
Hello all,
I have an S21 Ultra that was originally a T-Mobile device, was unlocked, and then flashed to "factory unlocked" 998U1 firmware as found on this forum, and used with AT&T. Since the shutdown of their 3G network, however, I have been unable to make or receive calls and the "Enhanced LTE Services" option under Network Settings is unavailable to me. After a ton of fruitless troubleshooting, AT&T says I need new firmware. I was going to install the AT&T-branded U1 firmware from SamMobile in hopes that would solve my issue, but whenever I try to go to the bootloader to flash the new firmware, the phone just boots normally instead. I can't seem to access the bootloader, even after factory resetting the device.
Samsung has offered to reflash the device back to factory settings, which would make it a T-Mobile device (unlocked, presumably?) again. Does anybody know if the AT&T firmware linked above will work with VoLTE on their network? Would I be able to flash to that again to get the bloatware-and-branding-free experience while still having the device work as a phone?
Thanks for any knowledge or help, I've been beating my head against this thing for nearly a month now.
I may have solved my issue! Fingers crossed, will confirm tomorrow once I'm sure, but so far, here's what it looks like:
I had installed what I believed to be standard Samsung U1 firmware which I assumed would work regardless of carrier - I believe from this thread but don't quote me on that. Regardless, it was unbranded. When AT&T shut down their 3G network, I was hosed because the U1 firmware I'd installed did not have VoLTE/"Enhanced LTE Services" or anything like that as an option I could enable. After a ton of time, I finally figured out that it was a firmware/baseband issue.
So I downloaded the AT&T "branded" U1 firmware from SamMobile but the recovery menu wouldn't let me access the bootloader for as-yet-unknown reasons. The instructions to hold volume-down+power got me into the recovery menu, but that was as far as I could get. However, Iater discovered that with the device plugged into my computer, I could boot it directly into the bootloader by holding volume-down+volume-up. With that accomplished, I installed the AT&T U1 firmware and viola! VoLTE options were available, and with my SIM card installed I could finally make calls again!
Will use it all day tomorrow, see how things go and report back.
Could you help me i am basically in the same boat! What firmware for at&t did you download and where? Thanks!
I used the firmware at this link: https://www.sammobile.com/samsung/g...M-G998U1/ATT/download/G998U1UES5CVCB/1627452/
I couldn't get to the bootloader from the recovery menu, but could by using both volume keys simultaneously while the phone was powered off and plugged into the computer. Good luck!
There's a good thread on Reddit regarding CSC issues when flashing branded S21 devices to U1 firmware. Essentially, on the S21 series, particularly for TMB CSCs, it tends to be difficult to get the correct CSC software for VZW and ATT, particularly after flashing to U1 from U firmware. See this,
https://www.reddit.com/r/GalaxyS21/comments/roqwkc