I just bought a phone on ebay. unlocked samsung galaxy s3 sgh-t999. It's supposed to be brand new and was in the orig. box. But the build of the firmware is ZS and in kies it says
PDA:EMC
PHONE: LK3
CSC: EMC (CHN) <- CHN I presume is China
also my android is 4.1.1 and I would like it to be at least 4.1.2 preferably 4.3
but of course OTA doesn't work because of the country code. It says registering device then processing failed.
I've tried to flash using odin but I get aboot error with some roms and in some versions as well as sbl2 error with some roms and some versions.
and my phone in download mode says it's an I747 -- the at&t model. In gs3->settings->about device it says its a sgh-t999 which is what it should be.
Kies says the firmware is up to date. arg frustrating.
Everything about this phone works except for updating the firmware.
So I asked for a replacement...which I got today. Same stupid problem, not only that, but this one isn't recognizing my cut micro sim. So if it's between the 2 I would like the original one since it recognizes the sim.
I have read that I can change the country code, but I do not want to root the phone since I want it under warranty.
what should I do to update my phone?
Thank you for any and all help
Related
I have a galaxy s3 when I received the phone I rooted and installed a custom rom straight away. I thought it was an unbranded handset but when I have installed the unbranded firmware Kies comes up with your phone does not support software updates.
Only by looking at a similar sourced phone .
Your codes are probably messed up and Kies sees no firmware to match them or their actually is none .
jje
I thought that I bought it second hand and when I connected it to Kies I'm sure it was the LG8 update. But connecting it to Kies it now says unavailable to update.
Wait which firmware is KOR ?
Fixed it thanks changed the CSC from KOR to BTU.
Hi
I posted this problem in another thread, but most likely it wasn't the best place to do so. Hopefully posting it here, someone might have a better perspective and might have an answer...
I've read through the various posts in the forum, but I cannot seem to get a complete / definitve answer to my problem.
Phone: Galaxy S3
Original Firmware: Stock Vodafone Ireland (can't remember the exact version, but can trace it if required).
Phone originally was network locked, but unlocked with official key from Vodafone (no voodoo etc).
Description:
Downloaded Stock XXBLG8 from this forum.
Used a Win 7x32 with no Kies installed and with ODIN 3.04 flashed the phone.
No problems detected during flashing. When completed, did *#1234#
Found that phone had been updated correctly to AP:I9300XXBLG8.
Changed CSC to BTU.
Checked phone in download mode and firmware listed as "Official Samsung", no yellow triangle.
Checked in Kies and found that phone was upgradeable via Kies (got LH1 update via Kies).
Problem:
Since update, have a problem accessing MMI codes. The basic ones like *#06# or *#0000# and similar, work fine. Others (more complex) for example *#7465625#, do not work. Typing them produces an error "Connection error or invalid MMI code". I know these particular codes worked before flashing to XXBLG8.
Apart from this, the phone seems to be working perfectly well.
Is there a solution to this problem?
Any help gratefully accepted.
Having the same problem myself. I was Voodoo unlocked and got the unlock code from Vodafone IRE today but it won't work. Keep getting the same errors as you.
I was on stock XXBLG8 too, tried it with the original Vodafone firmware but still had problems. Would be interested if anyone had any more info about this.
They've probably been disabled by samsung. But they do work again on the latest JB leak.
Sent from my GT I9300 using buttery Jelly Beanz
I have an S3 that I rooted a few ago, using CF-Auto-Root-m0-m0xx-gti9300.tar.md5 and Odin. The main reason was to use ClockWorkMod to backup an image of the phone.
Last week it started to play up. It regularly freezes and the WIFI will not connect. As I had it rooted, I tried the cyanogenmod 9.1 ROM. I still had issues with the WIFI on this, which led me to think that it was a hardware problem. I have gone back to my original backup (after rooting the phone), and it seems fairly stable as long as I keep the WIFI off.
I wanted to try reverting to the stock ROM, and if that doesn't help, I was hoping to try and get it sorted under warranty.
I was following the excellent guide on http://forum.xda-developers.com/showthread.php?t=1710613 but I cam a bit stuck on selecting the stock ROM to revert to.
I'm on the Orange network but I got the phone from dial-a-phone, so I didn't know if I should use the unbranded ROM or the Orange ROM. Orange has also merged with T-Mobile, so there is a third possibility, EE.
Using the keyboard shortcut, my phone reports:
AP: I9300XXEMC2
CP: I9300XXEMC2
CSC: I9300OXAEMC2
Do these refer to the original software or the firmware I flashed to get root permissions?
Any advice welcomed!
Thanks
It will be unbranded BTU.
Dial-a-phone is owned by phones 4 u. All these companies (CPW etc) supply unbranded handsets so they can be sold on all the networks they resell for. That way they're never left with a surplus of O2 phones etc, because they have 1 stock.
If you connect your phone to Kies it will tell you your version, unbranded BTU will be like the screen clip attached, if you don't have that download it from Sammobile and install via Odin
Hello
i put my cloesed my phone and put it on charge and tried to open it next day and it didnt open. Logo of samsung is flashing.. My phone is GT-I9300 sim unlocked and dont know what carrier it is.. I tried kies software it showed " update is not required" . but i have noticed that by putting phones s/n number kies software showed my phone is TMU which is United Kingdom T-mobile . after i tried odin and found firmeware for TMU from sammobile. it failed and showed "There is no partition".What should i do now ?
Try the rescue firmware from general forum, flash with Odin. But sounds like the emmc chip is damaged, new motherboard required.
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
SOLVED
cw9002 said:
I bought a s9+ from swappa around February. I bought my mom one from the same supplier a week ago. At first I was concerned that her's had ATT logo until I realized it would change once a tmobile sim was put in. Her's is now SW ver Tmb/Tmb/Tmb. Then I noticed she is at Android 10.0 UI ver 2.0. I am stuck at Android 9 UI ver 1.0
So It seems I was worried about the wrong phone. It is MY phone that can't get updates. My baseband is:
G965USQU7CSK6 which I believe is an ATT baseband. my SW ver is Tmb/Tmb/Att
I tried connecting to smart switch and it says I am up to date. I tried putting in an at&t sim card (that no longer is in service) and smart switch doesn't complain about anything but it still says it is up to date. Doing OTA while using At&t sim card also says I am up to date. I am CLEARLY not up to date. My last update says Nov.1, 2019.
I have used Odin before...mostly for rooting phone. I haven't rooted since the s5 ( where I could take the battery out ). Little paranoid to use Odin considering I can't take the battery out, but with good instructions I will proceed.
Any help on how to update and especially update on tmobile network would be extremely appreciated.
btw I'm in the US and my model is SM-G965U
-Craig
--UPDATE
I have researched a bit and found that it IS possible to change the firmware over to Tmobile using a patched version of Odin.
I downloaded from
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
the 3.13.3_3B_PatcheD.zip
I downloaded G965USQS7CSK3_G965UOYN7CSK3_TMB.zip
from sammobile, which is for Android 9
I would love to be able to use HOME_CSC but that may not work. I could really use some hand holding going through this process.
Is this the correct firmware? Should I be using Android 10 firmware if that is ultimately what I want? HOME_CSC or no? I notice they have the 10 version:
PDA G965USQS7DTB1
CSC G965UOYN7DTB1
as well, which is Android 10 for Tmobile. Also, knox ? will this trip the knox counter thing-a-ma-jig?
Thanks
Click to expand...
Click to collapse
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
cw9002 said:
ok, so I bit the bullet and decided to go ahead. I used
odin 3.14.1_3B_PatcheD.zip just to be sure
I made sure my phone was unlocked: yes it changes carriers if I put in different sim. When in Tmobile sim Settings->Connections->Mobile Networks->Network operators , yes it has a search networks button and it eventually comes up with other carriers so....safe to say I had unlocked phone ( but not samsung unlocked ie. SM-G965U not SM-G965U1)
I used the latest android 9 firmware. and I used HOME_CSC ( even though I did a backup with smart switch b4) Everything went smoothly, and I still have my apps and now I can get an ota security patch for it. Will write back once I am up to Android 10. oh, btw I am still at SW ver Tmb/Tmb/Att , but I've got ota updates so I don't care
Click to expand...
Click to collapse
I am now at the same baseband version as my mom. Everything worked perfectly. I suggest you go with the least change possible to get to the point that you are able to do OTA updates. For me this was going to the latest Android 9 that they had at sammobile since I was on Android 9 and going with the Tmobile version. I hear the carrier doesn't even matter these days, but I decided I wanted to make sure it was Tmobile compatible so I chose the Tmobile version from sammobile. Happy trails to you in your endeavors. Hopefully you can learn something from mine.
Hey, I really want to thank you for this! I had the same issue and was exploring similar solutions. After several days of researching alternate plans, I was about to give it up as too risky until I found your post - by googling for hints: "SW ver. TMB/TMB/ATT"! You helped me take the dive, and I'm now happily past having a second-hand S9 (sm-g960u) that wouldn't do an OTA update. After a flawless flash, my first OTA request got me to Android 10, (UI 2). now I have a follow-up update scheduled for the wee hours. (And, yes, I'm still at "TMB/TMB/ATT".)
Perhaps like you, I started by investigating the possibility of flashing the UNLOCKED ("U1") firmware. After learning it was possible with the _patchedD Odin, it still scared me enough that I decided on a more conservative approach and followed your exact advice. I especially appreciated your plan to flash NOT the latest update, but the last Android 9 TMB update. That turned out to correspond to the ATT version on my phone, making TMobile either unable or unwilling to offer an OTA update.
History: This is my third used S9. While all were sold as UNLOCKED, only the first had the "U1" model suffix (SM-g960u1). When the second one booted up as a TMobile phone, I felt tricked - but also lucky that I got the right carrier. That's when I learned about the difference in model numbers. As you noted the U1 firmware is factory unlocked - attached to no carrier. When my third phone booted up with a Verizon greeting I figured I could be facing trouble - even though it accepted my TMB sim card.
The seller explained to me that my phone was part of a batch of ATT phones, all "SIM unlocked" using a Verizon sim card. I think sellers of phones with claims to be unlocked should be required to specify whether FACTORY or SIM unlocked.
Hope this great contribution of yours will continue to help others.