Hi,How to extreact file vendor.img by use tool ?
Thank you.
If it's a raw image then you'll need to convert it into something readable first with a tool such as simg2img.
Afterwards, use a program to mount the ext4 image if you're on windows, or mount it with the mount command if you use linux, then you're free to extract it.
Related
I'm confused on how to extract blob files using blob tools. I am running Windows XP and 7 and this is my first port
If anyone could guide me through the steps with appropriate commands in command prompt, that would be great.
Blob tools is nice and simple to use
To extract a blob:
1. Download the ROM.zip or other multiple partition blob file and extract the file called 'blob' (Or 'recoveryblob' or whatever..) out of it.
2. Place the 'blob' in the same folder as 'blobunpack.exe' (You can rename it if you have multiple blobs and need to distinguish them)
3. Open up cmd.
4.
Code:
cd C:\directory\of\blob
blobunpack blob (Or the name of the blob, no extension required)
[I]Let it do it's thing for a moment...[/I]
exit
5. You will now have many blobs with different file extensions, each of these file extensions is a different partition of the TF.
EBT is the bootloader
SOS is the recovery
APP is the os, and etc...
Good luck.
I can't speak for Windows, but in linux, it's pretty easy. The commands would be
blobunpack <insert blob here>
you'll get some or a bunch of files like blob.APP, blob.LNX, blob.SOS, blob.EBT. It depends on what is packed in the blob. A proper blob will start with MSM RADIO UPDATE or something like that. If not, it's not a packed blob, but probably just blob parts.
EBT is the bootloader.
APP is an ext4 filesystem that you can loop mount in linux. Don't ask about windows.
SOS and LNX are boot images/Android! magic files that you can unpack wiht the boot tools (bootunpack). Rebound has a thread in the dev section about making an insecure boot image- it sounds unrelated, but it has all the information about boot.img's.
As far as getting the tools, I think there might be some windows binaries floating around, but again, I can't speak from experience. If you have linux, you can just compile them from source and go to town. Grab the boot tools while you are at it and save yourself some time.
Hello !
I'm trying to set up a dual boot with Ubuntu and Android on my TF101.
I'm using Frank's Tool to do so.
I know i must have the boot.img the recovery.img and the system.img files, and that is the problem : i can't manage to dump my current ROM in img format. I tried with several Recoveries, but i just can't...
All i have in the best scenario is the following :
boot.img
recovery.img
system.ext4.dup
or :
boot.img
recovery.img
system.ext4.tar.a (400+ mb) and system.ext4.tar (0 kb)
Is there any way to grab the system.img from my current ROM, of am i forced to use the one provided in OLiFE Prime (which is fully stock... :crying: )
Many thanks in advance.
What file formats are the .img files? Linux doesn't care about the extension at the end like windows does. You could name the file dog_food.blah and linux is just as happy.
If you just need dumps of the partition, then the dd command will work for system. These will probably be ext4 filesystems.
What are the file types of the olife files that you want to change? From the linux command line, you can just type "file <some system.img here>" and it will tell you. I'm guessing it will say ext4 filesystem. Those tar files you have can probably be converted to what you need.
Disclaimer, I haven't dual booted my tablet and I don't know a thing about Frank's tools.
EDIT: I spent 30 seconds looking at Frank's tools, which appear to be an nvflash interface for windows. I suppose this means you want everything in an nvflash-able format. boot.img and recovery.img will be ANDROID! packed files, while system.img will be an ext4 filesystem.
To be sure, boot.img and recovery.img will start with ANDROID! There are also some boot tools by Rayman and other sources if you want to manipulate these. I think you can grab the system with "dd if=/dev/block/mmcblk0p1 of=/Removable/MicroSD/system.img" It will take a while and will be a large file, maybe 500MB. Depending on where your sdcard is, you might have to change that bit around.
If any of this doesn't make sense, then feel free to google or ask. Good luck!
i need to figure out How to differentiate between Sparse Img and raw img because i want to mount a raw img so that i can edit the apks and jar files in it.
i have a file named system.img but whenever i am trying to mount it using the command "sudo mount -t ext4 -a loop system.img outout/" i am unable to get the apks and jars to edit.
i also want to know how to make a binary file executable.
in short i want to get the system folder which contains the framework,apks,media,bin,xbin,usr,etc...folders and i am a noob in ubuntu. I have the rom inside which is the system.img but i dont know how to extract the system.img and weather the system.img is in a raw stste ot sparse state and i have all the binaries in that same folder such as simg2img,img2simg,make_ext4fs,etc.... but i dont know how to use the binaries.
i am using a VirtualBox with windows 10 as host and Ubuntu 16.04 as guest.
So can anyone help me with this.
Hey everyone!
Basically I am trying to create a custom ROM for my Lenovo TB3-850M, I downloaded the firmware and I got all the Mediatek images such as preloader and boot-sign.img and system-sign.img but I was unable to unpack system-sign.img using ASSAYED Kitchen or SuperR Kitchen or any third-party system.img unpacker. Any help will be appreciated! Note that I can use both Linux and Windows.
If you want to try to unpack it download the firmware from here: http://lenovo-forums.ru/files/file/1621-lenovo-tab3-a8-tb3-850m_s100034_170217_row/
Thanks in advance!
Regards,
addas
I'd like to unpack the system-sign.img of a Lenovo Vibe B stock ROM, using a Linux computer (no Windows available). Magic is BFBF... Flashing with SP and backing up with TWRP is not an option. Thanks -
Update: Did it. Here's how:
- extract system-sign.img from firmware archive
- dd if=system-sign.img of=system.img bs=$((0x4040)) skip=1
- simg2img system.img system.ext4
- mount -r -t ext4 -o loop system.ext4 /mnt
- PROFIT.
simg2img can be found here: https://github.com/bgcngm/mtk-tools.git (no source though). The unpack-MTK.pl script doesn't recognize the (special?) magic of this firmware, thus one has to simply skip the MTK headers and let the subsequent steps ignore the trash at the end of the file (checksum, etc.). Before running simg2img you may get an idea of the unsparsed file(system) size from "file system.img". HTH!
@addas4, did you eventually succeed? Of course, repacking is still an unresolved issue...
~~
Hello,
I've followed this tutorial (https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/) to extract system.img from super.img and edit it. So far, I was able to extract system.img from super.img and mount it to a folder in fedora. The problem is I cannot modify the files, I tried all ways I could think about but had no luck as the source is write-protected, so it only mounted it as read-only. I tried to copy all the files to different folder using rsync, but the system.img file is getting bigger than original and when I make it to super.img with lpmake, the phone doesn't work and stuck in bootloop. Does anyone has any idea about this?
Thank you