[XPERIA X10 Android Development] xeviro:
Fastest way to decrypt your own branded ROM by Binary

You may find the ConvertTools below.. This is just sick :D:D

Old way of decrypting ROM

Below is the guide to decrypting ROM which comes from SEUS. By following this guide, you will have your branded ROM decrypted as SIN files and later you can flash back the ROM to X10 with flashtools. So you can root and debrand all you like without worry because later you can flash your branded ROM back to your X10.

Tools:

jerpelea SIN Reconstructor

http://hotfile.com/dl/52847024/13749f6/SIN_Reconstructor.rar.html

Requirement:

Your Xperia X10 must have the any version of the branded ROM installed first. If you already rooted or debranded it, you must rebrand it with your ROM first. See other threads about how to achieve this. The SIN Reconstructor tools cannot be used to extract the tho downloaded ROM files directly.

Step 1. Getting the extracted ROM from SUES

Task: Getting the targeted ROM files ready to be flashed with SEUS.

Do an update with SEUS to get your latest branded ROM, and let the ROM to be flashed to your X10. After this you will have the two files in SEUS db ready and next flashing, you don't need to download anymore and SEUS will flash it directly for you.

Task: Installing the extractor files to SEUS

Inside SIN Reconstructor, you will find com.sonyericsson.cs.usbflashnative_2.10.6.24.jar in seus directory. Backup your usbflashnative.jar from your SEUS plugin's directory somewhere else first, then copy the com.sonyericsson.cs.usbflashnative_2.10.6.24.jar file to plugin directory and then rename to the one you back up just now.

Task: Extracting ROM with dump0

Now you create a file in SEUS root. You need to create a file name dump0, make sure its dump0, not dump0.txt if you create the file using notepad and rename it. The run the SEUS update again. This will reflash your X10 then afterward, you get a lot of sign and bin files in SEUS root directory. Then you move the file somewhere else first

Task: Extracting ROM with dump1

Same as above but now you need a file name dump1, and the file dump0 must not exists in SEUS directory. After you are finished with reflash, you will have a lot of sign and bin files again, then move somewhere else.

Step 2. Identifying the bin and sign files

Because the extracted rom files are named in number, you need to identify and rename them first. When renaming, you need to rename pair of sign and bin files to the designated name.

When making SIN files, you only need to create this file below:

amss.sin

boot.sin

dsp1.sin

recovery.sin

system.sin

userdata.sin

The rest of SIN files is the same with other debranded SIN files you downloaded before which are:

amss_fs.sin

apps-log.sin

cache.sin

fota0.sin

fota1.sin

How to identify is very easy, find the file and the rename

amss file size is about 15Mb

boot file size is about 5.1Mb

dsp1 file size is about 8Mb

recovery file size is about 5.4Mb and bigger then boot.sign

system file size is the largest

userdata file size is 4Kb

When you have all this pairs renamed, copy them to SIN Extractor files directory.

Then we need to recheck the rebuild.cmd against the sign file size. Guides taken from rebuild.cmd

@echo off
@echo sizes are adjustable for every sign file
@echo if your file size differs from mine
@echo adjust count= vith the value obtained from
@echo size of .sign file -17 and correct the value
@pause

@echo amss.sin
@..\tools\dd if=../files/amss.sign bs=1 skip=13 count=4074>amss.sin
@..\tools\cat ../files/amss.bin >>amss.sin

Meaning that if the amss.sign file size is for example 5017, then you need to change the count into 5000.

If you finished to this step, you have the you decrypted rom almost ready, all you need to do is copy the amss_fs.sin, apps-log.sin, cache.sin, fota0.sin, fota1.sin from other debrand ROM you downloaded.

Then you have your decrypted ROM ready. Mission accomplished ;)