Search results

That's good to be aware of, but not really a deal breaker, or wouldn't be for me. I leveraged the tendency of the factory screen protector to scratch to purchase a cheap phone off e-bay. I'd find the one with the worst looking screen with okay looking everything else then when I got the phone...

This phone was exclusive to a GSM carrier in the USA, so it seems unlikely that you are going to find help. I imagine that the modem has the capability to communicate via CDMA with the correct firmware since it shares most hardware with any other Qualcomm S7 (this is way outside of my knowledge...

Sorry about that. Now I finallyI see it in the active key settings under Settings > Advanced Features > Active Key. I thought it was a toggle, but it's just described there and is apparently always supposed to work. Unfortunately, I can confirm that it doesn't seem to work on the 3CRG2 build.

I don't think you could ever use the active key to take photos. You can launch apps with it, but a cursory google search doesn't reveal anything. Even the official Samsung page which seems to point at a Nougat OS doesn't indicate you can. I can't tell if the battery is better. I was already...

I have CRG2 running. Still April 1 security update. I don't see any changes so far... But, it also seems to run fine...?

If it helps, I could post the hashes for the files I download directly from ATT and then a second user could post what they see from mail.ru and we can confirm that they agree so that at least the files are legit. khaliullov is trustworthy AFAIAC.

SS-G891AUCU3CRE7-to-U3CRG1-UP and SS-G891AUCU3CRE7-to-U3CRG2-UP are up on ATT servers. Haven't installed either for fear of a beta trap, but they exist. khaliullov will probably put them up on the mail.ru site soon. Read the forum to find that site or to check how to download these from ATT...

The full ROMs that are available are factory meaning that they will have all the bloat. There isn't much in the way of ROM development for these phones because of their locked-down nature. However, you can carefully go through the app list and disable a whole heck of a lot and thereby hide much...

I've been using CRE7 for a while now and don't see too many drawbacks, if any. There are lots of minor changes for the good, battery life is about the same or maybe slightly better. The only major issue I have been having is with roaming from Canada to the US. My phone hasn't been able to...

Update -- I just re-ran the CTS Profile and SafetyNet checks on my phone with U3CRE7 and it now passes. A week ago it didn't. Innnnnnteresting.

It seems that with the betas, Google's SafetyNet API doesn't classify the phone as unmodified in terms of something called the CTS Profile. So, Google Pay doesn't work. But, in terms of your question, Knox doesn't seem to care about those things so all things Knox related work on the betas that...

For future reference, when you see the "No Command" screen with a little dead android character, if you hold power while clicking vol up then release recovery should start up. If you are in recovery and don't select "reboot system" then the phone will continually reboot to recovery first...

I'm flashing it now and will be headed to the US this weekend so will be able to see if the roaming issues are still present. The paranoid part of my brain that doesn't know how these things actually work is worried that my IMEI has been blacklisted off ATT for having unauthorized betas on my...

U3CRE7 is up on ATT servers. I'm sure khaliullov will have it on his cloud site soon.

No problem. Glad you got where you want to be. NB: don't hold out for many more nougat versions. Maybe one more official OTA security update but I'd be really surprised if the next update wasn't official Oreo.

You are on the right track. Download the ODIN that works for the S7 Active from the mail.ru site where you got the firmware. Yes, you have the correct firmware despite the long name. It seems to work fine for people. Use google to find videos on how to use ODIN to apply a new firmware. It's not...

At the very least, make your title less alarming and less general. Give your thread a title that describes what you see the problem as so people like me who don't care about the topic aren't lead to read your thread because it wasn't clearly titled. Second, by your logic, everyone with a gripe...

Can a moderator delete this thread? I don't see how pining over a phone that's three generations old is useful and even relevant to the S7 active. What are we supposed to do, ditch our phones and go buy an older phone that is no longer supported and likely to have worn out batteries and the...

Thanks for the great feedback and review. I'm in Canada so hadn't tried google pay as I don't think its available here yet? But I did just try setting it up (running CRE5) and can confirm the error you get regarding a rooted or modified phone. Can you confirm that Google pay works with CRE2...

Look through recent posts pointing at a full firmware from the cloud site maintained on mail.ru. If you have U3CRE2 installed, it's very important that you download ONLY a firmware with the version 3 bootloader unless you want brickage. Download that full firmware for S3BRD1. Also on that site...

As always, if you don't want to (or can't) mess around with ODIN, then wait until ATT releases the official update. Thanks to khaliullov I was able to revert from CRE2 back to BRD1 then up to CRE5. I've installed this as of yesterday and am not seeing any issues yet. I can't comment on the...

S3BRD1-to-U3CRE5 is up on ATT servers. Nothing above version 5 as yet.

Just a heads up that on U3CRE2 I'm having much difficulty with international roaming from Canada to the US. Something is up and I reckon it has to do with the delay in releasing Oreo to the S7s. So, just a warning to hold off on updating to that version if you had it in mind to. One more month....

This is all you need to know. If the full firmware that khaliullov posted was tampered with and if the user had somehow managed to get their phone to accept it (impossible) then the OTA update to CRE2 would have failed the signature check. Apparently it didn't and if you go through this process...

The update files are but ATT doesn't post full ODIN flashable firmwares on their site AFAIK.

Yeah, this looks like an incomplete upload mistakenly placed in the firmwares section. There's a complete version of that update under the OTA section.

update from S3BRD1-to-U3CRE2 is up on ATT servers. That makes two updates to U3CRE2 so that "might" be the official Oreo for the phone. I'm not seeing any major issues with CRE2 having used it for a few days now. But, to be sure you don't get stuck on a dead branch, you should wait until...

Ha ha. Darn. Luckily, the CRE2 Oreo seems pretty solid. Has nice new goodies and the only bug I've found so far is that I can't make the icon frames go away on the stock launcher. But, there are a lot of features I never use, so can't say this has been any kind of thorough test. Here's hoping...

Ah, I'm an idiot. I had assumed that going from bootloader 2 to 3 would be an update rather than a security patch, so I was looking for S2BRD1 and U3BRD1 but not S3BRD1. I see that build now. 41MB and must contain the April security updates. I saw your message right after installing U3CRE2, so...

I'm missing something. There's CRD1 which is Oreo and BRC1 which is Nougat. The full update filenames are U2BRB5-to-U3CRD1 and U2BRB5-to-S2BRC1. I haven't seen a BRD1 either on ATT's server nor on the mail.ru cloud site.

Can you give the full build number please? It's BRD1 not BRC1? I'm asking because I'm not able to download that from ATT

TL;DR: 1) you aren't missing out on anything by not being able to access the att server and poke around. Everything there gets mirrored out on the mail.ru site. 2) You can educate yourself to check for these things on your own and it wouldn't hurt you to spend the time to gain that skill set...

S2BRC1-to-U3CRE2 is up on ATT servers

I learned by reading through this thread and links from here to one that used to be on 4pda.ru which seems to be gone? Also, having a basic knowledge of linux has helped. You can certainly modify the user agent in your browser and do the same brute-force thing that I do at the command line with...

Works for me from another IP. I think the IP I was using has been filtered.

Haha. Thanks! The Python user agent had failed a while ago and I switched to a null UA. Anyhow, carry on. On attempting that, it doesn't work. Maybe my IP has been blocked? Anyhow, carry on.

Unfortunately, ATT has modified their server settings breaking the current means of accessing the updates. I don't have time or the means to reverse engineer this, so I won't be able to update this thread any longer. If anyone out there wants to work on this, now would be the time. All the best.

The change from V1 to V2 happened with the November, 2016 update which DID NOT change the android version. The Android version stayed at 6.0.1. You can look this up yourself here: https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1136420?make=Samsung&model=SamsungG891A...

There is no full ROM with bootloader 3 available right now. You've requested it numerous times and the answer is the same, there's nothing that can be done. Please watch the thread silently. When a new ROM with bootloader 3 arrives someone will post where to get it and then you can proceed...

Thanks for testing and reporting back to us. Bummer that it's not stable so likely not the official update.

Which build/baseband are you using? So far, none of the Oreo build are official so it sounds like you've run into a bug in a beta build. It would help us to know which build that is so others may avoid it.

I have the same battery issues in BRC1 or perceived issues. I tested yesterday and got 26 hours out of the battery in a pretty normal day with a few hours of SOT and bluetooth audio streaming and hotspotting. The battery drains really fast in use, but the phone seems to doze well when left...

ATT servers. See earlier posts in this thread about using command line tools to download. Eventually it will get loaded up onto the mail.ru cloud site made available by XDA user khaliullov who figured out how to download these updates from ATT.

SS-G891AUCS2BRC1-to-U3CRD6-UP is up...

I think it means you can't downgrade. If RD4 proves to be the official, then you have no worries. If not, you'll have to wait for an Oreo ROM to surface with the version 3 bootloader and that's on the upgradable path. Seems to happen a few times a year...

Check again. The ATT page has been updated to reflect BRC1 as the current official. However, they do sometimes allow upgrade from two different versions. So you may be able to upgrade from BRB5 and BRC1 if Oreo is the next release. it's not impossible that RD4 is the official. Just as the RC1...

The upgrade path has gone BRA7 -> BRB5 -> BRC1 Samsung announced that the normal S7 variants are getting Oreo in mid-May, so I would think that it will be a CRE* build with one more security update (S2BRD*) coming out soon before the May Oreo release.

Possibly. My theory is that, because RD1 and RD4 are updated off of RB5 and because it's been confirmed that RC1 is the official April update I think that there will be an BRC1 to CRDX or BRC1 to CREX update where the X is some unknown number. I'd be surprised if either of the RD1 or RD4 updates...

I explored the main S7 ATT forums last night and saw that they are working with newer Oreo betas than the CRC8 that are discussed above. That reminded me to looks at versions with an updated bootloader (U or S 3 instead of U or S 2). With that in mind, looks like some new Oreo trials are...

If anyone sees the OTA from ATT, can you comment if it's S2BRC1?