Related
Hi!
I flashed my phone a month ago and have ever since then desperately trying to find help. No luck so far.
I installed 2.3.4 because it wasnt realesed here in sweden. but then the phone became russian and i couldnt use 3g anymore. i went to samfirmware.com and tryed out like every firmware but nothing worked, i tried updating via kies but most of the time it would say that my phone does not support updating via kies, but once it worked and it update back to the russian 2.3.4 firmware, i dont know what to do! please help me.
Are you using a small regional type cell carrier? A friend of mine had a issue much like this before where they rooted their phone and installed CM7 which changed the radio(baseband) and they lost MMS and some other features because the small carrier was not supported. The only way we could get it back was by taking a nandroid backup of same model device from the same carrier that hadn't been touched other than root and restore that onto their phone and that resolved the issue. Not sure if this helps you or not.
adammwhiles said:
Are you using a small regional type cell carrier? A friend of mine had a issue much like this before where they rooted their phone and installed CM7 which changed the radio(baseband) and they lost MMS and some other features because the small carrier was not supported. The only way we could get it back was by taking a nandroid backup of same model device from the same carrier that hadn't been touched other than root and restore that onto their phone and that resolved the issue. Not sure if this helps you or not.
Click to expand...
Click to collapse
Well it helped a luttle, but what do you mean with small carrier and such? i am not very good at english so i dont understand alot. is there a copy of a untouched ace???
What I mean by small carrier is that in the US we have Verizon, AT&T, T-Mobile etc. but we also have small carriers like Bluegrass where I live at. With these small carriers if your radio gets updated from a ROM install then it is very hard to find a replacement radio to flash back onto the phone. If this is the case in your scenario then you will need to find someone on the same carrier with the same model phone that has not installed a customer ROM but has rooted their device to make a nandroid backup then restore that to your phone.
adammwhiles said:
What I mean by small carrier is that in the US we have Verizon, AT&T, T-Mobile etc. but we also have small carriers like Bluegrass where I live at. With these small carriers if your radio gets updated from a ROM install then it is very hard to find a replacement radio to flash back onto the phone. If this is the case in your scenario then you will need to find someone on the same carrier with the same model phone that has not installed a customer ROM but has rooted their device to make a nandroid backup then restore that to your phone.
Click to expand...
Click to collapse
well..... **** -.-
Thanks dough!
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Yeah, just don't flash any odin files.
aooga said:
Yeah, just don't flash any odin files.
Click to expand...
Click to collapse
can you clarify please?
seattleboi1982 said:
can you clarify please?
Click to expand...
Click to collapse
Not sure what you mean. You can flash any rom from any variant of the S5 (obviously not the exynos variant, but there's hardly anything for it anyway). When I say rom, I mean a zip that's flashable in cwm or twrp. NOT the files that you flash in ODIN (tar, md5). DON'T flash those files from any other phone except the G900T.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
fffft said:
Well yes, but the way it works may not be quite the way you picture it. If you flash your phone to TMobile it isn't a 100% change over to TMobile as you probably assume it would be. Picture your phone as having two parts.. a baseband + ROM. The baseband is basically just the bootloader and modem. It's very hard to change the baseband and it's hardly ever done. So your baseband will more than likely remain ATT forever no matter what you do.
But that isn't likely to be a problem either. The baseband is compatible between ATT and TMobile and pretty much any other GSM system too. Otherwise you wouldn't be able to roam on other systems. You can change the ROM part to TMobile and your phone will act, smell and behave like a TMobile phone in pretty much every way that is likely to matter to you. The only obvious snag is that automatic OTA updates may or may not work, if that matters to you.
The customary way to change your phone to TMobile would be to root it, install a custom recovery e.g. TWRP. Then flash a TMobile ROM (or custom ROM if you want to) from TWRP. Note that installing a custom recovery like TWRP will change your Knox warranty bit. That might have warranty implications if your phone is still under warranty. Some carriers don't care about Knox - you can check the ATT forum to see how ATT handles warranty claims.
Alternately, if Knox matters to you, you may be able to flash a full stock TMobile image to your phone with the Odin program. This works for some carriers and not others. I don't know how ATT's locked bootloader would react to that. It's just a possibility that you could investigate if Knox and warranty are an issue to you. It would probably mean using a newer root method that doesn't trip Knox, then flashing a full TMobile firmware image, along with the correct TMobile PIT file. Hopefully Odin would just ignore the baseband and just write the ROM, while preserving the Knox bit. But you'd have to confirm that the ATT bootloader won't go bananas over the attempt i.e. search the forum to find out what happened when other people tried it.
.
Click to expand...
Click to collapse
actually its T-mobile S5 flash to to make it like ATT S5. Samsung is a differant beast for me as i am usually a HTC or Moto user.
seattleboi1982 said:
actually its T-mobile S5 flash to to make it like ATT S5.
Click to expand...
Click to collapse
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
fffft said:
Your original post stated the opposite. Unintentionally I'm sure, but it goes to show that clarity counts.
It's much easier to go in that direction because the 900T uses an unlocked bootloader and TMB is generally less restrictive.
So yes, you can install an ATT (or other custom ROM) onto a 900T.
Keep in mind that it is not necessary to do so. The 900T will work fine on ATT with it's original firmware. But you can change the ROM to ATT if you want to for some reason. The proper way to do so is to find an ATT PIT file, then flash a full stock ATT firmware + PIT to your 900T. Most people don't bother with the PIT file and occasionally that leads to bootloops and soft bricking.
Anyway, go ahead and flash it if you want. Odin won't change the baseband, but everything else (ROM) will transition to ATT. FWIW, I think that a custom (debloated) ROM e.g. Phoenix ROM (which is not branded for ATT or TMB) is a nicer experience and better performance than using the ATT ROM. But up to you of course.
There is a XDA thread on S5 PIT files that has the 16 GB version of the ATT PIT if you need it.
.
Click to expand...
Click to collapse
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
aooga said:
Odin will change the baseband. There's no need at all do do anything with ODIN. All it does is cause more problems if he does something wrong. I would just use TWRP and flash a stock ATT rom.
Click to expand...
Click to collapse
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
OP: Why do you need an ATT rom anyway? If you tell us what part you actually need, it might be easier than flashing an entire rom, either with odin or twrp.
fffft said:
Installing a custom recovery like TWRP will trip Knox. That probably isn't an issue as TMobile doesn't care about Knox and virtually everyone says that it does not affect how TMobile handles warranty claims. But the OP should still know about Knox in advance in case it is an issue for him somehow.
I agree that a flashable zip is easier than Odin if the ROM that he wants exists in that form. Specifically, I don't know if anyone has repackaged an ATT ROM into a zip format. If someone has, then i agree with your approach. If not, he would have to use Odin.
IMO, the OP would do best to install something like the unbranded Phoenix ROM via TWRP.
Odin will not usually a foreign baseband to be flashed. Not that he necessarily has to try. You can use Odin to flash AP, CP, and CSC, but not the BL. Only when the constituent components are unavailable do you need to use the full OEM Odin image.
.
Click to expand...
Click to collapse
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Lostatsea23 said:
How would someone deal with tmobile warranty without a tmobile account?
Is that possible at all?
Like via prepaid or something? Just wondering..
I would trip knox if I knew I had something to fall back on.
Click to expand...
Click to collapse
No, you need to be a tmobile customer with a postpaid account.
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Well. Theres my options lol
aooga said:
No, you need to be a tmobile customer with a postpaid account.
Click to expand...
Click to collapse
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
fffft said:
Do you have a source or even solid rationale for that? I don't disagree that TMB, like pretty much any carrier treats current, postpaid customers better. But I have not seen any written policy or even credible assertions that TMB disavows their warranty for prepaid or ex-customers. AFAIK, if you bought the phone from TMB, postpaid or prepaid, you have a warranty through TMB. The obvious impediments being a stolen phone or account in serious arrears.
Discretionary powers exist, so it's sometimes difficult to distinguish between common practice or what they can be persuaded to do versus actual policy. Policy is a definite advantage in negotiations, so if there is anything written that says prepaid or ex-customers must deal with Samsung directly, I'd like to see that.
Everything in my direct experience is to the contrary. TMB honours warranty and doesn't care about Knox. They do have less respect for prepaid customers. But the few prepaid TMB customers that I know still had TMB handle their warranty claims.
.
Click to expand...
Click to collapse
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account. They ask for the phone number and last 4 of your ssn. Maybe you can convince them to make an exception, but when I tried with ATT, they told me since you're not a ATT customer, we can't help you.
aooga said:
Source would be experience. When you call, you cannot speak to a warranty rep unless you have a tmobile account.
Click to expand...
Click to collapse
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
fffft said:
All right. Your experience is completely contrary to mine. With no evidence of that being policy, I can only assume that you've encountered less helpful CSRs. Anyone finding themselves in a similar position may well prevail if they try talking to different CSRs.
.
Click to expand...
Click to collapse
Have you actually done an exchange with a carrier that you don't have service with? Just think about it...they don't have any of your info. CC, ssn, email, even your full name. If for some reason the customer doesn't ship the defective phone back, they can't charge you. If tmobile has a way of doing this for non-customers, I'll gladly shut up
aooga said:
...
Click to expand...
Click to collapse
I already expressed my opinion on this. If you disagree, so be it. And it's tangential and off topic in this thread.
Getting back on topic, the OP asked if he can flash an ATT "ROM" onto his TMB 900T phone.
Yes he can. We agreed that the easiest way to do so is to use TWRP, provided that he does not mind Knox being tripped. And of course, assuming that someone has repackaged an ATT ROM into a flashable zip format.
The alternative is a traditional Odin flash. He can flash ATT firmware onto his TMB 900T phone. It should be done in conjunction with the appropriate ATT PIT file. But those who are impatient or don't know about PIT files, usually don't run into problems eschewing the PIT. I won't advise that approach though.
Two last considerations. There isn't necessarily a good reason to do any of this in the first place. A TMobile S5 can roam on or use an ATT SIM directly. And without missing out on anything that the average user would notice. But it is possible to so for sundry reasons. As one way of changing the CSC and opt into an automatic OTA update scenario. To gain carrier specific ATT apps and so forth.
There is a lot of confusion regarding the mechanics of transitioning a phone from TMB to ATT for these sundry goals. A phone has a ROM, which is the apps and most of the system files. That can certainly be changed.
And then there is the low level baseband. The baseband can be updated with something newer from the same carrier that the phone originated from. But it is difficult and hard to find a good reason to change the baseband to a different carrier. To be more specific the baseband represents the bootloader and modem. A modem from one carrier works just fine on another carrier 99% of the time. So pragmatically, the best approach is to simply update the modem to a newer version from the original carrier, regardless of what carrier you actually use the phone on. There is rarely something carrier specific in a modem module.
If you enjoy fighting with Odin, you can flash some modems from foreign carriers. It will also sometimes brick your phone. And Odin often refuses to proceed with the flash for various reasons. So again, not recommended. Nor necessary in most cases.
The bootloader is exponentially harder to change to another carrier. Not to mention almost pointless except for cosmetic reasons and involves having Odin jump through a lot of hoops. Difficult enough to do that it isn't inaccurate to say it can't be done. It can't be done by most people. And it would be rare to hear a reason with merit for doing so.
.
.
seattleboi1982 said:
OK, i have searched around and have not found anything to my question. Is it possible to flash the ATT version ROM to the T-mobile version?
Click to expand...
Click to collapse
Why would you want to run an att rom, no wifi calling? lol, anyways, what rom are you trying to run?
i would like to run as close as possible to an AT&T ROM as im an ATT subsciber with a T-mobile phone. especially now with VoLTE.
Hi:
Newbie here, so please bear with me. I am fairly techie, but never really worked on phones (I'm a Windows / Network engineer by trade).
I had an S6 Edge on the Vodafone network, and live in an area with poor cell coverage. So, I fully took advantage of wifi calling. I've upgraded to the S8 (gorgeous phone, BTW) so I gave the device to my missus, who made the mistake of buying an EE iPhone, and hates it.
We unlocked the phone to the EE network, but the wifi calling option has vanished, and I've been told that this is by design, as only phone purchased directly from EE have wifi calling enabled.
Been looking around, and have seen that if we root the phone and flash it with an EE image, then things should be hunky dory. However, having never undertaken a project like this on a phone, I'm seeking some guidance, as I don't want to completely brick the device.
Are there any idiot-proof step-by-step guides on here to do this?
Cheers in Advance
Steevi93 said:
Hi:
Newbie here, so please bear with me. I am fairly techie, but never really worked on phones (I'm a Windows / Network engineer by trade).
I had an S6 Edge on the Vodafone network, and live in an area with poor cell coverage. So, I fully took advantage of wifi calling. I've upgraded to the S8 (gorgeous phone, BTW) so I gave the device to my missus, who made the mistake of buying an EE iPhone, and hates it.
We unlocked the phone to the EE network, but the wifi calling option has vanished, and I've been told that this is by design, as only phone purchased directly from EE have wifi calling enabled.
Been looking around, and have seen that if we root the phone and flash it with an EE image, then things should be hunky dory. However, having never undertaken a project like this on a phone, I'm seeking some guidance, as I don't want to completely brick the device.
Are there any idiot-proof step-by-step guides on here to do this?
Cheers in Advance
Click to expand...
Click to collapse
It's actually a lot simpler than you think. No need to root all you have to do is flash the EE firmware through Odin (Samsung flashing tool) and voila, EE Wi-Fi calling will appear. Also volte will be available too.
If you need step by step I can help.
I need model number and android version and I can link you the firmware.
callumbr1 said:
It's actually a lot simpler than you think. No need to root all you have to do is flash the EE firmware through Odin (Samsung flashing tool) and voila, EE Wi-Fi calling will appear. Also volte will be available too.
If you need step by step I can help.
I need model number and android version and I can link you the firmware.
Click to expand...
Click to collapse
Hey dude.... after trolling through this forum some more, I was able to find what I needed to flash the firmware onto the device... However, Wi-Fi calling (as an option) does not seem to appear yet, but I wonder if that is due to the lack of SIM card (wife put it back in her iPhone, so I could sort this at work.
If I've downloaded the wrong stuff, then I'm happy to redo.
Model Number: SM-G925F
Android Version: 7.0
Baseband Version: G925FXXU5EQF1
Steevi93 said:
Hey dude.... after trolling through this forum some more, I was able to find what I needed to flash the firmware onto the device... However, Wi-Fi calling (as an option) does not seem to appear yet, but I wonder if that is due to the lack of SIM card (wife put it back in her iPhone, so I could sort this at work.
If I've downloaded the wrong stuff, then I'm happy to redo.
Model Number: SM-G925F
Android Version: 7.0
Baseband Version: G925FXXU5EQF1
Click to expand...
Click to collapse
When you downloaded the firmware was there 5 files in the zip? Or just the one AP file?
Did you look in phone app > settings then scroll to bottom for Wi-Fi calling option? If you flashed an EE firmware it should be there mate.
As well as the EE firmware you need to have the EE csc. You have this csc, EVR?
callumbr1 said:
When you downloaded the firmware was there 5 files in the zip? Or just the one AP file?
Did you look in phone app > settings then scroll to bottom for Wi-Fi calling option? If you flashed an EE firmware it should be there mate.
As well as the EE firmware you need to have the EE csc. You have this csc, EVR?
Click to expand...
Click to collapse
Hi... There was only the one file (the AP file, I believe)_ and no, when I checked the phone settings, wifi calling was not showing as an option. If you have a link to the correct firmware, I'm happy to reflash the phone, as I have everything here with me at work.
Steevi93 said:
Hi... There was only the one file (the AP file, I believe)_ and no, when I checked the phone settings, wifi calling was not showing as an option. If you have a link to the correct firmware, I'm happy to reflash the phone, as I have everything here with me at work.
Click to expand...
Click to collapse
Flash this version from here
http://updato.com/firmware-archive-select-model?record=75717719616711E7963AFA163EE8F90B
The version you flashed previous was PRT Poland version.
Flash the one I posted it is UK EVR and then you will have Wi-Fi calling.
callumbr1 said:
Flash this version from here
http://updato.com/firmware-archive-select-model?record=75717719616711E7963AFA163EE8F90B
The version you flashed previous was PRT Poland version.
Flash the one I posted it is UK EVR and then you will have Wi-Fi calling.
Click to expand...
Click to collapse
Thanks.... I will give that a go when I get home. Cheers.
Steevi93 said:
Thanks.... I will give that a go when I get home. Cheers.
Click to expand...
Click to collapse
No problem
Steevi93 said:
Thanks.... I will give that a go when I get home. Cheers.
Click to expand...
Click to collapse
If by chance you encounter hidden.img fail in Odin don't panic.
Just unpack the firmware and remove the hidden.img. repack and flash again.
callumbr1 said:
If by chance you encounter hidden.img fail in Odin don't panic.
Just unpack the firmware and remove the hidden.img. repack and flash again.
Click to expand...
Click to collapse
Heya.... no such "issues" so to speak. Just one where my baby kicked the USB cable, causing a brief disconnect during the flashing process. This, of course, sent me into a spiral of panic because the entire phone crashed, with errors, recovery messages invoking Smart Switch, and the like. However, restarting the phone and connecting it to Odin completely recovered the phone.
Initially, the flashing worked, but it didn't enabled Wi-Fi calling, so I reset the phone back to factory settings, flashed it again and voila!!!! Worked like a charm! Then restored the backup from Smart Switch that I made yesterday, and the missus now has a full functional EE phone with Wi-Fi calling.
Thanks very much for your help mate.... you're a legend.
I'm gonna keep Odin, as it seems like a great recovery tool as well. :good:
Steevi93 said:
Heya.... no such "issues" so to speak. Just one where my baby kicked the USB cable, causing a brief disconnect during the flashing process. This, of course, sent me into a spiral of panic because the entire phone crashed, with errors, recovery messages invoking Smart Switch, and the like. However, restarting the phone and connecting it to Odin completely recovered the phone.
Initially, the flashing worked, but it didn't enabled Wi-Fi calling, so I reset the phone back to factory settings, flashed it again and voila!!!! Worked like a charm! Then restored the backup from Smart Switch that I made yesterday, and the missus now has a full functional EE phone with Wi-Fi calling.
Thanks very much for your help mate.... you're a legend.
I'm gonna keep Odin, as it seems like a great recovery tool as well. :good:
Click to expand...
Click to collapse
Hey buddy,
Brilliant news mate enjoy. Glad I could help you.
Yeah keep Odin as it's always very useful in times of need. However you shouldn't have any issues from now :good:
Thanks the posts if you can mate :good:
Hi XDA haven't been on here for a while.
So I have a question I was given a S9+ from Sprint it's unlocked I'm currently using it on TMO but I don't have wifi calling nor video calling. I wanted to see if it was possible to flash a TMO firmware. Since it's still on July's patch here's a screen shoot of current firmware.
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
If you figure it out, let us know. I'd be interested in giving it a go.
berzerkus said:
I moved from Sprint to Tmo, and just put in the sim and then updated the firmware through the system update interface. All works as expected.
The difference may (or may not) be, if the phone was unlocked by Sprint or by another method. My wife's phone was unlocked via "another method" and cannot get it to update system software. I haven't bothered looking into it further though, as we don't expect to keep the S9+ too much longer.
Click to expand...
Click to collapse
Colombia81er said:
Yes mine was unlocked different method so it won't update normally.
That's why I asked if I could cross flash to TMO
Click to expand...
Click to collapse
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
if your phone is unlocked via whatever method, it wont interfere with system updates. OTAs will happen at regular intervals based on the firmware flashed on the phone and the recovery status. Stock recovery means that youll get OTAs, if youre not, its likely a glitch and has nothing to do with the unlock status.
If youre looking to get your phone working on tmob and its a spr phone, all you really need to do is unlock it, put the new sim in it and configure the APN. If you want full features like voLTE and wifi calling, then youll need to flash a tmob firmware version on your phone which requires the patched version of Odin. I have a Cricket branded (originally, at least) S9 and i flashed the U1 firmware on it via patched Odin and the phone now thinks its a factory unlocked S9, as i also unlocked it via "alternative methods". Perfectly seamless transition and i get OTAs all the time
berzerkus said:
If you figure it out, let us know. I'd be interested in giving it a go.
Click to expand...
Click to collapse
Sorry to revive the post, so i finally did the update it worked flawless i did the update to the latest firmware G965USQS7DTB1_G965UOYN7DTB1_TMB now i got Wifi Calling and VoLTE.
I used Odin3-v3.13.1-Patched
Unrar the firmware and then just load the files in Odin
Heres a great tut https://www.youtube.com/watch?v=bnPkwICq_Bw&t=
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
its a verizon tablet so thats normal.. u need to change csc is all
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
jmwfl2000 said:
Thought that was part of flashing it with the patched version of Odin with a different CSC version of the firmware, but I've not done this before. Any suggestions or resources you can point to on how to do this? Thanks!
Click to expand...
Click to collapse
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Gotcha, so change the CSC first, then flash the matching firmware? What's the best method for changing the CSC on the S7+? This process? https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
Any suggestions on how to change the CSC? I've hit a wall and haven't been able to find a way to change it and then flash the desired firmware.
elliwigy said:
patched odin only removes hash checks.. all the firmware has multi csc (all the usa csc) so simply flashing firmware doesnt change csc
Click to expand...
Click to collapse
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
bs3pro said:
You need to flash with odin, wipe, then pop the other carrier sim in, on reboot it will boot with that carrier sw.
Click to expand...
Click to collapse
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
jmwfl2000 said:
Ok, so SIM out, Odin flash with the TMB firmware. Then, what do you mean "wipe?" Is that just choosing the CSC file in Odin so that it resets all data, or some step after to wipe it?
Click to expand...
Click to collapse
jmwfl2000 said:
So I tried again with these steps and had the same result, back into the Verizon firmware.
Removed Tmobile Sim
Odin flash TMB firmware
Tablet reboots automatically into VZW firmware
Then booted into recovery mode and performed a factory reset and cache wipe
Reinserted Sim and reboot
Tablet still boots into VZW firmware
I also tried this same process but with the unlocked "USC" firmware with the same results.
Am I supposed to somehow prevent the first boot after odin flash to perform the factory reset? I've tried that unsuccessfully but maybe I have the timing off or something.
Click to expand...
Click to collapse
dunno wat ur flashing but all the firmware is the same.. theyre all multi csc.. so simply flashing different firmwares wont change csc lol
I don't know if this will help but on some samsung phones you can change the csc by opening the dailer and typing "*#272*IMEI number#"
edit: IMEI must me copied from the about tablet section in the settings. Press on the IMEI for a second and it will be copied to clipboard. Typing the IMEI will not likely not work.
After entering this in the dailer a menu pops up and you can select csc. Note this will usually factory reset the device.
Yes if you try this, please let me know if it works. I have the T878u 5g from Tmobile.
Any update on this? I purchased an SM-T978U (on Samsung website that is t-mobile S7+)
I expected it to not be carrier or network locked but it was locked to the t-mobile network.
Would love to flash an unlocked firmware but I can't find SM-T978U firmware, let alone U1 firmware...... I realize that flashing U1 firmware won't unlock the network but T-mobile support tells me the device can't possibly be truly carrier locked because the IMEI isn't even in their system. So I thought maybe the carrier lock is in their app tied to the system instead of the actual device??
Anyway has anyone found the firmware for these devices? Sammobile doesn't seem to list SM-T978 as a device
These devices don't have a dialer so entering the IMEI method mentioned above won't work unless there is a trick?
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
not sure y u tagged me lol.. i know hiw csc works.. in fact, in my last comment before this one you can see I clearly said just flashing firmware won't change the csc? seems like basically what you said but in a few words
K3N422 said:
Guys, for cross flashing, you must factory reset from within the OS before you flash. the newer security measures will not allow the device to accept even a full flash if the device is activation locked to an account. that is likely why you are flashing and still getting the vzw stuff to come up.
@elliwigy , though the devices are all loaded with multiple csc's, and you can change them on demand (if you know how), that will not automatically load the carrier branded bloatware that comes with each firmware, and certain settings that may, or may not, be enabled or disabled by the carrier. An example being native video calling that the verizon firmware has and the unlocked firmware does not.
I almost always flash my Verizon devices with the U1 XAA unlocked software. Among other things, this lets me get security patches faster, as i get them when sammy releases them, not when vzw gets around to it. I say almost always because there are still a few devices, like my tab s6, that are vzw models with some minor hardware changes that prevent it. But in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
Where is this U1 XAA firmware to download? Specifically for the SM-T978U?
RE: jmwfl2000 -I always untick the "Auto-Reboot" box when flashing new TWRP images to prevent stock recovery from being reapplied.After the first boot all should be well.
K3N422 said:
in the case of my Tab S7+ and my Note20Ultra, they are both rocking U1 XAA firmware.
Click to expand...
Click to collapse
I'm pretty stumped like OP. Where are you finding U1 XAA for Tab S7+? Doesn't seem to turn up anywhere. Would definitely appreciate it if you could provide a link. Thanks.
I tried resetting before flashing and unchecked the auto-reboot but mine still returns to Tmobile. I just want the call and text on other devices feature.
Edit: I go the feature to work without flashing a new firmware but I am still looking for U1 XAA for the tab if anyone found it.
jmwfl2000 said:
Purchased a sim unlocked SM-T978U (Verizon Tab S7+ 5G) and am trying to flash the unlocked or Tmobile stock firmware to it. I've gotten "passed" flashes everything when flashing all of the files from the corresponding stock firmwares, but everything it boots back into the Verizon firmware. Any suggestions as to what I'm doing wrong that would cause this? I've probably flashed this thing 20 times at this point.
Click to expand...
Click to collapse
I bought an unlocked Verizon Tab S7, probably same seller. Its brand new, stil has plastic on it. Are you wanting to unlock Tmobile 5G bands?