I want to create an image for the Arm chip and deploy it on my Samsung Note 3. I have a compiled copy of
the Samsung source. I added another module to this copy for added functionality. I then downloaded a copy of the stock firmware, which I have used a number of times to flash my phone. I took the boot.img file of the stock firmware split it open with a tool online, and replaced the zImage with the zImage that I got from compiling my source. After several attempts, I seem to be able to create a complete tar.md5 file of everything in the directory of modified stock source. When I flash the phone with this file using Odin, the file goes in fine, but the phone is stuck in download mode. I am trying to figure out the main cause of phone going into download mode, and is the root cause one of packing the files incorrectly or did I not include a file that is required? Here is what I did to create the tar file with md5 authentication: 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 > N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar cp N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 md5sum N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar >> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 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 ( Note: Here tarfile.tar is the file I made, and I am comparing it with the original tar file that came with the stock rom, which is called N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5. I figured I make this clear since in the first portion of my question, where I was explaining how I created the new tar file, above I used the longer version name to refer to both of them ) 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 have to say that I just realized I did not include any .km files from the batch I compiled myself into the modified stock rom. I am going to investigate this further and try to add them. Do you think that is necessary? I did compare the boot.img files, and the one I created by adding my zImage to it is larger than the one that came with stock rom. 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? Sean -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
