I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy
Samsung source. I added another module for this copy to add functionality. Then I downloaded a copy
stock firmware, which I used several times to launch my phone. I took the boot.img file
the spare firmware is decomposed using an online tool and replaced zImage with zImage, which I received
from compiling my source. After several attempts, I seem to be able to create the complete tar.md5 file
Everything in the catalog of the modified stock source. When I launch the phone with this file using Odin,
The file is going fine, but the phone is stuck in boot mode. I'm trying to find out the root cause
a phone that enters download mode, and is the main reason for incorrect file packing or not me
include the file you want? Here is what I did to create a tar file with md5 validation:
I created the tar file: tar -H ustar -c aboot.mbn sbl1.mbn rpm.mbn tz.mbn sdi.mbn NON-HLOS.bin boot.img recovery.img
system.img.ext4 cache.img.ext4 modem.bin> tarfile.tar
cp tarfile.tar tarfile.tar.md5 md5sum tarfile.tar → tarfile.tar.md5
Then I tried to perform a health check by comparing the file with the tar archive in the image that I used to
collapse my phone with the file command, and here is what I get (note: I put my results in
catalog/ expermental and the unpacked verified tar file in the directory / originalstck / originaltarfile) (
, , tarfile ,
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 - , ):
@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
(: tarfile.tar - , , tar, rom, N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5.) , , tarfile.tar /experimentalstock N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 /originaltarfile dirctory. 1- tarfile.tar . . , . boot.img, , , zImage, , , rom. Samsung, . 2- - , ; tar.file : tar (GNU) POSIX N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 tar POSIX. GNU ?
: , , ? , ?
, , . , ? Kernel :
user@ubuntu:~$ locate -r '^/home/user/androidkernel3/.*.km$'
/home/user/androidkernel3/arch/arm/mvp/commkm
/home/user/androidkernel3/arch/arm/mvp/mvpkm
/home/user/androidkernel3/arch/arm/mvp/oektestkm
/home/user/androidkernel3/arch/arm/mvp/pvtcpkm
user@ubuntu:~$