how to build a flashable image from source for Sprint Variation of Note 3

zohal52

Member
Apr 23, 2014
7
0
0
Greetings
I need some help with packing a compiled image of the Samsung Source into a flashable image. After that I downloaded the stock image of my phone from SamMobile, and unpacked it. I then used an script called umkbootimg to replace the zImage in boot.img with mine and can created another boot.img. Here is what I have now:
stock3$ ls
aboot.mbn recovery.img
boot.img rpm.mbn
cache.img.ext4 sbl1.mbn
initramfs.cpio.gz sdi.mbn
modem.bin SS_DL.dll
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 system.img.ext4
N900PVPUCNC5_N900PSPTCNC5_SPR.zip tz.mbn
NON-HLOS.bin zImage
I have tried to use tar –H ustar –C command to pack the files into a tar ball. I then added md5, and zipped the whole thing with zip command. But could not use twrp to flash it. I have also looked into Odin and Heimdall. The greatest success I have had so far has been an image that puts my phone into boot loop, and I had to recover. What is the fastest way I can create an image from this?
 
how to build a flashable image from source

I need some help with packing a compiled image

Just so you know, a compiled image is object, not source. Source is human-readable (assuming you know the programming language) code. A compiled image is a series of bits (or binary numbers or hex numbers or however you decide to represent it). .img, .bin and .dll files are object (more properly, machine language) files. A .c or .h file would be source. They would be used to compile the .bin or .dll files.
 
Look at step 12 of post 7 in that thread? I know you want to just dismiss any help people give, but really, take the 10 seconds to look. It's there.
 

Forum statistics

Threads
955,567
Messages
6,965,272
Members
3,163,335
Latest member
Phodyeu7