I can't update my Android OS to 11 it's still on Android 10. When I tried going to Phone Settings > Software updates> Download and install> Your software is up to date. Is there a way to get this Android 11 or 12 update to my device Baseband Version. G973USQS4ETK2
Looks like you have a USA phone, I assume on a USA network? Looks like USCellular?
What carrier and country are you in? I see there are updates for your firmware as recent as this month... that would be Android 11. 12 is not on US phones yet.
Its under T-mobile US I guess I was able to look the information up and I saw the baseband version is under T-mobile. Is there a way to patch Android 11 or even 12 to this cause I also tried rooting this but I'm having a hard time downloading stuffs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It stopped Updating since this last patch.
First off, if you want to root, I think you will be able to - your BL version is 4 (5th from end number in the build version or the baseband version). It's not free to root this way, but I believe you can. However, if you do that, then I don't think you can update to any newer version of stock ROM, because you cannot update the bootloader (which is part of the other releases). Also not, rooting may wipe your phone too.
As for the other question, show me your full software info page, so I can see the CSC codes and other things. I want to make sure they make sense.
My guess is that because you have a U phone (as opposed to U1 with a multi-CSC setup) that you would not be able to patch/update the phone. This is because the U is typically locked to the carrier updates, and if it's looking for USCellular, that would explain why your TMo carrier can't update it. You could reflash to a U1 ROM using ODIN, and this should allow updating in the future, but it will likely require a wipe (you could try an upgrade flash, but I don't recall if this is possible from U to U1). This will also update the bootloader which means you can't root today, but you would be up to date.
So, decide how you want to go first... because you can't have both (root + updated... unless you do custom roms, which I am not versed in, but you are liklely going to give up some things with custom roms, from the superficial reading I've done there)
I think it would be best to move from U to U1 to still have updates.
Dharhil said:
I think it would be best to move from U to U1 to still have updates. View attachment 5519565
Click to expand...
Click to collapse
So my phone looked much like yours does, xaa/xaa/tmb. Couldn't get updates either. I used patched Odin and flashed latest xaa version, and used 'home' csc, resulting in keeping user data.
I wanted to keep everything much as it was because using Mint Siim, I'm able to get voip / vowifi, but it also does 'carrier aggregation', so I get a little LTE+ icon indicating such, signal is very good also. Doing the update kept everything working as it was.
I don't plan on rooting so the bump in BL version didn't care about.
cheers
I agree with @AsItLies - your phone looks like it's already on a multi-CSC ROM (XAA). Not sure why it's not updating, but since you're already there, you should be able to do the Odin update as an upgrade, using the "home" CSC and it should update the ROM at the very least. Ideally, your phone should show TMB/TMB/TMB, because the first one is the current SIM, the second is the carrier, and the third is the original CSC (which you can't change anyway)... for example, mine shows TFN/TFN/SPR (Tracfone aka Total Wireless, in my case). My ROM is a U1, though... maybe that's why both of yours is not changing the XAA properly?
I'd say, give the U1 a shot, with the HOME CSC and upgrade mode in ODIN and see if that works. But before you do that, BACKUP EVERYTHING YOU NEED, just in case.
I would recommend using Frija to download the ROM (much faster than web downloads)... but the rest of the info is available on various threads here on XDA. I would recommend reading through the guide posts here THOROUGHLY before doing anything: https://forum.xda-developers.com/t/g973u-and-g973u1-firmware-links-here.3905852/
If you still have questions, you can ask there or here...
@AsItLies are you on a U or U1 ROM? Just curious...
@schwinn8 it's funny you should ask that, because when I first got my phone it said 973U. Now, after the update I described above, it says 973U1.
I'm guessing that indication isn't used to determine if an update is available, could be wrong, but I *think* an update just depends on if it was originally U or U1, and you're running the original firmware. So anything that is multi csc but was originally a U, I don't think that will OTA update (only manually with patched Odin).
Anyway, there are very few updates left, so not too worried about it, doing it manually is quite easy. Pretty sure A12 will be the last we'll see.
cheers
Agreed, not a big deal regarding updates now... but was just curious... I'm surprised to see you're still showing XAA/XAA... I figured those would change.
I had issues with one of my wife's phones (we bought two S10+ phones at the same time)... hers refused to switch to TFN for some reason. Sadly, she NEEDED it because she used the old-fashioned voicemail and app. I could see the app on my phone (where the CSC change worked fine) so I knew what I needed, but couldn't get it to happen. I ended up returning that phone (Ebay) and getting one that was already setup for TFN... and that one is fine. Funny thing, I think it was an XAA as well, but I don't remember now).
I've also seen a thread here that says CSC won't change anymore for users. But even that post has very mixed info... as my experience confirmed. So weird.
/rant
I don't know what am I doing hahah. I tried flashing in ODIN but it failed and trying to click start again saying SetupConnection... and nothing happens... I think it has to to with this?.
I don't know what "this" you're referring to? Did you read up about how to use ODIN? Did you watch any videos on it via Youtube (if that's your preference)? Did you install drivers?
schwinn8 said:
I don't know what "this" you're referring to? Did you read up about how to use ODIN? Did you watch any videos on it via Youtube (if that's your preference)? Did you install drivers?
Click to expand...
Click to collapse
I did two thing but I dont know which is which fixed it I downloaded an Update manually via Frija for SM-G973U (that I don't know it even exist bcxz sammobile doesn't have a record of it) and the 2nd one is I downloaded Odin3 v3.13.3 to flash the downloaded software. (previously i was using Odin3 v3.14.1)
I'm not sure, but it sounds like you figured it out? Congrats... yes Frija will sometimes get you a newer version than is normally seen. Or a version specific to your phone. Not a bad thing.
One thing I will warn you, I have read that many people are having issues with apps and features in Android 12... I'd recommend NOT getting that if you can prevent it. I prefer to let other people deal with the bugs before I have to get into them... but that's just me.
Related
So, as you may know, some people are having a problem where registering for the OneUI beta with a US phone just kicks them back to the Samsung+ homepage without the registration actually going through.
The CSC in Samsung phones is a code that indicates the region/carrier in which the phone is registered.
As far as I know, all US Unlocked phones come with an XAA CSC, which indicates USA Unbranded, but as soon as you insert a Verizon/T-Mobile/etc SIM card, it gets set to that specific's carrier CSC.
I have come to suspect that the problem has to something to do with the region/CSC in which the device is being used, regardless of the physical model (mine is an US Unlocked SM-N960U1, which should be covered by the beta program, but since I never inserted a US Carrier SIM card, I still ahve the default XAA CSC).
Can somebody please chime in on this? You can check your CSC by going to Settings - About Phone - Software Information - Service Provider SW Ver and checking the third and last line. In my case it says XAA/XAA/XAA
If you are successfully registered in the beta, and your CSC code is the same as mine, then it means I'm wrong. If you are having problems registrating, and your CSC code is XAA or some other US unbranded code, then my theory might be right and we might be able to enter the beta by flashing another CSC.
Thank you very much for reading!
I got a ATT note 9, flashed Unlocked firmware I got CSC XAA/XAA/ATT, I can see the banner I can click on it but it will return me back to original banner without a welcome message :s
Nachorl250 said:
So, as you may know, some people are having a problem where registering for the OneUI beta with a US phone just kicks them back to the Samsung+ homepage without the registration actually going through.
The CSC in Samsung phones is a code that indicates the region/carrier in which the phone is registered.
As far as I know, all US Unlocked phones come with an XAA CSC, which indicates USA Unbranded, but as soon as you insert a Verizon/T-Mobile/etc SIM card, it gets set to that specific's carrier CSC.
I have come to suspect that the problem has to something to do with the region/CSC in which the device is being used, regardless of the physical model (mine is an US Unlocked SM-N960U1, which should be covered by the beta program, but since I never inserted a US Carrier SIM card, I still ahve the default XAA CSC).
Can somebody please chime in on this? You can check your CSC by going to Settings - About Phone - Software Information - Service Provider SW Ver and checking the third and last line. In my case it says XAA/XAA/XAA
If you are successfully registered in the beta, and your CSC code is the same as mine, then it means I'm wrong. If you are having problems registrating, and your CSC code is XAA or some other US unbranded code, then my theory might be right and we might be able to enter the beta by flashing another CSC.
Thank you very much for reading!
Click to expand...
Click to collapse
I have the Verizon version and it worked fine. Initially i was having issues like you were, but i read another post that said to go to settings>apps then select the Samsung + app and clear the data /cache. After i restarted i got in and had the beta software within 10 minutes
OneUI Beta
My Note 9 is a TMO locked device so yesterday I flashed the unlocked SM960U1UEU1ARH2 firmware via patched ODIN, using the CSC_OMC_OYM instead of the Home CSC and leaving the USERDATA blank . Everything went smooth, the TMO power-on screen logo was finally gone and after several in succession OTA updates it ended up with the version N960U1UES1ARJ9 with a solid LTE signal and everything that I usually use working without issues. Deleted Samsung+ and re-installed the Samsung+ Beta APK and after signing up the beta registration option showed right away, registered, rebooted the device and went to the software 'download and install update' option in settings and there it was ; the N960U1UEU1ZRKP update. Lately I've been switching from a Huawei Porsche to this Note 9 but needless to say Huawei is pretty slow as far as updates, now with this update the Note 9 definitely feels like a new device and as it seems the Huawei will be up for sale pretty soon. Yes the update is that cool and so far everything is working without any hiccups.
View attachment 4659136
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zimoss said:
go to settings>apps then select the Samsung + app and clear the data /cache. After i restarted i got in and had the beta software within 10 minutes
Click to expand...
Click to collapse
I tried that with no luck
sFranKv said:
I got a ATT note 9, flashed Unlocked firmware I got CSC XAA/XAA/ATT, I can see the banner I can click on it but it will return me back to original banner without a welcome message :s
Click to expand...
Click to collapse
So the problem is also a thing for people with the ATT CSC. My theory is losing strength lol
rayporsche said:
My Note 9 is a TMO locked device so yesterday I flashed the unlocked SM960U1UEU1ARH2 firmware via patched ODIN, using the CSC_OMC_OYM instead of the Home CSC and leaving the USERDATA blank . Everything went smooth, the TMO power-on screen logo was finally gone and after several in succession OTA updates it ended up with the version N960U1UES1ARJ9 with a solid LTE signal and everything that I usually use working without issues. Deleted Samsung+ and re-installed the Samsung+ Beta APK and after signing up the beta registration option showed right away, registered, rebooted the device and went to the software 'download and install update' option in settings and there it was ; the N960U1UEU1ZRKP update. Lately I've been switching from a Huawei Porsche to this Note 9 but needless to say Huawei is pretty slow as far as updates, now with this update the Note 9 definitely feels like a new device and as it seems the Huawei will be up for sale pretty soon. Yes the update is that cool and so far everything is working without any hiccups.
View attachment 4659136
View attachment 4659137
Click to expand...
Click to collapse
So we might have luck flashing another CSC. Thank you for your input!
Nachorl250 said:
So, as you may know, some people are having a problem where registering for the OneUI beta with a US phone just kicks them back to the Samsung+ homepage without the registration actually going through.
The CSC in Samsung phones is a code that indicates the region/carrier in which the phone is registered.
As far as I know, all US Unlocked phones come with an XAA CSC, which indicates USA Unbranded, but as soon as you insert a Verizon/T-Mobile/etc SIM card, it gets set to that specific's carrier CSC.
I have come to suspect that the problem has to something to do with the region/CSC in which the device is being used, regardless of the physical model (mine is an US Unlocked SM-N960U1, which should be covered by the beta program, but since I never inserted a US Carrier SIM card, I still ahve the default XAA CSC).
Can somebody please chime in on this? You can check your CSC by going to Settings - About Phone - Software Information - Service Provider SW Ver and checking the third and last line. In my case it says XAA/XAA/XAA
If you are successfully registered in the beta, and your CSC code is the same as mine, then it means I'm wrong. If you are having problems registrating, and your CSC code is XAA or some other US unbranded code, then my theory might be right and we might be able to enter the beta by flashing another CSC.
Thank you very much for reading!
Click to expand...
Click to collapse
Bought mine direct from Samsung...I use Tmobile for service...I successfully registered an received the update via OTA...
my csc codes read TMB/TMB/XAA
When I put in a different SIM, the first two blocks change to the carrier, last one never changes
whelmar said:
Bought mine direct from Samsung...I use Tmobile for service...I successfully registered an received the update via OTA...
my csc codes read TMB/TMB/XAA
When I put in a different SIM, the first two blocks change to the carrier, last one never changes
Click to expand...
Click to collapse
That's odd, my looks like this XAA/XAA/ATT....
funny thing is that I'm not even using a ATT sim on it
That's because the first one is the active CSC, the second one is the CSC your phone thinks would be best for the SIM card you have inserted, and the last one is the one that came with your phone/firmware.
Nachorl250 said:
That's because the first one is the active CSC, the second one is the CSC your phone thinks would be best for the SIM card you have inserted, and the last one is the one that came with your phone/firmware.
Click to expand...
Click to collapse
that makes sense, thanks
Now would be cool if anyone outside the US like me, with an Unlocked US note 9 was able to enter to the beta xD
I have Sprint. Do I have to put in a sim from like TMobile to get the beta?
Sent from my SM-N960U using Tapatalk
Nevermind I'm sure this won't work.
However could we use update zip in stock recovery? Stock phone here.
hayabusa1300cc said:
I have Sprint. Do I have to put in a sim from like TMobile to get the beta?
Sent from my SM-N960U using Tapatalk
Nevermind I'm sure this won't work.
However could we use update zip in stock recovery? Stock phone here.
Click to expand...
Click to collapse
You need to be on the U1 firmware.
Can I flash this, without issue and not being tripped on Knox?
Sent from my SM-N960U using Tapatalk
sFranKv said:
I got a ATT note 9, flashed Unlocked firmware I got CSC XAA/XAA/ATT, I can see the banner I can click on it but it will return me back to original banner without a welcome message :s
Click to expand...
Click to collapse
I have the same issue with mine.. trying from last 3days but the problem is the same.. tried clearing cache by rebooting and all. Nothing helped. My firmware is VZW/VZW/XAA
For the model # does it say 960U1 or 960U, if it doesn't say U1 then it won't work.
I'm on ATT, but I have the factory unlocked model that I bought from Samsung directly and I was able to get the beta after clearing the cache
Someone please help
Blind_Guardian said:
For the model # does it say 960U1 or 960U, if it doesn't say U1 then it won't work.
I'm on ATT, but I have the factory unlocked model that I bought from Samsung directly and I was able to get the beta after clearing the cache
Click to expand...
Click to collapse
Yes,my model is 960U1. But I cannot register for the banner.. the banner is still available.
Nachorl250 said:
So the problem is also a thing for people with the ATT CSC. My theory is losing strength lol
Click to expand...
Click to collapse
And with Verizon too.. I cant either register
divyasharma20 said:
And with Verizon too.. I cant either register
Click to expand...
Click to collapse
Are you running the U1 firmware?
Mr. Orange 645 said:
Are you running the U1 firmware?
Click to expand...
Click to collapse
Yes
I'm somehow stuck on N960USQU1CSAA, and each time I check for an update, I'm told that my "software is up to date"...
I have an ATT Sim card, and active ATT Service, but somehow my software updates broke...
How can I get N960USQU1CSC1 or N960USQS1CSD1?
Although, I'd prefer to do update.zip, and not ODIN... Any hope for this?
Thanks in Advance...
Why not ODIN man? It may solve your problem.
Sent from my SM-N960F using Tapatalk
Okay, I could odin... Just desperate to get this thing solved... (although confused how I got hung up on an old version)
Where can I get the ATT version of this firmware?
I see a Verizon CSD1 -- is that identical to the ATT CSD1? Should I get OTAs if I install the Verizon version?
Here ya go.
https://androidfilehost.com/?fid=1395089523397944212
Sent from my SM-N960U ORE0
THANK YOU!
butchieboy said:
Here ya go.
https://androidfilehost.com/?fid=1395089523397944212
Sent from my SM-N960U ORE0
Click to expand...
Click to collapse
Can I straight ODIN this, or do I have to do anything special?
I always factory reset 1st for best results. Many dont like to lose data but me..clean install is best.
Sent from my Still Rooted NOTE 8
I'm downloading this file now (thanks for the link) - am I correct in assuming that this particular file is specific for AT&T-carrier-branded Note9's? I've been pulling my hair out (what little I have left), since I got this phone, it's NEVER received an OTA update - EVER. After much trial from AT&T tech's, their last-ditch solution was factory reset & wait for system to update. So, I'm gonna do something I haven't done since my Note 2, & ODIN this FW.
Shanghai.Knight said:
I'm somehow stuck on N960USQU1CSAA, and each time I check for an update, I'm told that my "software is up to date"...
I have an ATT Sim card, and active ATT Service, but somehow my software updates broke...
How can I get N960USQU1CSC1 or N960USQS1CSD1?
Although, I'd prefer to do update.zip, and not ODIN... Any hope for this?
Thanks in Advance...
Click to expand...
Click to collapse
BereanPK said:
I'm downloading this file now (thanks for the link) - am I correct in assuming that this particular file is specific for AT&T-carrier-branded Note9's? I've been pulling my hair out (what little I have left), since I got this phone, it's NEVER received an OTA update - EVER. After much trial from AT&T tech's, their last-ditch solution was factory reset & wait for system to update. So, I'm gonna do something I haven't done since my Note 2, & ODIN this FW.
Click to expand...
Click to collapse
I have the same exact problem, I downloaded this last night. Does it need to be odin or can I flash through recovery?
Hi All! I believe this was the Verizon version, but I did it anyway.
Had to use ODIN...
GREAT NEWS:
1.I DID NOT LOSE DATA using ODIN (NON ATT VERSIONS DO NOT WIPE DEVICE~!)
2. It booted up with the ATT Logo.
3. I Immediately got a notification of the April update upon reboot, and it downloaded the ATT update, and installed it NO PROBLEM!.
Shanghai.Knight said:
Hi All! I believe this was the Verizon version, but I did it anyway.
Had to use ODIN...
GREAT NEWS:
1.I DID NOT LOSE DATA using ODIN (NON ATT VERSIONS DO NOT WIPE DEVICE~!)
2. It booted up with the ATT Logo.
3. I Immediately got a notification of the April update upon reboot, and it downloaded the ATT update, and installed it NO PROBLEM!.
Click to expand...
Click to collapse
Do I ODIN all the files in that download? Won't it remove my data if I ODIN the "USERDATA" part?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey Guys....Me too sailing in the same boat. Please guide me if we can just install the updates manually and not the complete software. Stuck on CSAA Version on SM-960U . TIA
xxcmb3k3xx said:
Do I ODIN all the files in that download? Won't it remove my data if I ODIN the "USERDATA" part?
Click to expand...
Click to collapse
do bl,ap,cp,home_csc.md5
userdata is just more carrier bloat. but might have things u want. but the one that might cause data loss is csc.md5. but home_csc.md5 should keep it.
but its always good to stars fresh sometimes.... so id actually say fill in all slots and USE csc.md5 to wipe clean.
I have a Galaxy Note 9 that was originally an AT&T Phone in USA. I purchased it unlocked in Canada and I use it on Fido Network. The Baseband version is N960USQU1CSAA. It is running One UI 1.0 and Android 9. Is there any way to root this phone? Do I have to use same baseband version?
Shanghai.Knight said:
Can I straight ODIN this, or do I have to do anything special?
Click to expand...
Click to collapse
Is this the link to ODIN Galaxy Note 9 Stuck in Baseband V: N960USQU1CSAA? I need to root my phone so I can recover lost whatsapp messages I desperately need.
Hello dears,
One of my clients called me related to a problem with their Note 8 device. At first it sounded like a typically bricked device problem but after taking a closer look on some of the screenshots they've sent me with the device it really got me confused as to what had happened to the device. I don't have the device with me at the moment so the screenshots is all I have until the client arrives but I'm posting this thread in hopes to find out if there is any possibility of fixing the device so that I put the client on the road for nothing.
From what I understood the client tried rooting the phone and it got into a boot loop afterwards (I don't know the exact process of rooting that they've tried, that's all they said to me), they also said that they've been with the device to someone else afterwards and they've tried a few times to resoft the device with some ROM variants on the phone but they've "failed"to fix the device in the end and my client got bored of waiting for them to keep trying.
I thought the phone may be soft bricked and I asked them for some screenshots with the device so that I can see what firmware they were running and also a screenshot with the phone model details on the back and so they sent the screenshots to me and a few extra more.
Now, the first thing that I see is that the phone strangely runs or has ran a DIFFERENT firmware version for a DIFFERENT MODEL. If you look at the screenshots posted bellow, you will see that the phone is a SM-N950F/DS but runs an N9500 Firmware/ROM (Chinese I guess). I am confused, I haven't see that before. Is it possible that the guys working at the phone before managed to install a wrong firmware and hard brick the phone even more?
I see that the ROM that is currently shown on the phone is indeed an official/stock one from Samsung so I also wonder if that's how the phone actually came out on the shelf since the client told me that they've bought it from around that region. But still, the rom is clearly made for another model from the one written on the back of the phone so I don't really know what to say I haven't met with this issue before.
Also, judging by the screenshots offered what would be the steps you guys would make to fix the phone (if possible) and what exact rom version should I flash via Odin if anyone has an idea.
Should I flash the stock N950F/DS firmware or the N9500 CHC/TWN stock firmware? What would be the steps to bring this device back to life ? I appreciate your patience and I hope that the phone can still be revived.
Here are the screenshots (I apologise for the quality but this is what the client has sent at the moment).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.
stonedpsycho said:
He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.
Click to expand...
Click to collapse
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.
BrainwashedUser said:
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.
Click to expand...
Click to collapse
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...
stonedpsycho said:
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...
Click to expand...
Click to collapse
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.
BrainwashedUser said:
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.
Click to expand...
Click to collapse
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".
StevePritchard said:
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".
Click to expand...
Click to collapse
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?
BrainwashedUser said:
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?
Click to expand...
Click to collapse
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.
BrainwashedUser said:
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.
Click to expand...
Click to collapse
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?
BrainwashedUser said:
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?
Click to expand...
Click to collapse
I am unsure with all the errors but try using Odin 13.3.1.
Similar Issue
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.
awetsm said:
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.
Click to expand...
Click to collapse
Looks like you have a refurbished note 8 korean model N950N with replaced body and faked software N950F .
The motherboard is Korean so don't try flash N950F software on it will fail in odin it won't work.
Only N950N firmware will work only on your phone and you can flash android 9 pie but be careful if you flash N950N firmware you will lose N950F software and also dual sim will no longer will work too because possibly your dual sim also converted by software not Hardware. Because there's no N950N Exists with dual sim model.
Specs:
Unlocked Samsung Galaxy Note 8 - N950U1
Product code: VZM
Baseband version: N950USQU3BRA5
Build number: NMF26X.N950U1UEU3BRA5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
Screenshots from About Phone and SamMobile app:
https://imgur.com/a/pcnbZZF
Been following guides on XDA and SamMobile to attempt flashing Odin the past 4 days with no success. It's an unlocked refurbished Verizon I got off eBay, but I've been using it on T-Mobile the past 2.5 years. Have tried both the Verizon and and T-Mobile firmware files (meant for N950U1) just trying to get to Android 9. At the moment I keep getting the message "All threads completed. [Succeed 0/Fail 1]" soon after pressing START. Do you have suggestions for what I can try next or what might be wrong?
It's also been brought to my attention that there's conflicting elements on the phone between N950U and N950U1 firmware and build. Not sure if this the source of all the trouble and if there's a way to fix it
Troubleshooting I've tried:
-Using various Odin builds (including patched)
-Making sure Smart Switch processes aren't running on computer during Odin flashing
-Waiting until the blue COM box shows in Odin
-2 factory resets of phone
-Updating through Smart Switch
-Buying a Verizon SIM to try initiating update
-Trying both N950U and N950U1 firmware
mountaineermh said:
Specs:
Unlocked Samsung Galaxy Note 8 - N950U1
Product code: VZM
Baseband version: N950USQU3BRA5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
Been following guides on XDA and SamMobile to attempt flashing Odin the past 4 days with no success. It's an unlocked Verizon I got off eBay, but I've been using it on T-Mobile the past 2.5 years. Have tried both the Verizon and and T-Mobile firmware files (meant for N950U1) just trying to get to Android 9. At the moment I keep getting the message "All threads completed. [Succeed 0/Fail 1]" soon after pressing START. Do you have suggestions for what I can try next or what might be wrong?
Troubleshooting I've tried:
-Using various Odin builds (including patched)
-Making sure Smart Switch processes aren't running on computer during Odin flashing
-Waiting until the blue COM box shows in Odin
-2 factory resets of phone
-Updating through Smart Switch
-Buying a Verizon SIM to try initiating update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
That's because you're trying to go from N950USQU3BRA5 which is N950U to N950U1 and I think Samsung eventually blocked going from N950U to N950U1 (someone else may know for sure) .. If you try downloading the N950U firmware instead it'll probably work.
MrMike2182 said:
That's because you're trying to go from N950USQU3BRA5 which is N950U to N950U1 and I think Samsung eventually blocked going from N950U to N950U1 (someone else may know for sure) .. If you try downloading the N950U firmware instead it'll probably work.
Click to expand...
Click to collapse
Thanks for getting back to me. An admin at SamMobile pointed out that my firmware and baseband don't match (my phone states that it's a N950U1 even though the baseband is N950USQU3BRA5). I don't know how this could be, as it's not something I did, but it's why I've been attempting the N950U1 firmware. In your opinion, is there a chance I'd mess something up even more by trying to flash the N950U firmware when the phone explicitly states in the "About Device" section it's an N950U1?
mountaineermh said:
Thanks for getting back to me. An admin at SamMobile pointed out that my firmware and baseband don't match (my phone states that it's a N950U1 even though the baseband is N950USQU3BRA5). I don't know how this could be, as it's not something I did, but it's why I've been attempting the N950U1 firmware. In your opinion, is there a chance I'd mess something up even more by trying to flash the N950U firmware when the phone explicitly states in the "About Device" section it's an N950U1?
Click to expand...
Click to collapse
What does it say in the About Phone section for build number? If they're all different versions that means your phone is a repaired device and they used different phone parts to get it to work and if you try flashing it it doesn't work and something could go through and then render the phone useless.
MrMike2182 said:
What does it say in the About Phone section for build number? If they're all different versions that means your phone is a repaired device and they used different phone parts to get it to work and if you try flashing it it doesn't work and something could go through and then render the phone useless.
Click to expand...
Click to collapse
Build number is NMF26X.N950U1UEU3BRA5
Baseband is N950USQU3BRA5
Here are screenshots:
https://imgur.com/a/pcnbZZF
If at anytime you are going from U1 to U or U to U1 you need to make sure and do a factory reset first. What I would do is download Phone Info app from playstore and use the app to do a refurbishment check. MrMike could be right with what he said. But you should not have any problems bouncing between U1 and U firmware. I do it all the time. You just have to make sure the bootloader is the same. Make sure you are using correct version of odin
Sent from my SM-N960U using Tapatalk
butchieboy said:
If at anytime you are going from U1 to U or U to U1 you need to make sure and do a factory reset first. What I would do is download Phone Info app from playstore and use the app to do a refurbishment check. MrMike could be right with what he said. But you should not have any problems bouncing between U1 and U firmware. I do it all the time. You just have to make sure the bootloader is the same. Make sure you are using correct version of odin
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I'm curious as to why his phone says N950USQU3BRA5 and also N950U1UEU3BRA5.. That's throwing me off. Haven't seen that before.
That is odd for sure. I'm wondering if its refurbished. There has been a lot of this exact same thing with devices bought off ebay.
Sent from my SM-N960U using Tapatalk
butchieboy said:
That is odd for sure. I'm wondering if its refurbished. There has been a lot of this exact same thing with devices bought off ebay.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
It was a refurbished phone from eBay, so I guess it all fits. I'm about to attempt flashing N950U firmware using the latest Odin, so hopefully that'll iron everything out
Just tried flashing the N950U firmware and it gave me the same fail message after trying to setup the connection. I used the official 3.14.4 build, the 3B Patched build, and the 3.12 PrinceComsy build.
I'm at a loss for what to do/try
Try finding user data for whatever carrier your flashing
Sent from my SM-N975U using Tapatalk
Could use some guidance. T-Mobile is upgrading its network in three days (1/29/21), and they've texted a notice saying:
To stay connected to the T-Mobile network, you must update your Note device's software by January 29, 2021 or your will lose your connection. Update instructions: t-mo.co/Note4Update
Click to expand...
Click to collapse
The link leads to a legit T-Mobile.com support page that leaves me puzzled. Questions:
I can't tell whether my Note 4 needs the update they say it needs, and if it does, whether my Note 4 can get the update. My "About Device" reports: Android ver. 6.0.1; Security Patch level August 1, 2017; Baseband ver. N910TUVU2EQI2.
Equally (if not more) important: my Note 4 is rooted with a debloated stock ROM. I know how to root, but know very little about root. All I know is I'm one of those for whom it is an open question whether smartphone life is even worth living without root. So the question is: Can I perform the needed T-Mobile update to maintain connection to their network, and still maintain root?
Any help will be much appreciated, and I apologize for the urgency and short notice.
Not much help, but I'm in the same boat. Currently trying to make sure my wife's phone that is *not* rooted will stay connected, but also have another N4T as my backup daily, whick def. NEEDS root. I am also awaiting a Librem 5 that I'd liek to connect to TMO and if that doesn't work its either going to be back to dumb phones for me *or* getting a mobile hotspot and doing everything on that connection....perhaps that and a dumbphone.
I have D/L the SM-N910T3 update (N910T3UVU3ETI1 firmware) from Nov 2020 and the 915 equiv from samfrew.com for ~$3 and tried to flash just the modem to her phone...no joy. If it ends up not being able to connect to the network on Fri I'm going to try the full firmware as IIRC the T3 and T models firmware are interchangeable....I guess I'll find out in a few days.
I think you're right tho....it needs the update and my guess is that the new firmware will kill root and *possibly* prevent BL from being unlocked...making it impossible to get it back. I have an older one of these phones somewhere that has the brickbug pretty bad and it may become a sacrifice to the root gods....
I found this post in the T-Mobile support community: Note 4 Update January 2021 It was just passed over by the *meh* support team. I for one, have the same baseband/modem as OP. Since SurfRodder gets no joy from the latest T3 on his T model, then I am sinking in the same boat.
Android Police mentioned that requiring VoLte is T-Mobile's agenda, however it was denied by T-Mobile. So one possible solution is to enable VoLte, and see if that solves it after the switch, if your ROM has that capability.
Settings=>Phone or Call=>Voice over LTE settings=>Use VoLte when available
I really don't want to flash back to stock, this model and I have been together a long time.
If I find out anything in 2 days, I will post here.
Right. I guess I'll brace for impact on the 29th. But what should I expect -- what will and won't work? Is my impression from your replies correct that, upon T-Mo network update, my Note 4 will function normally for calls and texts, and be able to run on wifi; that the main thing I stand to lose is my mobile data connection?
I don't know. We're in this together. I'm hoping nothing happens and the Baseband ver. N910TUVU2EQI2 continues to work. If not, I'm going with these steps in order until one works.
Enable VoLte. No?
Flash the latest T3 Baseband (onto my N910T) No?
Flash to stock ROM and perform an OVA update. If the update ALSO updates the Baseband, then I'll reflash my ROM (Maximum OVrDrive) and give that a whirl. I'm no expert, so maybe compatibility will cease. Dunno.
Last step is to live with a bloated stock Note 4 and reassess.
I'm also in the same situation. Running a SM-N910T with the N910TUVU2EQI2 baseband and LineageOS 14.1 (Android 7.1.2)
There's no option in Settings to enable VoLTE.
I did check the phone's IMEI on the T-Mobile website and it says the phone will work after the 29th, but I don't know how much I should rely on that.
I don't want to upgrade to a new phone because it works perfectly fine and does everything I need it to.
I'll be watching this thread for any help or guidance because this has me really, really worried.
Thanks everyone.
Just got off the smartphone with a T-Mo tech somewhere in South Asia. I asked about the software update that was being pushed for the Note 4. She said that the update would affect only the baseband version, bringing it up to N915TUVU2DTI1.
So, I started researching how to update the phone while rooted, and found this thread: https://forum.xda-developers.com/t/...ut-losing-data-using-flashfire.3342896/page-2 -- Still reading through it to make sure I understand it.
One obvious question is: where to download this particular baseband version?
That's the latest news. Keep posting about this.
N915T? I tried to flash that modem yesterday without success. I even downgraded Odin to the 3.07 because older versions work better with older firmware (current is 3.14). I am going to attach the modem from N915T firmware I downloaded yesterday from SAMMOBILE. The modem associated with this package is N915TUVU2DTI1 as indicated here: SAMFREW.
(File Deleted - See post #10)
This might be nothing, but I took a look at the SM-N910T firmware on Sammobile.
Download Samsung GALAXY Note 4 SM-N910F firmware
Download the latest Samsung firmware for GALAXY Note 4 with model code SM-N910F. Check out our free download or super fast premium options.
www.sammobile.com
There's _two_ labelled N910TUVU2EQI2, one from 2017 (which I thought was the last firmware published for this phone) and one dated 10-29-2020. And I noticed that the newest one's date is exactly 90 days before the network upgrade on Jan 29, 2021. And 90 days sounds, to me, like a legal requirement. It's also the only new firmware in the last three years. I haven't downloaded it or tried to flash it, but since it's the only new firmware listed for years, maybe that's the update T-Mobile's pushing to this phone for this network change?
Thoughts? Has anyone tried flashing this firmware?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOLVED. The T-Mobile page is a typo. This is the proper modem: N910TUVU2ETI1. I successfully flashed it via Odin and the phone works properly as of 2/1/21.
Baseband ver. N910TUVU2ETI1. File is too large for upload so I linked it here:
Odin Download (Instructions in Post #17)
N910TUVU2ETI1 Download (For the SM-N910T)
Is that firmware for the Galaxy Note Edge (SM-N915T) or Galaxy Note 4 (SM-N910T)?
I'm asking because the firmware links you posted earlier (here) are for the Edge.
The first modem I posted was for the N915T because T-Mobile posted that it was the most current update for the N910T!!! See it here: T-Mobile N910T Software Updates. This is why I have been pulling my hair out! It's bad information! I screened it because if they change it, I don't want to be considered insane.
The link in my post (#10) above is the latest baseband/modem for the N910T, the regular T-Mobile Note 4.
N910T 2014-Date said:
I think I solved it. The T-Mobile page is a typo. I think this is the proper modem: N910TUVU2ETI1. There is no previous version with this name, and it's similarly named as the new T3 version. I successfully flashed it via Odin and the phone works properly. I guess I'll see tomorrow. Baseband ver. N910TUVU2ETI1. File is too large for upload so I linked it here:
Click to expand...
Click to collapse
Yeah, I ended up seeing that on either samfrew.com or mobik.top last night and did the same for her phone (when I got home tonight)...I guess we'll see tomorrow. I need to keep looking for another brickbug'd device as the first one I found has a bad screen too...I've gone thru several versions of these phones over the years between VZW, TMO, and DualSim versions. In any case, hopefully the ETI1 modem works and we can leave it be....otherwise I'll have to find another of my "bad" Note 4 T's and sacrifice it to see if I can regain unlocked BL...
edit:
links (note both still say Sep 2017 build date on linked pages, but previous page shows the Oct/Nov 2020 date ans also include proper modem)...also some of these require payment:
Samfrew: https://samfrew.com/download/Galaxy..._USA-__/OOfa/TMB/N910TUVU2EQI2/N910TTMB2EQI2/
SAMMOBILE: https://www.sammobile.com/samsung/galaxy-note4/firmware/SM-N910T/TMB/download/N910TUVU2EQI2/515094/
mobik.top: https://mobik.top/samsung/firmware/358462
1/29 - So far so good. SM-910T is working this A.M. with Baseband ver. N910TUVU2ETI1 Download
I've made no changes to my SM-N910T and it continues to function normally. Honestly, this is exactly what I hoped would happen.
I"ll continue to monitor this thread and post any changes I observe. I'd ask anyone in a similar situation to do the same.
N910T 2014-Date said:
1/29 - So far so good. SM-910T is working this A.M. with Baseband ver. N910TUVU2ETI1 Download
Click to expand...
Click to collapse
Just to make sure: I can use Odin to flash this and keep root? Will I be flashing only the modem (CP) , or also AP, BL, CSC, etc.? Stupid-Proof instructions would be welcome.
In ODIN, just use CP. Your root will remain. Use the file I liked to in Post #10, it is the baseband/modem only. Procedure:
From your phone: SETTINGS => ABOUT DEVICE => BUILD NUMBER => Click about 7-8 times
Go back one page and open DEVELOPER OPTIONS
Check USB DEBUGGING
Remove battery from phone
Open ODIN => Click CP => Find downloaded baseband/modem file and click. This preloads the file.
Plug USB cable into computer - DO NOT plug into phone yet
Replace battery
Turn phone on holding VOLUME DOWN, HOME, POWER BUTTON
Plug phone in
Press VOLUME UP - Wait for driver install and for ODIN to recognize your COM
In ODIN press START
That should do it.
One week after the network upgrade and my SM-N910T is still functioning normally.
Did anyone's device stop working properly?
aka_GrimJack said:
One week after the network upgrade and my SM-N910T is still functioning normally.
Did anyone's device stop working properly?
Click to expand...
Click to collapse
Mine's still running -- I think as if nothing happened; I haven't checked my 4G speed, but it still reads "LTE". I haven't yet flashed the new modem, though I still plan to.
No problems here. I'm still using the same old rooted phone and ROM. I see no changes after upgrading to the new modem.