I have a samsung vibrant I need boot.bin and sbl.bin files (I found only the sbl.bin).
accidentally burned both files to a version of I9000.
I have no problem if these files are in the package UPDATE.
I gave up so I searched the entire web and not found.
Thanks to everyone who could help
I have a samsung vibrant I need boot.bin and sbl.bin files (I found only the sbl.bin).
accidentally burned both files to a version of I9000.
I have no problem if these files are in the package UPDATE.
I gave up so I searched the entire web and not found.
Thanks to everyone who could help
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?
yo
hi darren.hoo, i faced the same problem as yours and i realised that we should actually boot our tab to the downloading mode before we launch Odin3,pda.Turn on the usb debugging too(i dont know if this is necessary or not).Anyway happy flashing!
*Odin can only read .tar / .md5 extension ,you dont have to extract everything.
Kruel
Hi Darren.hoo,
To read the image files - It depends.
boot.img and recovery.img requires potentially a script to seperate the ramdisk and also the kernel. There are many good article on many wikis that explains which hex point is the seperator between the two.
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
bootloader.bin - you'll need a hexeditor of some sort. This is as is a bin file (data file)
Not sure about the others. (cache - i'd assume you can recreate anyway and the modem i guess is another binary that requires a hexeditor.)
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Hope this helps.
Really great tips!
frankus0512 said:
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
Click to expand...
Click to collapse
no luck with this:
debian:/home/darren/gtab/rom/EUR/P7500XWKG9# mount -oloop system.img /mnt
mount: you must specify the filesystem type
But from what I've got from searching xda a lot, maybe it's RFS filesystem?
frankus0512 said:
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Click to expand...
Click to collapse
this tip just really solved my problem.
I've got a tar.md5 file with three files in it: boot.img, system.img, recovery.img, but I don't
want to flash recovery.img coz I've already flashed CWM, yesterday I tried delete recovery.img from the tar ball and then flash it, then ODIN tells me that the files is invalid by
md5sum. I didn't know earlier that it records md5 checksum at the end of the tarball file.
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
span_01 said:
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
Click to expand...
Click to collapse
samsung firmwares should have -t rfs but you have to have a linux kernel on your dev machine that has a rfs modules
http://forum.xda-developers.com/showthread.php?t=1081239
darren.hoo said:
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?[/QUOTE,
........................................
hello,
you can extract system.img by android kitchen but it is long process to setup kitchen.
you make it .tar file to flash as pda in odin.
if you want to extract system.img, contact me by email, [email protected]
I will tell you .
Click to expand...
Click to collapse
Hi guys, I could successfully unpacked and repacked system.img on 4.0.4 for my Galaxy S III by learning from xda, add root files, delete unnecessary system apps, etc, and using "tar -cvf ...." to make an tar pack to flash with ODIN, thx to all xda developpers.
But when I did this again on new GSIII 4.1.1 firmwares like DI2, My phone jammed in the 2nd screen, could someone help me?
Here is what I did on 4.1.1 firmwares in Ubutu, just like what I did on 4.0.4
1. unpack system.img from tar files
2. exchange system.img to system.img.ext4 in Ubutu
3. unpack system.img.ext4 with
Code:
mkdir systest; mount -o rw,loop system.img.ext4 systest
oh just forget the folder name.
4. modify the files in systest folder blablabla
5. repack system.img from systest folder using
Code:
sudo mkuserimg.sh -s systest systest-new.img ext4 temp 1536M
6. then make a new tar file to flash with recovery.img, hidden.img etc.
This tar file could be flashed with ODIN successfully, but like I said above, my phone didn't response in the 2nd screen with Samsung logos, I've wiped userdata in stock recovery but it didn't work.
Then I didn't modify any files, just unpack and repack system.img, flash it with ODIN, my phone remains the same
Could someone kindly to figure it out what I did wrong on new 4.1.1 firmwares? Is it about Samsung file format in 4.1.1?
Oh no replies until now...:crying:
I tested other 4.1.1 firmwares, unpack and repack system.img, then zip into new tar file, flash it, also stuck on the Samsung Logo with vibration
but it worked on all 4.0.4 firmwares
I've been searching for awhile without any luck. Trying to make a firmware file and need the system.img to be converted to sparsechunk files. What is the best way to go about this?
bump