Att oreo on my tmobile s7

[SIGMAxB]

https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread

Can I flash this with flasfire if so how

 

[PGHammer]

https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread

Can I flash this with flasfire if so how

Won't flash on T-Mobile - it expects AT&T firmware (SM-G930A) - not anything else. I tried it (SM-G930T) and got error 7 in second stage with that exact reference (expected SM-G930A; got SM-G930T). This would have to be edited to take that second-stage reference out to work.)

 

[SIGMAxB]

You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release

 

[PGHammer]

Death Cookie Firmware in Non-DeathStar Phones - Yes; However

You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release

Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.

 

[SIGMAxB]

Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.

Which version of att firmware did you flash ? Is it worth flashing the Oreo update

 

[PGHammer]

Which version of att firmware did you flash ? Is it worth flashing the Oreo update

The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.

I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)

 

[PGHammer]

Beginning of Round Two - CRB6

The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.

I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)

I reset the phone, and kicked off testing of CRB6, and I did one thing differently; I left the SIM in the phone. I had a purpose for that - I was looking for bugbears that apply to non-AT&T carriers (T-Mobile, VZW, Sprint, et. al.) Amusingly, there aren't any. I did the flush (U Firmware version of BRA1) then applied the AT&T version of BQL1 (back-to-back via ODIN). Then came the ADB via SD card single-file updates (recovery mode for these) and there are only two - BQL1 to BRA1 (from Round One) and the new CRB6 update (courtesy of Samsung Firmware Science) labeled update_2.zip. It replaces update.zip, and is not opened or extracted - apply it as-is. After this update applies, follow the new-customer steps as you did for Round One - no changes here.

 

[bkup]

If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly

 

[SIGMAxB]

If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly

Can I get a copy please

 

[PGHammer]

Why I Did It The Way I Did

Can I get a copy please

When someone gets a proper copy, link it to the thread - the very reason I did NOT do it that way was because a proper copy of AT&T BRA1 didn't exist. (You can't get it from SamMobile or UPDATO either - much to my frustration; the latest ODINable AT&T firmware was BQL1.)