I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
live_in_the_sky06 said:
I converted my unlocked US Note 10+ to T-Mobile. I am not receiving any OTA updates. My phone says that I am on the current software with December 1st Security patch.(the package I flashed in Odin) SL8 There is a January update available SLB but my phone doesn't see it. I know I can just manually flash it but it's kind of inconvenient. Anyone else able to pull updates after converting? In the T-Mobile app my device shows as "Unknown device" so I'm not sure if I should go back to the unlocked US firmware or try to figure if I goofed along the way. Thanks for any help.
Click to expand...
Click to collapse
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Yeah I did that. I'll back up my data and flash the old update, factory reset, and then see if it'll pull the latest update. Thanks. I've read where a couple of people are having issues with ota updating
I brought my Sprint Note 9 to TM. I didn't flash anything, but couldn't get OTA updates. I know I could have flashed TM, but I was lazy. I called my TM experts. They called Samsung. Samsung looked up to see where the nearest Samsung tech was. It was at a Best Buy. She was in the Geek Squad area. She evidently flashed the TM firmware. After that I was able to get the TM OTAs. There was no charge for this. I happily upgraded to the 10+ 5G when TM got it. I love it! It also came with Android 10 on it.
scottusa2008 said:
Did you use the non home csc when (and do the factory data reset after successfully) flashing the phone with T-Mobile firmware?
If you didn't then that can cause the issue your having with OTA.
Click to expand...
Click to collapse
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
live_in_the_sky06 said:
... In the T-Mobile app my device shows as "Unknown device".....
Click to expand...
Click to collapse
This is normal since you brought your own device and didn't purchase it from T-Mobile.
live_in_the_sky06 said:
So I flashed the old firmware, used the non csc file, hard reset and I still can't pull an ota. Not sure what's wrong.
Click to expand...
Click to collapse
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
scottusa2008 said:
This is normal since you brought your own device and didn't purchase it from T-Mobile.
Your not doing something right or have skipped/missed a step..
When flashing the t-mobile firmware do so in it's entirety. Be sure to use the userdata as well.
The flashing process is pretty easy and rather straight forward, but as a refresher follow the instructions at the bottom of this post
https://forum.xda-developers.com/showpost.php?p=80072192&postcount=1
Click to expand...
Click to collapse
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
live_in_the_sky06 said:
That may be the issue. The tutorial I used said not to flash the userdata. So when I do this again, I should flash the Tmobile userdata along with it.
Click to expand...
Click to collapse
Yes
scottusa2008 said:
Yes
Click to expand...
Click to collapse
Thanks for your help
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But for some reason, AT&T doesn't allow their firmware to be publicly available (for any of their devices). I pay for a subscription to a website that gets the official releases (usually) before they hit SamFirm/Frija, and also gives me access to AT&T firmware. So I'm providing it here as a favor to anyone who would make use of it.
Manual Odin flashing in this case would be designed for those of you who:
- want to flash AT&T firmware onto a T-Mobile or Metro device that has been SIM unlocked, in order to have AT&T's customizations and enhancements
- want to manually update to a newer version on your device, either because you don't want to wait for the OTA or because OTAs aren't working on their device (usually because you're using it on a different carrier because AT&T requires an active AT&T SIM to be inserted in order for their devices to successfully check for an OTA update)
This is not a "beginner's guide to Odin flashing"-type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware, I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=305872
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you.
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data
**I do not have one of these devices and this has not been 100% verified, until someone actually tries it. Until it's been verified, you're responsible for backing up your data, taking precautions to avoid an FRP lock, etc
- From what I've seen so far, there are some builds that only AT&T will get, some that only T-Mobile and Metro will get, and some that all 3 carries will get. Since T-Mobile (use region/CSC TMB) and Metro (use region/CSC TMK) firmware can be freely downloaded by anyone at any time from SamFirm/Frija, I won't be posting their unique builds here. I also won't be posting any builds that all 3 carriers get. U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside. So that means that any U firmware version (no matter the carrier) can be flashed to any U device (no matter which carrier's firmware it's running) at any time.
So I'll only be posting AT&T-exclusive builds and even then, I won't post every single one. I don't have unlimited bandwidth on my subscription site, and it takes a lot of time and effort to download the files, extract them, create the HOME CSC, zip them all back up, and upload them to AFH. I'll try to post at least one build per month though
- Switching from one carrier's firmware to another carrier's will require use of the USERDATA file, and also a factory reset. If you just want to manually update instead of waiting for an OTA, then you only need to flash the 4 base files (use HOME CSC if you want to avoid a factory reset).
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
I recently tried to install the tmb version of n976u att but when it starts it doesn't load that version and it still continues in ATT that I'm flashing bl, ap, cp, csc, what am I doing wrong?
dr.jonirafael said:
excellent post I have some questions, how could I have a completely clean N976U version, is there any firmware that is not with any operator? or can i install version u1 of 975n?
Click to expand...
Click to collapse
Not possible. No unbranded firmware exists for this model
Can I put the 976(5g) on the 975U?
JapAnEEzE said:
Can I put the 976(5g) on the 975U?
Click to expand...
Click to collapse
The answer hasn't changed since you last asked it.
(in other words it is still no)
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
fncd said:
Thank you for the link, it helped out more than you know. I have an unlocked N976U (originally on AT&T) that I tried to flash to T-Mobile. And for whatever reason, it didn't work. The phone kept telling me sporadically that there was no sim card installed, and the phone was trying to connect to service using CDMA instead of GSM. As you can guess, that doesn't work.
Considering that Samsung only sells one model of the Note 10+ 5G in the states, and that same model supports three different 5G networks, I have no idea why I cannot get this thing to work. I've never had a problem with a flash before (S9 / S10), but until I went back to the firmware above, I had zero network access. Currently the CSC shows XAA/XAA/ATT. While I know that the last one is the product code and will never change, the first two (XAA/XAA) should be able to be changed to TMB. The Dialer code that I attempted to use *#272*IMEI# Doesn't work either.
Any ideas on what I can try to get this thing up and running on T-Mobile with their branding and what not?
Click to expand...
Click to collapse
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
iBowToAndroid said:
Did you flash all 5 files, including USERDATA? Did it perform a factory reset?
Click to expand...
Click to collapse
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
fncd said:
It did in fact flash all 5 files from the TMB download that I had found. That is where all of my troubles began. Prior to that I wiped the phone, went into recovery, wiped it again and then rebooted to the boot loader. The first time I did it, the phone didn't even know what the IMEI was. It wasn't until I flashed the AT&T firmware that the IMEI came back. As it stands now, most everything is working, except that I'm still on the December patch and it doesn't find updates. I got it working around 2am last night using the older AT&T flash (SL3_1), so this evening I'm going to grab the N976U_TA4_1.zip from AFH that you posted and see what happens there.
I am totally clueless as to how all of the craziness occurred.
Click to expand...
Click to collapse
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
iBowToAndroid said:
What source did you get the firmware from? It sounds less-than-reputable, if it made your phone act that way afterwards
Click to expand...
Click to collapse
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
fncd said:
I found the build numbers on the web, but downloaded the actual files with SamFirm. I didn't see any of the TMB builds on XDA, so google became my friend (or enemy in this case).
Click to expand...
Click to collapse
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
iBowToAndroid said:
Did it boot up with the T-Mobile logo and all other T-Mo bloatware?
Click to expand...
Click to collapse
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
fncd said:
No. The phone never booted with the T-Mo logo. In fact, even now it boots with the Samsung logo.
I'm guessing that the XAA/XAA/ATT is what is causing that to happen.
If the phone were more popular it would be easier I think to find the firmware numbers and guarantee that I have the right one.
Click to expand...
Click to collapse
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
iBowToAndroid said:
Well SamFirm will only ever give you 100% correct official firmware, so as long as that's where you got it from, there shouldn't be anything wrong with it. You could try re-downloading it just in case, but I would have expected Odin to flag the md5 if it was an issue of a corrupted download, etc.
Not getting the T-Mobile bloat (assuming that you flashed all 5 files) is definitely strange.
Before you flashed anything, did you ever insert a T-Mobile SIM and see if it prompted you to restart to apply new carrier settings?
Click to expand...
Click to collapse
So here's the thing. The first time I ever inserted my T-mo sim, I got a message about settings, and the phone restarted. It still wasn't T-mo branded, nor did it have any of the bloat (I think that is expected, no?). No other time did it ever ask me, even after being completely wiped. However, after the subsequent installs and wipes, I always had my sim in it.
Odin never threw an error, but of course, that doesn't stop me from potentially downloading the wrong firmware for my device, correct? But in reading your first post, the firmware should all be interchangeable, so I have no idea what caused it to want to see CDMA instead of GSM. Or the super wonky IMEI issue.
I'm on the way home now and will try it again, knowing that I still have the ATT firmware saved in case something goes wrong.
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
fncd said:
I'll also make sure that the build numbers I found are indeed from the N976U, but I don't see how that could have been wrong. One question just to be sure... The region code for samfirm that I need to use would TMB, yes? Is there anywhere I can go to make sure I AM using the right build? I could only find the numbers with google.
Click to expand...
Click to collapse
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
iBowToAndroid said:
Yes, that's the correct region. You can flash any valid build that you want, but SamFirm will always only give you whatever the newest/latest version is.
When you first inserted the T-Mo SIM, did it remove the AT&T apps and bloatware?
Click to expand...
Click to collapse
When I first got the phone, it had the ATT ringtones on it, but I never noticed the boot screen being ATT. After the flash though, those were (and are) completely gone. And when I first put my sim in there, I didn't see any ATT apps on it at all.
Edit: Should have noted that I bought it used, but did confirm with AT&T that it was paid off and unlocked by them, but is it possible that the previous owner removed the apps with the *#2xxxxxx# code change? (he did claim to have worked for Samsung recently before moving to my area to another tech company...who knows if that's true or not). Unfortunately I couldn't get that code to do anything. Shrug.
---------- Post added at 12:09 AM ---------- Previous post was at 12:01 AM ----------
Looking at your page here: https://androidfilehost.com/?w=developers&did=4128
It looks like another user posted the T-Mobile flash for January. At least I know (or believe I know) that that will be another trusted source. I'm downloading that now in the hopes that it has the userdata and such in the zip as well. I will flash that over in just a few minutes and see what shakes out.
---------- Post added at 01:01 AM ---------- Previous post was at 12:09 AM ----------
Update: So here is where things get super weird and really have me wondering what is going on with this thing. If I try to flash the latest (march) TMB firmware, the phone boots and doesn't get signal (CDMA mode). If I reset the phone and then flash the latest ATT firmware (on AFH, I think it's February), the phone works perfectly, but still no ATT customization. So. If it holds true that the 4 base files are the same, then the only thing that can be causing that is something in the newer TMB userdata / csc files, right? As those are the only differences.
All of this being said and carrier bloat aside, the phone says it's on LTE+ right now, but the download speeds (according to ookla) are over 200mb (20Mb) / sec. Which, according to Venturebeat is the speed of T-Mobile's 600Mhz 5G service, which is plastered all over my area.
Long story short - As long as I'm flashing ATT Userdata / CSC, then the phone operates normally - though I won't get updates until I can get that XAA/XAA/ATT changed to ATT/ATT/ATT. Flashing any other Userdata / CSC after December 2019 causes issues with the radio.
I do appreciate all of your help, and while my post count is non-existent, I have done my homework as best I can before posting (constant lurker)
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
change csc
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
p3r1k0 said:
ms-n976u t mobile
i just to have same problem because i use the code *#272*imei and i change to xaa
my phone restart and no brand was on it like it was unlocked model not bloatware csc change to xaa/xaa/tmb
but the code to change csc did work anymore i try different ways but nothing help change firmware did help ether samtool not support
i try the realterm method didn't work
the only thing that work was buy 3 credits on ebay to samkey
change with samkey the csc to tmb and i get the updates right away and all the tmobile bloatware come back
well i post this just to let people be careful when using the *#272* imei code
Click to expand...
Click to collapse
Was there anything that was broken or missing on the phone, after you changed it using the code? Were there any functions that did not work?
No luck for me
dr.jonirafael said:
To be able to change XAA / XAA / ATT you must use samkey to buy 3 credits and change the csc to ATT or TMB if you want it to be t mobile
Click to expand...
Click to collapse
For most devices, Tmobile even has in their forums how to flash to a different carrier. However, their directions require you to flash the "unlocked" version of the phone (XAA) first, then the carrier specific firmware to change it over. For the Note 10+ 5G, there is no unlocked version. Samkey lists the 5G as not supported. I have tried a flashing a few different ways to move my ATT version to Tmobile, and it always boots with ATT even after Odin saying it was flashed successfully.
I have a ATT N976U note 10+5g which i'm using on verizon , it works great but each time att releases an update for it i cannot get it over ota and verizon only has updates for the N976V version. Does any one know where and how i can manually download the att updates to install them with odin afterwards ?
eddiemc12 said:
I have a ATT N976U note 10+5g which i'm using on verizon , it works great but each time att releases an update for it i cannot get it over ota and verizon only has updates for the N976V version. Does any one know where and how i can manually download the att updates to install them with odin afterwards ?
Click to expand...
Click to collapse
Years ago, I had the same issue with a Note 2,an AT&T version, but using it on another network (T-Mobile).
I had to go so far as to getting a month's worth of service w/pre-paid AT&T to connect to their servers to pull the update. Same a bit later with an LG device.
Fast forward to a year or two ago & some state this isn't necessary, but, it sounds like the same is holding true for you.
My suggestion is to find someone with an active AT&T SIMCard, see if you can borrow it to pull the update.
Another suggestion is to use Samsung's desktop PC tool Smart Switch, see if that works.
Otherwise, I'm stumped, unless you're familiar with Odin & someone here can locate the latest firmware to flash.
This should help with why your encountering difficulty finding (and a way to obtain) AT&T firmware.
https://forum.xda-developers.com/galaxy-note-10+/how-to/att-note-10-5g-n976u-firmware-files-t4059721
scottusa2008 said:
This should help with why your encountering difficulty finding (and a way to obtain) AT&T firmware.
https://forum.xda-developers.com/galaxy-note-10+/how-to/att-note-10-5g-n976u-firmware-files-t4059721
Click to expand...
Click to collapse
these haven't been updated in a while
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
What bloatware (and stuff) are you referring to regarding the VZW image?
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
The Verizon firmware isn't a "Verizon owned" firmware, it's just a variant that Google has released because when Google sent out the "global" firmware for testing Verizon reported issues with it, and it was too late to incorporate the fixes and send out another firmware to all carriers for testing.
The variants in firmwares have nothing changed in them other than the radio/modem/network files and maybe app versions if the variant had to be built at a later date and picked up a new app version in the build process. The firmwares are exactly the same. They don't come with any additional bloatware, because Verizon's networking specific apps are actually already included in the base firmware and are enabled/disabled on the presence of a Verizon SIM. The bloatware you are delivered is when setting up the phone and the setup wizard will offer the carrier bloatware to be installed depending on the carrier of the SIM.
Run the firmware designated for your carrier. You might have service issues if you don't, but it will run almost the same.
I ran the Verizon variant on my phone with T-Mobile and I got service just fine, however it appears that Verizon wanted the scaling for network strength to be changed because it reported 0 bars even though I had service. It also wanted to try really hard to latch onto mmWave, so it appears that Verizon wanted that and potentially more changed.
Just run the online flash tool from Google to get updated, or follow the tutorial threads in the help section.
cmh714 said:
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
Click to expand...
Click to collapse
You'll have to flash more. There's also the modem inside the image and there are also APNs and other files for networks on the system image or vendor image too, so it's really just best to take the whole firmware.
Ok so I should just flash over the global and so as usual then right?
stalls said:
Ok so I should just flash over the global and so as usual then right?
Click to expand...
Click to collapse
You mean flash the Verizon firmware over the global firmware you already have on your phone? Yes, it will be fine. You don't need to wipe the phone.
Long story short -- I originally got a Verizon Z Fold4 from Best Buy a few months ago but switched carriers to T-Mobile this morning. My Z Fold4 has the latest firmware from Verizon (still have all the Verizon bloat and Verizon boot screen), and I was wondering if there was a way to force it to download/install the latest T-Mobile firmware instead.
I have the latest T-Mobile firmware .zip (BVK3) from Sammobile but haven't been able to figure out if there's a way to install it.
allthemalarkey19 said:
Long story short -- I originally got a Verizon Z Fold4 from Best Buy a few months ago but switched carriers to T-Mobile this morning. My Z Fold4 has the latest firmware from Verizon (still have all the Verizon bloat and Verizon boot screen), and I was wondering if there was a way to force it to download/install the latest T-Mobile firmware instead.
I have the latest T-Mobile firmware .zip (BVK3) from Sammobile but haven't been able to figure out if there's a way to install it.
Click to expand...
Click to collapse
On the SamMobile download page there is a box at the top right, marked, "Instruction Files", that contain the full details on how to install firmware using the Odin PC suite.
[email protected] said:
On the SamMobile download page there is a box at the top right, marked, "Instruction Files", that contain the full details on how to install firmware using the Odin PC suite.
Click to expand...
Click to collapse
I imagine there's no way to do it if I only have access to a Mac right now?
allthemalarkey19 said:
Long story short -- I originally got a Verizon Z Fold4 from Best Buy a few months ago but switched carriers to T-Mobile this morning. My Z Fold4 has the latest firmware from Verizon (still have all the Verizon bloat and Verizon boot screen), and I was wondering if there was a way to force it to download/install the latest T-Mobile firmware instead.
I have the latest T-Mobile firmware .zip (BVK3) from Sammobile but haven't been able to figure out if there's a way to install it.
Click to expand...
Click to collapse
Just a question beforehand.. Is your unit unlocked (that way it can work with your new carrier)?
Switching from one carrier to another in terms of firmware is a simple process, Patched ODIN and get the firmware for TMO from SAMMOBILE for example and follow the instructions, try not to do a dirty flash (not wiping) to ensure better results.
joancolmenares said:
Just a question beforehand.. Is your unit unlocked (that way it can work with your new carrier)?
Switching from one carrier to another in terms of firmware is a simple process, Patched ODIN and get the firmware for TMO from SAMMOBILE for example and follow the instructions, try not to do a dirty flash (not wiping) to ensure better results.
Click to expand...
Click to collapse
Yes, it's unlocked and already switched over to T-Mobile.
Will patching ODIN flag Knox and void my warranty?
allthemalarkey19 said:
Yes, it's unlocked and already switched over to T-Mobile.
Will patching ODIN flag Knox and void my warranty?
Click to expand...
Click to collapse
It will not, I did this countless times with my S22 Ultra.
joancolmenares said:
It will not, I did this countless times with my S22 Ultra.
Click to expand...
Click to collapse
I just flashed the T-Mobile firmware via ODIN but I still have the Verizon boot screen and Verizon bloat. Not sure what I did wrong or what I'm not doing right
allthemalarkey19 said:
I just flashed the T-Mobile firmware via ODIN but I still have the Verizon boot screen and Verizon bloat. Not sure what I did wrong or what I'm not doing right
Click to expand...
Click to collapse
On a device that's been network unlocked, when you insert a different carrier's SIM, you should get a popup box prompting you to "restart and switch" to apply the new carrier's configuration. If you don't get that popup, then there are other ways to force the change, but it requires professional software
allthemalarkey19 said:
I imagine there's no way to do it if I only have access to a Mac right now?
Click to expand...
Click to collapse
See... https://www.droidthunder.com/download-jodin3-for-mac/