Related
Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Cliff666 said:
Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Click to expand...
Click to collapse
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
thisisapoorusernamechoice said:
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
Click to expand...
Click to collapse
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Odin will do it as long as there are full install files for you to use.
Cliff666 said:
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Click to expand...
Click to collapse
You need an AT&T SIM card in the phone in order to install AT&T OTA updates. You can't use Kies to update because AT&T won't let Samsung post AT&T firmware on Kies. So your only option is to use Odin and the guide posted above.
Hello everyone. While I'm not new to visiting this website, I am new to posting here, so forgive me if I make a mistake.
My S5 doesn't have an active at&t Sim card, and before you say to use Odin to downgrade to PA2, or to go to Best Buy/ Samsung Experience or whatever it's called, the USB port on my phone is broken (currently I charge it wirelessly). My S5 is on PA5, and I would like to update it to the latest version of Marshmallow (PH2 I believe).
Can anyone tell me where I could get the files to do so via the recovery menu? Or even better, can someone provide them? I'd really appreciate it.
If not, borrowing a Sim card is still an option, but it's gonna be a long while before I can do so.
As of now you must downgrade to PA2 first. For now this is the only way.
Your best bet is to find someone with ATT sim card and use it to OTA
Hi. My fiance has the G900A galaxy s5 and it will not update. Its on 5.0 lollipop. Ive been trying to update it to marshmallow for months now and it won't. It always says software is up to date. It has enough room to update cause I know marshmallow is a big file. Does anyone here know why it won't update?
Its never been rooted or tampered with at all.
Anybody??
I'm having the same issue
I'm having the same issue, however, my daughter's ATT S5 is on Tmo. I put an ATT SIM in it yesterday and it showed the update available, but won't pull it down because we can't turn on her WiFi. I wiped the phone and restarted and still cannot turn on WiFi. Now I'm looking for a way to run the OTA update over ADB.
I had a similar issue. I missed one or two previous OTA updates and found that my phone would not update to 6.0 Marshmellow. AT&T store could not assist and was referred to Samsung employee at Bestbuy whose kiosk happened to be not working. I tried with Odin, Kies, and Samsung Sync all of which do not work since ATT does not supply them with their firmwares. They all just showed my phone as up to date. I found a thread on how to manually update via emergency mode. I followed the directions and downloaded the firmware. Dropped the file into my external sd card, named it update.zip, and rebooted in emergency mode. I was able to update with one of the in between firmware and after that then allowed me to use the OTA. I am on an ATT S5 active. I bet you would need to do something similiar since you're still on 5.0. I believe there was 2-3 in-between updates before the latest.
http://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016
Updated do not show up unless a valid AT&T SIM is in the phone. For some reason it checks to see if you have a valid AT&T service account before accepting the request to connect to the OTA update server. You will not get an update otherwise.
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
ww007 said:
Hi everyone,
This is the first time I've done any phone flashing so please excuse any ignorance on my part.
I have the N960U1 and I'm trying to flash it to the AT&T firmware so I can use HD voice and wifi calling and such. I had the stock firmware fully updated to the November 2019 security patch before I started.
So this is what I've done so far:
1. Downloaded the latest U1 AT&T firmware files from sam mobile here
2. Loaded all the files into Odin 3.13.3, using HOME_CSC to preserve my data. The sam mobile file did not have any USERDATA files so I left that blank.
3. Flash was successful and phone rebooted normally. However, no AT&T boot-up screen was shown and no AT&T apps present (good), but also no wifi calling option in settings and I confirmed by calling another AT&T phone that HD voice was not present either (bad). Basically it seemed like nothing changed.
4. Found this thread with USERDATA (I used the one under the SGA-2 folder).
5. Re-flashed everything as in step 2, this time adding the USERDATA I obtained in step 4.
6. Odin said the flash failed, phone booted to the Emergency screen so I thought I had bricked my phone but luckily I was able to re-flash as in step 2, omitting the USERDATA again.
7. Again, phone boots normally but nothing has changed. Still no option for wifi calling.
8. Called AT&T to check if they needed to provision my phone or SIM card or something, but the rep I spoke to said there's nothing to do on their end and she sees that wifi calling is actually enabled on my phone.
I've also read that the newer Samsung firmwares are supposed to auto-detect which provider's SIM card you have in and load the appropriate firmware automatically, so I removed my SIM card while the phone was still on, turned the phone off, put the SIM card card back in, and turned my phone back on. Still nothing changed.
What am I doing wrong here? And why isn't the phone automatically loading the appropriate AT&T firmware since I have an AT&T SIM?
I should note that I've had this phone pretty much as soon as it came out and I know that the older firmwares did not have that auto-detect thing. I guess I should also be wondering why my phone didn't load up the AT&T firmware when I updated it to Android 9 the first time, or whenever they started the auto-detect thing. Is there something you need to do to trigger it?
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
bober10113 said:
did u use patched odin 3.13b?
also for it to change u need to wipe. so use csc.md5
because the sim was already in the phone. no changes are detected so no csc swap. ( sales code is identical as before because u never changed sims. so that's why u need to wipe. csc will auto detect and change only if a different carrier sales code sim is inserted. then it will wipe fone by itself. so in your case a simple factory wipe might do it or just reflash U firmware but this time choose csc.md5)
Click to expand...
Click to collapse
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
ww007 said:
Thanks for the reply. I did not use the patched Odin, just the unpatched one. From what I've looked up, the difference seems to be cosmetic and the patched version failing less? For the most part, flash succeeded (except when I tried to mix and match a different USER DATA file). Are there any specific differences with the patched version?
I was hoping to keep my data and settings, but I will try to flash it next time with the wipe when I know I won't be needing my phone for a while. Do I need a USER DATA file to succeed? Because sam mobile didn't have it in their AT&T file.
Thanks again!
Click to expand...
Click to collapse
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
bober10113 said:
patached odin is to switch from U to U1 firmware and vice versa. there's a thread about it. maybe check it out?
https://forum.xda-developers.com/galaxy-note-9/how-to/u1-note-9-official-firmware-guide-to-t3927478
firmware links are old but the general logic on how to do it should still ring true
Click to expand...
Click to collapse
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
ww007 said:
Yeah I saw that thread, but it seemed pretty specific about converting from AT&T to unlocked, and I didn't see anything about the other way around. And for some reason, the latest U firmware for AT&T on sam mobile is only 8.1.
That was actually going to be my first option (downloading the AT&T U firmware and flashing on my U1 phone). But as I mentioned, sam mobile's version is outdated.
Which actually brings me to another question: how is there an AT&T (or any other carrier) version of the U1 firmware? Is that supposed to convert the unlocked phone to a carrier branded one?
Click to expand...
Click to collapse
just use samfirm tool or frija to dl firmware.
Hi guys,
I have a question about obtaining Android 10 AT&T firmware for the SM-960U. I'm currently having an issue where I bought the Samsung Galaxy Note 9 N960U1 factory unlocked from Samsung themselves. My current carrier is AT&T. However, I've realized for a while that my area doesn't have a good signal (1 bar to no service) due to the location where I am. I am trying to install AT&T's firmware with the boot logo and its software's bloatware to obtain Wi-Fi calling. However, I am having trouble. Currently, I've flashed my N960U1 with AT&T's U1 Android 10 firmware from the site using Odin. I see that it's been flashed successfully after doing a clean install and see AT&T firmware in the phone. However, it did not give me an AT&T boot logo screen or give me the Wi-Fi calling option. This is carrier unbranded. It's still the same like it's from the factory unlock no carrier firmware. So, after doing some research, I see that what I have to do is: clean flash AT&T's U1 firmware on the device (which I did), then, finally, install the U firmware to bring on the AT&T boot logo screen and WiFi calling. However, I am unable to do the 2nd part, because the only available firmware for U firmware (AT&T's bloatware) is Android 8. Due to the bootloader being version 4 in Android 10 and version 2 in android 8, I cannot downgrade even on a cracked Odin version. The phone gives me a SW REV error and odin gives me a write error. I worked on this for 8 hours, don't try to fight me on this lol. This is because Odin understands that the phone can't be downgraded due to the bootloader version being higher. This can be seen in the firmware names when comparing (Android 8: N960USQU1ARG6. Android 10: N960U1UES4DTD1).
In summary, I need to find the SM-960U AT&T carrier-branded Android 10 firmware. Right now, on Sam Mobile for N960U, the only firmware that comes up is Android 8. Downloading the latest firmware for the SM-N960U1 on Sam Mobile doesn't help me obtain wifi calling and the AT&T boot logo. Any suggestions? I really need help and appreciate it if you guys could help me. I can't find AT&T's U anywhere. Thanks!
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Awesome. I’m going to try this tomorrow. I’ll update this post with the results! Thanks for the help.
butchieboy said:
You can flash any U firmware they are the same. As long as you have At&t sim it will provision to your sim. Since you are U1 you will need to do factory reset before flashing with Odin. You can use USC..Tmobile..Verizon. Dont use User data when flashing just use BL..AP..CP..CSC. At&t doesnt post their locked firmware for whatever reason.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader:
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer port also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just updated.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Carl_Sagan_Cosmos said:
I am really glad I found your post and I'm going to attempt this same procedure today. Quick question, does it matter if / when your SIM is inserted into the phone? Just wondering if I need to leave it in or out during this process or whether that will even have an affect? Is your Wi-Fi calling still working currently, btw?
Click to expand...
Click to collapse
Hey Carl! Sorry for the late response. I'm glad you found my post as well!
I apologize for this, I should've mentioned this in my original post: please leave the AT&T SIM card inserted in the device the entire time during this process! When the phone reboots after Odin flashes, the first thing it searches for is what SIM is inserted so it can flash the appropriate carrier setting. Do not remove the SIM during any part of the process from start to finish.
Secondly, yes! The WiFi calling feature is working great on the phone. I'm glad after two years of having the phone I was able to get the feature this month. Good luck. Please let me know if you were successful in flashing the firmware, I'd really like to hear your results! My notifications are turned back on for this thread.
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
abulnass said:
What to do if i don't have at&t sim card, not even usa sim card, i'm in egypt and brought my n960u from usa, i installed u1 firm but realized that no wifi calling or volte so tried to install tmobile carrier firm and nothing appeared then tried at&t and also nothing appeared, neither the options nor the boot logo for tmobile or at&t.
what to do please help!
Thanks in advance
Click to expand...
Click to collapse
If you are trying to flash T-Mobile or AT&T bloat ware without a carrier SIM card, it will not work.
Hi. What if I have an AT&T sim card, but I'm also outside US. Not sure if the sim card is active or not.
My biggest worry was, I just had my phone factory unlocked so I can use a local sim card here in the country.
Will this work? And if it will, will my phone go back to being locked by AT&T?
Hi, I tried this process the way you have it listed and it is not working. I keep getting a device info error in Odin. Tried the newest firmware and an older version
robertj51 said:
Hi guys! After 18 straight hours of fiddling and researching, not getting a definite answer from XDA and Sammobile forums since my phone was on the latest bootloader v4: I've finally been able to find out how to do this, thanks to butchieboy and a culmination other forums, I've finally been able to successfully figure this out!
Basically, here are the steps to successfully do it if you're on Android 10/bootloader v4 and want to make the switch without downgrading the software on a lower bootloader. Make sure you do a clean reinstall beforehand. Everything should be off the phone.
1. Download and flash U1 firmware from samfw as a clean install. I used ATT's U1 firmware (follow the instructions below to do so). I did this first and was confused about why I didn't get the bloatware after. However, this is only the first step.
2. I found the latest firmware from Verizon for the SM-960U (not U1), and downloaded patched Odin 3.13.1b onto my computer. I downloaded these both from samfw's website. You'll need the patched version to be able to switch from U1 to U firmware. I used Verizon's instead of T-Mobile's because they had posted the latest version for Android 10.
3. Run Odin as admin, make sure you're using a computer with open USB ports for data transfer (one of my computers gave me an error, switched to another one, it worked fine). Make sure you use a good data transfer cable also.
4. Enable USB debugging on the device, and reboot the phone into recovery mode. Don't connect it to the computer yet. Do not remove the SIM card during any part of this process. Leave it inserted the entire time.
4. Load up BL..AP..CP..CSC as butchieboy states. Do not use home_csc and do not use userdata. They are not needed. CSC needs to be used because it has to be a clean install in order for this to work properly. By not using userdata, the device will load up the appropriate carrier bloatware automatically using the SIM card provided!
5. Go ahead and connect the phone via a data transfer cable. You will see a serial COM port labeled in blue connected on top. Now flash Verizon's U firmware
6. The phone should successfully flash via Odin, and it will reboot
7. I had gotten into this weird recovery state at first when it rebooted. I forgot the error name on the bottom and was confused at first it was SW REV or something I think. However, I think the reason for this is because the phone doesn't know which carrier setting to apply just yet. There were options to reboot, update from SD card, and more.
8. Select "reboot" using the power button!
9. You'll see the AT&T logo as the phone reboots! Not sure why my phone didn't end up erasing, it just apparently did an update.
The first thing I see after the apps loaded was... the WiFi calling setup screen... Victory! Thanks to everybody who posted on online forums. And thanks to butchieboy for the straightforward answer. I hope this helps anybody online looking to do the same thing whether it's their Note 9 or any other device. Good luck!
Click to expand...
Click to collapse
right at the beginning using odin it threw me an error, but it's probably because I used CSC home ...? How can I verify on Samsung Note 9 if I have an unlocked bootloader ..?
Edit: He used CSC not CSC home and an older version of odin. And I have a sim from Europe and it works great.
I need help, i have a sm n960u factory unlocked at&t branded using straight talk at&t sim. I have no volte or wifi calling settings. With special code they are greyed out and provisioned. Is there any way i can fix this issue?