General Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices

[JazonX]

Any new trick / Workaround to pair a Gear Watch 3 to a Rooted S22 ?

 

[gav83collins]

It would be great if you could point out the typos so that I can fix it. I've checked the text for typos but either I'm missing them or thinking my way of spelling is the correct way

yeah my bad, i just re read it and couldn't find them ??? so i copied and pasted into google docs to double check, that didn't find them either, i must be going mad lol

 

[darsh79n1]

hello guys i need help i just got the S22 ultra UAE version ... i tried to flash Egypt rom but it didn't work via odin any clue?

 

[STZ-Mech]

Maybe someone can help me here.
I have an sm-g991b/DS and want to unlock all the LTE bands ( 5g if possible). It seems unless I am wrong, that the LTE bands are restricted to the specific CSC bands, even though the phone supports all the ones here in Canada.

If anyone knows if there is a world wide CSC, or CSC that has all of them unlocked, that would be great. Even a way to search the CSC for the best match band wise.

 

[JazonX]

hello guys i need help i just got the S22 ultra UAE version ... i tried to flash Egypt rom but it didn't work via odin any clue?

UAE Version and Egypt version has the same firmware. It wont change the CSC without a SIM Card from Egypt.

 

[darsh79n1]

UAE Version and Egypt version has the same firmware. It wont change the CSC without a SIM Card from Egypt.

I got EGY sim but still give me error... I found that UAE version have TRA s/n... Its not allowing me to make full rom flash

 

[Adam1906KSC]

Hello
What is exactly csc code for uk unbranded galaxy S22 BTE or EUX?

 

[JazonX]

What's the working method to Mock location without getting detected now ?

 

[Macusercom]

Hello
What is exactly csc code for uk unbranded galaxy S22 BTE or EUX?

Depends on the device. Afaik on S22 devices the EU CSC code always is EUX. For S21 and lower it probably is BTE contained within the OXM multi-CSC firmware. The CSC stuff got a lot easier on the S22 series since it now uses one firmware/CSC instead of splitting the release into different regions

 

[mhenawy]

Maybe someone can help me here.
I have an sm-g991b/DS and want to unlock all the LTE bands ( 5g if possible). It seems unless I am wrong, that the LTE bands are restricted to the specific CSC bands, even though the phone supports all the ones here in Canada.

If anyone knows if there is a world wide CSC, or CSC that has all of them unlocked, that would be great. Even a way to search the CSC for the best match band wise.

did you manage to fix that ? i need to enable Channel 149 for the WIFI and i have tried many different firmwares and my service provider firmware remains the same - this channel is blocked in my country and i need it for wireless android auto in my car

 

[Anubhav02t]

Some one please tell me if i install
this Indian firmware

https://samfrew.com/download/Galaxy__S22__Ultra__/qn1s/INS/S908EXXU2AVF1/S908EOXM2AVF1/

on my s22 ultra sm-s9080 S9080ZHU2AVF1 csc is BRI
Will it work ? i need to enable native call recording anyhow

 

[gwm121]

odin latest has a splash screen that says ...please be sure to delete your google account/samsunng account before downloading the binary
PLEASE what does this mean
is it true
is this for running odin on w10
or using odin to tansfer twrp to fone
PLEASE.. do i use with odin for twrp
.tar
.tar.md5
iimg.tar
other
problem i have is after loading pixel 9 rom onto samy s4 19505 twrp doesnt come up anymore, and so far all versions of twrp ive loaded show success but fone boots to rom not twrp recovery.(i take batt out after success and attemt next startwith vol up pwr home)

 

[Kibbitzer]

I have a question. If my phone (S21 Exynos 991B) came with an Android 12 OWO/ZTO multi-CSC ROM, which only includes south american CSCs, and is currently in the ZTO CSC (Brazilian unlocked), could I flash an OXM/DBT (which includes ZTO) Android 13 ROM over it using only home_CSC, or do I have to reflash everything (regular CSC + PIT and everything, wiping all data)?

 

[GalaxyA325G]

I wanted to summarise a lot of information I found out during researching

I very much thank @Macusercom for summarizing this information which, I too, was confused about as I (oh, so very innocently) asked for advice for flashing my locked-up Samsung A32-5G - where this information MacUserCom kindly provides is NOT in the canonical threads on the subject!

as Samsung devices are quite different from OnePlus or Google devices in that they don't support fastboot but only ODIN.

Speaking of fastboot mode, it would be nice if someone (MacUserCom perhaps?) can summarize the following (confusing to me) modes:

• Android recovery mode
• Debug mode
• Download mode
• Fastboot mode
• Odin mode
• Recovery mode

Having never myself used most of these modes, nonetheless I made a sorry attempt at describing them for the Galaxy A32-5G over here but I don't really know what I'm doing (which I openly admit).

There are a lot of ODIN versions out there.

While I too found lots of Odin versions out there, in my searches for how to load firmware on a Samsung, I also found many confusing references to Frija and to Bitfrost which seem to obtain the correct bootloader, application processor, core processor, consumer software customization (with or without the partition information table) and userdata md5 files.

What might be nice for the confuserati like I am would be a summary which explains how these often listed tools fundamentally differ:

• Odin (Norse king) Seems to be the "burner" program
• Frija (wife of Odin) Seems to obtain the firmware files
• BitFrost Also seems to obtain the firmware files

And maybe even a quick explanation of how these Android APKs play a role in the process.

• CheckFirm Seems to tell you your current & updated firmware
• Magisk I'm not sure what this does for Samsung devices
• TWRP I'm not sure what this does for Samsung devices

Specifically which of the above apply to Samsung devices, and more importantly to save time, which do not apply to Samsung phones.

If you unlock your bootloader, Knox will be tripped.

I don't know what Knox does so it might be useful to ask for a summary of what Knox does, and what it won't do after being "tripped" (although that seems to be covered in terms of using electronic payment systems).

But does someone have a summary of what Knox is and whether we can remove it from our Samsung phones or not?

• Knox (as in the fort?)

So if you flash a signed Samsung firmware, it shouldn't trip KNOX. If you flash an unsigned firmware, it will trip it. But as a general rule of advice: signed firmware are flashable in ODIN with a locked bootloader.

Given there are so very many ways to download firmware...

• https://fota-cloud-dn.ospserver.net/firmware/DBT/SM-G998B/version.xml
• https://doc.samsungmobile.com/sm-g998b/dbt/doc.html
• https://www.sammobile.com/firmwares/
• https://updato.com/firmware-archive-select-model/
• https://github.com/zacharee/SamloaderKotlin/releases
• https://samfrew.com/
• https://samfw.com/
• https://github.com/nlscc/samloader

How can we tell if the results we download are signed or unsigned?
And how can a noob know which of the sites above are reputable?

If you unlock the bootloader, you are at risk of tripping KNOX and you are responsible for that happening either way. No matter what I or someone else says on XDA or any other website. So never unlock the bootloader if you can't accept tripping KNOX.

I guess luckily for me, apparently the Samsung Galaxy A32-5G with an "8" in the bootloader version 5th-digit-from-the-left, can't be unlocked (and can't be rooted, apparently).

But I don't even know what it means to "unlock" a bootloader yet.

The firmware numbers actually have meaning.

That was a nice example which I appreciate, where the only thing I'd like to know additionally is how to tell if it's "signed" or not (see above).

Simply toggling "OEM unlock", going into download mode and unlocking the bootloader will not actually unlock it. There is a reason why after enabling the bootloader unlock in download mode, you should go to the developer settings and "confirm" it.

As a datapoint, apparently for my Samsung phone, there is no way to get that OEM Unlock to show up in the USB debugging menu that I know of, so my only addition here is that it's not always there in the menus (the carrier removed it).

By opening up the developer settings and checking the "OEM unlock" toggle, the bootloader actually becomes unleashed and accepts non-signed images. Meaning an AP file modified by Magisk will now be accepted. If you do not do this, it will not.

This is extremely useful information which is not intuitive to noobs like I am who just want to understand what they can do with their phone.

If you flash in ODIN, always flash AP, CP, BL and CSC!

Again, very useful because it's not intuitive to noobs like I am!

Use adb on your PC (lot of tutorials out there), and type in:
adb shell
magisk --remove-modules

However: that requires you to have adb debugging enabled and to have your PC already confirmed as a computer that is allowed to connect via adb. If you have not done this, do this:

I use adb every day (with scrcpy to mirror Android onto Windows) where I just want to note for others that as of around Android 11 or 12, adb works completely wirelessly now.

As you may know, adb always could be connected first by USB and then disconnected to work wirelessly, but now adb is completely wireless.

The two commands you need are "adb connect" or "adb pair" (same thing, but with encryption).

Here are examples, assuming IP addresses and random codes:

First, establish that your phone is on the Wi-Fi network (and not pluggegd into USB although I don't think USB matters here).

• C:\> ping 192.168.1.2 (obviously use your phone's IP address)

Then connect (or pair) the phone to the Windows adb server:

• C:\> adb devices (to start the adb daemon on Windows)
• C:\> adb connect 192.168.1.2:43210 (random port listed on phone)

Or... if encryption is your shtick...

• C:\> adb pair 192.168.1.2:43210 123456 (random port & pin listed on phone)

Then...

• C:\> scrcpy (mirror screen, keyboard, mouse, clipboard)
• C:\> sndcpy (mirror sound)

It's also extremely helpful to add the new (as of Android 12?) pull-down "tile" for "wireless debugging" which isn't there by default - but you can add that helpful tile (which you use every day!) by doing this...

First you have to turn on "Wireless debugging" for adb to work completely wirelessly on your home or office Wi-Fi network...

• In Android 11 or 12 "Developer options"
• Turn on the "Wireless debugging" switch

Then, you will find it useful to add the Wireless debugging tile...

• In Android 12 "Developer options"
• Click on "Quick settings developer tiles"
• Turn on the "Wireless debugging" tile

That will add the useful on/off switch to your available tiles.

• Then move it to a convenient location in your pulldown tiles

Note the reason you use this brand new tile every day, all day, is that the "Wireless debugging" switch goes OFF each time your Wi-Fi disconnects from your access point - so you're constantly turning it back on.

Especially if you have your Wi-Fi set up for privacy (which is a different story altogether, explained over here & here).

If you use the device's hardware keys to boot into safe mode by pressing certain keys during booting (look it up, it varies from device to device. It can be volume up/down etc.),

For the Galaxy A32-5G, I listed those key sequences here after testing them out myself (most of them anyway). It's confusing so you need a specific listing for each and every Samsung model. Sigh.

There is no use in wiping /cache in recovery.

I saw that option when I tested all the key sequences for my Galaxy and one sequence went into Android Recovery Mode. This is good information to know that it's not needed. Thanks.

If your device is at 100%, plugged in and not in use. But if you're like me and not charging your device past 80%, it will not be built(!)

Mine is set to stop charging at 85%. I don't think Samsung provides an option for 80% so that may only be a typo but just in case, I bring that point up. Also, while we're at it, Samsung hides that setting, which means it's not intuitive to find.

• On my A32-5G with Android 12, it's in
  • Settings > Battery and device care
  • Longpress on the report of "Battery 1d 5h left"
  • Then press "More battery settings"
  • Turn "Protect battery" on

"To extend the lifespan of your battery, limit the maximum charge to 85%."

I may update this thread in the future.

Please do.
And thank you for this information as almost everything was new to me as I strive to see what I "can" do with my Galaxy A32-5G.

With that in mind, it would be nice to list the "things" people "can" do with their Samsung phones, in general terms, such as...

• Flash the firmware
• Unlock the bootloader
• Root the device

etc.

It would be great if you could point out the typos so that I can fix it. I've checked the text for typos but either I'm missing them or thinking my way of spelling is the correct way

I'm not worried in the least by the few typos (at least the OP is written in real (Br)English and not in the classic incomprehensible Chinglish or Desish!) but if you want to know what (minor) typos I saw when I read it....

In the original post, do a "Control F" in your web browser and search for "KNOW will be tripped" and change it to something like "Knox will be tripped".

Type "Control+F" and search for "The lastest version is v3.14.1" and change it to something like "The latest version is v3.14.1".

Type "Control+F" and search for "This is no Samsung specific" and change it to something like "This is not Samsung specific".

Those are so minor that I shouldn't even bother the OP to mention them, but this next one is confusing because I can't tell if he means it or if it's a typo. Type "control + F" on your keyboard in your web browser on the OP and search for " the bootloader actually becomes unleashed", where I think he means "unlocked", not "unleashed", right?

I already mentioned this above but if you search for "not charging your device past 80%" I think that's 85% according to my phone settings. Note all of these typos & thinkos are extremely minor (and I'm sure my own post has just as many or more typos & thinkos).

What's the working method to Mock location without getting detected now ?

Being a noob to flashing, I don't understand why this question is in this firmware flashing thread unless flashing has some implication for setting mock location apps, but without flashing, the way I get mock location apps to work is the following (which may be naive of me to mention as I don't know how it applies here to flashing).

1. First thing I do is I download a free ad free mock-location app such as Lexa Fake GPS Location and I set its settings as desired, e.g.,
   • Choose a fake gps location on the map
   • [x] Start on boot
   • [x] Spoof Wi-Fi provider (dunno what this does though)
   • [x] Auto altitude
   • [x] Simulate moving
   • etc.
2. Then I set that app to be the mock location app in my Android 12 "Developer options" entry titled "Select mock location app"
3. Normally my "Location" teardrop tile is off but when it goes on, then the mock location will be the default presented to apps.

Based on the need for the question from @JazonX, I have to ask... Does firmware flashing affect that mock-location process?​

​

And what does it mean to be "detected" in his question?​

 

[happyhector]

I have a question:
My Galaxy S20+ has several csc Codes, since it is a somehow refurbished version:
DBT/DBT,XEF/EUX/XEF

hence, it is not receiving OTA updates.

Question:
if i flash it with an XEF (not EUX) version via frija/Odin, will it start to receive OTA Updates again?

and, on a side note: will my language be french then?

EDIT: I just learned that there is no such thing as an EUX version of firmware (aparently) so i changed that to XEF

 

[Hektor1154]

SafetyNet/CTS Profile FAILED on stock device FIX

Hey, in case anyone is struggling with the same problem, I just wanted to share a fix since I was not able to find anything online. SafetyNet/CTS Profile FAILED on stock device FIX
The problem: I have a locked bootloader, a completely stock latest Android 13 (as of 2023/02/28), then I did n OTA directly from the settings menu in the mobile (normal update - as always) and suddenly have 'CTS Profile Failed' → Google Pay, my company work profile enrollment and other apps stopped failing due to this check failing. From time to time I enable USB debugging and adjust some small stuff like permissions to write secure settings, etc. which should not be a problem, and it was not until the SW update.
My Device: Samsung S21 Ultra 5G Exynos (not that it matters)
Software: ORX - Android 13 - 2023/01-03 security patch (source of the problem)
What I tried:
- remove every flag I set through adb put
- removed every app like Permission Manager X, brevent, ...
- reflashed the latest FW from scratch through odin (keeping the data -> chossing HOME_CSC)
- cleared cache from Recovery menu
- every possible trick in the book
FIX:
- reflashed the ORX version for my device with a FW with a build date: 2023/01/311/32530 (keeping the data and everything in the phone) and now suddenly the checks are passing again .

Hope this help somebody with the same struggle.

 

[Craith]

If you go into Settings > About phone > Software information > Service provider software revision you'll find different CSC codes: AAA/BBB/CCC/DDD

AAA is the current CSC
BBB is the best CSC for SIM card 1
CCC is the best CSC for SIM card 2 (if dual SIM is possible)
DDD is the factory CSC that cannot be changed

I have an n985f demo unit, which has DDD (4th csc) set as WWB. From what i gathered that is a live demo csc and it affects if calling/data works. I know you said that it cannot be changed, but is there a way to bypass it?
Very informative thread, thank you very much!

 

[Macusercom]

I have an n985f demo unit, which has DDD (4th csc) set as WWB. From what i gathered that is a live demo csc and it affects if calling/data works. I know you said that it cannot be changed, but is there a way to bypass it?
Very informative thread, thank you very much!

Demo units are quite different from retail units. There is no way to flash a standard firmware and I'm not sure that this can be bypassed. Often these units also are stolen as I don't think they should land in an average user's hands. I would return it if you can

 

[JazonX]

I have an n985f demo unit, which has DDD (4th csc) set as WWB. From what i gathered that is a live demo csc and it affects if calling/data works. I know you said that it cannot be changed, but is there a way to bypass it?
Very informative thread, thank you very much!

You can convert LDU to Normal Units by Patching the IMEI using a Samsung CPID Service. Costs depending on the service provider you can find, and after the patching is completed, You can use it as you wish with any CSC you want.
Device needs to be not - rooted, and on U1 firmware.

 

[Craith]

Demo units are quite different from retail units. There is no way to flash a standard firmware and I'm not sure that this can be bypassed. Often these units also are stolen as I don't think they should land in an average user's hands. I would return it if you can

I worked at a retail store and the samsung reps left them for us when they added the newest device on the display so it kind of landed on my hands. I used to have it working on a previous android version but i messed up with upgrading to U5. Thank you for your answer!

You can convert LDU to Normal Units by Patching the IMEI using a Samsung CPID Service. Costs depending on the service provider you can find, and after the patching is completed, You can use it as you wish with any CSC you want.
Device needs to be not - rooted, and on U1 firmware.

As i wrote above i did have it work on U1 with patched certificates etc etc, but i messed up and upgraded to U5 so i'm kinda stuck with a brick. I tried everything i could find software side but nothing so i'm propably gonna swap the motherboard since it's in a pretty good condition as a device. Thank you for your answer!