Add language
I test samsung s2 i9100
Extract I9100XXLPQ.tar.md5 --> factoryfs.img (sgs2toext4.jar) --> factoryfs.ext4.img
Ubuntu
...
mkdir /mnt/system
mount factoryfs.ext4.img /mnt/system
cp framework/*.apk /mnt/system/framework/ <---Language change here
cp app/*.apk /mnt/system/app/ <---Language change here
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
umount /mnt/system
step1:
tar cvpf factoryfs.tar factoryfs.img
md5sum -t factoryfs.tar >> factoryfs.tar
mv factoryfs.tar factoryfs.tar.md5
factoryfs.tar.md5 flash with odin failed
step2:
tar -H ustar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
your_odin_package.tar.md5 flash with odin
boot.bin ok
cache.img ok
factoryfs.img <--- failed here
....stop here.....
please, help me!
Thanks!
thanhlapvn said:
Add language
I test samsung s2 i9100
Extract I9100XXLPQ.tar.md5 --> factoryfs.img (sgs2toext4.jar) --> factoryfs.ext4.img
Ubuntu
...
mkdir /mnt/system
mount factoryfs.ext4.img /mnt/system
cp framework/*.apk /mnt/system/framework/ <---Language change here
cp app/*.apk /mnt/system/app/ <---Language change here
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
umount /mnt/system
step1:
tar cvpf factoryfs.tar factoryfs.img
md5sum -t factoryfs.tar >> factoryfs.tar
mv factoryfs.tar factoryfs.tar.md5
factoryfs.tar.md5 flash with odin failed
step2:
tar -H ustar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
your_odin_package.tar.md5 flash with odin
boot.bin ok
cache.img ok
factoryfs.img <--- failed here
....stop here.....
please, help me!
Thanks!
Click to expand...
Click to collapse
I think tar cvf factoryfs.image is basically just a tar file not a repacked ext4.image file so i think you should use the command or a tool to repack the image file and that you should continue step 1 or 2 with the repacked file, so what I am suggesting is you dont need these two lines
tar cvf factoryfs.img /mnt/system <---suspect here (!)
e2fsck factoryfs.img <--- can abort
after unmount, repack it in whatever way you like ,then proceed with step 1 or 2 with the repacked file.
Edit:And by repacking I dont mean compressing into a tar again, there maybe tools available for repacking.
Hmm I been meaning to ask you but did you try pushing both apk via a signed zip file through the stock recovery?
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
Hmm I been meaning to ask you but did you try pushing both apk via a signed zip file through the stock recovery?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I create update zip (cwm) change language ok but i like build md5 flash via odin (no need recovery, no need root, no need update ver same ver pack update...)
thanhlapvn said:
I create update zip (cwm) change language ok but i like build md5 flash via odin (no need recovery, no need root, no need update ver same ver pack update...)
Click to expand...
Click to collapse
Lol, yeah to each his own preferences. But I always prefer the shortest way, where minimal action is needed, and with root I can make most changes from inside the OS, but I am intrigued which language did you insert?
Edit :Since the matter is over add Solved in title.
Sent from my GT-I9100 using xda app-developers app
Related
Hi,
Can anyone please provide me T959TLKG2 modem for download.
thanks in advance for any help given.
demetris_I said:
Hi,
Can anyone please provide me T959TLKG2 modem for download.
thanks in advance for any help given.
Click to expand...
Click to collapse
I don't think you can rip the modem.
Hi,
Thanks for your reply.
You can rip the modem using root explorer after you rooted the phone.
Browse system with root explorer and find modem.bin copy paste it onto sd card and the post it here
demetris_I said:
Hi,
Thanks for your reply.
You can rip the modem using root explorer after you rooted the phone.
Browse system with root explorer and find modem.bin copy paste it onto sd card and the post it here
Click to expand...
Click to collapse
I just searched EVERY directory, there is no modem.bin to be found. It can't be ripped in anyway with a stock rom.
Are you rooted?
With root, run adb and use:
adb shell
su
cat /dev/block/bml12 > /sdcard/modem.bin
dd if=/dev/block/bml12 of=/sdcard/modem2.bin bs=4096
exit
exit
Then md5 them to see if they are the same but i think cat /dev/block/bml12 > /sdcard/modem.bin will do the trick just fine.
demetris_I said:
Are you rooted?
With root, run adb and use:
adb shell
su
cat /dev/block/bml12 > /sdcard/modem.bin
dd if=/dev/block/bml12 of=/sdcard/modem2.bin bs=4096
exit
exit
Then md5 them to see if they are the same but i think cat /dev/block/bml12 > /sdcard/modem.bin will do the trick just fine.
Click to expand...
Click to collapse
I've got the modem.bin file for you, where can I put it so you can download it
EDIT: N/M I just made a mediafire account... I will post link as soon as I know which is proper file to post for you.
When I md5sum, I'm a little confused... heres what I did..
for one I did
md5sum -t t959_gb_modem.tar >> t959_modem.tar (not a type, did use different filenames)
mv t959_modem.tar t959_modem.tar.md5
This left me with 2 files... one which was the tar modem, 12.8mb,
t959_gb_modem.tar... and the other file was 1kb, t959_modem.tar.md5
The second time I did this...
md5sum -t t959_gb_modem.tar >> t959_gb_modem.tar (same filenames)
mv t959_gb_modem.tar t959_gb_modem.tar.md5
this left me with one file, 12.8mb, t959_gb_modem.tar.md5
I guess what I need to know is which is the proper method to use so the file will flash in ODIN.
As for the tar command, I use tar -H ustar -c modem.bin > t959_gb_modem.tar
thx, Maniac
I dont need odin flashable, just zip/rar it and upload it, thanks
Modem.bin should be 12,0 MB (12.582.912 bytes) when right click and select properties on it
Multiupload would be great.
http://www.multiupload.com/
thanks again
P.s
for odin flashable tar size should be:
Size:12,0 MB (12.585.032 bytes)
Size on disk: 12,0 MB (12.587.008 bytes)
After you have the correct modem.bin
Modem.bin should be 12,0 MB (12.582.912 bytes) when right click and select properties on it
Then to make it odin flashable you need a linux live cd or linux installation on hdd then:
tar -H ustar -c modem.bin > T959TLKG2.tar
MD5 it for a security check:
md5sum –t T959TLKG2.tar >> T959TLKG2.tar
Rename the tar file like this:
mv T959TLKG2.tar T959TLKG2.tar.md5
And you will have:
T959TLKG2.tar.md5
Odin flashable
The file I have is 12.8m so I think
there may be something wrong. But i'm at work now so I can't upload now.
Sent from Samsung Fascinate (XDA Prem)
No problem, and thanks.
Maybe you see what reported 12.288kb which is correct
Thanks for everything, modem found in full dump link by harimgs.
great modem btw
Can anybody tell me how i can mount a system.img (under the linux)?
I would like to change any files and repack to odin flashable file.
Is this possible or not??
Thx
TiBiSMART said:
Can anybody tell me how i can mount a system.img (under the linux)?
I would like to change any files and repack to odin flashable file.
Is this possible or not??
Thx
Click to expand...
Click to collapse
I hope this will help you..
http://www.freeyourandroid.com/guide/building_roms_for_odin
TiBiSMART said:
Can anybody tell me how i can mount a system.img (under the linux)?
I would like to change any files and repack to odin flashable file.
Is this possible or not??
Thx
Click to expand...
Click to collapse
i helped myself (and http://andwise.net/?p=403)...
mkdir sys
./simg2img system.img sys.raw
mount -t ext4 -o loop sys.raw sys/
change what you want...
./make_ext4fs -s -l 1610612736 -a system new_system.img sys/
put the system.img to the odin flashable tar (extension only .tar not tar.md5!!!)
Hello, everybody.
In this tutorial we draw our One Package Samsung Rom format. Tar.md5 to get it in parts, the necessary files in Odin so that allows passing the full rom, change, or remove portions of it, before the flash, as CSC and MODEM . In the example, I will work with the Galaxy Ace S5830B.
Required:
1) Cygwim;
2) Rom file in .tar.md5.
Tutorial
1º) Download and install Cygwin from the link above. See the video tutorial to help you install:
2º) Get rom servers: SamMobile, Samsung Updates ou Information 4 All/
3º) Go to the folder C:\cygwin\home\Assis¹ and create a folder called ROM.
4º) Extract the zip and move the rom tar.md5 to the folder C:\cygwin\home\Assis\ROM:
5º) With everything ready to go work. Open a terminal and type Cygwim:
cd rom
Click to expand...
Click to collapse
5.1) Let us create the first package, APBOOT:
tar -xvf S5830BVJLP4_S5830BVJLP4_S5830BZTOLP4_HOME.tar.md5 arm11boot mibib oemsbl qcsbl
tar -H ustar -c arm11boot mibib oemsbl qcsbl > APBOOT.tar
md5sum -t APBOOT.tar >> APBOOT.tar
mv APBOOT.tar APBOOT.tar.md5
Click to expand...
Click to collapse
6º) Creating CODE:
tar -xvf S5830BVJLP4_S5830BVJLP4_S5830BZTOLP4_HOME.tar.md5 boot.img recovery.img system.rfs
tar -H ustar -c boot.img recovery.img system.rfs > CODE.tar
md5sum -t CODE.tar >> CODE.tar
mv CODE.tar CODE.tar.md5
Click to expand...
Click to collapse
7º) Creating MODEM:
tar -xvf S5830BVJLP4_S5830BVJLP4_S5830BZTOLP4_HOME.tar.md5 amss
tar -H ustar -c amss> MODEM.tar
md5sum -t MODEM.tar >> MODEM.tar
mv MODEM.tar MODEM.tar.md5
Click to expand...
Click to collapse
8º) Creating CSC:
tar -xvf S5830BVJLP4_S5830BVJLP4_S5830BZTOLP4_HOME.tar.md5 csc.rfs
tar -H ustar -c csc.rfs> CSC.tar
md5sum -t CSC.tar >> CSC.tar
mv CSC.tar CSC.tar.md5
Click to expand...
Click to collapse
Okay, now just go on Odin and put each file in its place and flashing.
Let the tests:
Credits:
Adaptation of these posts: [HOW TO] Extracting baseband from .tar.md5 and Custom Odin images
Obs. :
You need to know what files make up each package. You can use any ROM already extracted to base.
¹Folder name must match the Windows user.
Note:
To Moderators
Since I'm not a good English and used Google translator to transcribe the Brazilian forum post where I created, I ask kindly make corrections of spelling and grammatical English to entedimento best of all.
This tutorial is for all Samsung rom in tar.md5 therefore evaluate the best location for posting.
Thank you.
nice tutorial dude:good:
this was very useful ty
I've tried multiple methods, but I can't seem to get the pre-rooted ROM to flash properly, however, the completely stock ROM flashes just fine, so I'm wondering what in the heck I'm doing wrong.
Here's what I've done after I add the su binaries and deodexed:
-- make_ext4fs WITH -s
-- make_ext4fs WITHOUT -s
-- make_ext4fs WITHOUT -s THEN img2simg
-- This method
After those, I tried these:
-- tar -H ustar -c sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin >> Flash.tar
-- tar cfx Flash.tar sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin
-- Using 7zip to add the file to a pre-existing tar
-- Renaming system.img to system.img.ext4 (Didn't fail, but it just hanged at recovery at the top and system.img.ext4 as the last log entry)
However, every time it gets to the system.img, it fails, saying "Complete(Write) operation failed."
Is there any fix to this? Or is my phone not accepting a custom system.img?
I've used both Odin3 v3.10.7 and v1.85
Thanks in advance!
hi
I purchased a Samsung Galaxy A8 A8000 from China. I did not like its ROM since it lacked Google Apps and other stuff. So i decided to port system apps (apps+priv-app) from an indian rom. I am totall new to ROM stuff and to linux as well but i decided to go with virtual box and learn few things along the way.
For this,
first i extracted indian rom, it contained following
boot.img, cache.img, hidden.img, modem.bin, recovery.img, sboot.bin and system.img
then i extracted chinese rom, it contained different files as below
aboot.mbn, boot.img, cache.img.ext4, hyp.mbn, modem.bin, NON-HLOS.bin, recovery.img, rpm.mbn, sbl1.mbn, sec.dat, system.img.ext4 and tz.mbn
Since i donot want to mess with partitions and modem and other stuff so i decided to port only apps from indian rom and built an odin flashable tar file
For this i navigated various forum, i even dont exactly remember all but i am thankful to all who wrote useful stuff that helped me decide what to do, well most important of these were
http://forum.xda-developers.com/showthread.php?t=1974014
http://forum.xda-developers.com/showthread.php?t=1941239
http://rwilco12.com/forum/showthread.php?tid=92
first of all i converted indian rom system.img to system.raw using following command in linux virtualbox ubuntu 15.04
simg2img indsystem.img indsystem.raw
then i mounted this raw image using this command
mkdir indsystem
mount -o loop indsystem.raw indsystem/
then i converted chinese rom system.img to system.raw using same command as above
simg2img chcsystem.img chcsystem.raw
then i mounted this chinese raw image using this command
mkdir chcsystem
mount -o loop chcsystem.raw chcsystem/
then i created a system_new.img.ext4 file of 3.1GB size with this command
dd if=/dev/zero of=system_new.img.ext4 bs=4k count=775000
then i formated new image with ext4
mkfs.ext4 system_new.img.ext4
then probably i override the file system check and then mounted new ext4 image
tune2fs -c0 -i0 system_new.img.ext4
mkdir system_new
mount -o loop system_new.img.ext4 system_new
here i had a problem, i could not copy files from both indian and raw mounted images to my new ext4 image since i did not have permission to copy to the destination folder. then i made use of superuser access
gksu nautilus /path/to/image/folder
then i had full access and copied chinese rom to my new ext4 image.
cp -v -r -p chcsystem/* system_new/
then i deleted app, priv-app, font, framework, media, etc/permissions/allfiles-starting-with-android.-and-com.-and-allshare_library.xml from ext4 image.
then i manually copied these folders and permission files from indian system raw image file to my new ext4 image file
next i copy /system/lib/libandroid_runtime.so from chinese rom to the system/lib/ directory of indian rom and then deleted lib folder from chinese rom and replaced it with indian rom
then i sync files with "sync" command
then unmounted all partitions.
I then replaced system.img.ext4 file in my original rom with one that i have just made.
Now i need to compile these files back into flashable tar files with md5sum check with
tar -H ustar -c image_1 image_2 > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
1. but before i do so I need some advance developer to please help me out and give some confidence as to the approach that i have used. is that correct.
2. Secondly, if someone can tell me tar ball flashing order for my rom since i heard it is important while compiling odin flashable tar file.
aboot.mbn, boot.img, cache.img.ext4, hyp.mbn, modem.bin, NON-HLOS.bin, recovery.img, rpm.mbn, sbl1.mbn, sec.dat, system.img.ext4 and tz.mbn
3. Also Is it possible that i convert system.img.ext4 into flashable odin tar file with above commands and flash only system image with Odin without messing with anyother settings.
Thank you
No one would like to help me out here.
Hi. I plan to do the same for my SM-A7000. did you get your to work?
waqasjeral said:
hi
I purchased a Samsung Galaxy A8 A8000 from China. I did not like its ROM since it lacked Google Apps and other stuff. So i decided to port system apps (apps+priv-app) from an indian rom. I am totall new to ROM stuff and to linux as well but i decided to go with virtual box and learn few things along the way.
For this,
first i extracted indian rom, it contained following
boot.img, cache.img, hidden.img, modem.bin, recovery.img, sboot.bin and system.img
then i extracted chinese rom, it contained different files as below
aboot.mbn, boot.img, cache.img.ext4, hyp.mbn, modem.bin, NON-HLOS.bin, recovery.img, rpm.mbn, sbl1.mbn, sec.dat, system.img.ext4 and tz.mbn
Since i donot want to mess with partitions and modem and other stuff so i decided to port only apps from indian rom and built an odin flashable tar file
For this i navigated various forum, i even dont exactly remember all but i am thankful to all who wrote useful stuff that helped me decide what to do, well most important of these were
http://forum.xda-developers.com/showthread.php?t=1974014
http://forum.xda-developers.com/showthread.php?t=1941239
http://rwilco12.com/forum/showthread.php?tid=92
first of all i converted indian rom system.img to system.raw using following command in linux virtualbox ubuntu 15.04
simg2img indsystem.img indsystem.raw
then i mounted this raw image using this command
mkdir indsystem
mount -o loop indsystem.raw indsystem/
then i converted chinese rom system.img to system.raw using same command as above
simg2img chcsystem.img chcsystem.raw
then i mounted this chinese raw image using this command
mkdir chcsystem
mount -o loop chcsystem.raw chcsystem/
then i created a system_new.img.ext4 file of 3.1GB size with this command
dd if=/dev/zero of=system_new.img.ext4 bs=4k count=775000
then i formated new image with ext4
mkfs.ext4 system_new.img.ext4
then probably i override the file system check and then mounted new ext4 image
tune2fs -c0 -i0 system_new.img.ext4
mkdir system_new
mount -o loop system_new.img.ext4 system_new
here i had a problem, i could not copy files from both indian and raw mounted images to my new ext4 image since i did not have permission to copy to the destination folder. then i made use of superuser access
gksu nautilus /path/to/image/folder
then i had full access and copied chinese rom to my new ext4 image.
cp -v -r -p chcsystem/* system_new/
then i deleted app, priv-app, font, framework, media, etc/permissions/allfiles-starting-with-android.-and-com.-and-allshare_library.xml from ext4 image.
then i manually copied these folders and permission files from indian system raw image file to my new ext4 image file
next i copy /system/lib/libandroid_runtime.so from chinese rom to the system/lib/ directory of indian rom and then deleted lib folder from chinese rom and replaced it with indian rom
then i sync files with "sync" command
then unmounted all partitions.
I then replaced system.img.ext4 file in my original rom with one that i have just made.
Now i need to compile these files back into flashable tar files with md5sum check with
tar -H ustar -c image_1 image_2 > your_odin_package.tar
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
1. but before i do so I need some advance developer to please help me out and give some confidence as to the approach that i have used. is that correct.
2. Secondly, if someone can tell me tar ball flashing order for my rom since i heard it is important while compiling odin flashable tar file.
aboot.mbn, boot.img, cache.img.ext4, hyp.mbn, modem.bin, NON-HLOS.bin, recovery.img, rpm.mbn, sbl1.mbn, sec.dat, system.img.ext4 and tz.mbn
3. Also Is it possible that i convert system.img.ext4 into flashable odin tar file with above commands and flash only system image with Odin without messing with anyother settings.
Thank you
Click to expand...
Click to collapse
Hi waqasjeral. Have you already ported the Indian rom to the a8000?