This will probably get moved, but I do believe it is development related because it is important to everyone who flashes ROMs but can't use ODIN for whatever reason (ie Linux/Mac users).
Seeing all the ROM cookers get asked so much to make system.imgs or update.zips to cater to the Linux/Mac users, I decided it was time to tell people how to just convert an ODIN Tar.
I will tell people how to do it on Ubuntu seeing that is what I have (in a VM), but once I have the patience to install Mac OS in a VM, I shall make a guide for that.
Please note that if the factoryfs.rfs is in RFS format (ie it's a stock ROM or it's a ROM by someone who doesn't like EXT4 for whatever reason), you will not be able to do this. The format the factoryfs.rfs is in (EXT2, 4, JFS, whatever) needs to be supported by your Linux kernel. You can check that by doing cat /proc/filesystems
After a lot of investigating, I have learnt that RFS is a broken version of FAT. You could poke around with it and try mounting it as vfat but I don't guarantee success.
ODIN TAR -> System.img
Download your TAR and save it to your Desktop (I will use Kyorarom Ascendency Beta)
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
tar cvf system.img system
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Copy the system.img to your phone
System.img -> ODIN TAR
Download a TAR from another ROM, and the system.img to your desktop.
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
rm -rf system/*
tar xvf ~/Desktop/system.img
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Put the factory.rfs into a TAR and flash it with ODIN.
Done! Hopefully this should all work nicely for everyone.
Nice One... Should be helpful for ROM Developers to provide system.img for their ROM's...
Nice one. Thanks. Though I don't use .imgs still was quite Informative.
Sent from my GT-I5800 using xda premium
Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez
cdesai said:
Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez
Click to expand...
Click to collapse
Can u pls explain tht furthur.
vsoft11 said:
Can u pls explain tht furthur.
Click to expand...
Click to collapse
Pretty much do the same thing but from in ADB shell, and instead of the command:
Code:
sudo -s
with
Code:
su
and
Code:
tar cvf system.img system
gets changed to
Code:
tar cvf /sdcard/system.img system
Also I'm pretty sure on the phone, /dev/loop0 is called /dev/block/loop0.
I'll probably have to wait until you put up a mac tutorial..
harkan89 said:
I'll probably have to wait until you put up a mac tutorial..
Click to expand...
Click to collapse
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....
Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me
mankokoma said:
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....
Click to expand...
Click to collapse
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
TearsDontFalls said:
Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me
Click to expand...
Click to collapse
Because I am foolish. I shall improve the guide later today.
harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
I got my Mac VM working so I will use that and make a Mac guide.
hillbeast said:
I got my Mac VM working so I will use that and make a Mac guide.
Click to expand...
Click to collapse
Yaay! Finally!
harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!
is there also a way to convert system.img to tar files...
cdesai said:
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!
Click to expand...
Click to collapse
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..
mohsin2cool said:
is there also a way to convert system.img to tar files...
Click to expand...
Click to collapse
Yes, I shall make a guide for that after Christmas.
harkan89 said:
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..
Click to expand...
Click to collapse
Macs don't use a /mnt directory. They use /Volumes, just like how Ubuntu is moving over to /media.
And I don't think the mach kernel supports losetup type stuff. I will make a Mac guide after Christmas.
HI
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.
devc0ol said:
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.
Click to expand...
Click to collapse
Sure. I will do it in the coming days.
nice guide, but will it also work if you convert it with CWM recovery?
JasonPurungrit said:
nice guide, but will it also work if you convert it with CWM recovery?
Click to expand...
Click to collapse
What do you mean?
Related
First sorry for my English
All credits are for zedomax, who has gotten it to work in Nexus One and for Desire is practically the same.
Sorry about "h t t p" of link adress I am very new here.
Original howto -> h t t p : / /nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
For now, I've only gotten it to work with Windows 7 and "CyanogenMod 5.0.8" and "Defrost2.0c" ROMs. The rom is important for get this works.
Practically almost all the steps are the same as in the guide of nexus one by zedomax. Well go:
Before anything, download ubuntu.zip from original HOWTO and unzip it.
Now download the updated script from zedomax.
h t t p : / /zedomax.com/android/bootubuntu
and overwrite the bootubuntu file of unzipped ubuntu.zip
1. First, you will need a rooted Desire.
zedomax say that you must have the latest version of busybox 1.16.1 but in Defrost2.0c works with 1.16.0 and cyanogenmod has 1.16.1. So we ignore this step from original guide.
2. Once you have a rooted Android phone, you will be able to run Ubuntu under Chroot.
3. Copy these six files from ubuntu.zip over into your SD card’s root folder under folder name “ubuntu“
4. Put your Desire in recovery mode. And connect it to your computer via USB.
5. I am assuming you've already installed the Android SDK (while you were rooting your phone) so let's head to your Android SDK directory and load up ADB Shell.
For Windows, go to your Android SDK Tools directory such as c:\sdk\tools and type "adb shell".
(FYI, cd is the command you can use to browse to your sdk\tools directory. For Windows, do cd \sdk\tools and for Mac/Linux, do cd /sdk/tools.
For linux and Mac, go to your Android SDK Tools directory such as /sdk/tools and type "./adb shell" or it can also be "sudo ./adb shell" for Ubuntu.
6. Once you are in the ADB shell, you should see a “#”symbol. Great, let’s start bootin’ Ubuntu right away.
7. Next, type "mount system", press enter and then type "mount sdcard". If you get this "mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy" ignore it, sdcard is already mounted.
8.- Next, type "cd /sdcard/ubuntu"
9.- Now we will write separate commands instead of using a script to see if something has gone wrong easily. Copy and paste each line separately and hit Enter at the end of each command.
rm /system/bin/fsrw <--(this problably return an error, ignore this)
rm /system/bin/bootubuntu <--(this problably return an error, ignore this)
rm /system/bin/unionfs <--(this problably return an error, ignore this)
rm /system/bin/mountonly <--(this problably return an error, ignore this)
cp -f fsrw /system/bin
cp -f bootubuntu /system/bin
cp -f unionfs /system/bin
cp -f mountonly /system/bin
cd /sdcard/ubuntu
chmod 4777 * <--(this problably return an error, ignore this)
cd /system/bin/
chmod 4777 *
cd /
umount sdcard
umount system
exit
Now select "reboot system now" from recovery menu of your Desire. When android fully loaded you need load up again ADB Shell.
For Windows, go to your Android SDK Tools directory such as c:\sdk\tools and type "adb shell".
Type "su" to enter superuser mode. Is very important not to forget this!
type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system"
type "mkdir /data/local/mnt"
10. Once that completes, type "bootubuntu" to "chroot" or boot into your new Ubuntu on your Android!
If you get the "root_localhost:/#" sign, congratulations! You've just installed Ubuntu on your Desire/Android phone!
the hardest part is complete!. From now, follows the original guide for the "nexus one" to get access to Gnome (visual desktop).
Other problems like keyboard mapping can fix it follow the original post from nexus one forum:
http://forum.xda-developers.com/showthread.php?t=718952
well, I hope this helps
thats pretty cool mate thanks ill try it out tonight when i get home from work
Thanks for this! Will give it a shot when I have a moment
Script?
Anybody fancy writing a nice script to do this for us? I'm on Holiday in Spain so I'm feeling pretty lazy.
Awesome, thanks a lot!
I'm on DJ Droid's Sense with Froyo 2.2, will try it.. hope it works! But do you know why it's rom specific? Is it because of busybox?
I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.
Works great for me, SixOclock rom with busybox 1.16.2
peewster said:
I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.
Click to expand...
Click to collapse
Try ./bootubuntu instead
as soon as i get home, i will.
Thnx
Is anyone nice enough to break the ubuntu.zip down into the 6 files and upload separately?
good job, works fine on SetRom 3.5
someone can post screenshoots ???
?¿?The uncompressed "ubuntu.zip" has a 2Gb .img!!!
peewster said:
I tried this out, and got stuck on bootubuntu from the bootloader menu.
command not recognized. . .
everything works ok until i try to boot ubuntu from the bootloader menu.
Click to expand...
Click to collapse
humm, are you get any error in this part?
cp -f fsrw /system/bin
cp -f bootubuntu /system/bin
cp -f unionfs /system/bin
cp -f mountonly /system/bin
and, where are you launching the bootubuntu command? You need do it from adb shell (at least until you set gnome) or terminal client directly from your phone, like better terminal emulator. Don't forget do "su" before launch bootubuntu. If it still does not work I recommend you start again the guide
why would anyone want to install ubuntu on a phone?
horadee said:
why would anyone want to install ubuntu on a phone?
Click to expand...
Click to collapse
Why would anyone not want to install ubuntu on their phone?
Ok, so it worked. I'm now logged in through adb into Ubuntu. But how can i run ubuntu directly from my phone ?
VNC?
10chars.
abc27 said:
VNC?
10chars.
Click to expand...
Click to collapse
I was wondering if you can run ubuntu (shell) directly from phone instead of adb
Anyone got screenshots?
Sent from my Desire using XDA App
Can any one help me out in converting .img files (system.img, userdata.img generate uring AOSP ROM build) into files (e.g. factoryfs.rfs,data.rtf etc) flash-able by ODIN?
abhijeet.pathak said:
Can any one help me out in converting .img files (system.img, userdata.img generate uring AOSP ROM build) into files (e.g. factoryfs.rfs,data.rtf etc) flash-able by ODIN?
Click to expand...
Click to collapse
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
The Dark Lestat said:
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
Click to expand...
Click to collapse
I have already tried that but my problem is that I am not extracting factoryfs.rfs from phone.
I have compiled froyo from AOSP an got system.img file as a result.
I tried renaming system.img to factoryfs.rfs, but ODIN is saying "Invalid image" in after selecting the file.
abhijeet.pathak said:
I have already tried that but my problem is that I am not extracting factoryfs.rfs from phone.
I have compiled froyo from AOSP an got system.img file as a result.
I tried renaming system.img to factoryfs.rfs, but ODIN is saying "Invalid image" in after selecting the file.
Click to expand...
Click to collapse
We do not have a custom recovery, so flashing the files is impossible.
With a custom recovery, we could've flashed the .img files directly.
The Dark Lestat said:
We do not have a custom recovery, so flashing the files is impossible.
With a custom recovery, we could've flashed the .img files directly.
Click to expand...
Click to collapse
I also extracted contents of system.img and repackaged it as update.zip.
But after selecting "apply sdcard:update.zip", it gives error like:
unable to mount /dev/block/mmblk something... an then
unable to mount SDCARD;update.zip
Installation aborted.
abhijeet.pathak said:
I also extracted contents of system.img and repackaged it as update.zip.
But after selecting "apply sdcard:update.zip", it gives error like:
unable to mount /dev/block/mmblk something... an then
unable to mount SDCARD;update.zip
Installation aborted.
Click to expand...
Click to collapse
As I've already said, we cannot flash it because we don't have a custom recovery.
By default, FroYo recovery flashing is dead.
The Dark Lestat said:
As I've already said, we cannot flash it because we don't have a custom recovery.
By default, FroYo recovery flashing is dead.
Click to expand...
Click to collapse
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
abhijeet.pathak said:
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
Click to expand...
Click to collapse
I think converting them will corrupt them. As of right now, I do not know of a way.
abhijeet.pathak said:
Then in this case, what can be done if I just want to package the files from system.img into factoryfs.rfs and flash them using ODIN?
Click to expand...
Click to collapse
A possible workaround is to mount a rfs image in magic iso and replace the files with yours
Then flash and it'll work
Another way is use update.bat method like lestat
cdesai said:
A possible workaround is to mount a rfs image in magic iso and replace the files with yours
Then flash and it'll work
Another way is use update.bat method like lestat
But the first one is best
Click to expand...
Click to collapse
The first one corrupts the system.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
The Dark Lestat said:
The first one corrupts the system.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Click to expand...
Click to collapse
Sorry didn't know that
So any other workaround?
cdesai said:
Sorry didn't know that
So any other workaround?
Click to expand...
Click to collapse
Nope. Using adb to replace the lib files kills the connection.
So, the only way is to flash.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
The Dark Lestat said:
Nope. Using adb to replace the lib files kills the connection.
So, the only way is to flash.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Click to expand...
Click to collapse
Lib files can be copied to sdcard then remove earlier lib files through terminal emulator via command
"rm -r /system/lib/*.ko"
Copy new files via same method
"cp /sdcard/*.ko /system/lib/"
I think it is possible way.
ROM- Apocalypse 1.0 Beta
Base- XXJPM
Kernel- Apocalypse (Apollo)
Boot Animation- Rudolf
Theme- Arun Verma (Me)
Kernel Scripts- Motafoca
Lock Screen- Kyrillos
forum.samdroid.net/f28/howto-extract-files-samsung-rfs-1693/
You can mount same base rfs file change all files you want or if you need delete all files add files you need and umount you may use root explorer to change files or any other method you find convenient. Remember One thing you'll have to mount rw to make changes.
Edit another link maybe helpful
forum.xda-developers.com/showthread.php?t=751827&page=2
Sent from my GT-I5800 using Tapatalk
arunmcops said:
Lib files can be copied to sdcard then remove earlier lib files through terminal emulator via command
"rm -r /system/lib/*.ko"
Copy new files via same method
"cp /sdcard/*.ko /system/lib/"
I think it is possible way.
ROM- Apocalypse 1.0 Beta
Base- XXJPM
Kernel- Apocalypse (Apollo)
Boot Animation- Rudolf
Theme- Arun Verma (Me)
Kernel Scripts- Motafoca
Lock Screen- Kyrillos
Click to expand...
Click to collapse
That doesn't matter. It still kills ADB.
Maybe someone can edit Heimdall source to add i5800 support and try to flash img from there
we have update.zip now, so that can work
The Dark Lestat said:
No need to convert... Just do this.
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl7 of=/sdcard/datafs.rfs
dd if=/dev/block/stl8 of=/sdcard/cache.rfs
exit
exit
Click to expand...
Click to collapse
Hey where to do this.
guyzz plssss say how to read or extract d rfs file plesss
its vvery urgent..... pless guyzz
any software plsss give d link pls
plsss
Chill man
Use magiciso and/or linux disk reader
Btw abhijeet, what about it now- u can flash via cwm or update.zip
I'm sure several people will be wanting this information, so I figured I would post it here for everyone. This will allow you to backup your system and create custom Odin images for restore purposes. For anyone unfamiliar with the Samsung system, they use Odin to flash things to the device, much like HTC has RUU and Moto has SBF. Odin files are either .tar files, or .tar.md5 files.
The .tar.md5 files are .tar files with the md5 checksum added to the end of the file. If you attempt to flash a .tar.md5 file, Odin will automatically check that the contents are what they should be before flashing and proceed with the flash if the md5 is valid, otherwise it will stop.
In Odin, you should use the PDA button for all flashing. The PIT button may be used as well, if we can get a valid .pit file for the device, but for now, PIT won't be used either. Other than PDA, Start/Reset are the only other buttons you need to worry about.
Now, on to creating the backup files. First, you will need your device to be rooted (perm or temp root will work), and you also need to have access to terminal on the phone, either via an emulator or adb shell access. To create the backup files, you won't need a Linux/UNIX system, but you will if you want to create a flashable Odin package. The following will output the files on the root of the SDCard, adjust the "of=" path if you want them somewhere else. It will also create the files for the proper filename for Odin as well. So to create the files, here are the commands you will use from root shell (#):
System:
Code:
dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096
Kernel:
Code:
dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096
Recovery:
Code:
dd if=/dev/block/bml9 of=/sdcard/recovery.bin bs=4096
DO NOT INCLUDE THE FOLLOWING IN ANYTHING BUT A PERSONAL BACKUP
Cache:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/cache.rfs bs=4096
DBData:
Code:
dd if=/dev/block/stl11 of=/sdcard/dbdata.rfs bs=4096
Data:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096
The last three files (cache, dbdata, data) may contain personal information, so do not include these 3 files in anything but a personal backup/recovery package.
To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:
Code:
tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
If you want to include cache/dbdata/data in the above for personal use, just add them after the "-c" and before the ">".
There are other files that may be in Odin packages, but they are protected by Samsung and cannot be dumped properly. The files are the bootloader, secondary bootloader, modems, and .lfs partitions. The files would be boot.bin, Sbl.bin, modem.bin (not sure what it would be for the CDMA/LTE dual modem here), and param.lfs. It however isn't that big of an issue that these can't be dumped as the can't really be altered by normal flashing of the device, and are usually only altered via OTA updates.
Thanks for this info imnuts! I unfortunately updated to the new update and would like to go back to rooted but cant until I downgrade.
Thanks!
Thanks for posting this. I'm going to attempt to make a personal backup and then I can factory reset the phone and make a stock version for people to use. I'm haven't installed the update yet either, so I'm hoping this will let people get back to ED1. I've also been playing around with theming using the fascinate community rom theme and ninjamorph to swap files. It'll take a while, but it's currently the only way I feel safe messing with framework-res.
wynalazca said:
Thanks for posting this. I'm going to attempt to make a personal backup and then I can factory reset the phone and make a stock version for people to use. I'm haven't installed the update yet either, so I'm hoping this will let people get back to ED1. I've also been playing around with theming using the fascinate community rom theme and ninjamorph to swap files. It'll take a while, but it's currently the only way I feel safe messing with framework-res.
Click to expand...
Click to collapse
I'm definitely looking forward to having a downgrade ROM image to get back to ED1!
So how do you add the last personal 3 i just got the droid charge and i am not very familiar with samsung files i had a droid x and a thunderbolt very shortly and am familiar with ruu and sbf but how do you add cache dbdata and the other one. I meab like the actual command not the instruction to put it after c
rami98 said:
So how do you add the last personal 3 i just got the droid charge and i am not very familiar with samsung files i had a droid x and a thunderbolt very shortly and am familiar with ruu and sbf but how do you add cache dbdata and the other one. I meab like the actual command not the instruction to put it after c
Click to expand...
Click to collapse
The only thing that would change would be the tar command. If you want to include the other files, it would be:
Code:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
You just need to pull the files from your phone and have them in the same directory that you're in in terminal, and have them named appropriately. It also doesn't matter what order they are in (that I know of), I just have them in alphabetical order for ease of reading.
So im going to try and do the voodoo lagfix for the first time ever but I wanted to make a backup. Im on ED2 and NOT rooted so how would I go about making these backups?
imnuts said:
The only thing that would change would be the tar command. If you want to include the other files, it would be:
Code:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
You just need to pull the files from your phone and have them in the same directory that you're in in terminal, and have them named appropriately. It also doesn't matter what order they are in (that I know of), I just have them in alphabetical order for ease of reading.
Click to expand...
Click to collapse
I tried the above and I keep getting this error message in the command prompt:
'tar' is not recognized as an internal or external command, operable program or batch file.
(I'm trying this on windows 7 professional)
Any help would be appreciated, thanks!
mypantsaretorn said:
I tried the above and I keep getting this error message in the command prompt:
'tar' is not recognized as an internal or external command, operable program or batch file.
(I'm trying this on windows 7 professional)
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
You wouldn't by any chance be trying the "tar" command at a windows command prompt, would you?
imnuts said:
To create the backup files, you won't need a Linux/UNIX system, but you will if you want to create a flashable Odin package.
To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:
Code:
tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
If you want to include cache/dbdata/data in the above for personal use, just add them after the "-c" and before the ">".
Click to expand...
Click to collapse
Course you might be running Linux in a vmware or Hyper-V environment....hint?
HTH
Damn! I didn't pay attention to the second part of that sentence! Lol
Thanks for the "hint"..
Sent from my SCH-I510 using XDA App
The other option would be using Cygwin, but I've never tried it, so it may or may not work.
imnuts said:
The other option would be using Cygwin, but I've never tried it, so it may or may not work.
Click to expand...
Click to collapse
cygwin works!
Edit: Here is how:
1. Search google for cygwin - download
2. Run - you will be prompted to get packages - I assumed "archive" was a good place to start - not sure if you need this or not...
3. When complete you will see a new icon on your desktop - double-click
4. Be patient as it loads
5. Copy the files output'ed from first post to same folder on PC
6. Back in cygwin:
a. cd x: (where x: is the drive letter of the drive that has the folder with the files)
b. tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin zImage > package_name.tar
c: md5sum -t package_name.tar >> package_name.tar
d: mv package_name.tar package_name.tar.md5
Complete output of commands:
These files are for the users to personalise their cygwin experience.
They will never be overwritten nor automatically updated.
`./.bashrc' -> `/home/UWINKET//.bashrc'
`./.bash_profile' -> `/home/UWINKET//.bash_profile'
`./.inputrc' -> `/home/UWINKET//.inputrc'
`./.profile' -> `/home/UWINKET//.profile'
Your group is currently "mkgroup". This indicates that neither
your gid nor your pgsid (primary group associated with your SID)
is in /etc/group.
The /etc/group (and possibly /etc/passwd) files should be rebuilt.
See the man pages for mkpasswd and mkgroup then, for example, run
mkpasswd -l [-d] > /etc/passwd
mkgroup -l [-d] > /etc/group
Note that the -d switch is necessary for domain users.
[email protected] ~
$ cd h:
System Volume Information
[email protected] /cygdrive/h
$ cd downloads
[email protected] /cygdrive/h/downloads
$ cd charge
[email protected] /cygdrive/h/downloads/charge
$ cd tarbackup/
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin
zImage > package_name.tar
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ md5sum -t package_name.tar >> package_name.tar
[email protected] /cygdrive/h/downloads/charge/tarbackup
$ mv package_name.tar package_name.tar.md5
[email protected] /cygdrive/h/downloads/charge/tarbackup
$
Hmm flash did not work with my personal data in it - got an error. Created a new .tar file with just factoryfs.rfs recovery.bin and zImage and was able to flash that. TG for TiBu!
jism31 said:
Thanks for this info imnuts! I unfortunately updated to the new update and would like to go back to rooted but cant until I downgrade.
Click to expand...
Click to collapse
How do you start doing this. How do I get to root shell (#)... Thanks
AD
I plan to get rooted on ED1 so I can get a stock image backed up, and have a clean base to work from. Still getting my head around the odin stuff first.
RaptorMD said:
I plan to get rooted on ED1 so I can get a stock image backed up, and have a clean base to work from. Still getting my head around the odin stuff first.
Click to expand...
Click to collapse
you dont have to do that its already done
http://forum.xda-developers.com/showthread.php?t=1085190
Well, I successfully followed all the instructions and have created my first ODIN flashable file, I have not tried to flash it yet. I'm just curious, I pull all the different .rfs, .bin, and zImage on this file and noticed it's about 1.8gb file. Is this normal?
Also, before I try to flash this. Should I have dissable voodoo lagfix and converted back to rfs before I dumped the files?
Thanks for all the help!
JKChad said:
Well, I successfully followed all the instructions and have created my first ODIN flashable file, I have not tried to flash it yet. I'm just curious, I pull all the different .rfs, .bin, and zImage on this file and noticed it's about 1.8gb file. Is this normal?
Also, before I try to flash this. Should I have dissable voodoo lagfix and converted back to rfs before I dumped the files?
Thanks for all the help!
Click to expand...
Click to collapse
Yes, that's normal for it to be so large as dd will dump the partition, including empty space. If you were to compress it with zip or lzma, it'd drop down considerably.
Not sure about the voodoo part as I've never dumped files from an ext4 partition. I don't see any reason why it wouldn't work, but I'd flash with caution and have another working image ready just in case.
imnuts said:
Not sure about the voodoo part as I've never dumped files from an ext4 partition. I don't see any reason why it wouldn't work, but I'd flash with caution and have another working image ready just in case.
Click to expand...
Click to collapse
Shouldn't be an issue as long as he keeps the voodoo kernel.
Sent from my SCH-I510 using Tapatalk
Anybody try this with voodoo yet ?
This tutorial is about how to export your /system partition or your own ROM.
Requirements
- ADB Shell for Windows, Linux, Mac OSX or Android Terminal Emulator installed on your GT-S5660
- If you are using Windows use cygwin else use Terminal in Linux.
Process
1. Install Cygwin from here, skip this step if you use Linux
2. Connect the Gio to the computer.
3. a) Open windows command prompt and type:
adb shell
Click to expand...
Click to collapse
3. b) If you use Android Terminal, open it
4. Whether you use option a or b from the previous step type this
dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096
Click to expand...
Click to collapse
5. Now you have a system.rfs file on your sdcard.
6. If you use cygwin place the system.rfs in this folder (where you installed it):
C:\Cygwin\home\%yourusername%
Click to expand...
Click to collapse
If you use Linux I assume you have the skill to set the correct paths yourself...
7. Now we are going to pack it into a tarball:
tar -H ustar -c system.rfs > thisismyrom.tar
Click to expand...
Click to collapse
if you have an additional moddified boot.img for example you could have typed this as well:
tar -H ustar -c boot.img system.rfs > thisismyrom.tar
Click to expand...
Click to collapse
8. Add md5 hash to our tarball for security and integrity checks
md5sum -t thisismyrom.tar >> thisismyrom.tar
Click to expand...
Click to collapse
9. Renaming our tarball with md5 extension:
mv thisismyrom.tar thisismyrom.tar.md5
Click to expand...
Click to collapse
10. Happy flashing with odin!
Shouldn't stl12 be system? And stl14 cache?
Also, you could make a shell script to automate part of your process. Scripts can be run from Cygwin and Linux.
Regards,
Darkshado
Sorry! Made a typing mistake. Corrected it!
No need of cygwin, adb in windows cmd will do fine, and use total commander to tarball it on windows, other tools mess it up n can brick your device
Hi!
How can i export the CSC (or all the ROM) from Android 2.2.1?
thanks
I may have got the wrong end of the stick here and this could be the wrong thread, but it does seem to be the most specific to my interest.
I'd like to be of service by exporting my own ROM (Stock Firmware) so others can use it themselves in case of disaster. I started a thread at Samfirmware.com here http://www.sammobile.com/forum/showthread.php?t=3420 because they don't have it on their list for Samsung Galaxy Ace, and I was surprised to see it got 64 views, so I presume there would be some modicum of interest in it.
I really don't have any experience with this but I am fascinated and keen to learn. I had assumed (and I know assumption is the mother of all f*** ups) that I could simply create a CWMrecovery backup and it could be zipped up and exported to other phones. But I read somewhere that this would include my google account details.
Anyway. If you can tell me a) how to be of some use regarding this b) tell me its not worth it but point me in the direction of a place where I can start to learn what to do or c) politely show me the exit sign and tell me not to darken your door again...I'd be most grateful
how i am know if my tablet "loop devices" support
or how i am kae him to suport loop devices
Code:
cd /sdcard/wherever/
cp /proc/config.gz ./
gunzip ./config.gz
cat ./config | grep LOOP
"LOOP" must be in all caps, or it won't work.
thanks
EndlessDissent said:
Code:
cd /sdcard/wherever/
cp /proc/config.gz ./
gunzip ./config.gz
cat ./config | grep LOOP
"LOOP" must be in all caps, or it won't work.
Click to expand...
Click to collapse
thanks bat you say
Code:
cd /sdcard/wherever/
bat what it is
Code:
wherever
what i am need put there
or how i am loop my device
mihael1996 said:
thanks bat you say
Code:
cd /sdcard/wherever/
bat what it is
Code:
wherever
what i am need put there
or how i am loop my device
Click to expand...
Click to collapse
It means to just cd wherever you like. It doesn't matter where you unzip the file. Just do it in whatever folder you want. All those commands do is copy the kernel configuration to whichever folder you're in, unzip it, search for the loop device configuration options, and print it to the screen.
EndlessDissent said:
It means to just cd wherever you like. It doesn't matter where you unzip the file. Just do it in whatever folder you want. All those commands do is copy the kernel configuration to whichever folder you're in, unzip it, search for the loop device configuration options, and print it to the screen.
Click to expand...
Click to collapse
realy thank you
can you say to me from where downlode this zip file ?
from here it ok ? http://forum.xda-developers.com/showthread.php?t=2246062
and do you have a skype ?
mihael1996 said:
realy thank you
can you say to me from where downlode this zip file ?
from here it ok ? http://forum.xda-developers.com/showthread.php?t=2246062
and do you have a skype ?
Click to expand...
Click to collapse
You're not supposed to download anything. You just use the commands I posted to copy and read your current kernel config. It's all on the tablet already. You just need to type the commands.
If you want to know if that kernel supports loop devices, you could flash it before running the commands I posted. Or, just ask in the thread.
No, I don't have Skype. I hate Microsoft and everything they touch.
where i am put this commands ?
Terminal Emulator