Related
Fastest way to decrypt your own branded ROM by Binary
Bin4ry said:
FYI:
You can also use the new tool here. Usage:
SEUSDECRYPT.BAT FILE_XXXXXXXX -> That gives you a FILE_XXXXXX.tgz -> Unzip -> Then Untar the File which comes out
If you SEUSDECRYPT the small 64kb File you get directly the loader.sin no need to unzip and untar
Regards
Bin4ry
Click to expand...
Click to collapse
You may find the ConvertTools below.. This is just sick
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
Code:
@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
For those asking why dump0 and dump1 will create same files, except for extra 8699.bin and 8699.sign, i just recreate the dump guide, i don't know if you just do with dump1 straightaway will get you the same thing if you do dump0 and dump1. too lazy to test.
Both Dump0 and Dump1 present will work
i really dont gettin over it,
could you please be so nice and do the decrypting of my A1 ( Austria) files?
kind regards DAuL
is not that i don't want to help. but decrypting rom requires you to flash your x10 with the targeted rom first. which means i need to reflash mine and do the whole thing again.
which part of the process give you.trouble. i'll help you solve it.
Sent from my X10i using Tapatalk
Could this thread be stickied?
bump! mod, make this stickie... please
If next root update come, which means i might reset my whole phone and root, and configure all over again, i might as well help you guys decrypt your branded ROM.
Please upload somewhere like megaupload or hotfile (except rapidshare) for me to download, and later i'll decrypt and post to the decrypted branded rom thread.
http://hotfile.com/dl/53464337/95a1a90/R2BA023_Nordic_Generic.rar.html
Can you plz decrypt this ?
Sent from my X10i using XDA App
Link broken. Upload again
Will Do Sunday, 2 more Days of holiday atm
Sent from my X10i using XDA App
just have it uploaded before root fw 26 comes. as well for anyone else which wanted for me to help decrypt their branded rom
Sent from my X10i using Tapatalk
To late i guess, i used the exploid root method and rooted the R2BA026 Nordic Generic firmware myself so its not needed anymore, but thanks anyway
MrKingLouie said:
To late i guess, i used the exploid root method and rooted the R2BA026 Nordic Generic firmware myself so its not needed anymore, but thanks anyway
Click to expand...
Click to collapse
Wow, that's good for you. Where is this exploit root method discussion anyway. Seems that i missed the posts. Even though i doubt i will use the exploit to root SingTel firmware now which is still a R2BA020 fw. hahaha.
we are couple steps behind the other, because the fw contains SingTel Timescape Live Traffic Update mods.
http://forum.xda-developers.com/showthread.php?t=740240
Seems to work on all firmwares up to 026
xeviro said:
Where is this exploit root method discussion anyway. Seems that i missed the posts.
Click to expand...
Click to collapse
It's here:
X10 Mini/Pro Root Method
You probably missed it because you thought it was about the X10 Mini/Pro. Actually, it started with instructions for using the new "exploid" root for the Mini, but then it was discovered that it also works (as is) with the X10.
The good thing about this root method is that you don't have to debrand or downgrade in order to use it. In other words, you can stay with whatever ROM you currently have and not have to lose apps, contacts, SMS, etc. But of course you can also debrand it and then root it if you want (which is nice if you want the latest firmware).
EDIT: Oops, MrKingLouie already posted the link.
Grospolina said:
It's here:
X10 Mini/Pro Root Method
You probably missed it because you thought it was about the X10 Mini/Pro. Actually, it started with instructions for using the new "exploid" root for the Mini, but then it was discovered that it also works (as is) with the X10.
The good thing about this root method is that you don't have to debrand or downgrade in order to use it. In other words, you can stay with whatever ROM you currently have and not have to lose apps, contacts, SMS, etc. But of course you can also debrand it and then root it if you want (which is nice if you want the latest firmware).
EDIT: Oops, MrKingLouie already posted the link.
Click to expand...
Click to collapse
Yes, unless your branded firmware stucks with R2BA020 like mine. Thanks for the replies anyway. I flashed mine with R2BA026 and root it.
xeviro said:
Yes, unless your branded firmware stucks with R2BA020 like mine. Thanks for the replies anyway. I flashed mine with R2BA026 and root it.
Click to expand...
Click to collapse
Cool. By the way, thanks for the tutorial. I managed to decrypt X10a Generic LAM R2BA026 with it. And heeeere it is:
X10a Generic R2BA026 (with X10Flash)
I'm trying to rip my branded rom but when i follow the steps i encounter some problems:
Step 1. after downloading the rom and flasing it to the x10 i cant find files ready & next flashed.
Step 3. I cant find the folder root in seus
Step 4. same as step 3
can someone help me?
Ok found the correct folders now but after replacing the plugin file SEUS wont start any more
ok, got it working. here are my dump files:
http://hotfile.com/dl/68373185/517b6c4/dump.rar.html
can anyone decript them for me?
Hi guys, Im trying to bring my phone back to rogers stock firmware and I can't seem to do it. I downloaded the unbricker tool and the firmware, which has 2 files named "1" and "2". I got no idea how to use the firmware with the unbricker tool, so can someone help me?
Thanks in Advance
Sounds like you downloaded the SEUS firmware files and you are trying to use the debricker tool which requires .sin files.
You can use the 1 and 2 file with SEUS software by following the instructions in that thread. You basically need to replace the files in a directory for SEUS while it's downloading them. One file is 16mb and the other is 125mb+. There may be a better firmware for you to download for use with the debricker.
wait im confused by your post can you try and maybe explain it a bit clearer? thanks
The 1 and 2 file are for use with the Sony Ericsson Update Service (SEUS) and not the debrick process. You'll need the Rogers files that are intended for use with the debricker and not the ones you have.
It is possible to use the 1 and 2 files to restore your phone to stock but it's more complicated and I'd suggest just getting the correct files.
I believe you need the first file (WWE_R1FA014 under X10a) in this thread:
http://forum.xda-developers.com/showthread.php?t=683793
okay and do I replace all the files? because when I tried to only replace the ones already there, it gave me the exclamation mark and I had to go back to the debranded version.
Read the thread for decrypted roms. You need to replace the .sin files from the flash tool with the .sin files from the firmware version you downloaded from that page. Then run the flah tool with the new files in it. Its pretty simple once you figure it out.
Sent from my X10i using XDA App
do I only replace the .sin files? and do I add the extra .sin files in?
Files 1 and 2 are not files that we are looking for.That link bring us wrong files.
Now do one thing download flash tool from here http://hotfile.com/dl/44983907/9d54b5e/XIOFUB.rar.html
Then downlaod files from this link http://hotfile.com/dl/43225669/598ad...4_DEK.zip.html.
The file we download from this link has two folders.extract them then copy files from them to flash tool folder. Then root your xperia x10 and you are ready with RB014 original one. You can update it from SEU. EASY!
hmm, everytime I replace the files, my xperia x10 gets the bricked picture. Do I HAVE to root it before reflashing?
edit: there is an "update.xml" file in the android.... folder and the phone folder. Which one do I use?
corruptfate said:
hmm, everytime I replace the files, my xperia x10 gets the bricked picture. Do I HAVE to root it before reflashing?
edit: there is an "update.xml" file in the android.... folder and the phone folder. Which one do I use?
Click to expand...
Click to collapse
In the Rogers rom file, there should be two zip files in there.
- android_1233-6929_R11A_R1FA014.zip
- phone.zip
Now
- Unzip the flashtool first, and then unzip the phone.zip to the flashtool folder and replace any files it prompts.
- Unzip android_1233-6929_R11A_R1FA014.zip and replace any files it prompts.
- Rename or delete System.sin and userdata.sin inside the flashtool folder.
- Rename system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin to system.sin
- Rename userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin to userdata.sin
Try to flash the phone again see if this will work (Just tried it yesterday, it worked for me.)
Regards
Sony-Ericsson System SIN 2 Android System IMG Converter
Here it is...
http://dl.dropbox.com/u/10158456/SIN2IMG.rar
i have successfully unpack around 10 SE x8 system.sin files..
could you try to unpack few more and give feedback thank you...
I have idea!
If someone back up system image of rooted 2.1 phone then i flash my phone with this image will i get rooted 2.1
as-mario said:
I have idea!
If someone back up system image of rooted 2.1 phone then i flash my phone with this image will i get rooted 2.1
Click to expand...
Click to collapse
it's not easy as you think. to flash the rom, you need rooted system.sin. .sin files only can be signed by sonyericsson.
take a look at this thread instead. all your idea is in this. lol. btw, this method works
http://forum.xda-developers.com/showthread.php?t=876868
Thats app creates .sin files.
as-mario said:
Thats app creates .sin files.
Click to expand...
Click to collapse
No. that app used to convert .sin from decrypted rom from SEUS to .img..you can extract it using unyaffs. trust me.
Ok convert sin to img.
Why then cant convert img to sin.
Coz SONY sign every sin they do, phone doesnt take unsigned sin files
Sent from my E15i using XDA App
I dont get it, after i have downloaded it, there is an EXE file, after i double clicked it, nothing happens = =
I am using windows 7 x64, and i have tried to set its capability with windows xp, still nothing happens~
Can anyone help?
it is command line app...
so you need to start -> run -> cmd
aZuZu said:
it is command line app...
so you need to start -> run -> cmd
Click to expand...
Click to collapse
but, after i got into there, nothing was happening, it said
"aZuZu SE SIN2IMG, v1.02.3 <c> anZuZu 2010.
Usage" System.Sin System.Img"
can anyone help >.<
usage: system.sin System.img
so in cmd
you write sin2img [path to your system.sin file] [path where you wanna to put new created system.img file]
This is freakin' brilliant! Thanks!
Edit: Make a Linux version.
have a try
It works with mono?
Edit: Okay.. So now it's a .img file. How do I crack this open and start playing around with it?
greetings..
thanks to all for trying...
as i recall there is kernel support for yaffs imgs with cloop.. or something..
but hey i'm xp user..
So the file is yaffs?
yaffs
a-k-t-w said:
So the file is yaffs?
Click to expand...
Click to collapse
it is actually yaffs v2.0 but mounting should be possible in linux
in win32 can be extracted with tool unyaffs.exe
Can anyone reupload the SIN2IMG tool ? I can't find any valid download link for it.
http://forum.xda-developers.com/showthread.php?t=979912
use aIUP from here rather...
I only need to convert it to img... i dont need to unpack it... Why there isn't any mirror with that tool ? is there something wrong with it ?
Hello!
As I'm currently learning about ROMs etc, I feel its important to be able to convert sin->img and then extract on my own.
The problem is however, I haven't been able to do that with the Xperia S system.sin.
I know that the .img is ext4 and not yaffs, but stuff I've tried without luck;
sin2img - errors out
aIUP - gives bad block no matter what
sin2img.py under ubuntu 10.04 - completes, but the output file seems to be corrupt (won't mount)
flashtool->sineditor->dump - same output as sin2img.py. ext2explore can extract the apps folder but nothing else. build.prop comes out corrupt
I redid the sin2img.py to .exe and ran under windows, produces same file as sin2img.py, still not working.
I've seen a couple of extracted filesystems from Xperia S, but I want to find out how they got extracted. PMs often get ignored or people are just too busy to respond so I ask here instead.
I've tried following firmwares;
LT26i_6.1.A.0.452_NCB.ftf
LT26_6.1.A.0.452_Generic_CH_1257-3740_.ftf
LT26_4.0.4 _6.1.A.0.452.ftf
Any help is greatly appreciated, thanks in advance!
I'm also encountering this problem.
Sent from my LT26i using xda premium
If someone could provide a successfully converted system.sin to .img, I could look at what goes wrong at my computer. And I'm talking about system.sin from ICS firmware.
Else the only thing I can think of is that all the system.sins I've tried have been corrupt or something likewise, since userdata.sin converts just fine
Bumping this because I have the same issue with the Xperia S system.sin and Xperia ion.
Getting an error such as this in the dmesg | tail after doing the "mkdir system; mount -t ext4 -o loop system.img system" command when trying to make a prerooted system image
EXT4-fs (loop0): bad geometry: block count 262144 exceeds size of device (140642 blocks)
Click to expand...
Click to collapse
Using ext2explore instead of yaffey guys. It's Xperia S firmware, not Xperia Arc
Phenombox said:
Hello!
I know that the .img is ext4 and not yaffs, but stuff I've tried without luck;
ext2explore can extract the apps folder but nothing else. build.prop comes out corrupt
Click to expand...
Click to collapse
lilude56214 said:
Using ext2explore instead of yaffey guys. It's Xperia S firmware, not Xperia Arc
Click to expand...
Click to collapse
He already mentioned ext2explore and that didn't work.
Sorry to revive this old thread. But I'm having the same issue and hopefully a solution has been reached within the last 2 years?
really don't understand what your guys talking about but im using winrar to extract ftf firmware file, then use flashtool to extract .sin file, then use ext4_unpacker to extract ext4 image file, thats all.
GVN.Gallus said:
really don't understand what your guys talking about but im using winrar to extract ftf firmware file, then use flashtool to extract .sin file, then use ext4_unpacker to extract ext4 image file, thats all.
Click to expand...
Click to collapse
My Flashtool is just null when you try to open a .sin file. So something isn't right lol.... Nevermind.. I think it really WAS a corrupt file. Tried fresh and it is good now
enigma99a said:
My Flashtool is just null when you try to open a .sin file. So something isn't right lol.... Nevermind.. I think it really WAS a corrupt file. Tried fresh and it is good now
Click to expand...
Click to collapse
Hi bro, what did you do to make it work? I've tried many times with different firmwares, extracting the system.sin with Winrar, then Extract data with sin editor in flashtool, and when I use the ext4_unpacker with the system.ext4 file, it says "Unknown file format". :crying:
In case my files are corrupted, how can I validate that? Please any help is really appreciated. Thanks!
brau__lio said:
Hi bro, what did you do to make it work? I've tried many times with different firmwares, extracting the system.sin with Winrar, then Extract data with sin editor in flashtool, and when I use the ext4_unpacker with the system.ext4 file, it says "Unknown file format". :crying:
In case my files are corrupted, how can I validate that? Please any help is really appreciated. Thanks!
Click to expand...
Click to collapse
Well... I am not exactly sure what causes that 100% but I think in some cases there might be some kind of encryption or something that is not allowing it to fully decode. But if you have tried many of them, I think something must be going on on your side. Maybe try unpacking with something besides winrar, etc. Also make sure you have the latest and greatest sin editor?
Are you able to successfully extract the data without errors in your sin editor?
HI !!!
i have tried several meothods but fail !!!
i have used Flashtool to extract file from system.sin but didnt get anything ...
also use ftf extracter but not work also ,,
i have used ext4 extracter but that also give wrong file size parameetor error in cmd ..
what should i do ???