Hi guys
There is a way to repack/unpack System.sin?
sin format on which operating system?Mac?Linux?
For unpack. Open Androxyde's flashtool > advanced > sin editor > choose system.sin and extract it. You will get system.ext4 file.
then use ext2explore to extract an ext4 file again.
Sent from my F5321 using XDA Labs
and how can i repack, whereas editing ?
Related
Hy guys if some one rooted their WT19i live with walkman phone
then please copy your system apps folder using root explorer and upload them
from original WT19i stock ROM
i really need them
You may get all files in a few steps:
1. Download firmware file (take it here).
2. Open it with 7-zip or WinRAR and extract somewere system.sin.
3. Download and unpack Direct SIN & YAFFS UnPacker in the same folder with system.sin.
4. Open console (cmd) from this folder and type:
aIUP.exe system.sin 4096 apps_LIVE
5. Your apps will appear in apps_LIVE folder.
Please delete my post
Can you use them with CM ?
.: SID :. said:
You may get all files in a few steps:
1. Download firmware file (take it here).
2. Open it with 7-zip or WinRAR and extract somewere system.sin.
3. Download and unpack Direct SIN & YAFFS UnPacker in the same folder with system.sin.
4. Open console (cmd) from this folder and type:
aIUP.exe system.sin 4096 apps_LIVE
5. Your apps will appear in apps_LIVE folder.
Click to expand...
Click to collapse
Please tell me if i want to extract other mobile phone sin files then what will be the command for them
i want to extract Xperia Arc sin files to .... ?????????????
and i am thankful to you for your info.......
The command will be the same.
Hi All!
My terminology:
Extract system.sin from original ftf file,
with Flashtool in SIN editor dumping the SIN -> system.ext4
Mount in ubuntu (losetup system.ext /dev/loop0) change permission chmod 777 /, /bin, /app
Then repack to SIN with img2sin....
I stucked here, cannot do it well when I want to refesh the changed system.sin, I got this error
15/034/2012 16:34:55 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="000A";ERR_DYNAMIC="0x0502: sin header verification";
If I can flash chmod-ed system.sin after its able to run XperiaSrootingKit, I think....
sry for my bad english :/
kaito83 said:
Hi All!
My terminology:
Extract system.sin from original ftf file,
with Flashtool in SIN editor dumping the SIN -> system.ext4
Mount in ubuntu (losetup system.ext /dev/loop0) change permission chmod 777 /, /bin, /app
Then repack to SIN with img2sin....
I stucked here, cannot do it well when I want to refesh the changed system.sin, I got this error
15/034/2012 16:34:55 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="000A";ERR_DYNAMIC="0x0502: sin header verification";
If I can flash chmod-ed system.sin after its able to run XperiaSrootingKit, I think....
sry for my bad english :/
Click to expand...
Click to collapse
Im sure .sin files can only be generated by Sony. Im sure I read something on this earlier.
DeanBoro said:
Im sure .sin files can only be generated by Sony. Im sure I read something on this earlier.
Click to expand...
Click to collapse
And if I change the header from the original SIN after img2sin ?
Any sin file is signed with something like checksum ... you cant generate it by yourself ... only sony can do that !
Hello,
How I can extract system.img and boot.img from .ftf or other ?
Thanks,
Up ! sorry it's importent
Use flashtool's decrypt feature.
Flashtool -> Advanced -> SIN Editor to extract sin content (you will get a .elf or .yaffs2 or .ext4 image depending of content type)
Flashtool -> Advanced -> ELF Extractor to extract elf content from kernel.elf and get zImage, ramdisk and rpm.bin (with 2012 devices line)
Androxyde said:
Flashtool -> Advanced -> SIN Editor to extract sin content (you will get a .elf or .yaffs2 or .ext4 image depending of content type)
Flashtool -> Advanced -> ELF Extractor to extract elf content from kernel.elf and get zImage, ramdisk and rpm.bin (with 2012 devices line)
Click to expand...
Click to collapse
So? When I got zImage, ramdisk and rpm.bin ??? I will get a boot.img
Androxyde said:
Flashtool -> Advanced -> SIN Editor to extract sin content (you will get a .elf or .yaffs2 or .ext4 image depending of content type)
Flashtool -> Advanced -> ELF Extractor to extract elf content from kernel.elf and get zImage, ramdisk and rpm.bin (with 2012 devices line)
Click to expand...
Click to collapse
hey mate.
so after using the ELF extractor i got a abunch of files including this
Code:
kernel.elf.Image
so i can simply rename it to boot.img and use it on my custom rom to boot?
kudos
Hi All,
A totally newbie question. I have compiled the naA-jb kernel at my end (no changes, just recompiled) and have the zImage file. I want to flash this on my U20i device now. However, I cannot find a way to do it. I read about fastboot, but it seems that X10 mini pro does not support fast boot. I tried the search key press, and connecting to PC for fast boot). In Flashtool the button to install the Kernel is always greyed out. Is there any way in which I can flash the kernel? My X10 mini pro is running naA-jb-03 kernel. I'm using Windows 8. Thanks.
Well I was able to solve the issue by using the Android Kernel Kitchen by championswimmer. Basically revolved around extracting the existing ftf file and creating a new kernel.sin file using the kitchen. Then replaced the kernel.sin in the original ftf. If there is any other way, you are welcome to answer.
New in nAa-jb-05
With nAa-jb-05 the above method will not work. This is so because it introduces lz4 compression for zImage and the ramdisk. Working on a way to get over this and will post an update.
So one way to do is as follows:
1. In flashTool, Use Extractors -> ELF and select the kernel.sin file from the original ftf.
2. It will output 2 files kernel.elf.Image and kernel.elf.2
3. Take kernel.elf.2 and use lz4 to decompress using the -d option.
4. Above step will output the ramdisk cpio file.
5. Use the existing method of Kernel tools to gz the cpio file and place your compiled zImage to get kernel.sin.
6. Use bundle creator in flashTool to create ftf.
Structure of nAa-jb-05
OK just to keep things in my mind clear:
1. Extract kernel.sin file from the ftf file using winrar or 7-zip
2. This kernel.sin file contains the kernel zImage and the ramdisk
3. In the nAa-jb-05 version of the kernel.sin file, the ramdisk (which is cpio'ed already) is compressed using lz4 compression. The zImage is also compressed using lz4, but that is during the kernel compilation time.
4. To extract the zImage and the ramdisk from the kernel.sin file, we can use the FlashTool. Fire up the Sin Editor and select the kernel.sin file. You can now click on the "Dump Data" button. This will dump the kernel.elf file and the kernel.partinfo file.
5. Now the kernel.elf (~ 8 MB in nAa-jb-05) can be extracted using the "Extractors -> Elf" option in FlashTool.
6. 2 files will be dumped from the ELF, the kernel zImage by the name kernel.elf.Image and the kernel.elf.2 file which is the lz4 compressed ramdisk.
7. If you open up the kernel.elf.Image file in a hex editor, you will be able to see the standard [0x00 0x00 0xa0 0xe1] pattern.
8. If you open up the kernel.elf.2 file you will see the lz4 magic sequence 0x184C2102 (little endian).
9. Now you can decompress the kernel.elf.2 using lz4 (you will need to compile on linux/(Ubuntu) from source). Also note that the magic number should be 0x184C2102 and not 0x184C2103 during the compilation stage.
10. Once decompressed you get the ramdisk.cpio.
11. You should be good from here.
I will follow-up with the "stich-up" up to "kernel.sin" with modified/re-compiled zImage method shortly.
Stitch-up related:
1. If modifying the init-ramdisk contents make sure to cpio and then do a lz4 compression.
2. Put it in the input folder of kernel-tool-master by championswimmer.
3. Place the compiled zImage (by selecting lz4 during compilation, config) in the input folder too.
4. Create a kernel.sin file using the kernel-tool-master
5. Use the kernel.sin file created above, to create ftf file using the Bundle creation option in FlashTool.
If changing version string kernel recompile
Also, take care that in case you modify the kernel during compilation, (such that you change the version string etc.), then you will need to recompile all the loadable kernel modules again. In this case, you would be required to re-compile the wireless modules again.
As a side-note, there is no need to use the build_wifi script for building the kernel modules. These are legacy, not required for 05 version of the kernel. modules_install should be good enough.
AW: [Q] Help flashing custom zImage on nAa-jb-03
QueryType said:
As a side-note, there is no need to use the build_wifi script for building the kernel modules. These are legacy, not required for 05 version of the kernel. modules_install should be good enough.
Click to expand...
Click to collapse
Are you interested in joining our Team? Please PM...
Sent from my U20i using xda app-developers app
Hi All,
Due to specific APP requirement, I need to modify some settings in kernel.
Here are all the settings I need to modify in default.prop:
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
Here are the methods I already try:
1. Android Kernel; Kitchen 0.3.1 (http://forum.xda-developers.com/showthread.php?t=1659584)
Fail at extract kernel.sin, cannot found RamDisk
2. dsixda's Android Kitchen 0.224 (http://forum.xda-developers.com/showthread.php?t=633246)
Fail at extract kernel.sin, cannot found RamDisk
3. kernel.sin unpacker by DooMLoRD (http://forum.xda-developers.com/showthread.php?t=1262656)
Fail at extract kernel.sin, cannot found RamDisk
4. Tools in Xperia FlashTool
Fail...
The kernel.sin was extract from 2.6.32.61-nAa-jb-06.ftf. (http://forum.xda-developers.com/showthread.php?t=2136471)
I already start studying how to compile nAa kernel...
Is there any easier way to apply this change?
Thanks!
Resolved.
It's because LZ4 compress format.
Here are the steps to Unpack nAa Kernel / Modify default.prop / Repack Kernel FTF
1. Decompress nAaKernel.ftf
You will got Kernel.sin
2. FlashTool => Tools -> Sin Editor => Select Kernel.sin => Extract data
You will got kernel.elf and kernel.partinfo
3. FlashTool => Tools -> Extrators => Elf => Select kernel.elf => Unpack
You will got kernel.elf.2 and kernel.elf.Image
kernel.elf.2 = ramdisk binary which compressed by LZ4!
kernel.elf.Image = zImage
4. Rename kernel.elf.Image to zImage
5. Rename kernel.elf.2 to ramdisk.lz4 and use LZ4 tools to decompress it
You will got a new ramdisk binary which was known as ramdisk.cpio
6. Rename ramdisk which extracted in step.5 to ramdisk.cpio
7. Copy ramdisk.cpio and zImage to ubuntu system.
8. Extract ramdisk.cpio and you will see default.prop
Make any modify you need.
9. Compress ramdisk folder to ramdisk.cpio
Here are the commands:
find . | cpio -o --format=newc > ramdisk.cpio
10. Compress ramdisk.cpio by GZip
Here is the command:
gzip ramdisk.cpio
11. Use Kernel Kitchen to create kernel.sin
Put ramdisk.cpio.gz and zImage in input folder under Kernel Kitchen.
Create kernel.sin by this tools.
12. FlashTool => Tools => Bundle Creation => select kernel.sin and loader.sin => Create your FTF
13. Flash into your device!
Although Puzzle & Dragons still cannot works on X10 mini with MiniCM10...
But I tried and learned something. :laugh:
thanks for explaining the process
it is very useful for me .
ramdisk.gpio decompress & compress
I tried to follow all steps, but isn´t work for me :'(
What I did:
1) decompress E15_2.6.32.60-nAa-05.ftf with 7z under windows: I get kernel.sin and loader.sin (OK)
2) extract data from kernel.sin with flashtool (0.9.16) under windows: I get kernel.elf and kernel.partinfo (OK)
3) extract elf from kernel.elf with flashtool (0.9.16) under windows: I get kernel.elf.2 & kernel.elf.Image (OK)
4) renamed kernel.elf.2 to ramdisk.lz4, and kernel.elf.Image to zImage; both under windows with f2 (OK)
5) decompress ramdisk.lz4 (3662KB) under windows (fastcompression . blogspot.com . es/p/lz4.html): I get ramdisk (4608KB) (it supposed to be renamed, so I expect it´s ok)
6) renamed ramdisk to ramdisk.cpio under windows with f2 (OK). Copy to ubuntu (QUESTION: zImage is used in ubuntu only in kernel kitchen???)
7) extract ramdisk.cpio (4718592- not command in the post): I used cpio -i -F ramdisk.cpio (9216 blocks); 4 new elements> default.prop init (files) android modules (directories)
8) I want to check I can extract & compress ramdisk (and make a "new" kernel), so I don´t do any modification
9) with only those 4 elements in the directory (default.prop init (files) android modules (directories)), I make ramdisk: find . | cpio -o --format=newc > ramdisk.cpio (PROBLEM: alert message "ramdisk.cpio has been increased, 4718080 new bytes has not been copied" other line "27647 blocks")
Original ramdisk.cpio was 4718582, but the new one is 14155264... 3 times more!!! I think the problemis here, but I don´t know how to resolve it
I have done the rest of the manual
10) kernel.sin created with kernel kitchen 0.2.3 under ubuntu (last kitchen version gives me an error, because in despite of choose create kernel.sin from zImage and ramdisk, it tries to do a ftf from kernel -not available- and ramdisk)
11) ftf creation under windows with X10 flashing tool 0.5.0.0 (flashtool 0.9.16 force me to write what device is for, but the cell is blocked, so I cann´t do it) OK
12) I tried to flash it, but it was aborted, so I expect ftf was incorrect
Sorry for wrote all: I thik the problem is extracting and compresing randisk.cpio, but I prefer to write everithing to be sure and be as clear as possible.
Any help will be great!