hi,
how can I extract the hole file system on rom/image files?
I would like to test a few things/apk from different releases, but I dont know how f.e. I can extract files from a rom...
Related
as topic says i want to extract some files from rom can any body tell how is it possible?
Hi,
I'm new here, and I want to make a custom firmware for my LG BL40. When I extract the .kdz file, there's a dz file. When I extract this file, there are many mbn files (like apps.mbn) and 3 .bin_1/2/3 files. It's the same with the LG GM750.
But how can I extract these .mbn files and the .bin_x files?
Thank you
Felix
is there nobody having an idea?
The little I've found is that mbn is an executable format.
Would seem to need to be decompiled.
I'm not sure on this and still looking around.
I'm not sure on this and still looking around
you need to use cygwin to extract files from your mbn files.
shreyas.kukde said:
you need to use cygwin to extract files from your mbn files.
Click to expand...
Click to collapse
Can you elaborate on your answer? what is needed to extract these files?
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to load, don't know how to modify it, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
if u wanna extract system.img then use dsixda kitchen.
put the img file in update original update folder then go to cygwin and choose make a working folder from rom.
it will identify your img file and then give an opt to extract it.
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...
I noticed that oreo was released on the Mate 9, I needed to grab some files from this device, particularly a file named "gps.default.so" or something around that located somewhere in system/lib64 or system/lib but a system dump would definitly be nicer.
Or, you can help me out in extracting the oreo firmware, I've downloaded it and extracted UPDATE.APP and used HuaweiUpdaterExtracter to then grab the system.img. But I can't mount it or extract anything from it. soo yeahhh
Extraction
Yuvch122 said:
I noticed that oreo was released on the Mate 9, I needed to grab some files from this device, particularly a file named "gps.default.so" or something around that located somewhere in system/lib64 or system/lib but a system dump would definitly be nicer.
Or, you can help me out in extracting the oreo firmware, I've downloaded it and extracted UPDATE.APP and used HuaweiUpdaterExtracter to then grab the system.img. But I can't mount it or extract anything from it. soo yeahhh
Click to expand...
Click to collapse
You can use superr's Android kitchen to extract everything from the system.img, he has a free version https://forum.xda-developers.com/apps/superr-kitchen
And for your information, that "update extractor" doesn't give you usable images as it strips the necessary header from the image. I had to use "splitupdate.pl" to get usable images. I have the extracted images, and there is no file called "gps.default.so" anywhere in the Oreo images, not in /system/lib, /system/lib64 or in /vendor/lib, /vendor/lib64. I do not have a dump of the nouget to check but the file does not exist in the Oreo images
EDIT:
Found the file, it is in the vendor partition, specifically /vendor/lib64/hw so you're going to have to extract vendor.img to get the file.