Hi there! I was trying to change region on my Active2 from XSG to SER, but after installing CSC for my R820 I ended up on endless loading.. So now I am looking for stock firmware for XSG (UAE). Where I can find it or buy it? Thanks!
Are you able to unpack/extract files with Tool 7Zip?
Because XSG is inside OXA package... means in all leaked SM-R820 FirmwareS.
IMHO something else wrong...
Maybe start from scratch...
What you did and which Files you used?
Filenames usefull to understand what you did...
Best Regards
Hi adfree, thanks for the answer!
Yes, I can unpack files with 7Zip.
First of all, I updated the firmware to 5.5.0.2 and got version R820XXU1DUA7.
Made full reset on the watches.
After that, I downloaded the necessary files to change the region to my PC.
I have booted the watch into wireless download mode.
I connected to the watch via Wi-Fi from PC.
In the AP, I selected the COMBINATION-FT40_R820XXU1ASI2.tar file and flashed it.
After that, I made a reset in netOdin, and added the file CSC_OXA_R820OXA1ASHF_usr.tar to CSC and flashed it.
After that, I tried to boot into recovery mode, but something went wrong: there was an endless loading with text "SAMSUNG Galaxy Watch Active2".
I realized that I had made a mistake because of Tizen version. I again booted the watch into wireless download mode and through netOdinflashed all 3 files from smR820XXU1ASHF (AP, BL, CSC). (downgraded to 4.0.0.6)
After that, I again flashed the AP combinative firmware COMBINATION-FT40_R820XXU1ASI2.tar, then again the CSC CSC_OXA_R820OXA1ASHF_usr.tar.
And again I got an endless download.
After that I tried many different firmwares, but none of them resulted in booting in recovery mode after combinative firmware.
After all I installed R820XXU1CTI4 AP_R820XXU1CTI4_usr.tar + BL_R820XXU1CTI4_usr.tar + CSC_OUA_R820OUA1CTI4_usr.tar. Now I can't even update the Tizen version, because after the update, when watches is loaded, it gives me a notification "Couldn't update software. Try again later"
I will be insanely grateful to you if you help me
And one more question. When I start Spay, it says "Your watch was modified and can't access Samsung Pay". Does it means I will be never able to access spay?
Maybe, if I will flash stock firmware for XSG R820XXU1DUA7 all of my problems will gone? I think update is not installing because watches trying to install R820XXU1DUA3 update, but for XSG region I need R820XXU1DUA7? Thats why I'm searching for R820XXU1DUA7
I think u need to downgrade to tizen 4 before u can change region
ah_cleo said:
I think u need to downgrade to tizen 4 before u can change region
Click to expand...
Click to collapse
Hi! Thanks for the answer!
As I said before, when I realized my fail with Tizen version, I have installed smR820XXU1ASHF it is 4.0.0.6 and after installed combinated firmware COMBINATION-FT40_R820XXU1ASI2.tar and again CSC CSC_OXA_R820OXA1ASHF_usr.tar. And still doesnt work, endless loading with text "SAMSUNG Galaxy Watch Active2"
Too old files.
Newer Files floating arond...
I have less time now... Will later search...
Best Regards
adfree said:
Too old files.
Newer Files floating arond...
I have less time now... Will later search...
Best Regards
Click to expand...
Click to collapse
Thanks adfree for idea! I've searched for new files and flashed 5.5 combinated firmware and all works fine! Thread can be closed. Thank you a lot!
Related
Hi,
Is it possible to change the landcode of t s4 mini? I live in the netherlands, but reveived a phone from Poland.
I would like to know if it's possible to change it to the netherlands and receive the regular updates from samsung, the kitkat update didn't come out in Poland yet.
thanks
Anybody?
SkyDrive. said:
Anybody?
Click to expand...
Click to collapse
U can`t change landcode without root + Samsung Galaxy S / S2 / S3 CSC or with Phone INFO ★Samsung★
But your current rom MUST have Multi-CSC and contain both ( 99% it won`t )
Easiest way is to download rom from sammobile for Netherlands (Vodafone) and flash it with Odin
SilviuMik said:
U can`t change landcode without root + Samsung Galaxy S / S2 / S3 CSC[/URL] or with Phone INFO ★Samsung★[/URL]
But your current rom MUST have Multi-CSC and contain both ( 99% it won`t )
Easiest way is to download rom from sammobile for Netherlands (Vodafone)[/URL] and flash it with Odin
Click to expand...
Click to collapse
Oh well, thank you for your reply.
I am going to flash it and see what happends!
SkyDrive. said:
Oh well, thank you for your reply.
I am going to flash it and see what happends!
Click to expand...
Click to collapse
While flashing the firmware you gave me an error occured!
Now my device seems to be bricked as Kies doesn't recognize the device for recovery, any idea how to solve this problem?
SkyDrive. said:
While flashing the firmware you gave me an error occured!
Now my device seems to be bricked as Kies doesn't recognize the device for recovery, any idea how to solve this problem?
Click to expand...
Click to collapse
http://www.s4miniarchive.com/2014/07/solution-what-to-do-when-odin-fails-at-hidden.img.ext4.html
Btw take care it will void your Knox warranty to 0x1
Or try to download another version of firmware ( KitKat ) and flash it with Odin 3.10
SilviuMik said:
U can`t change landcode without root + Samsung Galaxy S / S2 / S3 CSC or with Phone INFO ★Samsung★
But your current rom MUST have Multi-CSC and contain both ( 99% it won`t )
Easiest way is to download rom from sammobile for Netherlands (Vodafone) and flash it with Odin
Click to expand...
Click to collapse
As far as I know changing the CSC will factory-reset the phone (Phone INFO ''CSC Changer' tells that as well).
I saw that Titanium Backup is backing up CSC application and data. Does anybody know what happens if one restores the CSC data with TB? Does this work without factory-reset?
Reason for asking is that I had a strange issue yesterday: flashing with ODIN failed 'Get PIT for mapping...'. The phone was starting up with the message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again'.
I removed the battery and then I could flash the firmware without problems. Later after setting up everything I noticed that my CSC changed from 'DBT' to 'KOR'
To be honest, I never had to change the csc. The european firmwares have multiple CSCs included are the right one should be chosen automatically at first boot up after flashing. And I really dont understand what CSCs really are. So I dont care about them. Flashing the belgium fw worked as well as the german one. Couldn't fnd any difference (accept for the Hello app^^). European people are bothering themselves way to much about this topic...
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
Hello,
I have changed the CSC of my Active 2 44mm (not LTE). Everything has been correct, except for two things:
1 - I still get the green letters when I start the clock, on the Samsung Galaxy Watch Active 2 presentation
2 - Now I try to upgrade by OTA (through the phone's app) and when it reboots, it says that the firmware could not be installed.
How do I fix both? Thanks
Put everything back the way it was (Fully Restore to Default) and try to update software.
Are you able to identify Model Name?
I hate this mm nons.nse.
Example:
SM-R820?
I am too lazy to google how long is yours... Firmware.
Colors in Booting is Engineer Bootloader sboot.bin (from Combination firmware) is still on device... this brings FOTA over the air to fail...
Because wrong Bootloader on device... from "chain of trust" selfcheck...
Best Regards
hi, I have a similar issue with the sm-r825f, after I changed csc to Germany... I got a watch from UK (BTU) unfortunately and wasn't able to set up esim. Now after I changed csc and flashed R825FXXU1ASJ3, esim works fine but I am stuck on ONE UI 1.5 and scanning for updates keeps failing.
What's the easiest way to make OTA work again?
Can I simply reflash a certain firmware? Can you recommend or link the files?
Sry if any information is missing!
Thank you all for your help!
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
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?