Is it possible to flash the 9860 model with another firmware? - Samsung Galaxy Note 20 Ultra Questions & Answers

To get faster updates?

Possible to maybe put the N986U1 firmware on it, but I think it uses a different modem - only other firmware that would be compatible in the N986N firmware.
Has anyone tried? no. I don't want to brick my £1000 phone

Does anyone want to try brick their £1000 phone? no

Right now 9860 has the most updated rom. Just FYI

Related

SM-G930V purchased in Australia

Hi All,
I have a moderate experience in flashing firmwares and modding my samsung devices over the years.
I have recently purchased an S7 which is unfortunately a SM-G930V model, i thought it would have been the SM0G930F which would have made life much easier.
I want to know if it is possible to get the original Australian firmware or even generic stock firmware on this device?
My issue is with the network settings where i have manually put in APN settings my match my carrier and 4G coverage in australia.
If not am i able to just flash a different baseband to this device preferably Australian?
I have read that flashing a different model firmware will soft brick the device, i just want some insight before i start breaking things, also what are my options.
Much appreciated, thanks, Will
You have the snapdragon s7, you can't flash the exynos 930f firmware on it, you can only flash the american firmware. You might have luck with the 930u unbranded firmware just do some research on it.
Thanks mate,
I'm going to flash this firmware using ODIN, do you know if it will be successful?
https://forum.xda-developers.com/att-galaxy-s7/how-to/xda-community-love-g930u-t3415875
not sure how to check my bootloader version etc
No clue, goto the verizon subforum and see if anyone flashed the 930u firmware on their 930v.
Just tried to flash the firmware to my phone and recieved an error, the phone is now stuck at download mode with error:
sw rev check fail : [system] fused 3 > binary 4
this means the bootloader won't accept the firmware?
LOL, guess ill try another firmware.. Any ideas?

How do I replace G930S (SK Telecom) firmware for G930F?

Hi, guys! I bought a second-hand, unrooted Galaxy S7, model SM-G930S that shows the SK Telecom logo on boot, so it seems it is from South Korea. I want to replace its firmware for the Brazilian one (I suppose it's one of the G930F variants), but since it's my first Samsung phone, I don't know how to do it and if it's possible to do it, but I already know some of the necessary version stuff though:
SM-G930S
AP: G930SKSU1DQJ1
CP: G930SKSU1DQJ1
CSC: G930SSKC1DQJ1
Can someone tell me if it's possible to replace it and how can I do it? Will I need the ODIN tool people talks about a lot here? What else?
If this is your first Samsung device, then I do not recommend you start playing with firmware installs. Try to use it first as it is and then, if you do not like it, custom the firmware.
RossTeagan said:
If this is your first Samsung device, then I do not recommend you start playing with firmware installs. Try to use it first as it is and then, if you do not like it, custom the firmware.
Click to expand...
Click to collapse
I have been with it for two months already. I do not like the korean firmware, thanks.
And, no, I do not want a custom firmware/ROM, a just want to know if it is possible (and how) to flash the Brazilian or International Samsung firmware, like I said above.
giovanealex said:
I have been with it for two months already. I do not like the korean firmware, thanks.
And, no, I do not want a custom firmware/ROM, a just want to know if it is possible (and how) to flash the Brazilian or International Samsung firmware, like I said above.
Click to expand...
Click to collapse
You can't flash the wrong model firmware to your phone
Well u cant just simply flash one varient's firmware over the other though the hardware is almost same. But u can install stock based costum rom like super stock rom which is debloated and a simple stock based rom i am using it right now on my S7 edge. you will like it i am sure. otherwise no way.

AU KDDI SCV35 and USA Model

Hi,
As I purchase and AU KDDI SCV35 model, is there any difference between firmwares? Can I use USA unlocked firmware on AU model? My phone is running SC03J firmware (to unlock SIM) and it's working fine.
silveraero said:
Hi,
As I purchase and AU KDDI SCV35 model, is there any difference between firmwares? Can I use USA unlocked firmware on AU model? My phone is running SC03J firmware (to unlock SIM) and it's working fine.
Click to expand...
Click to collapse
No, you can't flash the US firmware.
murtaza02 said:
No, you can't flash the US firmware.
Click to expand...
Click to collapse
What if I only use the AP image without the others. Why SC03J firmware can be flashed on SCV35 but US unlocked U firmware can't?
silveraero said:
What if I only use the AP image without the others. Why SC03J firmware can be flashed on SCV35 but US unlocked U firmware can't?
Click to expand...
Click to collapse
Different partition sizes, and the Japanese variant has some minor hardware differences like the NFC chip I believe, and some LTE bands.
The 3 Japanese variants themselves are identical, and I'm sure their firmwares can be flashed on each one, just like you can do with the U/U1 variants, but you can't flash a firmware for one variant on an entirely different one.
You can TRY using the AP image only, but it'll most likely result in a soft-brick, possibly a hard brick, or the phone and/or Odin rejecting the image due to model number mismatch.
so whats the similar firmware for SCV35 sassing S8 + then?
murtaza02 said:
You can TRY using the AP image only, but it'll most likely result in a soft-brick, possibly a hard brick, or the phone and/or Odin rejecting the image due to model number mismatch.
Click to expand...
Click to collapse
Did anyone try this out? I have a SCV35 and I want to Americanize it.
Chipsnsit said:
Did anyone try this out? I have a SCV35 and I want to Americanize it.
Click to expand...
Click to collapse
Didn't work. Probably won't.
Too many differences between the variants.
Sent from my SM-G965F
Hi. I have same problem. Any solution to flash SCV35 with other firmware like g955f g955fd ?

*UPDATE* Bootloader v3

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.

Changing CSC code from a different model number

Hey Guys, I am in desperate need of help.
So I bought the note 20 ultra (model N986-U) from a seller in Texas (I live in Canada). The phones original csc code was ATT/ATT/ATT. I have a rogers sim card (csc code RWC). I noticed the phone is still stuck on One UI 2.5 because I am not connected to the ATT network.
So I tried changing the CSC using SamKey. I bought some credits, followed the steps and now for some reason my CSS is XAA/XAA/ATT.
I understand now that my phones model does not have a RWC firmware. Frija can't find the software for the SM-N986U running RWC but has no problem finding the software for the SM-N988W running RWC.
Is there any way for me to update my phone without bricking it? In an ideal world I would get OTA updates. Can I download the CSC_HOME file from the SM-N986W and flash it on my SM-N986U?
I'm really sorry for the noobish questions, I read so many threads and watched so many videos but I don't have the balls to experiment with such an expensive phone.
I know you can flash U1 firmware on a U device without any issues.
That's what I did to mine.
As for flashing W software on a U/U1 device, it's technically possible considering they are identical hardware, but I cannot say for sure what impacts it might have to the phone's performance.
You can always manually flash current U firmware.
rjohnstone said:
I know you can flash U1 firmware on a U device without any issues.
That's what I did to mine.
As for flashing W software on a U/U1 device, it's technically possible considering they are identical hardware, but I cannot say for sure what impacts it might have to the phone's performance.
You can always manually flash current U firmware.
Click to expand...
Click to collapse
Hey thanks for the answer,
I ended up flashing the W firmware on the phone and it worked flawlessly! Now the phone shows that it's a model N986W. OTA updates still don't work tho, even though the csc shows RWC
tripleaaa123 said:
Hey thanks for the answer,
I ended up flashing the W firmware on the phone and it worked flawlessly! Now the phone shows that it's a model N986W. OTA updates still don't work tho, even though the csc shows RWC
Click to expand...
Click to collapse
Glad it worked. Grab the latest firmware for RWC and then wait for the next update. (N986WVLU1DUB5)

Categories

Resources