When I downloaded the shipped-roms, there are lots of .img files
I want to open them, but I dont know how to open, can anyone tell me?
How to open and edit the .img files.
On Linux you can mount the file if your kernel supports the yaffs filesystem, the other (easy) way is with a tool called unyaffs.
I think that in order to customize a ROM it needs to be in ZIP format, right?
At least in ZIP format I was able to browse the contents of ROMs while in FTF it didn't work with 7zip, or at least the contents are not easily readable.
So, can anyone help me converting FTF to ZIP? I'm on Windows 7.
I tried a tool called F2Z but it didn't work with my Sony Xperia Miro FTF ROM file.
Thanks in advance.
Cheers
Try with dsixda kitchen http://forum.xda-developers.com/showthread.php?t=633246
Sent from my D2303
john3voltas said:
I think that in order to customize a ROM it needs to be in ZIP format, right?
At least in ZIP format I was able to browse the contents of ROMs while in FTF it didn't work with 7zip, or at least the contents are not easily readable.
So, can anyone help me converting FTF to ZIP? I'm on Windows 7.
I tried a tool called F2Z but it didn't work with my Sony Xperia Miro FTF ROM file.
Thanks in advance.
Cheers
Click to expand...
Click to collapse
1. Open .zip with WinRar or 7zip. Extract system.sin
2. Use the sin extractor tool in FlashTool.
3. The result is a system.ext4 file.
4. If on Linux or OS X, mount it and zip the system folder. On WinRar you can use a tool like Ext2Extractor to do the job.
5. ????
6. Profit.
Hello everyone,
I am tying to make a "light" official rom of the Z3 by removing some *.apk of an *.ftf file.
I have extracted all the folders from the *.ftf (ftf - system.sin - system.ext4 - files...) and removed all the apk I don't want, but I don't know how to make a new "system.sin" from all the files I have extracted. I looked from the internet, but I am a little noob.
Can someone help me to build a new *.ftf file to flash it with Flashtool ? :crying:
Dracow said:
Hello everyone,
I am tying to make a "light" official rom of the Z3 by removing some *.apk of an *.ftf file.
I have extracted all the folders from the *.ftf (ftf - system.sin - system.ext4 - files...) and removed all the apk I don't want, but I don't know how to make a new "system.sin" from all the files I have extracted. I looked from the internet, but I am a little noob.
Can someone help me to build a new *.ftf file to flash it with Flashtool ? :crying:
Click to expand...
Click to collapse
As far as i known you can't edit .sin / .ftf files as they are signed using sony private key that no one has...
Technical info here:
https://gist.github.com/dosomder/8ed79b26a5e063efa5ef
"And that is the reason why we can not create custom firmwares for Xperia. If you still don't understand, RSA is an asymmetric function.
This means it's using a private key to create the signature and a public key to read it. So even if we find the public key
(which is somewhere on the device), we can never find or guess the private key. Therefore we can not create a valid signature."
But you can create a .zip firmware to be flashed via recovery
I used Flashtool-sin editor on "system.sin" that give me "system. ext4".
With ext2explore I opened " system.ext4" and extracts all files and folders (app, privateapp, etc, build.prop...).
From folders "app" and "privateapp", I removed the *.apk I don't want, but I don't know if I can build a new " system.sin".
There is really no way to reverse ? Make a "system. ext4" from the folders I modified, and convert it in "system.sin" ?
If we can do something in a way, can't we do it on "reverse way" ?
Dracow said:
I used Flashtool-sin editor on "system.sin" that give me "system. ext4".
With ext2explore I opened " system.ext4" and extracts all files and folders (app, privateapp, etc, build.prop...).
From folders "app" and "privateapp", I removed the *.apk I don't want, but I don't know if I can build a new " system.sin".
There is really no way to reverse ? Make a "system. ext4" from the folders I modified, and convert it in "system.sin" ?
If we can do something in a way, can't we do it on "reverse way" ?
Click to expand...
Click to collapse
It cannot be done. 100% impossible.
If you want to make your own rom Google [NUT]'s method to create your own rom.
There is also a tool to create your own prerooted flashable zip, but if course, all of this requires root
Thanks a lot for all your answers...
I won't try to make it in zip...
Hi!
I'd like to know where the OTAs are stored in our M2. Anyone that hasn't done yet the update download, and that has Root permissions, can use this app to find where they're stored, and if possible, upload it and post a link to it.
Thank you!
Do you still needed the file, sir ?
FunSucker said:
Do you still needed the file, sir ?
Click to expand...
Click to collapse
Yep. It's for some research
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
FunSucker said:
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
Click to expand...
Click to collapse
Yes please! Thanks
oke, sir. when finished i will share the link.
Oke sir, check this out --> Google Drive
FunSucker said:
Oke sir, check this out --> Google Drive
Click to expand...
Click to collapse
Great, thank you very much!
Okay, so this is what I got:
The update zip refuses to be flashed in UBL devices. FOTAkernel system is broken after you open the bootloader, which leads us with an unused partition (but that's other thing). The recovery logs just say: WARN: Status Rooted, ERR: Bootloader is unlocked.
I've tried to force it using AOSP Recovery commands
Code:
echo 'boot-recovery' > /cache/recovery/command
echo '--update_package=/sdcard/update.zip' >> /cache/recovery/command
reboot recovery
But just got a big nope.
So, now time to have a look at it. I tried to unpack it several times but no luck. The reason seems to be, very probably, because this is a LZMA compressed file (as 7-Zip reported) but with 2 additions at the end (which corrupts the entire read of it): An unencrypted/uncompressed XML which points out which is the software available right now in the phone (<source>), and which is the version that is going to be installed (<target>), plus, some a weird <generation> section. This is the XML
Code:
<?xml version='1.0' encoding='ISO-8859-1'?>
<metadata version="3.3">
<product>
<manufacturer>Sony</manufacturer>
<model>D2302</model>
<hwplatform>msm8226</hwplatform>
</product>
<update>
<generation>
<version>1.1.2</version>
<date>2015-12-28T12:10:19Z</date>
<rb_version>7.0.15.117</rb_version>
<rb_ua_version>7.0.15.117</rb_ua_version>
</generation>
<source>
<software>
<revision>18.6.A.0.175</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</source>
<target>
<software>
<revision>18.6.A.0.182</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</target>
</update>
</metadata>
And, right after that, I can perfectly see a SIN header, so I isolated it and, looks quite similar to the FOTAkernel.sin included in FTFs (330613072905Z010U S1_FOTA0 ‚"0), I personally guess it's a very, very small ELF binary, by the size of it.
So, the problem now comes to isolate the 3 parts, the LZMA file, the XML and the SIN, separetly. After that, I think we can probably have a look insde them.
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
FunSucker said:
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
Click to expand...
Click to collapse
I've tried many tools and combinations (ext4, .img, etc) and none of them worked... I'll think more about it.
Hi all
I want to extract all system files from LL system.sin to deodexed so i used flashtool to convert it to .ext4 but Linux reader cant see anything in system.ext4
Please help. thanks
Try ext2explore. It works flawlessly with Z5's ext4 file.