I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I used the following
command to create a tar file with md5 authentication: tar cf - aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img system.img.ext4 | tee tarfile.tar | md5sum - which gave me a tar file called tarfile.tar. I then tried to do a sanity check by comparing the file with a tar archive in an image I have used to flash my phone with using the file command, and here is what I get ( note: I put my results in the /expermental directory and the unpacked validated tar file in /originalstck/originaltarfile directory ) : @ubuntu:~/expermental_stock$ file * aboot.mbn: Hitachi SH big-endian COFF object, not stripped boot.img: data cache.img.ext4: data info: ASCII text initramfs.cpio.gz: gzip compressed data, from Unix modem.bin: x86 boot sector N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive N900PVPUCNC5_N900PSPTCNC5_SPR.zip: Zip archive data, at least v2.0 to extract NON-HLOS.bin: x86 boot sector recovery.img: data rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped sbl1.mbn: data sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped SS_DL.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows system.img.ext4: data tarfile.tar: POSIX tar archive (GNU) tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped zImage: Linux kernel ARM boot executable zImage (little- endian) file ~/originalstock/originaltarfile/* /aboot.mbn: Hitachi SH big-endian COFF object, not stripped /boot.img: data /cache.img.ext4: data /modem.bin: x86 boot sector /N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5: POSIX tar archive /NON-HLOS.bin: x86 boot sector /recovery.img: data /rpm.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped /sbl1.mbn: data /sdi.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped /system.img.ext4: data /tz.mbn: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped There are two things that concern me with the above output as I am comparing tarfile.tar in /experimentalstock directory with N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 file in the originalstock/originaltarfile dirctory. 1- tarfile.tar is smaller. I added more modules to the source. But that may be explained by the source I started from. I started from the Samsung source code which may not contain the telecom provider's files. 2- My other concern is the output associated with the file command; for tar.file I get: POSIX tar archive (GNU) and for N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 I get POSIX tar archive. Is there a difference between the GNU version vs. whatever is the default format? But the bigest problem I have right now is that even though I was able to load the tarfile.tar using Odin, a gui tool made by Samsung, and adb side load, yet another file loading method, while stock rom was on the deive. Neither worked. Adb sideload gave more useful messages stating: E:footer is wrong E:signature verification failed My problem seems to be I don't know enough about comparing and vlaidating the two tar files ( that is the one I download and works fine and the one I want to create. Is there any help you can give me with this? ) I have located the tar manual and I am going through it. If there is any help you can give me, I would certainly appreciate it. Sean Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma - which is living with the results of other people's thinking. Don't let the noise of other's opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary. Steve Jobs
