is it possible to downgrade P to O? (and keep knox) - Samsung Galaxy S9 Questions & Answers

EDIT: it is possible, and worked just fine for me
- - - - - - - - - - - - - - - - -
Hi guys.
recently got a used s9, did all the updates (for security updates) and didnt even look, just kept updating and find myself on android P.
I've played around with it and found it less intuitive and pretty lacking in some regards. (and may possibly have some issues relating to the OS too; battery and phone)
software updates says:
Code:
current version: G960FXXXXU2CRLO / G960FOXXM2CRLO / G960FXXXU2CRLI
Security patch level: 1 January 2019
SM-G960F, Phone status: Official, baseband version G960FXXU2CRLI, Kernel version: 4.9.59-15076275, build verison: ppr1.180610.011.G960FXXU2CRLO
I'm wondering if it's possible to flash back to official Android O, while retaining untripped KNOX. (having KNOX in a usable/official status)
I've read online that it should be possible to do, but talk of using the "OEM unlocking" option has me weary.
I dont want to blindy follow a guide to find i've broken KNOX or have a brick.
some of you guys are pretty cluey. so i thought it be a good first place to ask.
cheers

Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
PoochyXXX

PoochyX said:
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
Click to expand...
Click to collapse
Hmm, thats what I'm afraid of.
The downgrade guide i mentioned was here:
https://techbeasts.com/downgrade-ga...xy_S9S9_Plus_to_Android_Oreo_from_Android_Pie
not sure how legit it is though.
I havent read anything on XDA on the forums here, hence my new topic.

Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine

*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
Ohhh
PoochyXXX

*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
AP_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship_meta.tar.md5
MD5: 4ECA2C5657506ADE7B9D3B1721B0F958
SHA1: 14063F2CF282E37C2C7D59D80FFF404C400D306D
BL_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship.tar.md5
MD5: 9529200BCE0C339B04152AC27DE34F5E
SHA1: 1821D68544490355042E7BF1589F2284FEF76324
CP_G960FXXU2BRJ1_CP10881699_CL14479316_QB19997556_REV01_user_low_ship.tar.md5
MD5: 8E07784192BCAF0454AB079ECBBD150D
SHA1: E7EFC1ED9E35C7B1F235792FAF46AFCAA945FF38
CSC_OMC_OXM_G960FOXM2BRJ3_CL14479316_QB20051937_REV01_user_low_ship.tar.md5
MD5: 17932E611CB0DF71C7B91BA84186843C
SHA1: 6BEE275DCC778124CB1EBF88EFA087538D9DCBE3
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.

tim455 said:
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
Click to expand...
Click to collapse
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October

*Detection* said:
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
Click to expand...
Click to collapse
Thanks for all the helpful information.
Downloading again now just to check hash comparison.
AP SWAEV: B:2 K:2 S:2 -- looks good.
I'll reply back in a few hours with my results.
Many thanks.

many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
To understand that you are downloading the BRJ6 firmware ?
Thx.

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
:good:

dinamo1975 said:
To understand that you are downloading the BRJ6 firmware ?
Thx.
Click to expand...
Click to collapse
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
*Detection* said:
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
Click to expand...
Click to collapse
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.

tim455 said:
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
Click to expand...
Click to collapse
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin

*Detection* said:
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
Click to expand...
Click to collapse
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)

tim455 said:
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
Click to expand...
Click to collapse
Not really, I am running DBT firmware with XEU CSC just because the DBT firmware updated first, once XEU releases the same update I`ll flash back, and so on

tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
What was the bootloader version of the Android 8 vs the version you had on Pie? Did you downgrade the bootloader as well?

can the same method be used to go down from 10 to 9? i have snapdragon 960w

Related

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!
If you're in Canada then just flash the Canadian firmware.
ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?
Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html
Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.
LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?
Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:
You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.
I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?
OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.
Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!

Help installing Verizon Firmware on Unlocked SM-N975U1

So I have a SM-N975U1 (unlocked) from samsung. I want to install the stock Verizon firmware (VZW) on the phone. I downloaded the following https://www.sammobile.com/samsung/g.../SM-N975U1/VZW/download/N975U1UEU1ASH4/286268
I installed the VZW firmware via Odin but oddly enough its still the XAA firmware. Not the stock VZW firmware I want. I want the full stock firmware. Verizon 4g icons, Bloat and all. Do I have to change the CSC on these newer models? Haven't done this since my note 8. I thought these stock firmwares were interchangeable? What did I do wrong?
Advice?
You have to download the verizon U version not the U1, I tried to do it and got stock on the activation screen
I see my mistake. Working flawlessly now!
cwwjr1681 said:
I see my mistake. Working flawlessly now!
Click to expand...
Click to collapse
Can you tell me how you did it? Which files?
crazychapin said:
Can you tell me how you did it? Which files?
Click to expand...
Click to collapse
The steps are the same as the S8, Note 8, S9, Note 9, S10.
Use Samfirm tool to download the latest firmware files. You need to use model SM-N975U and region code is VZW for Verizon.
Then use patched ODIN 3.13.1_3b to install.
All other instructions can found by searching the Note 9 forums.
Mr. Orange 645 said:
The steps are the same as the S8, Note 8, S9, Note 9, S10.
Use Samfirm tool to download the latest firmware files. You need to use model SM-N975U and region code is VZW for Verizon.
Then use patched ODIN 3.13.1_3b to install.
All other instructions can found by searching the Note 9 forums.
Click to expand...
Click to collapse
Did odin take a long time Saying file analysis Before start flashing? Mine stays like that for more than 10 mins and nothing happens
crazychapin said:
Did odin take a long time Saying file analysis Before start flashing? Mine stays like that for more than 10 mins and nothing happens
Click to expand...
Click to collapse
Ten minutes is a little long. It sometimes locks up. Reset and close out ODIN. Then set it back up. Do a factory reset from recovery mode and then immediately go to download mode and hit start.
crazychapin said:
Can you tell me how you did it? Which files?
Click to expand...
Click to collapse
I am not sure what a "Patched" oden others mentioned even is. I do not think I used that. I used SamFirm to download EVERYTHING I needed file wise. As for Odin. I got it from here https://odindownload.com/
I used these Settings in SamFirm
Model: SM-N975U (even though I am on the U1)
Region: VZW
Manual Box Checked
PDA: N975USQU1ASH4
CSC: N975UOYN1ASH4
Phone: N975USQU1ASH4
Make sure you use CSC file. Not Home CSC. Also install UserData. Then you should be all set :good:
cwwjr1681 said:
So I have a SM-N975U1 (unlocked) from samsung. I want to install the stock Verizon firmware (VZW) on the phone. I downloaded the following
I installed the VZW firmware via Odin but oddly enough its still the XAA firmware. Not the stock VZW firmware I want. I want the full stock firmware. Verizon 4g icons, Bloat and all. Do I have to change the CSC on these newer models? Haven't done this since my note 8. I thought these stock firmwares were interchangeable? What did I do wrong?
Advice?
Click to expand...
Click to collapse
Do you know does the unlocked version on Verizon work with sms over wifi? I'm not guessing it doesn't since my Pixel worked flawlessly at my desk in the basement at work. I assume I would need to flash the Verizon firmware as you have?
So I'm trying to decide which version on the 10+ to buy. Will I lose any features if I flashed a Verizon rom onto an unlocked 10+ ? Are there any benefits to having the unlocked vs carrier device? Thanks
cwwjr1681 said:
I am not sure what a "Patched" oden others mentioned even is. I do not think I used that. I used SamFirm to download EVERYTHING I needed file wise. As for Odin. I got it from here https://odindownload.com/
I used these Settings in SamFirm
Model: SM-N975U (even though I am on the U1)
Region: VZW
Manual Box Checked
PDA: N975USQU1ASH4
CSC: N975UOYN1ASH4
Phone: N975USQU1ASH4
Make sure you use CSC file. Not Home CSC. Also install UserData. Then you should be all set :good:
Click to expand...
Click to collapse
https://lmgtfy.com/?q=patched+odin
And no, patched ODIN is not necessary when flashing carrier firmware, although it is necessary when flashing back to the U1 Firmware. I just use it for everything as it seems to cause less issues.
Hi, I have completed the following steps numerous times. I first wiped data and cache then installing the u1 firmware. My note 10 plus sm-nn975u was originally T-Mobile. I had placed a Spectrum sim inside before the flash. Once on U1 spectrum Charter APN settings show up and all works fine. However I wanted to flash to the CHA OR Charter Spectrum firmware. I wiped data and cache and flash. My phone then comes up with T-mobile start screen and bloat. Are the Charter files on Sam fakes or am I missing something. I am totally blind, so when the phone boots after flash it doesn't say its rebooting to apply carrier settings, it just boots on up to setup screen where I turn on voice for the blind and begin setting up. I even tried to reboot after flash with no sim and it says please insert sim but no reboot or prompt to reboot after sim installation.
I am using odin 3.13.1_3B. Please help.
Mr. Orange 645 said:
https://lmgtfy.com/?q=patched+odin
And no, patched ODIN is not necessary when flashing carrier firmware, although it is necessary when flashing back to the U1 Firmware. I just use it for everything as it seems to cause less issues.
Click to expand...
Click to collapse
Verizon s10+ 5g to unlocked s10+
I have the Verizon n976v note 10+ 5g. I’m looking to put the unlocked firmware on it. I get an error (failed) with modified Odin. Is there an extra step?
ebkbk24 said:
I have the Verizon n976v note 10+ 5g. I’m looking to put the unlocked firmware on it. I get an error (failed) with modified Odin. Is there an extra step?
Click to expand...
Click to collapse
i have the same device.. the N976V is verizon note 10 plus 5g.. its not the same as the U1 variants.. i assume the fail is a secure check fail? thats bcuz the U1 is signed with different keys..
so far all the 5g devices have been carrier specific models and firmware is not interchangeable between them
There is no SM-N975U in the list or when i type it in?
Mr. Orange 645 said:
The steps are the same as the S8, Note 8, S9, Note 9, S10.
Use Samfirm tool to download the latest firmware files. You need to use model SM-N975U and region code is VZW for Verizon.
Then use patched ODIN 3.13.1_3b to install.
All other instructions can found by searching the Note 9 forums.
Click to expand...
Click to collapse
Can you post a link. there is no 975u in the list
bimbo77777 said:
Can you post a link. there is no 975u in the list
Click to expand...
Click to collapse
Link to what?
Pie
Mr. Orange 645 said:
Link to what?
Click to expand...
Click to collapse
To the android pie download for SM-975U. It's not on samfirm Only SM-975U1 is on there
bimbo77777 said:
To the android pie download for SM-975U. It's not on samfirm Only SM-975U1 is on there
Click to expand...
Click to collapse
There's no links to Samfirm. The SamFirm tool is a Windows application you download and install to download full firmware files to your computer.
N975U is 100% available on the SamFirm tool.
Mr. Orange 645 said:
There's no links to Samfirm. The SamFirm tool is a Windows application you download and install to download full firmware files to your computer.
N975U is 100% available on the SamFirm tool.
Click to expand...
Click to collapse
Not available on it. This won't let me upload screenshots but it only has 975U1 if you manually type in the list ends at n960s
bimbo77777 said:
Not available on it. This won't let me upload screenshots but it only has 975U1 if you manually type in the list ends at n960s
Click to expand...
Click to collapse
Then you aren't using SamFirm. There's no list that pops up.
Go to www.google.com
Go to the search bar
Type in "SamFirm tool"
Until you do that and research what I'm talking about, I can't help you.

Can an International (F) firmware be flashed into a Korean (N) Device?

I'm tired of these ****ty korean bloatware.
I've been trying to flash F firmware on my unrooted N device for a week now with no success, it's always some kind of PIT/Partition error, ticked/unticked Re-partition, ticked/unticked NAND erase, Used/Unused PIT file, patched Odin, unpatched Odin, nothing works, always "Fail Secure (PIT)" error.
someone told me that the F CSC had a different partition than the N CSC, so how do I re-partition? why does it keep failing?
Can an International (F) firmware be flashed into a Korean (N) Device?
why isn't there a clear answer to this question anywhere?
yes i did. actually i took mine to a local mall mobile service shop. the tech guy installed twrp and installed a custom rom- something named lamlazy azmobile bla bla.. . it was all good. the ONLY thing missing was- OTA update. i did lot of youtube and google on this- in some i found the OTA still available in that particular rom while in others that OTA option is missing. that's why i reverted back to the stock KT-variant firmware.
right now i am on the hunt of how to just root and 'hack' the original firmware- just so i can get rid of KT apps which are in control of my only, current gripe- there is no Preferred Network selection option like you see on a global firmware. I only see 3G/LTE Auto and 3G Only options. I need unlocked 2G only, 3g only, 2g/3g auto, 2g/3g/lte auto option.
so, to answer your question- yes it is absolutely possible to convert any korea variant S9+ into global variant. at least with custom rom- not yet sure if it is possible with stock global rom/firmware.
Coomer91 said:
I'm tired of these ****ty korean bloatware.
I've been trying to flash F firmware on my unrooted N device for a week now with no success, it's always some kind of PIT/Partition error, ticked/unticked Re-partition, ticked/unticked NAND erase, Used/Unused PIT file, patched Odin, unpatched Odin, nothing works, always "Fail Secure (PIT)" error.
someone told me that the F CSC had a different partition than the N CSC, so how do I re-partition? why does it keep failing?
Can an International (F) firmware be flashed into a Korean (N) Device?
why isn't there a clear answer to this question anywhere?
Click to expand...
Click to collapse
rizwan312 said:
yes i did. actually i took mine to a local mall mobile service shop. the tech guy installed twrp and installed a custom rom- something named lamlazy azmobile bla bla.. . it was all good. the ONLY thing missing was- OTA update. i did lot of youtube and google on this- in some i found the OTA still available in that particular rom while in others that OTA option is missing. that's why i reverted back to the stock KT-variant firmware.
right now i am on the hunt of how to just root and 'hack' the original firmware- just so i can get rid of KT apps which are in control of my only, current gripe- there is no Preferred Network selection option like you see on a global firmware. I only see 3G/LTE Auto and 3G Only options. I need unlocked 2G only, 3g only, 2g/3g auto, 2g/3g/lte auto option.
so, to answer your question- yes it is absolutely possible to convert any korea variant S9+ into global variant. at least with custom rom- not yet sure if it is possible with stock global rom/firmware.
Click to expand...
Click to collapse
yes you can do it, and no you dont need to bring it to a shop and pay someone. Just get patched Odin and the F variant firmware you want to flash.
rizwan312 said:
so, to answer your question- yes it is absolutely possible to convert any korea variant S9+ into global variant. at least with custom rom- not yet sure if it is possible with stock global rom/firmware.
Click to expand...
Click to collapse
already ahead of you, I installed Soldier rom with a F CSC but there some issues that you start to notice after a while because the the partition for the N CSC isn't the same as the F CSC, so the F CSC doesn't install completely.
see here: https://forum.xda-developers.com/showpost.php?p=80760253&postcount=4895
youdoofus said:
yes you can do it, and no you don't need to bring it to a shop and pay someone. Just get patched Odin and the F variant firmware you want to flash.
Click to expand...
Click to collapse
like I stated in my op, patched odin didn't work for me no matter what I did, and I haven't seen anyone so far that confirms that it actually works in flashing an F firmware on an N device. so did you actually flash a F firmware on an N device yourself?
Coomer91 said:
already ahead of you, I installed Soldier rom with a F CSC but there some issues that you start to notice after a while because the the partition for the N CSC isn't the same as the F CSC, so the F CSC doesn't install completely.
see here: https://forum.xda-developers.com/showpost.php?p=80760253&postcount=4895
like I stated in my op, patched odin didn't work for me no matter what I did, and I haven't seen anyone so far that confirms that it actually works in flashing an F firmware on an N device. so did you actually flash a F firmware on an N device yourself?
Click to expand...
Click to collapse
i have not, but have seen reports of others doing so on other iterations of galaxy phones. what errors did you get in odin?
youdoofus said:
i have not, but have seen reports of others doing so on other iterations of galaxy phones. what errors did you get in odin?
Click to expand...
Click to collapse
always Secure Check Fail (PIT).
Coomer91 said:
always Secure Check Fail (PIT).
Click to expand...
Click to collapse
unpack both the korean firmware's CSC and the F CSC that youre trying to use, remove the pit from the F firmware, replace it with the Korean PIT, repack the file and flash it.
you can also try an older version of Odin, as that has caused so many headaches for folks in the past. Odin version mismatches can be a mother trucker
oh yes, i had the same issue when i tried patched odin. i didn't know much about PIT. so, after fiddling around for some time, i went back to stock KT firmware. by the way, have you seen this?
https://www.youtube.com/watch?v=ycpnsWJdURQ
According to this, we need to root our phone, then remove CSC folder and restart. then copy-paste couple of files in the system folder. He did it on his Note 4 though. But my problem with network selection limitations and bloatwares are exactly the same as he was showing on his KT variant Note 4.
anyway, i will surely try extracting the PIT file fron N firmware and replace that in F firmware. any tips/guide how can i do that please?
Youdoofus said:
unpack both the korean firmware's CSC and the F CSC that youre trying to use, remove the pit from the F firmware, replace it with the Korean PIT, repack the file and flash it.
you can also try an older version of Odin, as that has caused so many headaches for folks in the past. Odin version mismatches can be a mother trucker
Click to expand...
Click to collapse
What is the pit ?
And has anyone successfully managed to flash a F firmware onto a Korean phone ?

Stock Firmware for Samsung Note 10+

I'm using Samsung Note 10+
Model number SCV45, a Japanese variant with a name tag "au" & has the Snapdragon processor, not Exynos.
I want to flash the stock Firmware again.
I have visited SamMobile website to download the firmware of Note 10+. But there are lots of model number available like -
SM-N975F
SM-N975U
SM-N975U1
SM-N975W
SM-N9760
SM-N976B
SM-N976N
SM-N976Q.... so on.
But i didn't found "SCV45" model number.
As far as I know, SM-N975U, SM-N975U1 is for USA region with Snapdragon variant & SM-N975W is for canda region, also with Snapdragon.
If I flash any of the firmware of USA or Canada variant on my Japanese variant device through Odin, is there will be a problem. I have no idea about that as I'm a new user of Samsung. I have always used OnePlus. So I don't have enough knowledge about Samsung firmware.
Please let me know about the fact.
hello
you cand find your firwares here :
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
yakapa40 said:
hello
you cand find your firwares here :
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download
Samsung Galaxy Note10+ Firmware Download SCV45 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Click to expand...
Click to collapse
Thanks a lot brother.
But actually, I want to try out US region firmware on my device. So I'm asking, is there any problem if I flashed
SM-N975U or SM-N975U1 firmware? What will happen if I do so?
I need a clear idea about that, because I don't have enough knowledge about Samsung firmware & also I don't want my device turn into a bricked device.
Hope, I will get a clear idea from this XDA forum about that.
maybe your device is rooted or there is a mixed firmware so coming back to original firmware is not without risk
can you post :
- device version:
on dialer : *#1234# or *#12580*369#
Here is the Device Version that you want
Actually today I tried to add a edu mail account on google and it's showing that "Can't create a working profile, here is what error message I got.
I have checked, I don't have root access. And I also running stock Firmware as I got OTA update from Samsung for One UI. So I don't know what is the actual problem. That's why I want to shift from current firmware to USA region firmware.
But I am in a doubt as I don't have enough knowledge about that.
you can't flash a N970U or U1 full firmware
maybe only the CSC part if it work but at your own risk
I believe you can try to flash some completely other version, but no one can be sure if it will work.
I would suggest to have a spare Japan OFW to reflash if anything goes wrong.
Your latest FW according to samfirm should be -> SCV45 -> Region KDI
Version: SCV45KDU1DVC3/SCV45QDI1DVC3/SCV45KDU1DVC3/SCV45KDU1DVC3
FIlename: SCV45_3_20220314133230_x92etays47_fac.zip.enc4
Size: 6010MB
yakapa40 said:
you can't flash a N970U or U1 full firmware
maybe only the CSC part if it work but at your own risk
Click to expand...
Click to collapse
Can you tell me about the CSC part? Why you recommend this one only? What about AP, BL & rest?
Ereniemis said:
I believe you can try to flash some completely other version, but no one can be sure if it will work.
I would suggest to have a spare Japan OFW to reflash if anything goes wrong.
Your latest FW according to samfirm should be -> SCV45 -> Region KDI
Version: SCV45KDU1DVC3/SCV45QDI1DVC3/SCV45KDU1DVC3/SCV45KDU1DVC3
FIlename: SCV45_3_20220314133230_x92etays47_fac.zip.enc4
Size: 6010MB
Click to expand...
Click to collapse
I know it's hard to find someone who has tried out what I asked for. I don't know whether it will work or not. But I just want to make sure that after flashing a different region firmware, it should not become a hard brick device.
If something goes wrong, at least I flash the SCV45, Japan variant firmware again & everything turns to a normal state as it is running now.
So should I proceed with SM-N975U, USA variant firmware? Will it gonna make my device hard brick? Can I come back to normal state by flashing SCV45 KDI firmware which is mentioned by you?
I need some suggestions. Nobody is answering
SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
I would suggest you not to flash bootloader if possible. Everything else can be dealt with if bricked.
SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
I would personally look for the model, which is the most similar to the japan one and just... pray while flashing
SabbirNaim said:
I need some suggestions. Nobody is answering
Click to expand...
Click to collapse
and also, dont forget to flash the "CSC" file, not the "home_CSC" to change the region. (the home_CSC doesn't change CSC and leaves your apps and other stuff intact. On the other hand, the CSC file wipes everything and changes the region.)
Ereniemis said:
and also, dont forget to flash the "CSC" file, not the "home_CSC" to change the region. (the home_CSC doesn't change CSC and leaves your apps and other stuff intact. On the other hand, the CSC file wipes everything and changes the region.)
Click to expand...
Click to collapse
I am too much grateful to brother for your suggestions what I actually expected for.
I will follow all your instructions.
I will flash the "CSC" file only. Thanks for let me clear about this thing.
I have just a little confusion about what you have told above.
You suggest me not to flash bootloader. Can you please give me a clear idea how can I skip it or at what step, I should not flash the bootloader? I have just this confusion.
SabbirNaim said:
I am too much grateful to brother for your suggestions what I actually expected for.
I will follow all your instructions.
I will flash the "CSC" file only. Thanks for let me clear about this thing.
I have just a little confusion about what you have told above.
You suggest me not to flash bootloader. Can you please give me a clear idea how can I skip it or at what step, I should not flash the bootloader? I have just this confusion.
Click to expand...
Click to collapse
Well... You have to flash through ODIN.
So. In the ODIN you have several options on what to do (what to flash). When you download the FIRMWARE you will have to decompress it. there will be different files -> BL (Bootloader - BL), PDA (the firmware - AP), PHONE (modem and stuff - CP) and CSC (vendor or region specific info).
Firstly I would try to flash only AP + CP + CSC. Which means Firmware + Phone + CSC. Be sure to flash the same version of Android as you have. In that case it should... maybe... probably work the same. If you have bootloader from Android 11 and you try to flash Android 11 from another version, it should work theoretically....
But if you try to flash eg. Android 12 over Android 11 it won't work because the Android 12 uses different bootloader and you need to update it.
It would be most desired to flash the bootloader also. But my suggestion for you is to try flash different version without the bootloader (if it can be done). Because if you don't screw up the bootloader, you will be always able to boot to bootloader a flash back the original firmware.
I don't have the knowledge to tell you, that if you flash USA version of bootloader to the JAPAN version of bootloader that it will work. It probably should, but I believe, noone can answer that and it's just that you will have to try it.
I believe that the ODIN will tell you that you are trying to flash firmware from completely different device and if you are sure to do that.
So again:
1) download firmware from different location with the same android version
2) decompress the firmware
3) in the ODIN -> add only AP, CP, CSC (don't add the bootloader)
4) try to flash!
If it doesn't work, you can try even to flash the bootloader, but I'm a bit worried about that one....
I am highly grateful to you as you have explained the whole thing so clearly. Now I understand all the steps that I need to do. Thank you so much for clearing up the matter in so much detail. Now I can proceed.
I will try as per your suggestion. Let's see what happened.
Thanks again.
bootloader is in AP !
yakapa40 said:
bootloader is in AP !
View attachment 5643845
Click to expand...
Click to collapse
Then what should I do?
before flashing a part of firmware , i think it's better to know more about root
i'm not familiar with root and my lastest rooted device is a galaxy S6
why do you want to change the firmware ?
yakapa40 said:
before flashing a part of firmware , i think it's better to know more about root
i'm not familiar with root and my lastest rooted device is a galaxy S6
why do you want to change the firmware ?
Click to expand...
Click to collapse
I have checked and I don't have any root access. I have told you why I actually want to change the firmware in some previous reply.
Here I am mentioning the whole problem again for your better knowledge.
Actually yesterday, I tried to add an edu mail account on google and it's showing that "Can't create a working profile", here is what error message I got.
I am running on stock official Firmware, I confirmed that as I got OTA update from Samsung for One UI. So I'm not using any custom OS.
But I don't know why it's showing that I am using a custom OS . That's why I want to shift from current firmware to USA region firmware to check whether the Japanese region firmware has issue or not.
But I am in a doubt as I don't have enough knowledge about switching from one region to another region firmware in Samsung devices.
I hope you can understand, though my English is not great

Question How to update to Android 13 today?

Hi, I have some spare time now and need to reinstall my Fold3 anyway.
So I would like to test Android 13 and am looking for the safest way, of course without triggering knox.
Can I download and flash via Odin Indian firmware from here: https://samfw.com/firmware/SM-F926B/bit/all/av/T(Android 13) ?
Or should I register as a beta tester?
My csc code is OXM via *#1234# and EUX via "samsung phone info" app.
Which way to go, please? Or point me please in the right direction.
Thank you.
Good question, im also interested in going odin way, so i could also need a secured way
I downloaded the INU rom and to keep data flash HOME_CSC, it keeps the csc that you have now
So did I. I flashed INU on my EUY F926B. When you flash Home-CSC you will keep your data.
Is that absolutely secure that ill keep my apps and setting? Got 2 Authenticator Apps for work on it
Bolvaron said:
Is that absolutely secure that ill keep my apps and setting? Got 2 Authenticator Apps for work on it
Click to expand...
Click to collapse
Been there, done that, if you have critical work apps, then wait for the official update if you are not 100% sure what you are doing.
ODIN says succeeded, so im crossing fingers. Have worked with it on an older Galaxy before, but never with Firmware from another country. In CSC ive taken the HOME_CSC_OXM_F926BOXM2DVK3_MQB58858275_REV00_user_low_ship_MULTI_CERT.tar.md5.
That should be right
Talderon said:
Been there, done that, if you have critical work apps, then wait for the official update if you are not 100% sure what you are doing.
Click to expand...
Click to collapse
I can report success, Authenticators are working, CSC is like before
Problem solved, I received official update today
Anyone in the US using VZW get the update?

Categories

Resources