Develop Bugs

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!

If you're in Canada then just flash the Canadian firmware.

ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!

LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.

ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!

LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.

ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?

Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html

Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?

TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362

ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.

LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.

ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?

Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:

You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.

I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?

OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.

Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!

is it possible to downgrade P to O? (and keep knox)

EDIT: it is possible, and worked just fine for me
- - - - - - - - - - - - - - - - -
Hi guys.
recently got a used s9, did all the updates (for security updates) and didnt even look, just kept updating and find myself on android P.
I've played around with it and found it less intuitive and pretty lacking in some regards. (and may possibly have some issues relating to the OS too; battery and phone)
software updates says:
Code:
current version: G960FXXXXU2CRLO / G960FOXXM2CRLO / G960FXXXU2CRLI
Security patch level: 1 January 2019
SM-G960F, Phone status: Official, baseband version G960FXXU2CRLI, Kernel version: 4.9.59-15076275, build verison: ppr1.180610.011.G960FXXU2CRLO
I'm wondering if it's possible to flash back to official Android O, while retaining untripped KNOX. (having KNOX in a usable/official status)
I've read online that it should be possible to do, but talk of using the "OEM unlocking" option has me weary.
I dont want to blindy follow a guide to find i've broken KNOX or have a brick.
some of you guys are pretty cluey. so i thought it be a good first place to ask.
cheers

Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
PoochyXXX

PoochyX said:
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
Click to expand...
Click to collapse
Hmm, thats what I'm afraid of.
The downgrade guide i mentioned was here:
https://techbeasts.com/downgrade-ga...xy_S9S9_Plus_to_Android_Oreo_from_Android_Pie
not sure how legit it is though.
I havent read anything on XDA on the forums here, hence my new topic.

Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine

*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
Ohhh
PoochyXXX

*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
AP_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship_meta.tar.md5
MD5: 4ECA2C5657506ADE7B9D3B1721B0F958
SHA1: 14063F2CF282E37C2C7D59D80FFF404C400D306D
BL_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship.tar.md5
MD5: 9529200BCE0C339B04152AC27DE34F5E
SHA1: 1821D68544490355042E7BF1589F2284FEF76324
CP_G960FXXU2BRJ1_CP10881699_CL14479316_QB19997556_REV01_user_low_ship.tar.md5
MD5: 8E07784192BCAF0454AB079ECBBD150D
SHA1: E7EFC1ED9E35C7B1F235792FAF46AFCAA945FF38
CSC_OMC_OXM_G960FOXM2BRJ3_CL14479316_QB20051937_REV01_user_low_ship.tar.md5
MD5: 17932E611CB0DF71C7B91BA84186843C
SHA1: 6BEE275DCC778124CB1EBF88EFA087538D9DCBE3
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.

tim455 said:
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
Click to expand...
Click to collapse
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October

*Detection* said:
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
Click to expand...
Click to collapse
Thanks for all the helpful information.
Downloading again now just to check hash comparison.
AP SWAEV: B:2 K:2 S:2 -- looks good.
I'll reply back in a few hours with my results.
Many thanks.

many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
To understand that you are downloading the BRJ6 firmware ?
Thx.

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
:good:

dinamo1975 said:
To understand that you are downloading the BRJ6 firmware ?
Thx.
Click to expand...
Click to collapse
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
*Detection* said:
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
Click to expand...
Click to collapse
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.

tim455 said:
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
Click to expand...
Click to collapse
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin

*Detection* said:
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
Click to expand...
Click to collapse
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)

tim455 said:
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
Click to expand...
Click to collapse
Not really, I am running DBT firmware with XEU CSC just because the DBT firmware updated first, once XEU releases the same update I`ll flash back, and so on

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
What was the bootloader version of the Android 8 vs the version you had on Pie? Did you downgrade the bootloader as well?

can the same method be used to go down from 10 to 9? i have snapdragon 960w

Help with flashing U1 firmware to my Verizon G960U

.

DetectiveTaco said:
I have a Verizon locked Galaxy S9 (G960U) and I want to remove all the carrier branding and crap since. With the US Snapdragon Samsung devices having the bootloader locked and preventing the ability to root or flash custom ROMs this is the only way I can get rid of the carrier branding garbage. Though there is so many firmwares and different versions of the G960U1 firmware that I don't know what to get. Or which version of Odin I need or what to do to flash using Odin. If anyone is willing to help and walk me through this process that would be amazing because there is no good detailed step by step guides or videos on YouTube on how to do it. Or they aren't recent.
Click to expand...
Click to collapse
get the patched Odin here
and the latest U1 firmware here
put the 4 files from the firmware in their respective spots, using CSC to factory reset the phone and HOME_CSC to flash the firmware without resetting.
let me know if youre not familiar with Odin enough to understand what im getting at

.

DetectiveTaco said:
I looked at the firmware link and it was build back in August but I am already on the September Security patch?
Click to expand...
Click to collapse
as long as its the same bootloader, itll work and itll update itself as normal once booted

.

.

.

.

DetectiveTaco said:
Update: I tried doing this using a different machine and it worked as it should. I am now running the U1 firmware. Thanks for the sources for the resources and reccomendations.
Click to expand...
Click to collapse
you bet man! glad it all turned out as we know it should

.

DetectiveTaco said:
One last question, did your CSC change when you flashed the U1? My CSC before flashing was VZW/VZW/VZW and it's still VZW/VZW/VZW. In the phone info app it says my firmwares CSC code is XAA which is what it should be since I flashed the XAA G960U1. But then it says the active CSC code is VZW. Does this mean I will not receive the unlocked OTA updates from Samsung directly like I thought I would, and instead I will still receive the Verizon OTA updates instead. http://imgur.com/a/KgooKUR
Click to expand...
Click to collapse
it should still get updates for the OTA version. What happened is when you put the vzw card in, the firmware chose VZW since that was one of the available CSCs in the package. No worries man

.

.

DetectiveTaco said:
Or is it like because the CSC is Country/Region/Operator and VZW was a part of the multi CSC package but the firmware uses the XAA CSC code it will pull the updates from the XAA provider in this case that being Samsung.
I will probably wait until the next update for XAA devices is pushed and see if I receive it. And I'll either report back here or PM you if I receive the OTA for the next XAA G960U1 update
Click to expand...
Click to collapse
thats what i was driver after. the version of firmware you flashed contains several CSCs and the vzw one is what the phone latched on to. If you popped another sim in there thats within that csc list, itll probably do similar stuff with that
yeah, feel free to hit me up. if you pm me on here, i might not answer super fast, but ill eventually get to it lol

.

DetectiveTaco said:
Yep sure thing. Hopefully the October patch will get pushed soon and ill found out.
Click to expand...
Click to collapse
oh, forgot to address one of your previous questions. You can flash those files all you want, the nice part about them is that if youre flashing a new version on top of the old one, just flash the CSC_HOME and it will keep your phone exactly how it was but still apply the update. Its pretty sweet

.

DetectiveTaco said:
Yeah I flashed the regular CSC going from G960U to G960U1 because how it was a bigger transition and I didn't want to leave traces of Verizon crap.
Click to expand...
Click to collapse
very good. thats a perfect example of when to use the CSC vs the HOME_CSC

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.

Stock Firmware for Samsung Note 10+

I'm using Samsung Note 10+
Model number SCV45, a Japanese variant with a name tag "au" & has the Snapdragon processor, not Exynos.
I want to flash the stock Firmware again.
I have visited SamMobile website to download the firmware of Note 10+. But there are lots of model number available like -
SM-N975F
SM-N975U
SM-N975U1
SM-N975W
SM-N9760
SM-N976B
SM-N976N
SM-N976Q.... so on.
But i didn't found "SCV45" model number.
As far as I know, SM-N975U, SM-N975U1 is for USA region with Snapdragon variant & SM-N975W is for canda region, also with Snapdragon.
If I flash any of the firmware of USA or Canada variant on my Japanese variant device through Odin, is there will be a problem. I have no idea about that as I'm a new user of Samsung. I have always used OnePlus. So I don't have enough knowledge about Samsung firmware.
Please let me know about the fact.

hello
you cand find your firwares here :
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com

yakapa40 said:
hello
you cand find your firwares here :
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Click to expand...
Click to collapse
Thanks a lot brother.
But actually, I want to try out US region firmware on my device. So I'm asking, is there any problem if I flashed
SM-N975U or SM-N975U1 firmware? What will happen if I do so?
I need a clear idea about that, because I don't have enough knowledge about Samsung firmware & also I don't want my device turn into a bricked device.
Hope, I will get a clear idea from this XDA forum about that.

maybe your device is rooted or there is a mixed firmware so coming back to original firmware is not without risk
can you post :
- device version:
on dialer : *#1234# or *#12580*369#

Here is the Device Version that you want
Actually today I tried to add a edu mail account on google and it's showing that "Can't create a working profile, here is what error message I got.
I have checked, I don't have root access. And I also running stock Firmware as I got OTA update from Samsung for One UI. So I don't know what is the actual problem. That's why I want to shift from current firmware to USA region firmware.
But I am in a doubt as I don't have enough knowledge about that.

you can't flash a N970U or U1 full firmware
maybe only the CSC part if it work but at your own risk

I believe you can try to flash some completely other version, but no one can be sure if it will work.
I would suggest to have a spare Japan OFW to reflash if anything goes wrong.
Your latest FW according to samfirm should be -> SCV45 -> Region KDI
Version: SCV45KDU1DVC3/SCV45QDI1DVC3/SCV45KDU1DVC3/SCV45KDU1DVC3
FIlename: SCV45_3_20220314133230_x92etays47_fac.zip.enc4
Size: 6010MB

yakapa40 said:
you can't flash a N970U or U1 full firmware
maybe only the CSC part if it work but at your own risk
Click to expand...
Click to collapse
Can you tell me about the CSC part? Why you recommend this one only? What about AP, BL & rest?

Ereniemis said:
I believe you can try to flash some completely other version, but no one can be sure if it will work.
I would suggest to have a spare Japan OFW to reflash if anything goes wrong.
Your latest FW according to samfirm should be -> SCV45 -> Region KDI
Version: SCV45KDU1DVC3/SCV45QDI1DVC3/SCV45KDU1DVC3/SCV45KDU1DVC3
FIlename: SCV45_3_20220314133230_x92etays47_fac.zip.enc4
Size: 6010MB
Click to expand...
Click to collapse
I know it's hard to find someone who has tried out what I asked for. I don't know whether it will work or not. But I just want to make sure that after flashing a different region firmware, it should not become a hard brick device.
If something goes wrong, at least I flash the SCV45, Japan variant firmware again & everything turns to a normal state as it is running now.
So should I proceed with SM-N975U, USA variant firmware? Will it gonna make my device hard brick? Can I come back to normal state by flashing SCV45 KDI firmware which is mentioned by you?

I need some suggestions. Nobody is answering

SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
I would suggest you not to flash bootloader if possible. Everything else can be dealt with if bricked.

SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
I would personally look for the model, which is the most similar to the japan one and just... pray while flashing

SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
and also, dont forget to flash the "CSC" file, not the "home_CSC" to change the region. (the home_CSC doesn't change CSC and leaves your apps and other stuff intact. On the other hand, the CSC file wipes everything and changes the region.)

Ereniemis said:
and also, dont forget to flash the "CSC" file, not the "home_CSC" to change the region. (the home_CSC doesn't change CSC and leaves your apps and other stuff intact. On the other hand, the CSC file wipes everything and changes the region.)
Click to expand...
Click to collapse
I am too much grateful to brother for your suggestions what I actually expected for.
I will follow all your instructions.
I will flash the "CSC" file only. Thanks for let me clear about this thing.
I have just a little confusion about what you have told above.
You suggest me not to flash bootloader. Can you please give me a clear idea how can I skip it or at what step, I should not flash the bootloader? I have just this confusion.

SabbirNaim said:
I am too much grateful to brother for your suggestions what I actually expected for.
I will follow all your instructions.
I will flash the "CSC" file only. Thanks for let me clear about this thing.
I have just a little confusion about what you have told above.
You suggest me not to flash bootloader. Can you please give me a clear idea how can I skip it or at what step, I should not flash the bootloader? I have just this confusion.
Click to expand...
Click to collapse
Well... You have to flash through ODIN.
So. In the ODIN you have several options on what to do (what to flash). When you download the FIRMWARE you will have to decompress it. there will be different files -> BL (Bootloader - BL), PDA (the firmware - AP), PHONE (modem and stuff - CP) and CSC (vendor or region specific info).
Firstly I would try to flash only AP + CP + CSC. Which means Firmware + Phone + CSC. Be sure to flash the same version of Android as you have. In that case it should... maybe... probably work the same. If you have bootloader from Android 11 and you try to flash Android 11 from another version, it should work theoretically....
But if you try to flash eg. Android 12 over Android 11 it won't work because the Android 12 uses different bootloader and you need to update it.
It would be most desired to flash the bootloader also. But my suggestion for you is to try flash different version without the bootloader (if it can be done). Because if you don't screw up the bootloader, you will be always able to boot to bootloader a flash back the original firmware.
I don't have the knowledge to tell you, that if you flash USA version of bootloader to the JAPAN version of bootloader that it will work. It probably should, but I believe, noone can answer that and it's just that you will have to try it.
I believe that the ODIN will tell you that you are trying to flash firmware from completely different device and if you are sure to do that.
So again:
1) download firmware from different location with the same android version
2) decompress the firmware
3) in the ODIN -> add only AP, CP, CSC (don't add the bootloader)
4) try to flash!
If it doesn't work, you can try even to flash the bootloader, but I'm a bit worried about that one....

I am highly grateful to you as you have explained the whole thing so clearly. Now I understand all the steps that I need to do. Thank you so much for clearing up the matter in so much detail. Now I can proceed.
I will try as per your suggestion. Let's see what happened.
Thanks again.

bootloader is in AP !

yakapa40 said:
bootloader is in AP !
View attachment 5643845
Click to expand...
Click to collapse
Then what should I do?

before flashing a part of firmware , i think it's better to know more about root
i'm not familiar with root and my lastest rooted device is a galaxy S6
why do you want to change the firmware ?

yakapa40 said:
before flashing a part of firmware , i think it's better to know more about root
i'm not familiar with root and my lastest rooted device is a galaxy S6
why do you want to change the firmware ?
Click to expand...
Click to collapse
I have checked and I don't have any root access. I have told you why I actually want to change the firmware in some previous reply.
Here I am mentioning the whole problem again for your better knowledge.
Actually yesterday, I tried to add an edu mail account on google and it's showing that "Can't create a working profile", here is what error message I got.
I am running on stock official Firmware, I confirmed that as I got OTA update from Samsung for One UI. So I'm not using any custom OS.
But I don't know why it's showing that I am using a custom OS . That's why I want to shift from current firmware to USA region firmware to check whether the Japanese region firmware has issue or not.
But I am in a doubt as I don't have enough knowledge about switching from one region to another region firmware in Samsung devices.
I hope you can understand, though my English is not great