How to open tar md5 file. Firmware TWRP recovery on Samsung

A tool for packaging firmware and their individual parts in .tar.md5 for subsequent firmware via Odin under Windows

For packaging, you need to place the firmware files in the \parts directory or extract them from the firmware file.....tar.md5, for this you need to place it in the root directory with the tool, run TAR.MD5 PACKAGER.bat and select the appropriate menu item.

A small tool to automate packaging in tar.md5 for UBUNTU
Download, unpack, go to the unpacked folder and

Small video review - You cannot download files from our server

“Permissions for files and directories”

Everything is forbidden
--x Disabled read and write, allowed execution
-w- Read and execute forbidden, write allowed
-wx Disabled read, allowed write and execute
r-- Read allowed, write and execute prohibited
r-x Read and execute allowed, write not allowed
rw - Read and write allowed, execution denied
rwx All allowed

***************************************************************************

A couple of good examples:

w-r–r– or 644 - the file is readable by everyone. The owner has write access to the file.
rw-rw-rw- or 666 - the right to read and write to the file is available to everyone.
rwxr-xr-x or 755 - everyone can read the directory and search for files in it. The directory owner can modify existing files, delete them, and create new ones.
rwxrwxrwx or 777 - everyone is allowed to write, read and execute in the directory.

Calculation example:
- - 0
r-4
w - 2
x - 1

Now, to find out the desired number, we sum up the numbers corresponding to the letters.
For example:
rwx = 4+2+1 = 7
–x = 0+0+1 = 1
r-x = 4+0+1 = 5 etc.

You can see the file permissions using the console (terminal emulator). For example, we go to any directory. Let it be system Enter the ls -l command and see what was found interesting there.

Since Android is based on Linux, this article is relevant for all Linux systems (Ubuntu, etc.).

/ - The root folder.
/bin - folder containing executable files and links to executable files. Executable files are programs that run at system startup, as well as the most necessary programs available to everyone. Example: ls, mount, pwd, unzip.
/data - folder with data about synchronization and accounts, passwords to wifi access points and vpn settings, etc.
/data/app is a folder containing installed programs and games.
/data/data - a folder containing application data, their settings, game saves and other information.
/data/dalvik-cache - cache program area for the Dalvik program. Dalvik is a Java virtual machine, which is the basis for the operation of programs that have the *.apk extension. In order to make the launch of programs faster, their cache is created.
/dev - a folder containing files for various devices, both real and virtual, as well as those devices that are not there, but which could be.
/etc - a folder containing configuration files used when loading the operating system and during the operation of various programs.
/lib - a folder containing libraries of functions required for various programs and the C compiler, as well as modules (device drivers) connected to the kernel.
/lib/modules/ - folder containing modules (device drivers) of the kernel, which have a .ko extension. This folder contains subfolders that match the kernel versions (for example, 2.6.32.9-default) that were installed on the system. That is, each version of the kernel has its own set of modules. This is very important and you need to pay attention to it. Often, when compiling the kernel, they forget to change the version, the new kernel uses the modules of the previous version when it is loaded, and the system does not boot. The current kernel version can be found with the uname -r command, the returned version must match the name of one of the folders in /lib/modules/ .
/mnt - contains folders for temporarily mounted file systems.
/proc is a virtual folder containing all the details of the Android system, including the kernel, processes, and configuration settings.
More details folder /proc
/proc is a virtual file system containing all information about the Android system, including the kernel, processes, configuration options, hardware information. All files in the /proc folder are also virtual and don't really take up any memory space (so these files are 0 bytes in size), the operating system creates them on the fly when the user tries to read them. Any manipulations in the /proc folder are possible only with superuser rights. The /proc filesystem can be thought of as an interface to internal data structures in the Android kernel. This interface allows you to get system information and change some kernel parameters while Android is running.

Many programs collect information from files in /proc, format them, and display the result to the user (top, ps, and others). There is a special folder /proc/sys in the /proc filesystem. It allows you to view kernel parameters and change these parameters on the fly without rebooting the system.

The virtual system's /proc files are not intended to be viewed with a normal text editor, as this may violate the integrity of kernel data. To do this, use the echo and cat commands.
/proc/nnnn - virtual folders with numbers correspond to each process running in the system.
/proc/net - virtual folder containing information about networks.
/proc/net/dev is a virtual file containing information about each network device.
/proc/sys is a virtual folder containing kernel configuration options.
/proc/meminfo is a virtual file containing information about memory (to view this information you need to type the command: cat /proc/meminfo).
/proc/version - virtual file containing information about Android kernel version (cat /proc/version command).
/proc/cmdline - a virtual file containing information about the parameters passed to the kernel at boot (command cat /proc/cmdline).
/proc/cpuinfo is a virtual file containing information about the processor.
/proc/loadavg - virtual file containing information about the average processor load; its information includes: CPU usage in the last minute, last 5 minutes, and last 10 minutes, as well as the number of currently running processes.
/proc/stat is a virtual file containing information about statistics related to the previous boot of the system.
/proc/uptime is a virtual file containing only two numbers: how many seconds the machine has been running and how many seconds it has been idle.
/proc/devices is a virtual file containing information about all currently configured and loaded character and block devices.
/proc/ioports - virtual file containing information about I/O communications ports used by devices.
/proc/filesystems is a virtual file containing information about all filesystems supported by the kernel.
/proc/mounts is a virtual file containing information about all mount points used in the device.
/proc/partitions is a virtual file containing information about all partitions.
/proc/swaps is a virtual file containing information about all swap spaces.

/sbin - a folder containing executable files of programs that are designed to manage the system itself. Example: ifconfig, man, mdev, vconfig.
/sdcard - folder containing files and folders on the SD memory card (if installed).
/sys folder containing the actual system configuration at the current moment. /sys is very closely related to udev as you plug (unplug) devices, the contents of the /sys directory change dynamically. You can look at an example. Run the ls /sys/bus/usb/devices/ command to see the current usb devices on the system. Now plug in the flash drive and run the ls /sys/bus/usb/devices/ command again. You will see that now there are more devices.
/system - a folder containing system files and folders with data and everything necessary for the Android OS to work.
/system/app – a folder containing system applications (sms, phone, calendar, settings, etc.), as well as applications installed by the device manufacturer (branded widgets, live wallpapers, etc.).
/system/fonts - folder with system fonts.
/system/media – a folder containing standard melodies for calls, notifications, alarm clocks and interface sounds, as well as boot animation (bootanimation).
/system/build.prop - a file containing a huge number of settings, such as screen density, proximity sensor delay time, wifi management, device name and manufacturer, and many other parameters.

After spending hours trying to find a way to convert zip files to tar.md5 files that can be flashed using ODIN. I came up with a solution that is mentioned in this guide. Most of the clouds does not allow to upload ODIN flashable tar.md5 files. So over the internet, you can only find zip files of custom ROMs and recoveries. There is a need to convert kernel zip to tar.md5 so that they can be flashed.

The following guide has a tool that can be used for converting .zip files to tar files. I have used this tool and it works fine. Beware flashing kernels is not a kids job, you can get your phone bricked, so proceed with caution. If you will follow the guide as it is, then don't worry. I have explained everything in details. Still, if you have questions or confusion, feel free to ask me in the comments.

How to convert Kernel Zip to Tar.md5:

The following are some prerequisites that you will need in order to proceed further. Make sure you know how to flash ROMs and recoveries, this guide is not for beginners. You must have basic knowledge of Android and flashing firmware and custom recoveries. Even if it's your first time, don't freak out. Do exactly as written in the guide and ask in the comments if you have any confusion.

Prerequisites:

• Before flashing, do make of your phone. So if there's some problem while flashing new kernel you can restore the backup and get back to the stable phone.
• You will need a kernel .zip file.
• Unzipping tool like WinRAR.
• A computer.
• ODIN v3.10.7. ( .)
• Samsung USB drivers. (You will have to install Samsung drivers on your computer. So that when you connect your phone to the computer, it recognizes it. Essential for using ODIN).

Note: Check these premade tar files can be flashed directly using ODIN. You might find the required one from this collection.

Step to step guide on how to convert zip file to tar (.tar.md5)

1. First of all download CreateTarForKernal.
2. Make a new folder on your computer's desktop, or somewhere you can find it easily.
3. Now extract CreateTarForKernalzip file into that folder.
4. Now on your computer:(This is to unhide some files)
   • goto Start
   • Write Folder Options.
   • Click to open it
   • Click on View Tab.
   • Uncheck “hide extensions for known file types”
   • Apply and OK.
5. Download the Kernel Zip and extract it into the folder you just created.
6. Rename boot.img to or whatever the name of .img file is to “ winter"(remove .img). If zimage file is already present in the folder then you don't have to perform this step. (Sometimes zimage.img file is present in some sub-folder of the kernel. Move it to the main CreateTarForKernel folder.)
7. Run tar.bat.
8. Once completed. You can rename the .tar.md5 file.
9. To ensure that the conversion was successful, see the size of the converted tar file. It should be almost the same as the kernel file you just converted.
10. Now you can flash easily using ODIN.
11. Just Add . tar.md5 file you just created to AP or PDA of ODIN, put your phone in download mode and connect it to your computer.

Important note:Mostly PIT files also flash the ROM so it might delete all data present in your phone.

That's all on how to convert kernel zip to tar file. If you have any questions or confusion feel free to ask me in the comments. Do give us feedback about how this guide worked out for you. In the above guide, I have also attached some premade tar files that are ready to be flashed using ODIN. You can select from them. If you find any suitable kernel for your phone. You can ask if you have any confusion while performing this guide to convert kernel zip file to tar file. Best luck.