The reason i want to do this is i own an ATT s6 edge (SM-G925A) but im in the uk and im on the H3G (3) network. It is network unlocked. It would be nice if the phone acted as if i had bought it here (able to update OTA, boot with 3 logo etc). I found the firmware on sammobile (SM-G920F), it was only a single file though, using Odin3 i loaded it into the AP tab, but i just got a fail and a soft brick which i fixed with the original ATT firmware that has 4 files. AP,BL,CP and CSC. I'll admit i'm not sure what they do individually.
I really want to know, is what i'm trying to do even possible and if so, where if i needed, can i get a more complete firmware file? I'd be really grateful of any help or advice, thanks.
Related
Hi Guys, I apologize if this is in the wrong forum. Noobie to this forum as i am stuck with a phone I can't get to work. I just bought a used phone which was made for the US market. It's an unlocked Verizon Galaxy S5. When I first turned on the phone and saw the Verizon logo I was a bit annoyed as I did not think an unlocked phone would have a propietary logo. So I tried to flash the phone with Odin. As I am with Bell Canada I tried to flash the Bell Canada ROM, but it wouldn't work. I tried looking for a ROM that would allow me on the Bell network but I did not find one that would actually take. I kept getting write error and the flash would fail.
I was finally able to successfully use Odin to flash the phone,. SO right now I have the latest ROM for the Galaxy S5 for USA.
Can someone point me in the proper direction as to which ROM i should be trying to get this phone to work on the Bell network and use 4g/LTE? Right now this USA ROM is not allowing me to connect with the 4g network. I can only call someone on wifi, which is pretty useless to me.
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.
I have been at this issue since Saturday and gone through a lot of possible solutions but to no avail. So first of all i am in Ghana. A friend came to me with his s6 edge that he had some issues with his phone going off when he unplugs the charger and getting stuck in a bootloop when turning it on unless he plugs a charger in before it boots up fully(even with full charge)
So first of all he wanted to do a factory reset(phone was not rooted). Factory reset completed successfully but issue still persisted.
Specs of the phone was:
android 5.0.2
model number = SM-G925F
original csc (i wasnt able to note that down because downloading stock firmware was going to be the last ultimate weapon. first i was going to try some custom roms to see if it fixed the issue. Besides it was working fine here in Ghana.)
So that's when i flashed a twrp and i dont exactly remember but i think i might have tried to flash a lineage OS or something. But long story short, when u try booting up, the samsung galaxy edge screen with powered by android came on and stayed there. and it did not go on to boot up.
After trying through the night i then decided to use the ultimate tool and flash a stock firmware. Try as i might none of them got past the "Repartition Operation Failed" portion of flashing it. The Pit File was becoming an issue. Tried firmwares for my country, countries nearer to us, contries in africa and finally even european firmwares. And since from reading from here and other forums that the F variant was an international version the international pit files should work but they werent.
All this while whenever i go to Odin Download mode on the phone, the product name there was SM-G925D. This started the confusion because at that point i had looked through alot of firmware and that was not an option. When i searched google for that, the search results mostly correlated it to SC-04G, which looking at it was a Japanese firmware. I didnt want to use a japanese Firmware for obvious reasons. At least i wanted a firmware that was by default in English. But after about 2 days and seeing a lot of answers saying stuff about going to settings and checking stuff there plus me wanting to see an interface and work my way from there i succumbed.
And lo and behold, it flashed on the first try(i used the 4-part files firmware. It was android 7.0). But when it came to booting up, the splash screen had changed from samsung bla bla bla powered by android to NTT DOCOMO powered by android. But it booted up and i skipped through the setup. i had to change the language to english but there were a lot of japanese bloatware that came with it. But as i expected when i popped a sim card into it, and restarted the phone, there was the not available symbol(circle with a bar across) where the network bars were supposed to be.
Seeing that this was not going to do, i went to the settings this time to check on any important details and this were the new details
android version 7.0(January, 2018)
model number=SC-04G
build number was now SC0.....(cant write the full code as im currently in odin mode)
But obviously it was the japanese network. After this i have downloaded more firmwares and they all fail at "Setting PIT...Re-Partition failed". Somtimes i try to mix the 4 files up using maybe the CSC portion of the Japanese firmware but BL, CP, and AP of firmware from my region. This time the error is "sboot.bin failed".
And that has been my grind till now. Downloading likely firmwares and all failing to doing extremes like the mix and match. When the mix and match with BL, CP, and CSC of Japanese with AP of my region works and eventually boots up, there is no touch input. The touch does not work. When that happens i just have to start all over with the SC-04G, which never fails to work.
I have even seen some things about changing csc files in the file explorer with root so i flashed the Japanese FW and rooted it. Went through the processes but to no avail.
PS:
The first part of the Odin screen where you choose to continue or reboot is now completely in Japanese whiles it was formerly in English.
And there is no indication on the phone itself that it was from Japan. The back says Samsung and below it says Galaxy s6 edge. Friend bought it from a shop in Ghana here brand new.(not from a carrier)
****So here lies my confusion. How come a phone with an original model number of SM-G925F have a Product name of SM-G925D in Odin and hence only Flash Japanese Firmware SC-04G(CSC code = DCM) but would not flash any of the international variants. Even if i can eventually get the Japanese firmware to read the sim card we can manage it that way. But thats for when there are no options left.
So please i would like to know your ideas as to how this is happening and any possible solutions that might be different from what my batallion of open tabs are telling me. You can also let me know if you want any more details i might not have included. Looking forward to hearing from you guys.
Update On Issue
I ended up using the japanese firmware in the end because it wasnt picking anything else.
This time after the setup process, it picked up the sim card and the imei is available. So since network is now available i just rooted it with cf autoroot and removed the japanese bloatware and everything looks normal now.
Except the original issue of going off randomly whn power cable is pulled out even when having full charge.
:good:
A few days ago I got my Samsung A21s (SM-A217M) and I wanted to test out different firmware regions (choose the one where I live) so I downloaded 3, one was from Brasil and the other 2 are from here (tripled checked the CSC) but when I try to flash the correct firmware from my region it passes but when the phone boots up it looks exactly the same from the brasilian firmware, same network providers, apps language, etc. I have even tried just flashing the CSC but nothing has worked at all. Is there something that im missing? Is there another method that will allow me to change to the correct firmware?
Converting your Unlocked device over to FirstNet firmware requires Patched Odin you need the v3.14.1 Patched version. You will also need the newest TMB (universal) carrier firmware, links below. Extract the zip when the download completes. You will not lose any data or factory reset during this process. You will need an ATT sim card.
S22
S22 Plus
S22 Ultra
Take your current S22 running the unlocked U1 firmware (don't skip this step, only U1 firmware can make the change to the ATT - CSC) and insert an ATT sim it has to be ATT not your FN Sim. If you don't have one you can try your local ATT store with a FirstNet rep and explain that you just need an unactivated ATT sim. If they give you any trouble, WalMart sells prepaid ones for $10.
Insert the ATT sim, you will get a pop-up explaining that the phone needs to restart to apply ATT settings. Let it restart. Once your phone is up and running, power it down.
Open Patched Odin and load up all the respective files from the folder you downloaded. Use BL, AP, CP and HOME_CSC (using the other CSC will factory reset and revert to XAA firmware.) now put your phone in download mode (boot up while holding power + vol up + vol down.) Once in download mode connect the phone via USB to your computer. Once Patched Odin recognizes the phone go ahead and flash. Your phone will reboot with an ATT logo. You can now swap back to the FN Sim.
Now you have a FirstNet S22.
What are the benefits of this? Just allows you to use a firstnet sim?
I assume since it's FirstNet, this works for the USA Snapdragon variant? Also, does this still trip Knox since you are just changing firmware and not rooting?
*** Took the chance. Works great and super easy. Thanks for the guide!
Does flashing to ATT firmware like this preclude the auto switch function of the unlocked model redownloading the appropriate firmware OTA when a different SIM (i.e. Verizon or T-Mobile) is inserted?
Will this void my warranty?
brajonrondo said:
Converting your Unlocked device over to FirstNet firmware requires Patched Odin you need the v3.14.1 Patched version. You will also need the newest TMB (universal) carrier firmware, links below. Extract the zip when the download completes. You will not lose any data or factory reset during this process. You will need an ATT sim card.
S22
S22 Plus
S22 Ultra
Take your current S22 running the unlocked U1 firmware (don't skip this step, only U1 firmware can make the change to the ATT - CSC) and insert an ATT sim it has to be ATT not your FN Sim. If you don't have one you can try your local ATT store with a FirstNet rep and explain that you just need an unactivated ATT sim. If they give you any trouble, WalMart sells prepaid ones for $10.
Insert the ATT sim, you will get a pop-up explaining that the phone needs to restart to apply ATT settings. Let it restart. Once your phone is up and running, power it down.
Open Patched Odin and load up all the respective files from the folder you downloaded. Use BL, AP, CP and HOME_CSC (using the other CSC will factory reset and revert to XAA firmware.) now put your phone in download mode (boot up while holding power + vol up + vol down.) Once in download mode connect the phone via USB to your computer. Once Patched Odin recognizes the phone go ahead and flash. Your phone will reboot with an ATT logo. You can now swap back to the FN Sim.
Now you have a FirstNet S22.
Click to expand...
Click to collapse
Hello, not trying to say anything is wrong just want to try and understand a little better. Why use the TMB carrier firmware instead of getting the CSC ATT from the website?
"https://samfw.com/firmware/SM-S908U/ATT"
GlJ0E said:
Hello, not trying to say anything is wrong just want to try and understand a little better. Why use the TMB carrier firmware instead of getting the CSC ATT from the website?
"https://samfw.com/firmware/SM-S908U/ATT"
Click to expand...
Click to collapse
ATT was not available at the time of writing. As you can see they rarely leak out. At this point in the game, you just want to download either the equivalent or newer build than you have on your phone, in order to avoid any data loss.
Flashing TMB (which historically has been near the front of the update pack) contains ATT in the firmware. Back at launch, the hotspot was somewhat finicky until you downloaded at least one ATT OTA update directly. I no longer have an S22 to test if this is still the case, but it was working last I checked.
brajonrondo said:
ATT was not available at the time of writing. As you can see they rarely leak out. At this point in the game, you just want to download either the equivalent or newer build than you have on your phone, in order to avoid any data loss.
Flashing TMB (which historically has been near the front of the update pack) contains ATT in the firmware. Back at launch, the hotspot was somewhat finicky until you downloaded at least one ATT OTA update directly. I no longer have an S22 to test if this is still the case, but it was working last I checked.
Click to expand...
Click to collapse
Alrighty thank you for the quick response honestly wasn't expecting that. I m going to try it I believe I understand the steps correctly and if not then gonna ask to exchange it for the ATT model. Thank you for all your info!