CSC (Consumer Software Customization): It is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and APN setting.
PIT (Partition Information Table): You only need it if you screw up your partition table or if the firmware specifically requires it because of a change in the partition table ...
Before you flash the recovery, untick the Auto Reboot option in ODIN. Then flash the recovery. After flashing in done, reboot your device directly to recovery mode from download mode by pressing Vol up + Power + Home button together. Now you will see the TWRP recovery is booted in your device. Now you can reboot normally and your TWRP will be installed.
According to this XDA-Developers forum post and this Droidguiding article:
BL stands for bootloader
AP represents the system partition (possibly stands for Android partition); under previous Odin versions, this was called "PDA"
CP represents your modem
CSC stands for Consumer Software Customization, this specifies the features your Android device gets ...
Per this page,
WARNING: Do not boot into Samsung's ROM without first applying our Root .zip. Samsung's OTA updates install /system/etc/install-recovery.sh and /system/recovery-from-boot.p, which cause Samsung's ROM to replace the recovery image you had just flashed with the stock recovery. Our Root .zip removes these files, thus preserving your custom ...
There is a cross-platform version of Odin called JOdin. It can run in a web browser, or locally after downloading the JAR file. Either one requires Oracle Java 8 to be installed first.
Web version: https://builds.casual-dev.com/jodin3/
Offline version: https://builds.casual-dev.com/index.php?dir=JOdin3%2F '
The offline version is started with $ java -jar /...
No, Official or custom firmware are only to be used with the device specified in its name
Using a different phone model may result in your hard bricking your phone
Is there a reason why you want to use a different phone model firmware over your own?
Is there any reason to update Android firmware via PC using software like Odin, rather than just doing an OTA update?
Since Android Lollipop, Google has moved to block based OTA updates which means if the system partition is tampered with (often done when rooting the device) the OTA upgrade would and should fail. How would you update the OS then?
In the case you weren't eager to look at the research, here's the solution.
In the same folder of your Odin executable, you'll find a file called Odin3.ini. Being it a configuration file, it defines the behaviour Odin should meet at startup. What we're interested into, though, is to examine its content, so fire up your text editor of choice and open the ...
PIT stands for Partition Information Table. A PIT file is basically a set of instructions defining the phone partition layout. You should use a it if you want to re-partition the phone with Odin.
You only need this file when repartitioning the device and you don't need to repartition it unless you mess up the partition table to begin with, or when ...
It depends on how the full flashable tar/kdz was obtained. If it was obtained from an OTA capture, what difference does it make? Just doing the OTA would then be the most direct from the manufacturer. Capturing is a popular deal, because big companies don't do free hand outs. The more experienced (ex. Sammobile) actually build their own tar ...
There's no fastboot for Samsung devices - Download mode is the semi-equivalent, except that it's only accessible via Odin/Heimdall. You will need appropriate drivers to get the PC to recognize a device in Download mode.
Most Samsung phones come with their BL unlocked or unlockable (notable exceptions are AT&T/Verizon devices). To root these devices, ...
After waiting a couple of days and not finding any answers, I restarted the device. It booted to a screen saying
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using recovery mode in Kies, but Kies gave me an error message saying that the device is not supported. However, I noticed that the text in the ...
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's Recovery checking script checks if a custom recovery is present and overrides it with system recovery<3e>.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin (and before the phone reboots).
As soon ...
It will not wipe data unless you explicitly choose to erase NAND (after which your phone would end up bricked).
Odin only flashes images into the device - it doesn't read data out. You're on the right track about using TWRP to reclaim data, just be sure to install one made for your device.
According to this guide it writes the bootloader of a working device onto the SD card. This guide is a bit more detailed and describes it as follows:
T Flash option in odin is for Samsung boot recovery via sd card. This option is checked when we are going to make Samsung boot able sd card to fix or unbrick Samsung dead boot devices. In this case we must ...
Solution by @beeshyams that worked in my case:
On Odin in the options tab; Uncheck the Auto Reboot option.
When Odin finishes the flashing procedure; use the suitable key combination to boot into TWRP Recovery Mode.
From the TWRP menu; boot into system.
Tip : In some cases, if a problem occurs try to flash an older version of TWRP
Note many ...
Flashing the correct img solved the problem:
heimdall flash --RECOVERY TWRP-188.8.131.52_A20_V1.2_by_Agrim720\[Black-themed\].img.img
File was found here: XDA-forum
Previously rooted with boot.img patched by magisk and vbmeta flashed:
heimdall flash --BOOT magisk_patched.img
heimdall flash --VBMETA vbmeta.img
I highly recommend to ...
It is Download mode you boot the device into to use Odin. I've included a bit more info if you wanted anything deeper.
See this post "What is Download mode"
As for Download mode, for example ODIN is commonly used on Samsung devices to flash ROMs, those devices needs to be in download mode prior to flashing. However, ODIN is not the official way ...
If you use Odin then I am asuming you have a samsung device. Depending on what Stock rom you use, I mean if you will flash using 1 file or 3 file rom, if you have a 3 file rom then you have to put in the pit file to, and then you can enable the re-partition.
If you use 1 file rom in odin, i think it will re-partition by default so you do not have to check ...
Samsung devices usually have no locked bootloader so you won't remove that. Official updates do however remove any trace of a working root.Your device is nowhere near a developer device but more a custom device served with a custom firmware of Verizon noticeable on the V in your model no.
Because of that custom Verizon model it is possible that the ...
As stated here by user90492, dont use the NAND erase all. It will completely wipe the NAND including bits required to boot.
Odin should theoretically wipe the partition before writing on it as it does a write by block. Odin did not format the data partition resulting in old contacts data being present. The tarball file you used must be missing the blank ...
The arguments which may be supplied in the recovery.command file:
* --send_intent=anystring - write the text out to recovery.intent
* --update_package=path - verify install an OTA package file
* --wipe_data - erase user data (and cache), then reboot
* --wipe_cache - wipe cache (but not user data), then reboot
As suggested by @MatthewRead, this answer will reflect the same fashion of the question - it will be editable by anyone who has something useful to say.
In regards to the original question, here are my latest findings:
For label [Options]:
Title: string. Used for changing the string displayed near "Odin"; freely customizable;
FactoryResetTime: unknown. I ...
I just reverse engineered the Odin3 ini part (using IDA 66 + HexRaysDecompiler & Rohitab API Monitor 2.32).
So these are all available ini settings + it's default values:
; These ini settings applies to Odin3 v3.12 (Compiled 21. jan 2016)
; [Avoid missing this or anything starting like 'Odin3. [Android + SLP]' ]
download mode is related to recovery where your device is ready to accept a new system image from the computer.
It is used to flash a new OS to the device.
In download mode, you can inject and install the OS (flashing).
but be careful while using this
Old Samsung devices (Galaxy S1 to S3 generations) where near impossible to brick unless you had the emmc bug or somehow flashed missmatched set of bootloaders. The best way to attempt to recover the device is grab a firmware package from samsfirmware or similar. Force device in to download mode with either key combinations or with a jig then proceed to flash ...