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."
To expand a bit on what @mweinbach*just said, @me2151*did some more testing, and he was able to successfully carrier switch from a 950U to 950W using Comsey ODIN. So it looks like Comsey ODIN is not patched as we originally thought. Not sure exactly what caused the tester's phone to brick, but it HARD BRICKED and had to be RMA'd at his expense. So we jumped on the forums here to warn others until more testing could be done. @mweinbach*wrote the article and @xdanilvaand I began posting here.*
We may have overreacted, but wanted to err on the side of caution to protect people from hard bricks.*
The Blv3 factory binary has not been tested, so still unsure if/how we will be able to use it, or if it will cause issues.*
For now, carry on as usual, but understand we still don't know the full implications of the Blv3 patches. One person has already HARD BRICKED, and @me2151*almost hard bricked testing all of this for us.
There is currently a group working on a fix for bricked devices, but for now consider it a hard brick. Don't chance it.
Is Oreo for the S8/S8+ a Blv3 firmware or is it BLV2?
just curious as I flashed my Verizon branded GS8 to U1 firmware to take the Oreo beta..
So If I own a Sm-G950U1 but I have been running G950U Tmobile Oreo beta and upgrade to the stable oreo I'll brick my phone? In order to prevent this I'll have to first go back to G950U1 on nouget and then go up to oreo?
I don't really want to do this because I am loving using the T-Mobile variant because it gives me multiuser (digits) since it's built in.
Does the same apply to exynos devoces?
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
ironbesterer said:
As far as I know, if you are on the Oreo beta, at least on the Snapdragon US variant, you are still on v2 (the number after the U in the build number is the bootloader version). Do not accept any OTAs and only update if you are completely certain you want to be stuck.
Click to expand...
Click to collapse
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
vimerate said:
Does this mean that we can update to a build with Bootloader v3, but don't expect to be able to change carriers afterwards? For example, I switched my S8 from ATT to XAA to get rid of the bloat. Should I restore to ATT on Nougat or can I stay on Oreo beta on the unlocked U1 firmware?
Click to expand...
Click to collapse
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
ironbesterer said:
You can stay on the unlocked firmware for now, but once you switch to one of the carrier firmwares with v3, you cannot go back to anything other than a carrier firmware with v3. You should be ok for now, but just be sure that the next time you update that it is not on v3 or you'll be stuck permanently or until a fix is found.
Click to expand...
Click to collapse
My question is I have an ATT unlocked device on Cricket Wireless running the oreo beta since I flashed it to unlocked firmware. Should I revert back to Nougat before the final oreo build or just stick with it?
Mr. Orange 645 said:
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.
Click to expand...
Click to collapse
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
raduque said:
So what you're saying is, I'm running U1 on my Note8, if I take an OTA with BL3, it will brick?
Click to expand...
Click to collapse
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Mr. Orange 645 said:
Yes I believe so. We are still looking into it. It may just be flashing with Comsey ODIN does it.
Click to expand...
Click to collapse
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
raduque said:
Honestly, I think that the latter is what does it. Are y'all flashing from a fully OTA'd BLv3 Carrier FW to the BLv2 U1 FW using Comsey?
There isn't a U1 FW with BLv3 yet, right?
Click to expand...
Click to collapse
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Mr. Orange 645 said:
There is not.
And I haven't personally tested it, but Comsey is required to flash U1, so we know it will brick the phone once it does reach Blv3.
Click to expand...
Click to collapse
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
raduque said:
So somebody flashed a full Odin U/carrier FW onto an actual U1 device and it bricked?
Click to expand...
Click to collapse
No on a U1. They tried to carrier switch on either a U or a W.
Ok... so they tried to go from a device running a Carrier fw on blv3 to... what? A carrier fw on blv2?
I know this is still early, but the more questions and answers I see, the more confused I am.
Do we know if all of these scenarios will have the same result?
a) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. A BLv3 OTA will brick the device. True/false/not yet known?
b) I have a AT&T (950U) branded device. I flashed it to become unlocked software (950U1). The device currently updates OTA with unlocked updates. Assuming a) is FALSE. Device will operate as normal U1 phone, but I will never be able to put 950U carrier branded software on it (via modded Prince Comsy), because that will brick it. True/false/not yet known?
c) I have a AT&T (950U) branded device. I flashed it to become TMobile (950U) device. It now get updates via Tmobile. Future OTAs will continue as normal and I can even use Odin to flash other carrier software (950U), but I can NEVER use modded Odin to flash unlocked software (950U1)? True/false/not yet known.
Based on what I've read right so far. It seems that the answers all remain theoretical, thus not yet known, but based on the Note8 update, the answers would be a) False. b) True. c) True.
Am I far off base???
The thing right now that I understand the least is the scenario a). I don't understand why if I have a phone that was 950U but is now 950U1, why it would get bricked. I do understand that attempts to change it once BLv3 hit are currently DOA, but that's different than simply keeping your phone in the stream that it is currently.
There are some good questions in this thread, I realize that its an evolving situation... So I have to ask directly... I have a Verizon branded 950U that I followed https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817 to switch to XAA and flash the U1 firmware, and I have taken part in the Oreo beta.
Currently my phone has Baseband Version G950U1UEU2ZRA8. There is an OTA update pending right now that is G950U1EUE2ZRAE/G950U1OYM2ZRAE/G950U1UEU2ZRAE. From what I understand, and what I am reading about this BLV2 vs BLV3 issue, based on the numbers in this, if I take this update, I'll still be BlV2, and be ok? If I should want to return to stock Verizon firmware, I can still do it safely?
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
KidJoe said:
What I am unsure of is.. If the phone gets updated to BLV3 while I have the XAA/U1 setup on my Verizon branded 950U phone, will I still be able to flash back to stock Verizon, then just not change to anything else? or once I get on BLV3 I am stuck with whatever firmware I have on the phone? Or is that part still unknown for sure?
Click to expand...
Click to collapse
I am basically the same as you except AT&T beginning rather than Verizon. I currently have the ZRAE Oreo beta software running on my phone. Based on everything said so far, there is no danger yet in downloading that OTA because it is still BLv2. The danger would be if the final Oreo version drops with BLv3 and you apply it. Then we're left with these different scenarios that are still being figured out.
Absent any concrete info, I'm going to just avoid the Jan security patch on my Note8.
If I have to flash back the Verizon software to have a non-brick device, well I'll just sell this thing and buy a cheap unlocked phone with microsd, wireless charging and a nice screen.
Was on ATT, unlocked, now on T-Mobile. Phone is 3 yrs old, sketchy; shuts off randomly, has issues. Want to flash firmware, but Sammobile doesn't have 915a. Since it's unlocked and on t-mobile network, can I flash with t-mobile firmware? Can you put any carrier's rom on an unlocked phone? Sammobile has "usa" firmware with no carrier designation.
https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915R4/USC/
Thanks.
How did it go??
Same phone same problem also on Tmobile now... what did you do??
Use firmware uploaded by makki666
drivesavw said:
Same phone same problem also on Tmobile now... what did you do??
Click to expand...
Click to collapse
Did you find a solution? I flashed the firmware uploaded by makki666 found in another thread on updates for Note Edge from at&t. Right now am using 6.0.1 but may revert to basic 5.1 1 to get temporary root & get rid of bloatware (have not figured out what is worse, outdated OS or bloatware). If you found a better solution, please posr
I have an unlocked phone on Marshmallow.
Will it become locked again if I upgrade it to Nougat using Odin and the official firmware?
algarues said:
I have an unlocked phone on Marshmallow.
Will it become locked again if I upgrade it to Nougat using Odin and the official firmware?
Click to expand...
Click to collapse
I just bought a used note 5 it was running marshmallow stock rom and i did upgrade from marshmallow to NOUGAT and still my phone is UNLOCKED.sim card+data+calls+sms all working nice and battrry life is amazing.
Model SM-N920T
i flashed this latest firmware below via odin v3.12
https://androidfilehost.com/?fid=1322778262903991333
Thank you for the firmware source.
Just to clarify, you flashed only that AP, no additional modem or bootloader files?
In addition, is T-mobile a cell phone provider also in Arab emirates? I did some search in internet and it seems the answer is no.
Would it be possible somehow to compare if your phone and mine have been unlocked the same way?
Thank you for any additional help
algarues said:
Thank you for the firmware source.
Just to clarify, you flashed only that AP, no additional modem or bootloader files?
In addition, is T-mobile a cell phone provider also in Arab emirates? I did some search in internet and it seems the answer is no.
Would it be possible somehow to compare if your phone and mine have been unlocked the same way?
Thank you for any additional help
Click to expand...
Click to collapse
No my service provider is Etisalat not Tmobile but i bought this phone on Craigslist and it was locked on Tmobile network so the owner sold me very very cheap he didn't know how to unlock it.
I bought it in 140$ and and it's brand new condition almost untouched.
i used a software in windows pc called "Z3X samsung tool pro v29.2" a cracked version to be honest to unlock this phone permanently.
After that i flashed nougat via odin just in AP tab and still unlocked.
I did not flash modem or bootloader separately because this firmware comes in full package Bootloader+Modem+CSC+System all you have to do is use AP tab and upload firmware then flash it.but remember you have to do factory reset from stock recovery immediately after flashing successfully otherwise it can get bootloop
Even though i try Tmobile sim unlock app that comes pre installed but it didn't worked cuz i don't have Tmobile sim card.
I am not sure your phone situation to be honest but since its UNLOCKED already so give it a nougat shot.
I have flashed both the ATT and USC firmwares for the SM-N970U1 but still no wifi calling option. At this point I don't know if I've actually flashed the ATT firmware or not. Odin says Pass. Under the Service Provider SW ver. it makes mention of ATT/ATT/XAA but I'm not sure if that means the phone is on the ATT network or if that's firmware info. How do I tell what firmware I've actually flashed?
rmrl2008 said:
I have flashed both the ATT and USC firmwares for the SM-N970U1 but still no wifi calling option. At this point I don't know if I've actually flashed the ATT firmware or not. Odin says Pass. Under the Service Provider SW ver. it makes mention of ATT/ATT/XAA but I'm not sure if that means the phone is on the ATT network or if that's firmware info. How do I tell what firmware I've actually flashed?
Click to expand...
Click to collapse
There is already a thread on this and one of the members was nice enough to post exactly what firmware to flash.
I suggest looking for that thread its exactly what you need
That thread is for the Note 10 plus. I'm asking about the Note 10. That's where I got the idea to flash the USC version from but like I said, didn't work.
rmrl2008 said:
That thread is for the Note 10 plus. I'm asking about the Note 10. That's where I got the idea to flash the USC version from but like I said, didn't work.
Click to expand...
Click to collapse
Bummer, figured the thread would give you enough guidance to get it done on the smaller one.
Of course samsung has to make it difficult lol
I used the home_csc file instead of the csc. That should not have been an issue. I assume I'm still on the unlocked firmware but I have no clue. I don't see any AT&T bloatware or Logo. I downloaded the firmwares from the sammobile site. Even downloaded from the samfirm app just in case. So I flashed 3 times. No difference.
rmrl2008 said:
I used the home_csc file instead of the csc. That should not have been an issue. I assume I'm still on the unlocked firmware but I have no clue. I don't see any AT&T bloatware or Logo. I downloaded the firmwares from the sammobile site. Even downloaded from the samfirm app just in case. So I flashed 3 times. No difference.
Click to expand...
Click to collapse
What did you type into the SamFirm when you searched for firmware for your AT&T?
SM-N970U1 and ATT
rmrl2008 said:
SM-N970U1 and ATT
Click to expand...
Click to collapse
Maybe ATT doesn't put their firmware online as I tried searching and couldn't find on SamFirm. I am on T-Mobile and we have 2 different firmware versions.
If I type in SamFirm the following:
1) SM-N970U1 and region: TMB - I will get pretty much same unlocked firmware that I had on the phone, nothing will pretty much change after flashing this firmware.
2) SM-N970U and region: TMB - I will get T-Mobile firmware that is on their branded devices and all features.
Ask the OP in the below thread for latest ATT firmware file(userdata). If you recently flashed firmware, but the firmware in the thread is a bit older, you may not be able to flash until newer version is released.
https://forum.xda-developers.com/galaxy-note-10/how-to/n970u-n970u1-firmware-links-t3957705
So should I search for SM-N970U and ATT instead?
I did also do an ota update when I first got my phone so I have the August security update. Not sure if that's an issue since I have newer update?
rmrl2008 said:
So should I search for SM-N970U and ATT instead?
Click to expand...
Click to collapse
Normally that is correct, but it doesn't look like ATT is putting their firmware up on server as other carriers do.
Go to the link I provided of that thread. Click on the first link that says U firmware. Then look a bit down where is says: SGO - 1 - 9.0. After this link opens, you will see first 2 files: N970U_SGO_1.zip and USERDATA_ATT... You can try to download these files, extract to a folder and flash including the userdata file. If it fails, then you may need to wait until this person provides new firmware and you will need to download the firmware and that userdata_att
Yeah At&t is horrible about posting firmware. I usually just use USC firmware and once installed it will provision to At&t based on sim and you will get all At&t carrier options such as Volte..wificalling..advanced messaging.
Sent from my SM-N960U using Tapatalk
Thanks yeah that's what I'm about to do. My mistake was downloading from the U1 section instead of U. So confusing. Why even have any carrier firmwares under the U1 section?
Flashed the U / USC firmware and got AT&T firmware.
rmrl2008 said:
Flashed the U / USC firmware and got AT&T firmware.
Click to expand...
Click to collapse
Are you on the July security patch? I just did this process with the ATT firmware and it says up to date with July security patch. On the U1 unlocked firmware, I was on August already. I just wanted to be sure I didnt mess up something and it wont update properly.
I am on the August security update. That was part of the USC firmware. I didn't do an ota update after flashing so at this point I don't know if ota updates will work for me.
rmrl2008 said:
I am on the August security update. That was part of the USC firmware. I didn't do an ota update after flashing so at this point I don't know if ota updates will work for me.
Click to expand...
Click to collapse
Did you download your files from here https://androidfilehost.com/?w=files&flid=297974 ? Thats here I got mine and its for the SGO firmware on Note 10. Im thinking something went wrong now becasue mine wont update OTA and smart switch says im up to date when there is another firmware for ATT out - ASH4 version.
I got it from samfirm which is the ash4 version.
rmrl2008 said:
I got it from samfirm which is the ash4 version.
Click to expand...
Click to collapse
Thanks. What did you put for Model# and region? I input SM-N970U and USA(AWS) and nothing pops up. Using samfirm 0.4.0
Use USC for region
Hey, first post so sorry if I say anything off lol.
I have a G996U purchased from Verizon that I flashed to U1 firmware like 2 years ago when I first got it, and have had no issues since. I had a OTA software update the other night that seems to have triggered a carrier lock in my phone. The phone works fine for 5 minutes, then I get a popup telling me the phone is locked and to contact Verizon, despite the phone being from Verizon and running a Verizon sim. I went to them and unfortunately nothing they did could resolve it (new SIM, eSIM, etc), so they shipped me a new phone via insurance. I'm wondering though if I could save myself the hassle of transferring everything and do an in-place flash on the phone to see if that clears up the issue. I am already on the newest firmware (G996U1UEU5EWB1), so I can't upgrade, but I was wondering if I'd be able to flash the same firmware already on the phone while keeping all my data. Thanks.
Yes, just flash with home_csc.
Arealhooman said:
Yes, just flash with home_csc.
Click to expand...
Click to collapse
Thank you, just also want to ask bc I'm actually not sure which software to go for. I thought I had flashed XAA long ago, and I'm definitely on U1 firmware, but when I check "Service provider software version" in settings, it says VZW rather than XAA. Is it safe to download XAA firmware for a reflash or should I just do VZW to be safe?
You can flash any csc firmware.