Develop Bugs

[Q] First timer with restoring Rogers GS3 to factory but keep unlocked

Hey there!
So here's my situation: I recently got rid of a Rogers cellphone plan and decided to sell my GS3. Someone I know, immediately showed interest and decided to buy it from me. Good! At that moment, the device was locked to Rogers and was running stock Samsung GS3 (SGH-i747M) firmware.
That person decided to play with the phone, try to root it, flash Cyanogenmod or whatever it may be, and having failed several times, he decided to return the phone and get his money back. I shouldn't have accepted to reimburse him knowing how much he fiddled with it but I did.
Anyways too late now. The good thing is that I believe the phone is 100% functional (it boots, runs perfect and under system info shows everything as usual except under Status > Device Status, it shows modified.
I am not 100% sure of that what means but I believe it has something to do with a modified ROM or something like that.
That person supposedly unlocked the device because he was with another carrier.
Now I am putting the phone in the classifieds. Obviously I would like to have the phone back to 100% factory settings and ROM, no aftermarket stuff whatsoever BUT I'd like to keep it unlocked (if that's possible).
That way, it will be easier to resell.
So here's my questions:
What does "Device Status: Modified" really means?
How can I find out if the phone has been altered in any ways?
If it has been altered, is there a LINUX based procedure to restore EVERYTHING back to factory?
If I restore whatever has to be restored, will it re-lock the device?
As you can see, I am a total noob in that field. I would appreciate if someone can help me to prepare this device to be resold.
I don't want to cause any problems to anyone, that wouldn't be fair.
I appreciate. Thanks!!!

Okay a lot of questions, you can download the stock firmware from Samsung updates and if it is rooted you can get triangle away on the play store and reset the counter the using kies or the Samsung galaxy s3 toolkit from mskip's to flash the original firmware, your phone should be unlocked as none of the procedures should/could reloj the simple card
Sent from my SGH-I747M using Tapatalk 4

jimchee said:
Okay a lot of questions, you can download the stock firmware from Samsung updates and if it is rooted you can get triangle away on the play store and reset the counter the using kies or the Samsung galaxy s3 toolkit from mskip's to flash the original firmware, your phone should be unlocked as none of the procedures should/could reloj the simple card
Sent from my SGH-I747M using Tapatalk 4
Click to expand...
Click to collapse
Ok I have verified with an app called Root Checker Basic, and it said that the device wasn't rooted. I wonder if this is reliable.
I wiull check mskip's toolkit or Kies to restore the stock firmware.
What a pain..
Thanks jimchee for replying!!

Actually it's pretty easy but you can probably sell it just as easy if it's rooted and that way you can clear the counter, there is also a post in the Samsung sIII THREAD for AT&T that will walk you through restoring to stock, just make sure you download the file for your device the link is also in the att thread, if you have any trouble pm me and I can help, I am just a tinkerer but been doing it since my 1st original Motorola Droid
Sent from my SGH-I747M using Tapatalk 4

Probably the easiest approach would be to look for the Samsung S3 V7.0 toolkit post. This is a flash (programming) tool. It would easily root your phone if it needs that. Then you can use the app referred to earlier to reset the phone to an "unmodified" status.
Then finally go to the Samsung updates site as suggested and flash the phone with a stock Rogers firmware. I'd recommend a 4.1.1. version. Probably your phone will still be unlocked at this point. But if not, the stock v 4.1.1. Rogers firmware will allow you to unlock it again from an onscreen menu (search for "S3 unlock code *#197328640#"). And your phone will report an unmodified status at the end.

mrwhite0732 said:
Hey there!
So here's my situation: I recently got rid of a Rogers cellphone plan and decided to sell my GS3. Someone I know, immediately showed interest and decided to buy it from me. Good! At that moment, the device was locked to Rogers and was running stock Samsung GS3 (SGH-i747M) firmware.
That person decided to play with the phone, try to root it, flash Cyanogenmod or whatever it may be, and having failed several times, he decided to return the phone and get his money back. I shouldn't have accepted to reimburse him knowing how much he fiddled with it but I did.
Anyways too late now. The good thing is that I believe the phone is 100% functional (it boots, runs perfect and under system info shows everything as usual except under Status > Device Status, it shows modified.
I am not 100% sure of that what means but I believe it has something to do with a modified ROM or something like that.
That person supposedly unlocked the device because he was with another carrier.
Now I am putting the phone in the classifieds. Obviously I would like to have the phone back to 100% factory settings and ROM, no aftermarket stuff whatsoever BUT I'd like to keep it unlocked (if that's possible).
That way, it will be easier to resell.
So here's my questions:
What does "Device Status: Modified" really means?
How can I find out if the phone has been altered in any ways?
If it has been altered, is there a LINUX based procedure to restore EVERYTHING back to factory?
If I restore whatever has to be restored, will it re-lock the device?
As you can see, I am a total noob in that field. I would appreciate if someone can help me to prepare this device to be resold.
I don't want to cause any problems to anyone, that wouldn't be fair.
I appreciate. Thanks!!!
Click to expand...
Click to collapse
Give this a shot.........works well. I've used it a number of times on both my phones ( SH-I747M/SH-I747 )
[ROM/RESTORE][AT&T/ROGERS/TELUS/BELL]Return to UNROOTED STOCK WITH FLASH COUNT RESET
http://forum.xda-developers.com/showthread.php?t=2363882
Once the phone is unlocked it will stay that way whether you go back to stock or not.

[Q] How to Network Unlock Galaxy S3 sgh-T999

I'm a bit of a noob, so apologies if this is in the wrong section. I've had a very difficult time finding threads that focus on those who have (stupidly!) applied the OTA 4.3 jellybean update, and what they can do to network unlock the phone. So here goes:
Samsung Galaxy SIII
SGH-T999
Android Version 4.3
Baseband Version T999UVUEMJC
Stock build. No root.
The closest step-by-step I've come across:
Remove T-Mobile SIM. Replace with ATT SIM. Reboot phone.
*#197328640# which successfully puts me into service mode.
This brings up the following menu:
MAIN MENU
[1]UMTS
[2]CDMA
[3]LTE
[4]SIM
From there its
[1]UMTS
[1] DEBUG SCREEN
[8]PHONE CONTROL
[6]NETWORK UNLOCK
[3]PERSO SHA256 OFF ...
Now, that's as far as I can get. The guide then says to go back to [6] and there should be an option, [4] NV INITIALIZZ.
This option is not there for me. (Note: at this point the PERSO SHA256 status is indeed set to SHA256_ENABLE_FLAG [0]).
Another guide suggested BACKing to the MAIN MENU and selecting option [5] run EFS SYNC() after selecting [3]PERSO SHA256 OFF.
I have done this and the screen reads: SYNC success. please reboot.
I do so, heart aflutter... only to be met with a SIM unlock PIN code entry screen.
Unlock fail.
Other threads have suggested downgrading to 4.1.1 in order for this to work and the necessary options be made available. Most of what I have read has said that attempts to downgrade from OTA 4.3 (with big brother KNOX) will result in a hard brick.
So, if you've made it this far... Has anyone figured out how to SIM unlock this particular phone running OTA 4.3 without rooting/downgrading?
If there is a more suitable thread discussing SIII's that are running 4.3 please direct me there.
Many thanks!

You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.

Perseus71 said:
You could try and flash a 4.1.1 Modem. After that, try the above process.
Note - In that process, you are required to be super patient at each step.
Click to expand...
Click to collapse
Appreciate the response.
Yes, most of what I have come across has indicated that I would need to get 4.1.1 by hook or by crook in order to network unlock the phone, having upgraded to 4.3.
I have some experience fiddling with such things, but many posts have also indicated that, with the new KNOX package in tow, backing down from 4.3 will hard brick this device. I am hoping that, with access to Service Mode, someone will discover a way to network unlock without root/flashing.
Thanks again!

Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.

Perseus71 said:
Are you Rooted ? If so flashing the LJC modem from Doc's thread won't brick your device.
Click to expand...
Click to collapse
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.

etrash310 said:
The phone is not currently rooted, no. Most rooting instructions I've seen are for 4.1.1 or 4.1.2. My guess is I'm going to have to root to unlock...
Could you direct me to instructions for rooting OTA 4.3?
Again, many thanks for taking the time to help.
Click to expand...
Click to collapse
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.

Perseus71 said:
Follow these. Effectively Flash Custom Rom using ODIN then flash SuperUser Zip.
Click to expand...
Click to collapse
Awesome. I will try this tonight.

etrash310 said:
Awesome. I will try this tonight.
Click to expand...
Click to collapse
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!

etrash310 said:
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Click to expand...
Click to collapse
So after all that, what is your current Rom and Firmware ? Can you try Root66 of 4.2 Rom ? Doc has Re-Hosted with mirrors.

I followed cLogic's guide that you linked to above and am running 4.3 rooted w/o Knox garbage.
Ended up getting phone network unlocked at a local hole in the wall phone shoppe. Figured it was worth a couple extra bucks to have it unlocked face to face in case code didn't work rather than fish out a reputable online source on my own.
Will be curious to compare its power usage to stock 4.3. Phone is working well, although it seems I will have to play with the APN settings as I am unable to send MMS messages... hmmm. Any advice off the top of your head?
I'd given root66 a try and also gave Doc's reposts another shot, but no dice.
So the sum of my endeavors are as follows:
1) If you want to network unlock your galaxy s3 on your own, DO NOT upgrade to jellybean 4.3 OTA until you do. It does not seem anyone has figured a way to ala ServiceMode in 4.1.1 yet.
2) If you have upgraded to 4.3 OTA you can use cLogic's guide linked to above to root your phone sans Knox.
3) If you have already upgraded to 4.3 OTA and want your phone network unlocked, you will have to pay to have it factory unlocked.
4) XDA is the bomb.

UPDATE:
Looks like the MMS messages I was trying to send finally went through... it just took an inordinately long time for them to do so.. not sure why yet.

Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.​
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.

since this worked on a note2, would it work on a sgs3 t999 that is already on 4.3?
fffft said:
Of dubious help to the OP, who had his phone commercially unlocked, but for others reading this thread or the OP's curiosity.. the 4.3 update has caused all kinds of grief. Amongst various bugs and battery drain issues, 4.3 has changed dialer codes or shuffled menus around. I can confirm the same results as the OP up to the point where he found that the initialize NV menu missing.
To progress further, I found that I needed:
An active SIM from a different carrier, with said SIM needing to be the phone throughout. This is in contrast to the previous method that worked without a SIM in the phone during the unlock procedure. I successfully unlocked a Note 2 with 4.3 using the steps in this techbeasts.com post.
And was successful with a 4.3 S4 using a slight variation (no NV initialize menu!.. back.. key input.. 1.. back). Both phones were M (Canadian) models.​
Reading between the lines of various reports in addition to first hand experience implies that there may be several different carrier specific dodges being employed here. Playing musical chairs with the missing menu items that now have different dialer codes, are now found on hidden sub menus (key input = 1) or in back up files.
The commercial unlock guys are using proprietary tools such as Samsung tool v 16.8. Which usually seem to be database based factory unlocks fetched (or calculated?) from their servers.
.
Click to expand...
Click to collapse

etrash310 said:
Well, no luck. Followed all the directions I could (provided by some awesome contributors including Doc) including:
1)Rooting using the aforementioned method and installing 4.3 with SU and no KNOX. Then just flashing stock modem 4.1.1 UVDLJC, in order to reveal the [4] NV INITIALIZZ option that is not present in Servicemode on jellybean 4.3 firmware.
--- This resulted in very slowed down system with no WiFi capability and no startup or shutdown sounds. Logging into Servicemode just resulted in a blank screen that said Servicemode.
--- Ultimately had to emergency restore firmware via KIES. (Thanks to reading a post by Doc on another thread). This got me up and running again.
2) Rooting using aforementioned method. And searching for stock 4.1.1 firmware in order to downgrade...
--- This has proven to be impossible. I can not find stock 4.1.1 anywhere. All links that have turned up have either been dead hotfile.com links or corrupted .zip files.
--- Additionally, I have been informed that once you upgrade to 4.3 OTA it is IMPOSSIBLE to flash an earlier firmware using ODIN. (Is is possible using CWM perhaps?)
In the end, it appears that the jellybean 4.3 OTA update currently has the community stumped as to how to unlock the SGH-T999 for use on another network with your only option to either convince T-Mobile to give you an unlock code or ordering one online. (And I've read of too many folks getting bogus codes ordering online...)
Still having fun trying, and its very cool to see all the hard work and info that folks like Doc are compiling on here. Maybe somebody is on the way to cracking this nut!!!
Click to expand...
Click to collapse
Well try this link .... http://forum.xda-developers.com/showthread.php?t=1949687

well i dont know if it will work for me because my t999 is running cyanogenmod 12.1

The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.

audit13 said:
The phone must be running stock 4.1.1 in order to sim unlock using the free method. Once the phone is on a 4.3 or newer bootloader, sim unlocking must be done using a code specific to the phone's imei. In order to enter the unlock code, the phone must be running a stock ROM or possibly a custom ROM based on a tw kernel.
Click to expand...
Click to collapse
So, I previously rooted my s3. It is locked to tmobile. Then I unrooted and tried to unlock it but of course after 4.3 update (LUVUBOH1 Big mistake I see! I tried to flash a different 4.3 stock baseband just to make sure I flashed stock rom but odin failed. I kept trying and even updated odin, but no dice. Any ideas??

Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.

audit13 said:
Do you have an unlock code? If not, you'll have to buy an unlock code and enter the code while running a stock ROM.
Click to expand...
Click to collapse
Yes, I did purchase an unlock code. I'm going to try a different sim. I THINK I'm running stock rom 4.3 LUVUBOH1.

When you insert a non T-Mobile sim, you're not prompted to enter a network unlock code?

Install stock SM-N910W8 on SM-910V

Hi, just bought an unlocked Note 4 from USA, it's the Verizon version.
I looked on your forum to find an answer, but I can't.
I'm from Canada, and I'd like to install a stock rom of the canadian version (n910w8), to have less Verizon/Amazon bloatware, and the french language available.
Considering that the N910W8 phone is pretty identical(from what I can see..), same CPU, would I brick my phone from installing this very rom "N910W8VLU1BOE2_N910W8OYA1BOE2_N910W8VLU1BOE2_HOME.tar.md5"?
And if so, why? And what are my alternatives?

see rooting and now you can unlock bootloader too first head to this post
then after that whatever your stock rom you can uninstall the blotware
here are another post for the blot which is safe to remove
and you can use that thing
I am using Indian sim and it is working great

'and you can use that thing'
That thing? The .md5 i mentionned?

When you boot the phone it says 'custom' and has a lock/unlock symbol?
You purchased it unlocked?

Futtermax said:
When you boot the phone it says 'custom' and has a lock/unlock symbol?
You purchased it unlocked?
Click to expand...
Click to collapse
I purchased it unlocked, but it has a Verizon logo whenever I boot it. So, would I be able to install the n910w8 without any trouble? Or is there a way to "install it" and during the process if it is not compatible it will tell it to me?

xDanny1992x said:
I purchased it unlocked, but it has a Verizon logo whenever I boot it. So, would I be able to install the n910w8 without any trouble? Or is there a way to "install it" and during the process if it is not compatible it will tell it to me?
Click to expand...
Click to collapse
He's trying to make sure that "unlocked" means that your bootloader is unlocked. It's a critical point, especially if your "unlocked" is referring to being open to all carriers.
If your bootloader is unlocked, you'll see an open padlock on the first boot screen. If the bootloader isn't unlocked, you won't be able to flash any ROMs until you unlock it.

douger1957 said:
He's trying to make sure that "unlocked" means that your bootloader is unlocked. It's a critical point, especially if your "unlocked" is referring to being open to all carriers.
If your bootloader is unlocked, you'll see an open padlock on the first boot screen. If the bootloader isn't unlocked, you won't be able to flash any ROMs until you unlock it.
Click to expand...
Click to collapse
Now, after a few more research I understand what you guys were trying to make me understand haha
I'm unlocking my bootloader, but my main topic question remain unanswered.
Will my phone be able to take the n910w8 rom even if I have a n910v? (once my bootloader will be unlocked and everything..)

xDanny1992x said:
Now, after a few more research I understand what you guys were trying to make me understand haha
I'm unlocking my bootloader, but my main topic question remain unanswered.
Will my phone be able to take the n910w8 rom even if I have a n910v? (once my bootloader will be unlocked and everything..)
Click to expand...
Click to collapse
The ROM, maybe. Will it work? Not without some serious help.
Since the Verizon variant of this phone isn't getting much developer love... it was locked until recently and true Developer Editions were rare and in smartphone terms, it's old... people are looking at the Snapdragon development.
The biggest headache will be getting the phone and data to work. The W8 is a GSM phone while Verizon uses CDMA.

douger1957 said:
The ROM, maybe. Will it work? Not without some serious help.
Since the Verizon variant of this phone isn't getting much developer love... it was locked until recently and true Developer Editions were rare and in smartphone terms, it's old... people are looking at the Snapdragon development.
The biggest headache will be getting the phone and data to work. The W8 is a GSM phone while Verizon uses CDMA.
Click to expand...
Click to collapse
Ok, I guess I could say I'm a superhero, my name, SuperStupid -_-
I finally got the padlock logo, rooted my phone, installed TWRP, tried to flash n910w8 rom, it didnt work, so I told myself, why not wipe everything, so I did.
Now I have a phone without OS, but! I kept the padlock and TWRP...
A new successful achievment for SuperStupid...
I'm currently downloading (with my superFast 1mb/s connection) the full firmware of N910V, which I didnt think prior to wipe everything, to keep a copy...
And I hope that I'll only have to put the file on my SD card, and then flash it...
I'll stay with my Verizon bloatware, as soon as I get it back, I won't try again soon to do this ****!!!

xDanny1992x said:
Ok, I guess I could say I'm a superhero, my name, SuperStupid -_-
I finally got the padlock logo, rooted my phone, installed TWRP, tried to flash n910w8 rom, it didnt work, so I told myself, why not wipe everything, so I did.
Now I have a phone without OS, but! I kept the padlock and TWRP...
A new successful achievment for SuperStupid...
I'm currently downloading (with my superFast 1mb/s connection) the full firmware of N910V, which I didnt think prior to wipe everything, to keep a copy...
And I hope that I'll only have to put the file on my SD card, and then flash it...
I'll stay with my Verizon bloatware, as soon as I get it back, I won't try again soon to do this ****!!!
Click to expand...
Click to collapse
You'll have to root again, ya know...

I have a Verizon Note 4 arriving today for use in Canada. The seller indicated that it is unlocked which I'm sure refers to the carrier and not the bootloader.
I've owned the Notes 1,2 and 3 and my most stable and satisfying experience was with the 3, not because it was the latest and greatest but because it was the only one I did not root and play around with. I'm getting older and I'm starting to value stability over features. I actually like stock touchwizz and enjoy the built in productivity of the spen. Carrier bloatware really is a minor inconvenience for me.
I've enjoyed the Note line but the Note 4 will be my last as the SD card and removable battery are very important to me. As long as this Verizon Note 4 gives me LTE coverage in the Greater Toronto area (which my research indicates it will) I'll keep it stock. A bonus would be if it shows up with Android 5.1.1 or is upgradeable via OTA or Kies. I don't really see any North American varient receiving Marshmallow and certainly not this Verizon one.

Can you flash N910W8 firmware/rom onto a N910V?
xDanny1992x said:
Hi, just bought an unlocked Note 4 from USA, it's the Verizon version.
I looked on your forum to find an answer, but I can't.
I'm from Canada, and I'd like to install a stock rom of the canadian version (n910w8), to have less Verizon/Amazon bloatware, and the french language available.
Considering that the N910W8 phone is pretty identical(from what I can see..), same CPU, would I brick my phone from installing this very rom "N910W8VLU1BOE2_N910W8OYA1BOE2_N910W8VLU1BOE2_HOME.tar.md5"?
And if so, why? And what are my alternatives?
Click to expand...
Click to collapse
Same here with a N910V wanting to know if N910W8 can flash ok to it. (but already unlocked mine with custom N910V roms on it) Been running LineageOS roms OK for a while but just too many bugs for something dependable.
Runs nice until you really need it not freezing on you lol.
Did try a custom W8 rom that was only flashable after installing TWRPCAN 3.0.2 in place of TWRP 3.2.3 and it did startup but phone ran really hot and broken WiFi so ended up going back.

N976U AT&T Note 10+ 5G Firmware Files Here

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 just need some help here...

I'm not sure where this should be posted.
I bought an unlocked S9 (SM-G960U) last February whilst flying through the US.
I knew something was fishy because even though it worked with my sim, the AT&T splash screen appeared when booting, but I was in a different country before I realised.
It's Android 8.0
Whenever I go to Software Update it says that i'm on the latest version of Android, nothing I can do to try and force this, tried Smart Switch, same issue. So my next avenue was to use a custom ROM or something - my experience with this is limited to many years ago (the Samsung Galaxy One!), and I believe it's a little easier now.
Anyway, I cannot flash or do anything, I've followed various guides, including to try and get TWRP on there but it looks like I cannot see the OEM feature to enable/disable in the developer tools options.
I'm hoping someone with a little patience can help me out a bit, I just want to get the best out of this phone (and Android Auto).

fakegeordie said:
I'm not sure where this should be posted.
I bought an unlocked S9 (SM-G960U) last February whilst flying through the US.
I knew something was fishy because even though it worked with my sim, the AT&T splash screen appeared when booting, but I was in a different country before I realised.
It's Android 8.0
Whenever I go to Software Update it says that i'm on the latest version of Android, nothing I can do to try and force this, tried Smart Switch, same issue. So my next avenue was to use a custom ROM or something - my experience with this is limited to many years ago (the Samsung Galaxy One!), and I believe it's a little easier now.
Anyway, I cannot flash or do anything, I've followed various guides, including to try and get TWRP on there but it looks like I cannot see the OEM feature to enable/disable in the developer tools options.
I'm hoping someone with a little patience can help me out a bit, I just want to get the best out of this phone (and Android Auto).
Click to expand...
Click to collapse
This device has a locked bootloader. possibly sim unlocked. You cannot flash twrp. No custom roms. Root at the best. You can search on how to use odin. Use a pc program called samfirm or frija to get the latest firmware to update

thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.

fakegeordie said:
thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.
Click to expand...
Click to collapse
You might have better luck cross-flashing your AT&T phone to unbranded firmware. See the thread here for more information. The best firmware to download and flash might be the SM-G960U1 firmware using the XAA CSC code. I flashed it on my unlocked Sprint S9 to de-brand it.

fakegeordie said:
thank you, this is helpful!
I downloaded Samfirm, and as typical with everything I'm trying, I've immediately hit a hurdle as ATT is not listed as a CSC code on there.
Click to expand...
Click to collapse
Yea att is hard to come by. M

Hai Karate said:
You might have better luck cross-flashing your AT&T phone to unbranded firmware. See the thread here for more information. The best firmware to download and flash might be the SM-G960U1 firmware using the XAA CSC code. I flashed it on my unlocked Sprint S9 to de-brand it.
Click to expand...
Click to collapse
thank you, I will try this if my other option fails...
So infuriating