Just FYI, it appears with the new Blv3 firmwares, the device will only accept official firmware. Meaning, no more flashing U1 firmware on the carrier models, or vice versa. No more flashing U or U1 firmware to the Canadian W models. Flashing between carrier firmwares is fine as long as it's on a carrier branded device (running TMB on a VZW device, etc). But running 950U firmware on a 950U1 will result in a brick, that is this far unrecoverable.
If your currently are running U1 firmware on a U device, vice versa, or running W firmware on a U or U1 device, or vice versa, you need to flash back to the firmware version that shipped with your device BEFORE you accept any OTAs that take you up to Blv3. Currently the S series is still on BlV2, but may go to Blv3 like the Note series just did.*
This has been tested and confirmed.
Credit goes to @me2151, @FatalONEM8*for discovering this and warning people. I didn't find the issue or test, it just passing on the info to hopefully save some bricks.
Update from @mweinbach:
EDIT: After being tested by XDA Senior member me2151, it turns out cross region flashing does work. Prince Comsy Odin is working, but we can not test if the factory binary flashing will hard brick your phone. So flashing US unlocked onto a US carrier device should work.
This myth has been completely busted. We are not sure what bricked the tester's phone. He was not trying to downgrade from Blv3 to Blv2, nor did it have anything to do with FRP lock or user accounts as some people (who weren't involved in the testing) suggested.
But as we have verified, and has also been verified by users here at XDA, Prince Comsy ODIN still works on Blv3. Carrier switching still works on Blv3. @BlueFox721 has posted the Factory Binary files for Blv3 as well as a guide for carrier switching.
So carry on! Canadians, feel free to use U software! U users, feel free to use U1 software!
I am happy to admit I was wrong, and I apologize for any frantic flashing and factory resets I caused. I genuinely was trying to prevent hard bricks, and decided to err on the side of caution, even if that meant I overreacted.
Thank you for understanding!
So when the new firmware comes out I will try this out.. give me a reason. To get an new device
---------- Post added at 10:17 PM ---------- Previous post was at 10:16 PM ----------
Just waiting o. The u1 firmwarre
smiley45 said:
So when the new firmware comes out I will try this out.. give me a reason. To get an new device
---------- Post added at 10:17 PM ---------- Previous post was at 10:16 PM ----------
Just waiting o. The u1 firmwarre
Click to expand...
Click to collapse
As long as you're ready to pay for one! LOL
Seriously, post back here when you test it.
There is currently a group working on a fix for bricked devices, but for now consider it a hard brick. Don't chance it.
Im confused by what is posted by OP. I bought an unlocked device directly from Samsung and if I recall, it was a U1. I immediately flashed the Verizon firmware version (1AQ15) and have been getting OTAs. This morning I updated via OTA to 3BRA5 with no problem. Given no issues, should I worry if I ever need to ODIN a Verizon firmware with v3 BL in the future?
Sent from my SM-N950U using Tapatalk
ferzmedina said:
Im confused by what is posted by OP. I bought an unlocked device directly from Samsung and if I recall, it was a U1. I immediately flashed the Verizon firmware version (1AQ15) and have been getting OTAs. This morning I updated via OTA to 3BRA5 with no problem. Given no issues, should I worry if I ever need to ODIN a Verizon firmware with v3 BL in the future?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
You may have lucked out. I'll bring it to the attention of the Telegram group.
Can somebody smarter then me explain what this means for me?
I'm currently a 950W device running BLV3 CRAD from the 950U
From what I understand, don't accept OTAs, so I've turned off auto update,
but from what I can see, I'm not able to register my phone to receive OTA's
because I'm on unreleased firmware.
ignore it, aslong as you flash a BL3 firmware through odin, I was on oreo too and used the nougat 7.1.1 with BL3 which was just released, you can flash with odin with no issues whatsoever, Only use firmware from N950U and youl be fine
chwads2k8 said:
ignore it, aslong as you flash a BL3 firmware through odin, I was on oreo too and used the nougat 7.1.1 with BL3 which was just released, you can flash with odin with no issues whatsoever, Only use firmware from N950U and youl be fine
Click to expand...
Click to collapse
Thats not necessarily true.
DeathSentinels said:
Can somebody smarter then me explain what this means for me?
I'm currently a 950W device running BLV3 CRAD from the 950U
From what I understand, don't accept OTAs, so I've turned off auto update,
but from what I can see, I'm not able to register my phone to receive OTA's
because I'm on unreleased firmware.
Click to expand...
Click to collapse
So far there have been no issues with the oreo leaks on blv3. But what we've seen is once the official releases come out, if you accept an OTA or ODIN to the new official firmware. It will brick if you're trying to use a different region CSC. I.e. running 950U firmware on a 950W or vice versa.
Mr. Orange 645 said:
So far there have been no issues with the oreo leaks on blv3. But what we've seen is once the official releases come out, if you accept an OTA or ODIN to the new official firmware. It will brick if you're trying to use a different region CSC. I.e. running 950U firmware on a 950W or vice versa.
Click to expand...
Click to collapse
Ohh okay, that makes sense, so for example, if I stay on this build, once an official odin of the 950W comes out with BLV3 I can safely odin to that?
DeathSentinels said:
Can somebody smarter then me explain what this means for me?
I'm currently a 950W device running BLV3 CRAD from the 950U
From what I understand, don't accept OTAs, so I've turned off auto update,
but from what I can see, I'm not able to register my phone to receive OTA's
because I'm on unreleased firmware.
Click to expand...
Click to collapse
DeathSentinels said:
Ohh okay, that makes sense, so for example, if I stay on this build, once an official odin of the 950W comes out with BLV3 I can safely odin to that?
Click to expand...
Click to collapse
Yes that is my understanding. We are still researching.
This is a very bastardly, and Apple like thing for Samsung to do! Not pleased that I'm going to have to either stay on my current build of Nougat forever or flash back to Sprint, as Sprint disables things like Samsung's built in caller ID and replaces it with their own pay app. Not to mention a tonne of other unwanted bloat.
How does the boot loader know the firmware has been cross flashed anyway? I thought all that mattered was that the image was signed by Samsung.
There are only Snapdragon Devices affected, or also exynos devices?
Gesendet von meinem SM-N950F mit Tapatalk
Logel said:
There are only Snapdragon Devices affected, or also exynos devices?
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
Snap drags only
Logel said:
There are only Snapdragon Devices affected, or also exynos devices?
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
TheMadScientist said:
Snap drags only
Click to expand...
Click to collapse
Exynos devices are affected too. Anything that uses Comsey ODIN.
Mr. Orange 645 said:
Exynos devices are affected too. Anything that uses Comsey ODIN.
Click to expand...
Click to collapse
True i didnt think about that half of it....
Oh well good thing I like where i'm at.
Forget sammy and Forget Oreo
I don't asked because the modded Odin, I asked because that new boatloader update. The boatloader for Exynos are different to Snapdragon. But I think you guys are right. I could bet that new secured boatloader entries are also into Exynos boatloader.
Edit: ok, i just have read the article again. Exynos boatloader are also patched [emoji852]
Gesendet von meinem SM-N950F mit Tapatalk
TheMadScientist said:
True i didnt think about that half of it....
Oh well good thing I like where i'm at.
Forget sammy and Forget Oreo
Click to expand...
Click to collapse
Yup, I just got a 64 GB Panda today from Google today. At least my wife likes the Note still.
Misterxtc said:
Yup, I just got a 64 GB Panda today from Google today. At least my wife likes the Note still.
Click to expand...
Click to collapse
WHAT?! Who am I going to harass in the N8 forums now?!
Related
Hello there.
I have a SM-925I from Brazil, but I realized that this variant exists in other countries... My question is, if I change the original rom for a rom from another country, but from the same model (SM-g925I) will it trip my knox? Will i miss my warranty?
I want to install lollipop 5.1.1
Thank You
If you're going to venture into ROM changing, forget about warranty
Sent from my SM-G920W8 using Tapatalk
Brava27 said:
If you're going to venture into ROM changing, forget about warranty
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Well, i think i'll wait then... too expensive in Brazil to lose warranty.
Thanks, man.
alexandreangeli said:
Well, i think i'll wait then... too expensive in Brazil to lose warranty.
Thanks, man.
Click to expand...
Click to collapse
Just root and be careful. I've rooted every device I've owned and don't care about warranty. If you're careful then you are good. Checkout ping pong root. It roots without warranty.
Brava27 said:
Just root and be careful. I've rooted every device I've owned and don't care about warranty. If you're careful then you are good. Checkout ping pong root. It roots without warranty.
Click to expand...
Click to collapse
Right, I will find out more about root and think hard before do it.
Thanks for the tips.
alexandreangeli said:
Hello there.
I have a SM-925I from Brazil, but I realized that this variant exists in other countries... My question is, if I change the original rom for a rom from another country, but from the same model (SM-g925I) will it trip my knox? Will i miss my warranty?
I want to install lollipop 5.1.1
Thank You
Click to expand...
Click to collapse
The only 5.1.1 version for the 925I are from the Indian version and it seems that Samsung has since held back a little with releasing it for other CSCs.
There have been a few reports of people flashing the 5.1.1 version on their 925I phones on Australia and no longer getting good 4g speeds. I'm going to wait until the Australian version of the update is released.
Having said that, if the firmware you want to flash is stock firmware produced by Samsung and is compatible with your phone variant (I.e a 925I stock firmware) regardless of CSC then flashing it via Odin should not trip Knox and should not interfere with your warranty. A couple of people here or there have stated that they've tried Knox this way but the majority (including me) have been fine.
You'll need to factory reset following changing to a different CSC if you want to receive over the air updates.
My suggestion? Wait for the Brazilian update. As for rooting, apart from blocking ads I've not missed having root at all.
Sent from my Galaxy S6 Edge
dlotters said:
The only 5.1.1 version for the 925I are from the Indian version and it seems that Samsung has since held back a little with releasing it for other CSCs.
There have been a few reports of people flashing the 5.1.1 version on their 925I phones on Australia and no longer getting good 4g speeds. I'm going to wait until the Australian version of the update is released.
Having said that, if the firmware you want to flash is stock firmware produced by Samsung and is compatible with your phone variant (I.e a 925I stock firmware) regardless of CSC then flashing it via Odin should not trip Knox and should not interfere with your warranty. A couple of people here or there have stated that they've tried Knox this way but the majority (including me) have been fine.
You'll need to factory reset following changing to a different CSC if you want to receive over the air updates.
My suggestion? Wait for the Brazilian update. As for rooting, apart from blocking ads I've not missed having root at all.
Sent from my Galaxy S6 Edge
Click to expand...
Click to collapse
you
Sent from my SM-G925I using Tapatalk
dlotters said:
The only 5.1.1 version for the 925I are from the Indian version and it seems that Samsung has since held back a little with releasing it for other CSCs.
There have been a few reports of people flashing the 5.1.1 version on their 925I phones on Australia and no longer getting good 4g speeds. I'm going to wait until the Australian version of the update is released.
Having said that, if the firmware you want to flash is stock firmware produced by Samsung and is compatible with your phone variant (I.e a 925I stock firmware) regardless of CSC then flashing it via Odin should not trip Knox and should not interfere with your warranty. A couple of people here or there have stated that they've tried Knox this way but the majority (including me) have been fine.
You'll need to factory reset following changing to a different CSC if you want to receive over the air updates.
My suggestion? Wait for the Brazilian update. As for rooting, apart from blocking ads I've not missed having root at all.
Sent from my Galaxy S6 Edge
Click to expand...
Click to collapse
Thanks, man. That was very enlightening. I'll wait for thrle brazilian update.
Thanks again.
Sent from my SM-G925I using Tapatalk
Hi,
I have been having trouble with Odin on my T-mobile S5. Only now I realized that my model is SM-G900T3, not samsung Galaxy S5 SM-G900T. So I can't flash ROM posted as they are for 900T, not 900T3.
Is there a repository for T3 ROM?
Or is there a way for me to use T ROM instead? The developer option has "OEM unlocking" but I am not certain what it does.
Thanks
redhonker said:
Is there a repository for T3 ROM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65063785&postcount=102
That's probably why you're having so much trouble trying to get on KitKat. The SM-G900T3 was never officially on KitKat, just lollipop (5.1.1)
It has only 5.1.1 ROM -- I guess the model came out later than G900T and only has 5.1.1 ROM
Is the bootloader locked?
I've seen post that people installed CM ROM for G900T on G900T3 successfully. Does anyone know if I can flash stock rooted deodexed G900T ROM on G900T3 with TWRP?
Thanks
redhonker said:
It has only 5.1.1 ROM -- I guess the model came out later than G900T and only has 5.1.1 ROM
Is the bootloader locked?
I've seen post that people installed CM ROM for G900T on G900T3 successfully. Does anyone know if I can flash stock rooted deodexed G900T ROM on G900T3 with TWRP?
Thanks
Click to expand...
Click to collapse
Yes you can. I'm in possession of a g900t3 and I can install any and all of the t-mobile TouchWiz roms. It's the same firmware as the g900t, I guess it's just a newer manufactured model.
Edit, bootloader doesn't seem locked, but there is an option in developer options to unlock bootloader anyways
xfrobex said:
Yes you can. I'm in possession of a g900t3 and I can install any and all of the t-mobile TouchWiz roms. It's the same firmware as the g900t, I guess it's just a newer manufactured model.
Edit, bootloader doesn't seem locked, but there is an option in developer options to unlock bootloader anyways
Click to expand...
Click to collapse
I did a search and found http://www.sammobile.com/forum/showthread.php?t=28068
It seems 900T3 will fail to boot up with 900T ROM. Have you tried it?
Thanks
Yes. I'm actively running vison-x OL1 rom. Was running the de-odex stock rom till I f'd it up messing with permissions. Both work no problems
---------- Post added at 08:29 PM ---------- Previous post was at 08:20 PM ----------
I got my replacement phone from tmoible store, backplate has AT&T logo.. lol. So much for that. I switched with my old sprint backplate so it has no company logo. But yes, I've worked it with tmobile roms, no problems at all. No reason to goto kitkat unless u r trying to unlock all frequencies. Tmobile works in the basement where I work, sprint s5 didn't get s*** for signal there
What are the steps to install the G900T ROM? Thanks
Sorry for such a delay, I've been having serious health problems. Before changing roms or rooting, enter developer settings and click he "unlock" bootloader option. Then you can use the same rooting techniques as the g900t. Use Odin to flash TWRP 3.0.0-0 recovery, then reboot to recovery and make a nandroid backup. Download whatever g900t rom you would like, and flash away. I am personally using the Vision-X rom from 3-4-16. Once you have the recovery installed and have a backup of stock rom, you are good to go. And you can Odin flash any g900t baseband, modem and it will work. Even kernels from the g900t can be used, flash them thru recovery. When TWRP asks to help root your phone, deny it at all times. It seems to f up the root on the custom roms that come pre-rooted already
Sorry for necro bump but is it confirmed that the T3 version bootloader is unlocked? And you can simply load CM/Lineage as you would a regular G900T? Thanks.
mario24601 said:
Sorry for necro bump but is it confirmed that the T3 version bootloader is unlocked? And you can simply load CM/Lineage as you would a regular G900T? Thanks.
Click to expand...
Click to collapse
if Odin fails during the Custom Rom Install and you have a ROM that is compatible with the T3 model from sammobile, then yes it is locked, if it proceeds and passes, then no the bootloader isnt locked. bear in mind it is normally that AT&T and Verizon who lock down their bootloaders to prevent downgrading
eidairaman1 said:
if Odin fails during the Custom Rom Install and you have a ROM that is compatible with the T3 model from sammobile, then yes it is locked, if it proceeds and passes, then no the bootloader isnt locked. bear in mind it is normally that AT&T and Verizon who lock down their bootloaders to prevent downgrading
Click to expand...
Click to collapse
I don't have one, was thinking of buying one which is why I was asking for confirmation before buying but thanks.
Sent from my Moto X using Tapatalk
mario24601 said:
I don't have one, was thinking of buying one which is why I was asking for confirmation before buying but thanks.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
you can find G900Ts on Amazon.com (better priced than the GS7 for sure).
Mine is carrier unlocked and brandnew as of last year. I compared Specs between G900T and G900T3, same phone.
Your Firmware is here
sammobile.com/firmwares/database/SM-G900T3/
eidairaman1 said:
you can find G900Ts on Amazon.com (better priced than the GS7 for sure).
Mine is carrier unlocked and brandnew as of last year. I compared Specs between G900T and G900T3, same phone.
Your Firmware is here
sammobile.com/firmwares/database/SM-G900T3/
Click to expand...
Click to collapse
Can't find any new non refurbished ones. The t3 version seems like only new ones out there.
Sent from my Moto X using Tapatalk
As far as flashing roms goes, there's no difference between the G900T & G900T3. If you're flashing firmware, however, there is a difference, Odin won't let you flash a G900T firmware image onto a G900T3, and vice versa. I own both a G900T & a G900T3. If you're buying a used/refurb, you're better off with the T3 because it's newer. When new firmware is published, I flash both phones with their respective firmware (V1 for the 900T, V3 for the 900T3), then the 900T is rooted but otherwise stays stock, and the 900T3 is flashed with a deodexed rom, all of which seem to be built from the V1 firmware and which work fine on the T3. Whatever the difference is, it seems to be in either the modem and/or the bootloader, and it's minor enough that it doesn't effect the booting of the rom.
invisiblewave said:
As far as flashing roms goes, there's no difference between the G900T & G900T3. If you're flashing firmware, however, there is a difference, Odin won't let you flash a G900T firmware image onto a G900T3, and vice versa. I own both a G900T & a G900T3. If you're buying a used/refurb, you're better off with the T3 because it's newer. When new firmware is published, I flash both phones with their respective firmware (V1 for the 900T, V3 for the 900T3), then the 900T is rooted but otherwise stays stock, and the 900T3 is flashed with a deodexed rom, all of which seem to be built from the V1 firmware and which work fine on the T3. Whatever the difference is, it seems to be in either the modem and/or the bootloader, and it's minor enough that it doesn't effect the booting of the rom.
Click to expand...
Click to collapse
Thanks so does this mean I can or can't load CM/lineage on the T3 version?
Sent from my Moto X using Tapatalk
I don't know how to make it any clearer. You can run any rom on a G900T3. I've yet to find one that doesn't boot. I'm currently running the G900T3UVS3GPK3 firmware on a G900T3 with the Resurrection Remix rom which is based on the official Lineage OS 14.X.
invisiblewave said:
I don't know how to make it any clearer. You can run any rom on a G900T3. I've yet to find one that doesn't boot. I'm currently running the G900T3UVS3GPK3 firmware on a G900T3 with the Resurrection Remix rom which is based on the official Lineage OS 14.X.
Click to expand...
Click to collapse
I'm really dense sometimes thanks appreciate the clarification. Placing my order for a T3 today.
Sent from my Moto X using Tapatalk
mario24601 said:
Thanks so does this mean I can or can't load CM/lineage on the T3 version?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
mario24601 said:
I'm really dense sometimes thanks appreciate the clarification. Placing my order for a T3 today.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I don't think you'll be disappointed. I don't know why anyone would bother with the S6 or S7, although I do have to say the S7 looks pretty sexy.
I got mine new from B&H Photo directly at their Manhattan store since they sell the T-Mobile model new and unlocked (they open the box, unlock it, and put it back in all without touching the battery as I was explained). Only difference I notice is that the battery door is now truly plastic for the black model instead of being a rubber type material as they originally were (I owned one when it was first released, so I remember). Heat seems to be another difference, and it is more easily felt with the plastic back. Battery seems to also suck alot more than the first ones, but I read that this is a Lollipop and Marshmallow problem, and the heat it added.
Other than firmware, does anybody know any OTHER differences? 3DMark fails to recognize it.
invisiblewave said:
I don't think you'll be disappointed. I don't know why anyone would bother with the S6 or S7, although I do have to say the S7 looks pretty sexy.
Click to expand...
Click to collapse
Well I got my T3 but couldn't root. I get a message that says FRP lock when trying to root via oden which is same process I've used on other S5s so not sure if this means bootloader is locked. Any thoughts? Thanks
Sent from my Moto X using Tapatalk
I usually would not do this but because of the cleaver way of putting it from a ZTE mod i figured I would share it as is
https://community.zteusa.com/commun...ming-soon-to-a-device-near-you?comment-26024=
peramikic said:
I usually would not do this but because of the cleaver way of putting it from a ZTE mod i figured I would share it as is
https://community.zteusa.com/commun...ming-soon-to-a-device-near-you?comment-26024=
Click to expand...
Click to collapse
They're finally releasing factory images, yay!
xxBrun0xx said:
They're finally releasing factory images, yay!
Click to expand...
Click to collapse
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
nsane said:
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
Click to expand...
Click to collapse
It's almost guaranteed we will get a stock B27 recovery image. I do not see them dumping MiFavor, not even with N.
Question is what kind of recovery method will they use (DFU/EDL flasher or just full zip) and can we generated custom "MiFavor" from them
nsane said:
They are going to give us something that they consider to be "stock"
Worst case scenario it's factory images
Best case scenario it's AOSP
Click to expand...
Click to collapse
Best case scenario it's both
**** just when I gave up on the phone and send it back to Newegg ?
Sent from my Pixel using XDA-Developers mobile app
So please let's go
I am so ready. I have been holding off on unlocking, installing recovery and root until something worth while shook loose. Let's do this!
UnBrick tool will be good. I'm waiting for it. I hope that they release soon.
Would be great if it's something with bootloader unlock
Hopefully it's stock images so I can finally root my phone free of worry.
System images all but confirmed! Great news!
https://community.zteusa.com/community/blogging/blog/2016/10/21/weekly-roundup-october-21-2016
Factory images and new bootloader unlock process coming next week. Update #3 to come in the following weeks.
Fingers crossed update #3 is the nearly stock nougat build we saw running on a Chinese axon 7 last week!
xxBrun0xx said:
https://community.zteusa.com/community/blogging/blog/2016/10/21/weekly-roundup-october-21-2016
Factory images and new bootloader unlock process coming next week. Update #3 to come in the following weeks.
Fingers crossed update #3 is the nearly stock nougat build we saw running on a Chinese axon 7 last week!
Click to expand...
Click to collapse
as long as they don't make you sign away our warranty for the bootloader unlock and stock image use, else I'll have to do it the old way and keep my warranty under US law.
Nothing for EU still. Looks like EU won't get an official unlock...
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
peramikic said:
It's almost guaranteed we will get a stock B27 recovery image. I do not see them dumping MiFavor, not even with N.
Question is what kind of recovery method will they use (DFU/EDL flasher or just full zip) and can we generated custom "MiFavor" from them
Click to expand...
Click to collapse
I'm guessing since they say that's in final testing and next update is almost ready to roll out, I'd more guess it will be with whatever that build is. But it will definitely just be a stock image, not AOSP.
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
keessonnema said:
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
Click to expand...
Click to collapse
The EU model has had just as many updates as the US one at this point. US got B18->B20->B27. EU has gotten B02->B03->B05.
Bootloader is slightly different, but the US model currently doesn't have support for that either, as they pulled it to rework it.
Where the US is definitely better is in communication from the respective ZTE branch.
TeutonJon78 said:
I'm guessing since they say that's in final testing and next update is almost ready to roll out, I'd more guess it will be with whatever that build is. But it will definitely just be a stock image, not AOSP.
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
The EU model has had just as many updates as the US one at this point. US got B18->B20->B27. EU has gotten B02->B03->B05.
Bootloader is slightly different, but the US model currently doesn't have support for that either, as they pulled it to rework it.
Where the US is definitely better is in communication from the respective ZTE branch.
Click to expand...
Click to collapse
Uhm the EU Version is still on Android sec Patches from 1. Juli for example. And b05 is somewhat unofficial, No ota yet.
Gesendet von meinem ZTE A2017G mit Tapatalk
keessonnema said:
Sadly this has nothing to do with the EU model whatsoever.
Very sad to see the EU model just 'ignored' and forgotten in terms of bootloader unlock and updates.
Click to expand...
Click to collapse
Total unacceptable and ridicules that kind of discrimination of ZTE part.
Seems European are B class customers to them.
WTF ZTE!
Sent from my iPad using Tapatalk
Close thread
Is there one for the S7 Active?
ThunderingLight said:
Is there one for the S7 Active?
Click to expand...
Click to collapse
Hasn't been found yet
Ok can you update the post once it has been found?
So, anyone flash this yet? I'm tempted but won't be back home to a PC (in case something goes wrong) until tonight. Just looking for some general impressions.
So, I did this. Pretty impressed with the overall device feel now, SE9 is nice . No hang ups other thank it took a long friggin' time, also remember this will WIPE all the data, so make sure to do a backup prior to. The initial/first phone setup is very iPhone-ish, imo.
bobloblaw1 said:
So, anyone flash this yet? I'm tempted but won't be back home to a PC (in case something goes wrong) until tonight. Just looking for some general impressions.
Click to expand...
Click to collapse
Be warned; this update is ONLY for SM-G930A firmware - it has a second-stage updater that blocks all other versions (including SM-G930T, which I myself tried). In other words, it is a carrier-specific update, folks.
PGHammer said:
Be warned; this update is ONLY for SM-G930A firmware - it has a second-stage updater that blocks all other versions (including SM-G930T, which I myself tried). In other words, it is a carrier-specific update, folks.
Click to expand...
Click to collapse
Will it work for sm-g930u at&t ????
mhdsweidan said:
Will it work for sm-g930u at&t ????
Click to expand...
Click to collapse
HIGHLY doubtful - not with a specific firmware check in place.
mhdsweidan said:
Will it work for sm-g930u at&t ????
Click to expand...
Click to collapse
You could try flashing G930A firmware in Odin and updating that way.
(Not sure it'll work though)
Sent from my SM-G955U using Tapatalk
If switching from u firmware back to att ql1 what version is capable of flashing att haven't been on carrier firmware since mm , wanna try Oreo
miko12312 said:
If switching from u firmware back to att ql1 what version is capable of flashing att haven't been on carrier firmware since mm , wanna try Oreo
Click to expand...
Click to collapse
What's your bootloader version? (5th from last letter in build number)
Sent from my SM-G955U using Tapatalk
FatalONEM8 said:
You could try flashing G930A firmware in Odin and updating that way.
(Not sure it'll work though)
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
If it weren't for this being a daily driver, I'd consider it. However, because it is, that's not an option. So I'll have to wait for either a neutral version or one that will work with the SM-G930T.
I am currently testing it out, I was on the latest U firmware and downloaded the latest ATT firmware, will update on how it goes
**EDIT
I am getting a model mismatch trying to flash G930AUCS4BRA1 (full odin file) on to a G930UUES4BRA1 firmware
micallan_17 said:
I am currently testing it out, I was on the latest U firmware and downloaded the latest ATT firmware, will update on how it goes
**EDIT
I am getting a model mismatch trying to flash G930AUCS4BRA1 (full odin file) on to a G930UUES4BRA1 firmware
Click to expand...
Click to collapse
Try using PrinceComsy Odin
Sent from my SM-G955U using Tapatalk
oreo otas
Goodnight friends, I started to update my phone to version 8.0 but it has more than 30 min in the option of patchin system files is normal or my step to better life is my s7.
Excuse me for my English since it is not my native language.
spend the fright of my life but finally install now approve to see how it works on android 8.0
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Has anyone been able to successfully downgrade back to RA1 after sideloading 8.0?
chewis559 said:
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Click to expand...
Click to collapse
Just reboot in recovery mode and wipe cache
chewis559 said:
Just flashed updateon my s7 and now mywifi is not working anyone else having this issue?
Click to expand...
Click to collapse
I had the same issue. The recommendation of rebooting into recovery and wiping Cache works.
:good:
this is the firmware Sprint is testing: G930PVPS7CRH1
Sprint Users rejoice, seems samsung is testing a new firmware for the unlocked S7 and will be a bootloader version 8
<latest>G930UUEU8CRJ2.DM/G930UOYM8CRJ2/G930UUEU8CRJ2</latest>
micallan_17 said:
this is the firmware Sprint is testing: G930PVPS7CRH1
Click to expand...
Click to collapse
I wonder why? They have already won the bootloader version race by a landslide.
lvpre said:
I wonder why? They have already won the bootloader version race by a landslide.
Click to expand...
Click to collapse
I know, and i have no idea why they are doing this.
my phone updated to it today
the ver my phone has isG930PVPU7CRG3 sprint
Sprint must really not want their phones be unbranded or flashed to another carrier.
Sprint Users rejoice, seems samsung is testing a new firmware for the unlocked S7 and will be a bootloader version 8
<latest>G930UUEU8CRJ2.DM/G930UOYM8CRJ2/G930UUEU8CRJ2</latest>
micallan_17 said:
Sprint Users rejoice, seems samsung is testing a new firmware for the unlocked S7 and will be a bootloader version 8
<latest>G930UUEU8CRJ2.DM/G930UOYM8CRJ2/G930UUEU8CRJ2</latest>
Click to expand...
Click to collapse
I hope this is true! You've been good at calling these so far! Great find!
micallan_17 said:
Sprint Users rejoice, seems samsung is testing a new firmware for the unlocked S7 and will be a bootloader version 8
<latest>G930UUEU8CRJ2.DM/G930UOYM8CRJ2/G930UUEU8CRJ2</latest>
Click to expand...
Click to collapse
I'm also very much hoping this is true - can I ask where did you find this information?
lvpre said:
I hope this is true! You've been good at calling these so far! Great find!
Click to expand...
Click to collapse
thank you, happy to help
kpl388 said:
I'm also very much hoping this is true - can I ask where did you find this information?
Click to expand...
Click to collapse
i use this link to check what firmware samsung is testing, see here
for sprint, use this one
this also means that, once this update is released, at least for the unlocked S7, we won't be able to downgrade to marshmallow or nougat . I assume samsung is doing this so remaining s7 users are forced to stay on oreo forever
micallan_17 said:
this also means that, once this update is released, at least for the unlocked S7, we won't be able to downgrade to marshmallow or nougat . I assume samsung is doing this so remaining s7 users are forced to stay on oreo forever
Click to expand...
Click to collapse
found this little gem too:
G930TUVS8CRJ1
Code says J= October...hopefully, sooner than later.
lvpre said:
found this little gem too:
G930TUVS8CRJ1
Code says J= October...hopefully, sooner than later.
Click to expand...
Click to collapse
i sure hope so since we're all stuck on august security patch
micallan_17 said:
i use this link to check what firmware samsung is testing, see here
for sprint, use this one
Click to expand...
Click to collapse
That's really useful - thanks so much!
---------- Post added at 02:11 PM ---------- Previous post was at 01:54 PM ----------
lvpre said:
found this little gem too:
G930TUVS8CRJ1
Code says J= October...hopefully, sooner than later.
Click to expand...
Click to collapse
I'm sure this is just coincidence, but I've been trying to get a Sprint S7 working properly on T-mobile's network and was communicating with both T-mobile and Samsung support all last week, advocating for both of them to increase their bootloader version. In particular, I think it makes sense for the 930U to always match or exceed the highest carrier version. I'm not sure if there's any substantive difference among bootloader versions, but that way users would always have the freedom to switch carriers. (The 930P often fails to make calls on T-mobile's network, since it doesn't support VoLTE).
This should probably drop around mid-November based on past updates and codes.
I have bootloader version 7 I think if it goes by the 5th number. I keep getting fuse errors when I try to flash this phone and I've never flashed anything before.
Redrobber502 said:
I have bootloader version 7 I think if it goes by the 5th number. I keep getting fuse errors when I try to flash this phone and I've never flashed anything before.
Click to expand...
Click to collapse
Sounds like you are trying to flash a firmware that isn't b7. This would result in the fuse error.
lvpre said:
Sounds like you are trying to flash a firmware that isn't b7. This would result in the fuse error.
Click to expand...
Click to collapse
Ahh OKay I figured mine was 7 because I'm on Oreo and my PDA: G930PVPS7CRH2. IM on the sprint variation and I'm just stuck at this point. I rooted my moto 4 plus the first day I tried which is a snapdragon as well. This Odin things tricky though. I guess I can't get the new xposed either then unless it's possible to install without flashing. I really would appreciate anyones help thanks ?
Redrobber502 said:
Ahh OKay I figured mine was 7 because I'm on Oreo and my PDA: G930PVPS7CRH2. IM on the sprint variation and I'm just stuck at this point. I rooted my moto 4 plus the first day I tried which is a snapdragon as well. This Odin things tricky though. I guess I can't get the new xposed either then unless it's possible to install without flashing. I really would appreciate anyones help thanks ?
Click to expand...
Click to collapse
I'm not sure about xposed, but if you're stuck with your phone in a non-functional state after trying to install a lower bootloader firmware, you can always re-flash the latest stock sprint firmware.