Which firmware to unroot? - Galaxy S6 Edge Q&A, Help & Troubleshooting

I would like to unroot my Edge with Odin, but I'm unsure which firmware to download. The phone came with G925FXXU1AOE4. I found several versions of this firmware with different regions. How do I select the correct one? How can I find which region firmware is on my phone? Does any of this even matter? I'm worried about loading a firmware that will give me a region or carrier lock, if that's even possible. Thanks for any insight.
AP: G925FXXU1AOE4
CP: G925FXXU1AOE3
CSC: G925FOJV1AOD6

OK, I got it done and here's how I did it. Hopefully it helps somebody else in doubt. First, I found a fantastic app called "Phone INFO *Samsung*". This is a great app that gives more info than you will ever need. The app revealed that my phone's firmware CSC is MTZ, which is Zambia. A little searching revealed that Tmobile provides service in this country. That explains why my phone already had a Tmobile APN set up. It worked perfectly right out of the box. Next, I went to Samsung-Firmware.org and found the exact same firmware I have. I loaded the firmware with Oden and the phone booted up with no root, no tripped knox, original just like new. I have since rooted again, set up to my liking and am enjoying the hell out of it. It has been working fantastic with Tmobile here in Chicagoland. Earlier today I was a couple hundred yards from a cell tower and had 4 bars, so I ran a speedtest and got the fastest speed I have ever seen anywhere (62 Mbps down, 26 up). I would recommend this firmware to anyone using tmobile who wants to stick with 5.0.2.

Related

[Q] Which stock image to use for dial a phone, UK

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

[Q] Phone settings say g900f but odin says g900t

Hi Guys,
2 months ago I bought a Samsung s5 in Hong Kong.
While travelling through South East Asia this device worked fine.
While traveling through New Zealand (Old home) this phone worked fine.
While traveling through America (New Home) this phone worked fine for the first 2 weeks (on the metroPCS network).
The problem:
Randomly after 2 weeks the s5 stopped connecting to the metroPCS mobile network even though the network was available (btw metroPCS uses the T-Mobile network). It gives errors such as network not available or cannot register with network.
Things I have tried:
-Im sure the APN settings of the phone have not changed and I have double checked to see if they are correct.
-replacing the sim card with another does not fix the issue
-soft and hard reset of the phone does not fix the issue
-Getting metroPCS to refresh the service on this number does not fix the issue
Other important info:
-This phone was purchased in hong kong but it is from the Philippians according to Kies's firmware information (XTC is the country code)
-It is running a custom allianceROM that must have been installed by someone in hongkong
-The device is rooted (superuser app installed)
-the model number as shown in settings is g900f BUT when attempting to flash with odin the phone displays g900t and fails to flash the latest Philippians verison of kit-kat
I have 2 questions:
1. Any ideas why my network connection has suddenly self destructed (and how to fix)?
2. Would flashing a stock ROM to my s5 help? and if so why is there conflicting information on which model I own (g900t/g900f)?
Please help. I do have some know how on flashing android devices but i've really hit the wall on this one guys!
Cheers,
Yetti.:cyclops:
It's not uncommon for the model # to be different with a custom rom as that is a very easy thing to edit in the build.prop. It should tell you under the battery which one it is. As far as the network issues, check to see if the baseband and IMEI are still there and not listed as unknown or incorrectly. It's possible you could get away with flashing the appropriate modem that matches with your update and that might work better in this region vs the previous one.
Please list the Alliance rom version and baseband version here in case it's relevant to your issue.
More info
Im not sure if this helps but looking through the build.prop file in the system folder my ro.product.local.region=GB
When in recovery mode the region is set to XTC (Philippians) using mutli-csc.
Also my IMEI number seems ok and is NOT blocked.
Cheers. Yetti :cyclops:
Baseband and rom etc
Thankls for your reply!
Sorry when you say "under the battery symbol" do you mean in /odins boot script on the device/ or /in settings on the phone/?
Baseband is g900TUVU1ANCH
Build Num: AllianceROM_G900F_XXU1ANCF
If the "no network" issue can be solved with the current firmware that would be the most desirable solution but going through the flashing process may be a good idea for my learning process, and will help with future updates.
Do you think getting back to a stock rom would help me?
tHANKS AGAIN!:cyclops:
Model confirmed to be g900t
Sorry i didn't understand the "under the battery" thing. I was lost in software world. The sticker under the physical battery says SM-900T so i guess that confirms that it is a t-moble verison (and the baseband is therefore correct).
I will try to flash the T-Mobile stock image to the phone and see if that works.
Also i will try to flash a modem (after i work out which one i need).
Cheers, Yetti :cyclops:
Current status.
Flashed the stock T-Mobile firmware to the phone. No success.
Flashed new modem to the phone. No success.
Will go to the T-Mobile store tomorrow to see if they can help (I doubt it but i have to exhaust all the options).
Any more help would be appreciated...
cheers, yetti:cyclops:
By under the battery I mean like to take off the battery cover of the phone and pull the battery out and look at the sticker found there.
G900t.
es0tericcha0s said:
By under the battery I mean like to take off the battery cover of the phone and pull the battery out and look at the sticker found there.
Click to expand...
Click to collapse
Yep it says g900t (see above)
As per flashing a modem. I have heard that it is possible to flash any modem for any version of the s5 to the phone. Some work well and others not so much. I have tried 2 T-Mobile modems (baseband) the G900TU1ANCH and the G900TUVU1BNG3 with no success. Do you have any recommendations for a modem to try (or even a custom ROM that might help?)
Cheers,
Yetti :cyclops:
I know that you mentioned they refreshed the service for your number, but do they have the correct IMEI in the system for your account? Metro makes a big deal about that now and you can't just take your SIM from another phone and pop it in a new one and go like you can with pretty much every other service (Cricket is like this too now).

unable to access the csc settings for unlocked s10 sm-g973u(1)

i have an unlocked s10 sm-973u1
i had stumbled onto the CSC setting which i needed and stupid me decided to switch it to XAA and the CSC setting disappeared. im not sure which firmware i was using. but ive tried different ones since and no luck.
i currently have G973USQU2ASF6 installed
service provider SW ver: SAOMC_SM-G973U_OYN_XAA_PP_0014, XAA/XAA/XAA
im feel lost. maybe im missing step. i thought i had bricked my phone a few times yesterday.
ive tried many routes and find myself just getting road blocks.
can anybody direct me into the right direction?
thank you
robert

Getting Tmobile Updates on phone with SW ver Tmb/Tmb/Att and Att baseband version

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.

Sm-g925f model wont accept any other stock firmware except sc-04g

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:

Categories

Resources