Develop Bugs

[GUIDE] Extract .rfs files

I came from HTC Hero to the Samsung Galaxy S GT-I9000
So I had never problems with cooking something up, but in the Galaxy I faced .rfs files and a flashing tool I can't use on linux...
So I searched through some boards to find a way to extract the .rfs files here a working guide for the S I9000.
What you need
Linux (tested with Debian testing)
It's pretty simple, execute this commands as root on your computer
SHORT WAY (thanks to mimocan)
Code:
# mount -o loop factory.rfs /some_dir
LOOOONG WAY
Attatch the rfs file to the loop device
Code:
# losetup /dev/loop0 /somedir/factoryfs.rfs
Create a directory to mount the device
Code:
# mkdir /somedir/mnt
Mount the device
Code:
# mount /dev/loop0 /somedir/mnt
the content of the rfs is NOT saved on the sdcard! you have to copy it!
Now you can copy the content from the /sdcard/tmp directory to the sdcard
Code:
# cp -R /somedir/mnt /somedir/factoryfs
hope this is helpful for someone

Code:
#mount -o loop factory.rfs /some_dir
should do the same

This works because rfs is based on vfat.
But have you ever tried this on cache.rfs or dbdata.rfs?
The mounted folder is empty. The cache.rfs in my case was around 1.2 mb.
Maybe the 1.2 mb are journaling data rfs uses?
I also tried mounting cache.rfs and dbdata.rfs directly on my sgs without any luck.
Since the phone has built in rfs drivers it should be able to mount it.

psternx said:
This works because rfs is based on vfat.
But have you ever tried this on cache.rfs or dbdata.rfs?
The mounted folder is empty. The cache.rfs in my case was around 1.2 mb.
Maybe the 1.2 mb are journaling data rfs uses?
I also tried mounting cache.rfs and dbdata.rfs directly on my sgs without any luck.
Since the phone has built in rfs drivers it should be able to mount it.
Click to expand...
Click to collapse
If you open the cache.rfs or dbdata.rfs from a PDA build (tested I900XXJP3) in a hexeditor you will see they are empty, just the headers and a lot of zeros

Have you been able to modify something from a rfs file and save it?

Actually Cache.rfs file in CSC is a renamed update.zip. At least with a few firmwares I have tried. So just open it with, for example, 7-zip and you can browse the files.

deleted............

Tried to mount a cache.rfs and got a "Device or resource busy".
Then tried to open it trough MagicISO, and voilá, I got the CSC files I needed

Now im into modifying factoryfs.rfs and hoping you can give me some tips.
Alt1
mount -o loop factoryfs.rfs directory & Copy files to a new place and edit them but how to create a .rfs from that point?
Alt2
sudo mount -v -o rw,loop,uid=$UID factoryfs.rfs Directory
Edit the files , umount the .rfs . Mount it again but the the changes are gone.
How do you do it?
Thanks.

a-son said:
Now im into modifying factoryfs.rfs and hoping you can give me some tips.
Alt1
mount -o loop factoryfs.rfs directory & Copy files to a new place and edit them but how to create a .rfs from that point?
Alt2
sudo mount -v -o rw,loop,uid=$UID factoryfs.rfs Directory
Edit the files , umount the .rfs . Mount it again but the the changes are gone.
How do you do it?
Thanks.
Click to expand...
Click to collapse
for me, i'll definitelty mod it elsewhere

ykk_five said:
for me, i'll definitelty mod it elsewhere
Click to expand...
Click to collapse
Thanks for answer.
Alt 1 i suppose you mean. But how to create the .rfs ?

a-son said:
Thanks for answer.
Alt 1 i suppose you mean. But how to create the .rfs ?
Click to expand...
Click to collapse
yess!!!!
how to recompile the .rfs ?????

KBJ911 said:
yess!!!!
how to recompile the .rfs ?????
Click to expand...
Click to collapse
BUMP!
Actually some cache.rfs aren't simple renamed zipfiles, as they (i.e. multi-csc) also contains more stuff
So I loopmounted rw the vfat cache.rfs, extracted and modified the contained sec_csc.zip (this one IS an update.zip structured file...)
But when I put it inside, sync, unmount and mount again to verify stuff, I got a corrupted filesystem and a corrupted zip file.
Any clue to successfully modify contents of such .rfs ?

mopodo said:
I came from HTC Hero to the Samsung Galaxy S GT-I9000
So I had never problems with cooking something up, but in the Galaxy I faced .rfs files and a flashing tool I can't use on linux...
So I searched through some boards to find a way to extract the .rfs files here a working guide for the S I9000.
What you need
Linux (tested with Debian testing)
It's pretty simple, execute this commands as root on your computer
SHORT WAY (thanks to mimocan)
Code:
# mount -o loop factory.rfs /some_dir
LOOOONG WAY
Attatch the rfs file to the loop device
Code:
# losetup /dev/loop0 /somedir/factoryfs.rfs
Create a directory to mount the device
Code:
# mkdir /somedir/mnt
Mount the device
Code:
# mount /dev/loop0 /somedir/mnt
the content of the rfs is NOT saved on the sdcard! you have to copy it!
Now you can copy the content from the /sdcard/tmp directory to the sdcard
Code:
# cp -R /somedir/mnt /somedir/factoryfs
hope this is helpful for someone
Click to expand...
Click to collapse
Is there a way to convert it back to rfs?

@all
Is there a way to convert it back to rfs?

criskelo said:
@all
Is there a way to convert it back to rfs?
Click to expand...
Click to collapse
If you used the shortway # mount -o loop factory.rfs /some_dir
than you can modify the files in some_dir.
when finished simple un mount the some_dir and the files are saved in the factory.rfs
Then tar and md5 the factory.rfs and you can flash it with odin

in windows use "magiciso" to extract .rfs

lownoise said:
Then tar and md5 the factory.rfs and you can flash it with odin
Click to expand...
Click to collapse
I lost at there, what does that means?

From linux
fastcx said:
I lost at there, what does that means?
Click to expand...
Click to collapse
From the linux command line you have to use
tar -cf filename.tar factory.rfs
md5sum filename.tar >filename.tar.md5

If you have extracted it with MagicISO and now just want to create it back to factoryfs.rfs can I do this with Cygwin and what would the command line be?

[ROM] Steam ROM 2.9.9.0 (JPA/JP7/JPM)

STEAM ROM 2.9.9.0 (it's not 3.0.0.0 because that would mean stable)
Steam ROM is a Steam Kernel based XWJPA/XXJP7/JPM ROM. Although this config is a bit old, I didn't had much time to experiment with the newer ones. This ROM is the common successor of both of my previous two ROMs
Steam ROM is a showcase of almost all features Steam kernel/recovery provides, including the recovery selection menu, or afterburner. It also has /system pre-lagfixed, so you won't need to do that after flashing. (the other filesystems are still rfs, as samsung's CSC install would format them anyway to rfs)
Main highlights
- ROM:XWJPA, CSC:XWJP7 Kernel: JPM (Steam Kernel 2.9.9.0)
- System is pre-converted to ext4
- All other partitions can be converted later
- Root is not installed, but can be installed later from the menu
- No theme is installed, but the battery indicator can be installed later from Afterburner
- Most samsungs apps are removed, but they can be installed later from Afterburner
How to install
The zip file contains everything you need to start, including Odin, a pit file, and all images. This is a complete rom, so you can always flash this with re-partition checked, and get all your previous data erased (sometimes data is kept, run a wipe data to be sure)!
You don't need to stick with the XXJP7 CSSC however, as CSC installs will be done by either 3e, or 2e recovery. After boot, you'll be asked which recovery version you want to use to install your CSC file. The rule of thumb is, that if your CSC file is old (made for Eclair), then you should choose 2e recovery. If it's new (made for Froyo) chose 3e recovery. You can chose to keep with Steam, but that will usually fail, as Steam is not designed to handle CSC updated.
What is Afterburner?
After you allow Steam to install, and the CSC files to setup, you'll be greeted (hopefully) with a list of post-flash options. Most of these options will simply
install back some of the removed applications. Simply check the apps you wish to use, and wait for them to get installed. If you change your mind, you can later re-visit the afterburner menu during recovery mode.
Be careful however, as the space is limited on /system, and afterburner doesn't yet check if there is enough space left on the device!
How to root?
Enter recovery mode, select Steam options, and install superuser
How to lagfix?
Enter recovery mode, select Steam options, and filesystem options

DL link:
- http://android.sztupy.hu/dl/Steam_ROM_eng_2.9.9.0.zip (english)
- http://android.sztupy.hu/dl/Steam_ROM_hun_2.9.9.0.zip (hungarian - use 2e recovery)

This is truly nice work. Make a 2.2.1 version?

Looks like awesome stuff sztupy!
Maybe next, a tool to convert the rfs factoryfs.rfs to ext4, from a PC? Or better yet, a tool to convert Samsung rom images from rfs to ext4 that can be flashed using Odin or something.

DocRambone said:
This is truly nice work. Make a 2.2.1 version?
Click to expand...
Click to collapse
First I have to get the kernel working on stock stuff. Then it'll be possible.

hardcore said:
Looks like awesome stuff sztupy!
Maybe next, a tool to convert the rfs factoryfs.rfs to ext4, from a PC? Or better yet, a tool to convert Samsung rom images from rfs to ext4 that can be flashed using Odin or something.
Click to expand...
Click to collapse
I don't think that can be done on a PC, as there are no rfs drivers. Creating a script that does the job using adb is easy though:
Code:
rem Should be on Steam kernel, with adb root option enabled
adb root
adb shell /sbin/steam mkdir -p /mnt/sdcard/convert
adb shell /sbin/steam mkdir -p /mnt/sdcard/convert/rfs
adb shell /sbin/steam mkdir -p /mnt/sdcard/convert/ext4
adb push factoryfs.rfs /mnt/sdcard/convert/
adb shell /sbin/steam truncate /mnt/sdcard/convert/factoryfs.rfs 291504128
rem The correct amount is got by multiplying the partition size from /proc/partitions by 1024
adb shell /sbin/steam losetup /dev/block/loop0 /mnt/sdcard/convert/factoryfs.rfs
adb shell /sbin/steam touch /mnt/sdcard/convert/factoryfs.ext4
adb shell /sbin/steam truncate /mnt/sdcard/convert/factoryfs.ext4 291504128
adb shell /sbin/steam losetup /dev/block/loop1 /mnt/sdcard/convert/factoryfs.ext4
adb shell /sbin/steam mount -t rfs -o check=no /dev/block/loop0 /mnt/sdcard/convert/rfs
adb shell /sbin/steam mkfs.ext4 -b 1024 -m 0 -J size=4 /dev/block/loop1
adb shell /sbin/steam mount -t ext4 -o noatime /dev/block/loop1 /mnt/sdcard/convert/ext4
adb shell /sbin/steam cp -dpR /mnt/sdcard/convert/rfs/* /mnt/sdcard/convert/ext4
adb shell /sbin/steam umount /dev/block/loop0
adb shell /sbin/steam umount /dev/block/loop1
adb shell /sbin/steam losetup -d /dev/block/loop0
adb shell /sbin/steam losetup -d /dev/block/loop1
adb pull /mnt/sdcard/convert/factoryfs.ext4
adb shell rm -rf /mnt/sdcard/convert

I will try this out, I am sure I will be as awed by this ROM as I was with Sztupy's earlier ones.

Sztupy always delivers.

nice work sztupy and i happy u coming back

Any one tried this yet?

Aylarth said:
Sztupy always delivers.
Click to expand...
Click to collapse
That is right.
Lets hurry up samsung to release 2.2.1 sources so we can get it rolling again?
I'm fed with da mess with JPU/JPX/JPY and JPM kernels

@ Sztupy,
So, this ROM is stock, right? No deodex, no zipalign. Can I flash DDJP6 MODEM on it? & can I flash HKAINU CSC from the recovery?

ragin said:
@ Sztupy,
So, this ROM is stock, right? No deodex, no zipalign. Can I flash DDJP6 MODEM on it? & can I flash HKAINU CSC from the recovery?
Click to expand...
Click to collapse
Yep, it's stock. Only the apps were removed + system was converted to ext4.
Official CSC's will work using 3e recovery.
I don't know about the modem, but I don't know why it wouldn't work oout of the box with another one.

sztupy said:
Yep, it's stock. Only the apps were removed + system was converted to ext4.
Official CSC's will work using 3e recovery.
I don't know about the modem, but I don't know why it wouldn't work oout of the box with another one.
Click to expand...
Click to collapse
Thanks for a quick reply. I have uploaded a CSC file to be installed thru CWM, and a MODEM file specific to my region. Can you tell me if it will work?
Thanks again.

Will this work on the Sprint Epic 4G? I'm asking only because this phone is known to have odd differences/bugs from the other Galaxy S phones.

Now that JPX source is available. Why not a sample?
Sent from my GT-I9000 using XDA App

Any development?

Waiting for 2.2.1 jpy release,it will rock

°Dexter° said:
Waiting for 2.2.1 jpy release,it will rock
Click to expand...
Click to collapse
Like its said above, Sztupy always delivers.

hd2 problem hang
my htc hd2 hang on disply how to solve this problem help me

[HOWTO] Backup your EFS partition

As with newer Samsung Android phones it is practically essential that if you go to the modding scene and start uploading custom roms you should have a backup of your efs
For simple backup of efs partition
by sishgupta
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
and for a full image of your brand new phone
as various users have stated there are other more correct ways of backing up your new efs partition,
the one i liked the most is this one by because it backs up all your partitions
by c0ns0le
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
deprecated just staying here because this started all the correct backup commands for your efs
In order to do this for your galaxy nexus you should have adb working on your machine and also debugging enabled in your phone
this is practically easy, your phone must be rooted, or at least booted with the boot.img of this thread How to Root GALAXY NEXUS
Code:
adb root
adb remount
adb pull /factory
and now backup that file to at least 2 places lol
I always get paranoid with this
have fun installing custom roms

i don't think that works for GN
Samsung changed their EFS recently on the new released phones
it's no longer how it was with the Galaxy S line of phones

No one know if we really can backup and restore /factory (EFS)?

this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img

Out of curiosity, what is efs?
I am pretty familiar with flashing my HTC Desire, but there is not an efs partition (AFAIK)?
Cheers!

It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium

420SYN said:
It backs up your imei information in case it gets corrupted by flashing custom roms and mods
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Cool thanks!
Stew

Is this something specific to Samsung phones? I have been rooting and flashing since the nexus one and have never needed this.
Doesn't clockwork mod back this up? If not, why not?
Sent from my LG-P999

dave_t321 said:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
Would it be if=/dev/block/platform/omap/omap_hsmmc.0/by-name/factory since this partition is named "factory" now?

If the efs is really in the /factory folder and its not hardlinked files sitting somewhere else is there a better way to save the files and keeping the permissions?
Using tar or gzip on them before?

So which method to follow in order to backup my efs folder?All information is under /factory

use
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
this is the right command as if you run ls on the by-name folder you can see that it is still efs not factory
factory must be a link to this

omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!

Could someone provide the correct commands to restore the efs folder please Ive backed it up just need to know how to restore it if something bad happens

There is a guide for it on these forums. Google 'efs restore android' and you should find it.
There is also an efs restore application that will use img files (like how we made in this guide) instead of just the nv_data.bin
Sent from my Galaxy Nexus using XDA App

does it actually work with this phone?

fun w/ shellfoo
Code:
IF YOU HAVE BUSY BOX INSTALLED
adb shell
su -
for i in $(ls /dev/block/platform/omap/omap_hsmmc.0/by-name/ | grep -v user)
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done
NO BUSYBOX:
adb shell
su -
for i in boot cache dgs efs metadata misc param radio recovery sbl system xloader
do
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/${i} of=/sdcard/${i}.img &
done

---------- Post added at 03:43 PM ---------- Previous post was at 03:15 PM ----------
[/COLOR]
dave_t321 said:
this should put an .img file in /sdcard. It's the same method as the one in the sgs2 section but with different paths.
Code:
adb shell
su
cat /dev/block/platform/omap/omap_hsmmc.0/by-name/efs > /sdcard/efs.img
edit: you'll need to be root, obviously
edit again:
this is technically better but does the same thing:
Code:
adb shell
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
Click to expand...
Click to collapse
i've foud this one..wich is better?
adb shell
su
busybox dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/data/media/my_efs_backup.img

They are the same with different output locations. The one that leads with busy box is for a configuration where the commands are not aliased for a busy box setup.
Sent from my Galaxy Nexus using XDA App

Similar thing happened to me. I got a 2nd nexus, decided to restore a nandroid from my 1st nexus onto the 2nd one. Restore went fine, it was like a clone of the 1st phone except the IMEI was corrupt with a generic 0049... one. I flashed the phone back to a google factory ITL41D and the IMEI was restored. Needless to say I won't be doing that again!
paratox said:
omg, i have a 0049... IMEI after flashing ICL53F via fastboot!
how could i restore my old IMEI?
edit: jippie, i got my IMEI back after flashing the ITL41F odin version from this post!
i suggest everyone to backup the efs before flashing other firmwares!
Click to expand...
Click to collapse

[HOWTO]Do a backup of your current kernel and use it for recovery

This is a new device and the development is starting quickly. Many user that haven't the device is starting to develop some stuff for it also if they don't have the phone ( like me ).
Kernel testing can cause softbrick that can be easy fixed flashing again the stock kernel. The following steps explain how to do a backup of your current kernel so you can use it to restore your device.
It's a very simple guide.....
IMPORTANT You need to use adb ( also terminal emulator is good) and you need to be root!
Code:
su
dd if=/dev/block/bml7 of=/sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
IMPORTANT: Write the commands exactly like i wrote and put attention that in the second command. I wrote "BML7" not "BM17" but you have to write without capital letter so "bml7" OK?
After this you'll have a file called kernel-backup.tar in your SDcard. Save it and, in case of softbrick testing a new kernel, put your phone in download mode and flash it with odin (PDA field).
Wish this can help you...
Bye

I got
Code:
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: removing leading '/' from member names
sdcard/boot.img
#
Nvm.. my bad

noobwithgalaxyy said:
I got
Code:
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: removing leading '/' from member names
sdcard/boot.img
#
Click to expand...
Click to collapse
check your sd card root. the files are there.

it creates two files..."boot.img" and "karnel-backup.tar"...
which one should I flash with Odin??

amlanpaira said:
it creates two files..."boot.img" and "karnel-backup.tar"...
which one should I flash with Odin??
Click to expand...
Click to collapse
The tar file

The problem is that odin wont flash it i guess !
Sent from my GT-S5360 using XDA App

It doesn't.. I checked..
Sent from my GT-S5360 using XDA App

noobwithgalaxyy said:
It doesn't.. I checked..
Sent from my GT-S5360 using XDA App
Click to expand...
Click to collapse
As i expected !!!we have big problem with odin ...
Sent from my GT-S5360 using XDA App

Yeah we do have a problem.. but Skin did make it work(flashing CWM was successful, even though it didn't work)
If he can let us know how and why other single file flashes do not work..

@ skin1980 can we convert somehow this tar file to update.zip so we can flash it from CWM recovery?

get back up ...
Thank you ..
now and discover how to use it if you need
I wonder if it has the backing of the baseband
Here in Brazil is put another baseband .... we are unsigned operators: /

Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?

Preterer said:
Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?
Click to expand...
Click to collapse
both the files are now on your sd card check them...........

rohit589769 said:
both the files are now on your sd card check them...........
Click to expand...
Click to collapse
You are wrong, there is only boot.img .

Preterer said:
Code:
C:\Users\hubert>adb shell
$ su
su
# dd if=/dev/block/bml7 of=/sdcard/boot.img
dd if=/dev/block/bml7 of=/sdcard/boot.img
# tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar cvf /sdcard/kernel-backup.tar /sdcard/boot.img
tar: not found
#
what am I doing wrong?
Click to expand...
Click to collapse
You have to install busybox!
look for busybox installers on Market!

I've created a tar and flashed it with odin. It works fine.
I'm currently working on a replacement for heimdall that will support this phone and some others. So if you make a backup you will be able to restore it later.

s0unds said:
I've created a tar and flashed it with odin. It works fine.
I'm currently working on a replacement for heimdall that will support this phone and some others. So if you make a backup you will be able to restore it later.
Click to expand...
Click to collapse
Keep us updated please for anything new!
Sent from my GT-S5360 using XDA App

Is the boot.img and kernel-backup.tar only sized 5MB?
Sent from my GT-S5360 using XDA App

qtu said:
Is the boot.img and kernel-backup.tar only sized 5MB?
Sent from my GT-S5360 using XDA App
Click to expand...
Click to collapse
It's a really small file, cause it's only Kernel, not whole sys.

Preterer said:
It's a really small file, cause it's only Kernel, not whole sys.
Click to expand...
Click to collapse
I see! Thanks a lot! Now, my kernel is backed-up.

[Request] How to flash system.img through ADB in CWM

I would like to try flashing the stock bell rom back on my phone but I never backed it up initially.
I've been having Bluetooth music issues with both kernelpanics and ho!no!s roms so I have to get stock to test if its the phone or just the roms while its still in warranty.
Thanks guys!!
Sent from my LG-P930 using XDA
EDIT:
Found stock system.img
What are the ADB commands to flash the file to my phone?

Bump for new topic. Found System.img of stock bell canada rom

adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14

Epyoch said:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
Click to expand...
Click to collapse
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory

Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.

Malnilion said:
Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.
Click to expand...
Click to collapse
I already used ADB to push system.img to my phone's SDCard root directory.
Are you suggesting that I reformat my SDCard through windows?
I just realized that I am lacking the boot.img of the stock bell ROM. system and boot are the two that are absolutely necessary to get the phone working correct?

Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...

Malnilion said:
Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...
Click to expand...
Click to collapse
I think I'll be using HO!NO!'s rom as a base for the boot.img, since he has a bell optimus LTE, not the AT&T phone. I'm assuming that he hasn't made any changes to the boot partition, since no custom kernel development has occurred for this phone yet.
I found a so called legit CWM backup of the BELL rom, in one of the lu6200 threads, http://forum.xda-developers.com/showthread.php?t=1472501
but recovering the backup only hangs on the LG logo. I did a "advanced restore" and restored only the system and boot files but that didn't get past the logo either...
It booted after an advanced restore with the "stock" system(from that thread) and the boot (from HONO's), but the WIFI wouldn't start, it said error.

Where did you get your stock bell system.img? and can you provide it?

hereric said:
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory
Click to expand...
Click to collapse
Mount sdcard in recovery.
After you enter adb shell
"mount /sdcard" (without quotations)
Then use the command "dd if=/sdcard/system.img of=/dev/block/mmcblk0p27"