[Samsung Galaxy S22 Ultra] GalaxyA325G:
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!

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).

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.

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?)

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?

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.

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).

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).

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.

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

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).

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.

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.

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%."

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.

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).

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).

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.

Then I set that app to be the mock location app in my Android 12 "Developer options" entry titled "Select mock location app"

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?​