Related
Hello. I have a problem with the droid 3 xt862. The phone is locked by verizon. The problem is that it has a software fault with the radio. In the setting of an android - "baseband version - unknown". IMEI - empty, the hardware menu * # * # 4636 # * # * in the phone info shows - unknown, disconnected, out of service, false. Unlock also does not work - after insert sim card - nothing happens, after entering the code to unlock # 073 887 * - "The process com.android.phone has stopped unexpectedly. Please try again"
I tried to flash swu with rsd, tried to flash other roms,tried to flash via recovery, bootstrap, safestrap , tried to "Flash Verizon DROID three OTA 5.6.890 to phone_psouza4", tried to flash a different radio.img - always in the baseband version - unknown.
P.S. I apologize for my English.
Has it ever worked on Verizon in your possession, or did you buy it this way? If you bought it this way you could probably send it back under warranty. I would definitely try to use this method http://forum.xda-developers.com/showthread.php?t=1339816 to flash back to stock. If it still has problems after flashing that way, then try to send it in anyway and see if they'll replace it.
If you bought it that way from someone else, try flashing using the above mentioned method and see if it works.
If it doesn't work or if it got this way because of you messing with the radio, I have no clue what else to do to fix it. Seems like it's above my level.
P/S: to unlock the phone using a Verizon unlock code, I believe the phone must be connected to an active line of service so that it can communicate with VZW. Entering the code only prompts the phone to communicate with them so they can unlock it from their end. So, it kind of makes sense that it would have no service whatsoever and that inserting a SIM would do nothing if the phone has no service from VZW and hasn't been unlocked.
BenSWoodruff said:
Has it ever worked on Verizon in your possession, or did you buy it this way? If you bought it this way you could probably send it back under warranty. I would definitely try to use this method http://forum.xda-developers.com/showthread.php?t=1339816 to flash back to stock. If it still has problems after flashing that way, then try to send it in anyway and see if they'll replace it.
If you bought it that way from someone else, try flashing using the above mentioned method and see if it works.
If it doesn't work or if it got this way because of you messing with the radio, I have no clue what else to do to fix it. Seems like it's above my level.
P/S: to unlock the phone using a Verizon unlock code, I believe the phone must be connected to an active line of service so that it can communicate with VZW. Entering the code only prompts the phone to communicate with them so they can unlock it from their end. So, it kind of makes sense that it would have no service whatsoever and that inserting a SIM would do nothing if the phone has no service from VZW and hasn't been unlocked.
Click to expand...
Click to collapse
I've already tried this method - successfully flashed (radio.img too), but there is no effect, baseband version - unknown and all the problems.
Thank you for your reply.
p.s. return is not possible, unfortunately.
w4_toleg said:
I've already tried this method - successfully flashed (radio.img too), but there is no effect, baseband version - unknown and all the problems.
Thank you for your reply.
p.s. return is not possible, unfortunately.
Click to expand...
Click to collapse
This phone has a 1 year warranty from Motorola (software included). If it doesn't work and has not been physically damaged, water damaged or has a bad ESN, Motorola will replace it. If you can't go through Verizon (no contract), then contact Motorola directly for a replacement.
Side note: If/when you send it back to Motorola, make sure it is bone stock and unrooted as this would clearly void the warranty.
Sent from my XT862 using XDA App
Sounds like they haven't even unlocked the phone from Verizon yet. Nothing will help this phone work on another carrier (other than Vodafone) if it hasn't been unlocked by Verizon. I mentioned above what to do if you can get a code from Verizon, otherwise good luck finding some code online somewhere.
I may be wrong, but even if you have a Verizon unlock code, I don't think it will work unless the phone is connected to a valid account, temporarily so it can communicate with VZW.
I have the same issue with my Droid3, help please
lost 3G edge2 work fine
eldar4uk said:
I have the same issue with my Droid3, help please
Click to expand...
Click to collapse
I've tried a lot of time: wipe factory/wipe cache/dalvik but nothing 3G. I've also unistalled safestrap. PLEASE without 3G is very frustrant!!!
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Bump?
Have you tried using Samsung Smart Switch?
DevicesNow said:
Have you tried using Samsung Smart Switch?
Click to expand...
Click to collapse
I didn't try Samsung Smart Switch, but I had reflashed it using Odin, and tried a factory reset and it didn't fix it, i got it fixed through Z3X box.
This happened to me also.
ashal said:
A few days after updating my phone to Nougat, my phone restarted itself, and after the restart, a security error showed up saying "This phone has been flashed with unauthorized software and is locked", and after unlocking the phone a screen came up saying that my device has been network locked and it can be unlocked using the device unlock app, and the invalid sim card error.
I was never rooted or anything like that, my phone had received OTA updates. I did not master reset, but I rebooted many times, and the error message appeared on every boot, but disappeared after a while allowing me to use my phone. And now, although the error doesn't seem to appear anymore, i still can't use my network, and when I checked the IMEI, it had changed to 350000000000006, and the one on the back is different.
Is there any possible way to fix this without sending this phone back to Samsung/T-Mobile for exchange, because I had bought this phone from USA but brought it to Pakistan, and Samsung Pakistan says that they would charge me for the repairs ( I still haven't visited them, they told this to me through mail).
HELP PLEASE?
Click to expand...
Click to collapse
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Hunterzzz said:
The same has happened with me. Can you please tell me how you managed to unlock. From where? how much it costed? Please help me. Thanks.
Click to expand...
Click to collapse
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
ashal said:
I had taken in to a repair shop who had a Z3X box. That's the only way to get it fixed. He downgraded my phone to Marshmallow and re-flashed the cert. I live in Pakistan and that costed my Rs.1000 (i.e. $10). Make sure you take your phone's box with you as a proof of purchase because changing IMEIs is illegal in many places.
P.S. I can't upgrade to Nougat now, if I will, the phone won't register to the network.
Click to expand...
Click to collapse
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Hunterzzz said:
Thanks mate. I also live in Pakistan - Lahore. I took my phone to Hafeez center and they charged me 1500. Now the phone is on Marshmallow. I'm receiving notification of update. I've tried 3 times but if failed to install. When I tap on update it downloads the OS which is about 1.3GB. then restarts to install but it fails when reaches 30%.
Can you please tell me why we can't update our phones. I'm using another s6 which is also of T-mobile and it's running fine on nougat.
Click to expand...
Click to collapse
Not sure about that but we can't update because probably our CERT files have been patched in EFS is messed, I got it done back in July 2017, and at that time, the guy who repaired it said that they didn't have Z3X's software update for Nougat, so they had to downgrade my phone to Marshmallow, and the patch they used won't work on Nougat. Don't know about yours though, maybe he used an updated patch or a different tool, you can ask that guy whether if its safe for you to update to Nougat or not, if he allows it, then try flashing Nougat through Odin, if it doesn't work you'll have to get it patched by him again. Don't update if he doesn't allow, otherwise he won't patch it again without extra charges, and if he allows that and something goes wrong you can blame him for that
I have done quite a lot of searching and it appears that what I am trying to accomplish should be possbile but I have had no luck.
I am trying to move an SM-N960U from AT&T over to Verizon using my Verizon SIM. As far as I can tell this model is compatible on both networks, but if someone could clarify why I am having issues, I would be grateful. Here is what I have going so far:
The SM-N960U is unlocked. I can confirm this on the AT&T site as well the phone as the unlocked animation plays every time.
When I insert the Verizon SIM (which is the correct SIM format, brand new even), the phone sees the number but will not connect to the Verizon network for data/calling
I have Odined the latest stock official Verizon ROM onto the phone, but this changes nothing for some reason. The AT&T software still persists after I install all of updated Verizon files through Odin (The AP, BL, CP, userdata etc). The install is always a success, and shows the loading bar etc, but nothing changes. It's as if nothing is installed.
I have used both regular Odin and the custom 3B Odin
I have factory reset the phone after the install as well, but the AT&T ROM remains.
I am out of ideas on how to get the phone to work on Verizon. Does anyone have an other ideas or see something I missed? Or is it just not possible?
thanks for any help
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?
Hello all,
I have an S21 Ultra that was originally a T-Mobile device, was unlocked, and then flashed to "factory unlocked" 998U1 firmware as found on this forum, and used with AT&T. Since the shutdown of their 3G network, however, I have been unable to make or receive calls and the "Enhanced LTE Services" option under Network Settings is unavailable to me. After a ton of fruitless troubleshooting, AT&T says I need new firmware. I was going to install the AT&T-branded U1 firmware from SamMobile in hopes that would solve my issue, but whenever I try to go to the bootloader to flash the new firmware, the phone just boots normally instead. I can't seem to access the bootloader, even after factory resetting the device.
Samsung has offered to reflash the device back to factory settings, which would make it a T-Mobile device (unlocked, presumably?) again. Does anybody know if the AT&T firmware linked above will work with VoLTE on their network? Would I be able to flash to that again to get the bloatware-and-branding-free experience while still having the device work as a phone?
Thanks for any knowledge or help, I've been beating my head against this thing for nearly a month now.
I may have solved my issue! Fingers crossed, will confirm tomorrow once I'm sure, but so far, here's what it looks like:
I had installed what I believed to be standard Samsung U1 firmware which I assumed would work regardless of carrier - I believe from this thread but don't quote me on that. Regardless, it was unbranded. When AT&T shut down their 3G network, I was hosed because the U1 firmware I'd installed did not have VoLTE/"Enhanced LTE Services" or anything like that as an option I could enable. After a ton of time, I finally figured out that it was a firmware/baseband issue.
So I downloaded the AT&T "branded" U1 firmware from SamMobile but the recovery menu wouldn't let me access the bootloader for as-yet-unknown reasons. The instructions to hold volume-down+power got me into the recovery menu, but that was as far as I could get. However, Iater discovered that with the device plugged into my computer, I could boot it directly into the bootloader by holding volume-down+volume-up. With that accomplished, I installed the AT&T U1 firmware and viola! VoLTE options were available, and with my SIM card installed I could finally make calls again!
Will use it all day tomorrow, see how things go and report back.
Could you help me i am basically in the same boat! What firmware for at&t did you download and where? Thanks!
I used the firmware at this link: https://www.sammobile.com/samsung/g...M-G998U1/ATT/download/G998U1UES5CVCB/1627452/
I couldn't get to the bootloader from the recovery menu, but could by using both volume keys simultaneously while the phone was powered off and plugged into the computer. Good luck!
There's a good thread on Reddit regarding CSC issues when flashing branded S21 devices to U1 firmware. Essentially, on the S21 series, particularly for TMB CSCs, it tends to be difficult to get the correct CSC software for VZW and ATT, particularly after flashing to U1 from U firmware. See this,
https://www.reddit.com/r/GalaxyS21/comments/roqwkc