Database Info

Editing system.img/YAFFS2 (custom ROM creation)

Basically I just want a stock ROM base with the sprint crap taken out and unrevoked added in with some other app mods.
I've grabbed all the sources for YAFFS2/yaffs2Utils and compiled them using cygwin.
Now when I go to extract the system.img all I get is a fonts folder.
I'm setting up a virtual linux machine to try to mount the image instead, but in the meantime anyone care to assist me?

Do a search for android basic kitchen .53. Made myself a custom rom off the .6 release
Sent from my Evo 4g using Tapatalk

stroths said:
Do a search for android basic kitchen .53. Made myself a custom rom off the .6 release
Sent from my Evo 4g using Tapatalk
Click to expand...
Click to collapse
Awesome!!!
Since you claim it works, I'll take your word for it and say I can't thank you enough!
(even if it doesn't do what I need, it should one step forward nonetheless)

Neotelos_com said:
Awesome!!!
Since you claim it works, I'll take your word for it and say I can't thank you enough!
(even if it doesn't do what I need, it should one step forward nonetheless)
Click to expand...
Click to collapse
It seems to be worthless for EVO, only generates update files...I can't even use it to extract the filesystem from system.img

my experience has been working with rfs and not yaffs2 so far.
i think you'll be needing yaffs2 tools, like unyaffs2, etc.
i googled, android system.img mount. seems like a great place to start:
http://wiki.xda-developers.com/index.php?pagename=Android system.img Customization
let us know what works or doesnt work?

If you are rooted with toast, you can flash the custom roms made with that kitchen. you can add or remove apk files before recompiling to the update zip format. I am typing this from my customized rom I made with that kitchen. The kitchen can root the rom for you, add apps2sd (havent tested that) and add wifi tether. I mainly went this routw as io wanted a rooted .6 rom to use after rooting with the Toast method. I am an Android newbie but managed to do this
Sent from my Evo 4g using Tapatalk

joeykrim said:
i googled, android system.img mount. seems like a great place to start:
http://wiki.xda-developers.com/index.php?pagename=Android system.img Customization
let us know what works or doesnt work?
Click to expand...
Click to collapse
Awesome, I figured I would need linux (why I installed it)
stroths said:
If you are rooted with toast, you can flash the custom roms made with that kitchen. you can add or remove apk files before recompiling to the update zip format.
Click to expand...
Click to collapse
I already said it's useless and I said why, it generates update files...
I need to actually extract/mount the original system, that is precisely what the thread title is about.

From the command line you can create a system dump using the following command
tar -cvf /sdcard/system.tgz /system
assuming both /sdcard and /system are mounted. you may have to use "busybox tar" instead.
You can run it from recovery mode.
To mount the filesystems while in adb shell use
"mount /dev/block/mtdblock4 /system" to mount system
and
"mount /dev/block/mmcblk0p1 /sdcard" to mount sdcard
if needed
As for making an update.zip you can take an existing one and replace the system directory inside it with your own custom one. Rezip it, no need to resign it for the EVO recovery, and flash away. Oh, and you'll have to delete any symlinks from the /system/bin directory inside the zip before flashing.

XT720 question, is it using mot_boot_mode script?

for those that can check on a rooted XT720, is the model using the /system/bin/mot_boot_mode binary still?
im just thinking if its possible to adapt my mods to the XT720 model too?
Please send PM with details if possible.. or maybe just send me a link to the firmware to download and ill check it..

yes, mot_boot_mode is still there in system/bin

en0203 said:
yes, mot_boot_mode is still there in system/bin
Click to expand...
Click to collapse
thanks.. but you got no "vunerable recovery" like G.O.T or OpenRecovery option?
so if we are to change the /system partition, it has to be done "live" somehow?

sorry i am not sure how it can be done but yes, there is no vulnerable rom for xt720 yet

skrilax has released open recovery for xt701 here - modmymobile.com/forums/f545/xt701-open-recovery-1-15-06-18-2010-a-553227/
xt701 and xt720 basically the same thing isnt it?

Void

Void now sense lx

I would have left as silent beta however the guide I sent out had errors so I decided to make public in the end also we need a new thread ^^

what about the incomings call?

j0c1323 said:
what about the incomings call?
Click to expand...
Click to collapse
incoming calls works like last zx hero's

j0c1323 said:
what about the incomings call?
Click to expand...
Click to collapse
what a gorgeous first post xD try it ^.^ as this rom is freshly cooked i'd say nobody could answer that
EDIT: Wifi broken atm

AWESOME!!!

Is the MTD Partition hack required?

G1ForFun said:
Is the MTD Partition hack required?
Click to expand...
Click to collapse
Yeah the partition hack is required

Awesome
Simply amazing.

yeah is it?
G1ForFun said:
Is the MTD Partition hack required?
Click to expand...
Click to collapse
i to would like to know this because i dont think ill do it (even though i really want to try this updated rom) because im worried ill get bricked flashing something recovery (not rom) related wrong (this whole thinking is probably noobish though)
EDIT Sorry i posted a little late i was typing before you answered that guy

Link2097 said:
i to would like to know this because i dont think ill do it (even though i really want to try this updated rom) because im worried ill get bricked flashing something recovery (not rom) related wrong (this whole thinking is probably noobish though)
EDIT Sorry i posted a little late
Click to expand...
Click to collapse
not really any chance of bricking all it does is when the phone partitions the /system/ /data/ etc to a specified size what we are doing is taking down the size of /data/ for say and upping the size of /system/ ^^ think of it the same way as partitioning a hard drive for tripple boot

I guess I'm the first to have the honor of an install error so here it goes;
Flashed partition hack with special MTD instructions
When i got to flashing the rom, it says
E:Cant chown.mod /system/xbin
(No such file or directory)
E:Failure at line 17:
set_perm_recursive 0 2000 0755 0

bigmoew said:
I guess I'm the first to have the honor of an install error so here it goes;
Flashed partition hack with special MTD instructions
When i got to flashing the rom, it says
E:Cant chown.mod /system/xbin
(No such file or directory)
E:Failure at line 17:
set_perm_recursive 0 2000 0755 0
Click to expand...
Click to collapse
did you make a file called "mtdpartmap.txt" on your sd card with the following of "161 4" before you flashed fr-recovery zip

yes, but not exactly
As per the instructions on firerats thread, before I flashed the MTD recovery, I created on my sdcard a txt file named mtdpartmap that contains
"mtd 161 4"
Should it only be "161 4"?

bigmoew said:
yes, but not exactly
As per the instructions on firerats thread, before I flashed the MTD recovery, I created on my sdcard a txt file named mtdpartmap that contains
"mtd 161 4"
Should it only be "161 4"?
Click to expand...
Click to collapse
yeah should be "161 4" without the mtd in it ^^

G1ForFun said:
Is the MTD Partition hack required?
Click to expand...
Click to collapse
yeah and it flies. faster then sunlight try it its really really great =)

xillius200 said:
yeah should be "161 4" without the mtd in it ^^
Click to expand...
Click to collapse
Alright, I'll try it again.
Can I suggest to you editing the original post because firerat's thread that you redirect to gives out these instructions for custom partition sizes:
Firerat said:
* configutaion
By default FR-recovery-v1.5.3-CustomMTD_S.zip will partition
System..... 90mb
Cache...... 2mb
userdata... the rest ..
But you can set your own system and cache sizes
the script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 85mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 85 2" > /sdcard/mtdpartmap.txt
Click to expand...
Click to collapse

ok im a noob on this mtd i have a mytouch 32b still need mtd?

so according to the directions on fireats page, since i have the eng spl i should be good to wipe all 5, flash the Hacked FR-recovery, reboot, flash the rom, then flash the Fr-boot zip, and then should be good to reboot and run?

bry1391ant said:
so according to the directions on fireats page, since i have the eng spl i should be good to wipe all 5, flash the Hacked FR-recovery, reboot, flash the rom, then flash the Fr-boot zip, and then should be good to reboot and run?
Click to expand...
Click to collapse
Make a file on SD crad called "mtdpartmap.txt" first with "161 4" inside ^^ then yeah do just like you said

un/repack .rfs files?

Is it possible to repack a .rfs file? It's easy to extract, but how do you repack?

You can't really repack them...
You can flash them to your, change them and redump them..
Or mount in linux and change... but becareful of permissions this way
Sent from my SPH-D700 using XDA App

chris41g said:
You can't really repack them...
You can flash them to your, change them and redump them..
Or mount in linux and change... but becareful of permissions this way
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
What do you mean by redump? Ill most likely try to change it by mounting in linux like you said...how could the permissions be messed up?

ugothakd said:
What do you mean by redump?
Click to expand...
Click to collapse
Code:
mount -ro remount /dev/block/stl9 /system
sync
cat /dev/block/stl9 > /sdcard/system_redump.img
ugothakd said:
Ill most likely try to change it by mounting in linux like you said...how could the permissions be messed up?
Click to expand...
Click to collapse
The problem is that rfs is proprietary. The file system can only be properly mounted on the phone.
However, since rfs is a backwards-compatible extension of vfat, you can still mount an rfs image with the vfat driver on any Linux machine. This works well enough to grab some files off it. The problem is that regular vfat doesn't support POSIX permissions (owner, group, mode bits, etc.), those are implemented as a proprietary extension. So if you modify an rfs image under vfat, the permissions may end up being not what you expect them to be when mounted on the phone.
The annoying part about modifying rfs images is that, at least under Eclair, an rfs file system couldn't be loopback mounted. I don't know if they can be mounted on an mmcblkp? device or only over an stl one, or even if this limitation is still there.

I don't know about mounting the rfs image directly on the phone.. but I do it on debian.. and the rest of what he said is correct.. as soon as you start changing things.. the links, and permissions may start getting messed up because vfat doesn't support links or posix permissions.. so you will have to be careful with those sorts of things.. but for small carefully made changes it will work

I get it...so redumping makes a .img file that can be (possibly) restored by cwm? So itd be a yaffs2 file system? Or would it still be an rfs file just renamed to .img.
Related to the permissions...if I wanted to say add a program like su or nano to a stock factoryfs.rfs, I would need to chmod the file in terminal emulator after making and odin'ing a tar file for it to work?

no.. rfs is an img regardless and its an rfs img.. he just put an img file extension, you would put an rfs extension and it would flash in odin.. i actually use a different method using dd, there is a tutorial in general i made called making an odin tar.. check it out..
you cant change the permissions when mounted because vfat doesnt support permissions.. you would need to flash it to the phone to change permissions, or.. add an initscript or something that does it..
i suggest leaving those types of things to the kernel though..

chris41g said:
no.. rfs is an img regardless and its an rfs img.. he just put an img file extension, you would put an rfs extension and it would flash in odin.. i actually use a different method using dd, there is a tutorial in general i made called making an odin tar.. check it out..
you cant change the permissions when mounted because vfat doesnt support permissions.. you would need to flash it to the phone to change permissions, or.. add an initscript or something that does it..
i suggest leaving those types of things to the kernel though..
Click to expand...
Click to collapse
I actually have...lol. I think I even thanked you for it. I'm thinking about ways that would help the et4g...they can't pull a stock kernel without root, and they're current method of rooting flashes a different kernel. If rooting can be done by odin'ing a slightly modified factoryfs.rfs, then they can get the kernel, then they hit the holy grail.

If I recall, the SGSII no longer uses rfs.

ugothakd said:
I actually have...lol. I think I even thanked you for it. I'm thinking about ways that would help the et4g...they can't pull a stock kernel without root, and they're current method of rooting flashes a different kernel. If rooting can be done by odin'ing a slightly modified factoryfs.rfs, then they can get the kernel, then they hit the holy grail.
Click to expand...
Click to collapse
So it seems someone needs to install a rooted kernel, install some stuff to the /system partition (su, busybox, bash, nano, recovery(?), whatever), and then dump the /system partition to an image.
Unless maybe I'm missing something...
It shouldn't matter what kernel you have installed while dumping /system.
Kind of off-topic, but still slightly relevant...
Does the Epic 4G Touch get fastboot like the Nexus S 4G did?
[EDIT]
mkasick said:
If I recall, the SGSII no longer uses rfs.
Click to expand...
Click to collapse
Good point, from what I've been told it uses EXT4, so you should be able to mount and edit as much as you like without worry.
[/EDIT]
=]

Son of a gun. I wrote up this nice guide, and it doesn't use rfs??? Thanks for telling me though. I'm still gonna post it. Check the et4g android development section to see it
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
nubecoder said:
So it seems someone needs to install a rooted kernel, install some stuff to the /system partition (su, busybox, bash, nano, recovery(?), whatever), and then dump the /system partition to an image.
Unless maybe I'm missing something...
It shouldn't matter what kernel you have installed while dumping /system.
Kind of off-topic, but still slightly relevant...
Does the Epic 4G Touch get fastboot like the Nexus S 4G did?
[EDIT]
Good point, from what I've been told it uses EXT4, so you should be able to mount and edit as much as you like without worry.
[/EDIT]
=]
Click to expand...
Click to collapse
Nope, good ol' odin like us. And they don't have a rooted kernel. The samsung source doesn't build right

ugothakd said:
Son of a gun. I wrote up this nice guide, and it doesn't use rfs??? Thanks for telling me though. I'm still gonna post it. Check the et4g android development section to see it
Click to expand...
Click to collapse
Could probably just add in some chmod / chown permission commands in there after the cp commands (where you copy su and superuser into the mounted image) and it should work as expected.
Also, I am required to use sudo whenever I mount a factoryfs.rfs file in my Ubuntu install here.
[edit]
ugothakd said:
Nope, good ol' odin like us. And they don't have a rooted kernel. The samsung source doesn't build right
Click to expand...
Click to collapse
Well the NS4G had both Odin and fastboot, I was hoping they would continue on with that. =[
[/edit]
=]

nubecoder said:
Could probably just add in some chmod / chown permission commands in there after the cp commands (where you copy su and superuser into the mounted image) and it should work as expected.
Also, I am required to use sudo whenever I mount a factoryfs.rfs file in my Ubuntu install here.
[edit]
Well the NS4G had both Odin and fastboot, I was hoping they would continue on with that. =[
[/edit]
=]
Click to expand...
Click to collapse
Thanks, I forgot the mount command required root...edited accordingly
Also, you'd have to boot up and chmod because it'l be mounted as a vfat image, which doesn't support permissions.
I also realized you'd need 2 epic touch's for this to work exactly right...

i can confirm the et4g uses ext4.. so you can mount and edit at will.. might need to edit as su on your linux box..

[GUIDE] another way to increase data partition size (non-dualboot)

having a 750mb for data partition like in my previous post seems interesting for everyone. however, make a 2nd rom isn't easy for everyone. there are some people who can't download a rom, which makes dualboot mod useless for them. well...I want to share the joy of having a bigger data partition, so I modify a kernel to enable 2nd ext3 sdcard partition as data partition. for now on lets call this mod **data-2sd**. the steps is quite easy.
preparation step:
1. download a modified kernel from here
2. rename the file to 'boot.img'.
3. repartition your sdcard. all partition is primary. 1st partition fat32. 2nd partition ext3. adjust the partition size to any size you want.
Click to expand...
Click to collapse
the steps:
1. install the kernel
2. make a blank file named 'bootsdcard' in your root sdcard
3. reboot your device.
notes:
1. this kernel is made based on irfanbagus's kernel. (credits for him)
2. if you already have 2nd partition in your sdcard, please reformat it.
3. don't use link2sd or a2sd.
4. clean you init.d folder (optional)
5. you'll need a fast sdcard for best result. our default sdcard is too slow.
Click to expand...
Click to collapse
well...thanks for irfanbagus who has make a dualboot kernel for us. as I have said, I modify the kernel based on his work. the modified script is not an efficient one. I have to admit that. feel free to edit the kernel if you don't satisfy with my work.
btw, I realize that not everyone want to use sdcard's 2nd partition, especially when their sdcard is slow and they have to wait till they have enough money to buy a faster one. well...you don't have to uninstall this kernel since I've made an option to turn off data-2sd feature simply by delete 'bootsdcard' from your sdcard. now, it will act as stock DXLC stock kernel with init.d support. when you already have a fast sdcard you can turn on data-2sd feature again by make 'bootsdcard' file in your sdcard.
you could find the modified files here
www.mediafire.com/download.php?cc1kg8s7cx27onb
www.mediafire.com/download.php?0xydu66254ic6yz
DISCLAIMER:
do it with your own risk. no need to thanks or press it. I'm just a noob. give that to the original dev instead.
KNOWN ROM INCOMPATIBILITY ISSUE
============================
please read this before install this kernel. these roms are reported to incompatible with this kernel. some user said it work, but some other said it doesn't work in these rom. to minimilize the risk, I'll list all reported incompatibility issue with my kernel.[/b]
Incompatibility list
1. chobits digital v1.8 and v2
2. m.u.r (merruk ultimate rom) v1
please inform me if you got another incompatibility issue with other custom rom[/quote]
ADDITIONAL STUFF
==============
if your rom incompatible with this kernel you may try this guide to increase your /data partition as well. you'll need a kernel with init.d support to use this method. please read carefully before modify your system.
1. go to system/etc/init.d
2. delete all a2sd and link2sd related stuff
3. create a new file named 01data2sd. put this script inside it
Code:
#!/system/bin/sh
unmount /data
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data
4. set the permission to 777 (rwxrwxrwx)
5. open your terminal manager. type these command.
Code:
su
mkdir /data/sd-ext
mount -t ext3 -o nosuid,nodev /dev/block/mmcblk0p2 /data/sd-ext
note: its blk-zero-p-two, not blk-O-p2
6. via root explorer go to /data.
7. copy all stuff in /data into /data/sdext.
8. open terminal manager. type these command.
Code:
umount /data/sd-ext
9. restart your device.
if you got bootloop, via adb, type these command
Code:
adb shell
su
mount -o remount rw /system
chmod 222 /system/etc/init.d/*
exit
exit
adb reboot
KNOWN ISSUE: gps not working.
NOTE: the bug is a lil bit annoying for several person. if you want a BETTER-FASTER-BUGLESS-BATTERY FRIENDLY method to save your internal memory, you can use my akuro tweak.
TERM OF USE AND SHARING:
this thread intent is for sharing. feel free to use, edit, distribute all material inside this thread which came from me. if there any parts of this mod which comes not from me please refer to the original dev I've mentioned in this thread. if want to share it to another forum or modify it you don't have to ask my permission. no need to credits, put links or whatsoever. you'll only need to remember that you should held all the responsibility by using this mod, modify it or distribute it. DO IT WITH YOUR OWN RISK
Click to expand...
Click to collapse

what is the advantage?

sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.

I see. I will try this, does it work on creeds 2.0?

it will work on all rom but will make your a2sd didn't work. please remove all a2sd script in init.d before use this mod.

So this will be my steps?
1. FLash your ROM/CUSTOM ROM
2. Delete the scripts in data/system/init.d via Root Explorer.
3. Make a file name "bootsdcard" in root directory of your sdcard.
Question : What file? .txt? .exe?
4. Flash the Kernel via Odin or other methods.
5. Reboot your device.
So now all my apps are on my SD? or all futured apps are on it?

just a plain file without any extension.
for the second question...this mod will change your data partition to 2nd sdcard ext3 partition. its completely different with a2sd or link2sd since it won't move any installed app in your device. your previous app will remain in your original data partition. when you activate the feature and reboot your phone, it would be like when you turn on the device for the first time.

so it will show 750mb not 190mb?

I will try this tomorrow
bla bla bla

devion14 said:
so it will show 750mb not 190mb?
Click to expand...
Click to collapse
it depends on your partition size. you can make it 750mb, 1gb, or any size you want.

does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..

Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2

kurotsugi said:
sgy's original data partition size is only 190mb. you can get 1gb or bigger data partition for your device by using this mod.
Click to expand...
Click to collapse
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment

devion14 said:
does it support init d tweaksthe kernel is based on what??
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
and what stock rom should i used? what roms have no sd card issues? im using dxlc1..
Click to expand...
Click to collapse
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
krishna_nirvana said:
Now I am using DDLC2 official firmware and my 2nd partition (ext3) size is 1.06 GB,
but I am not using any kernal and other thing, I am using pure official ROM and
rooted my mobile thats all. From lot of months I am using this second partition
with Link2sd app.
See this attachment
Click to expand...
Click to collapse
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
tandob said:
Sir. I dont have to modified the custom rom with modified updater-script? I just have to flash the kernel and then custom rom with the formated 1st. Fat32 and 2nd. Ext3. ?
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.

What is the Base Firmware of This Modified Kernel?
I Hope its DXLC1? Or ?

tandob said:
Click to expand...
Click to collapse
is it for real?
kurotsugi said:
it supports init.d script. however, there are some script in init.d which will mount your 2nd partition in different place. its better to remove them before you activate this feature.
it works for both custom and stock rom.
thats your choice. however this mod doesn't require any app and you don't have to link your app to to ext partition. when you uninstal link 2sd you'll lose all your app in ext partition.
nope. you don't need to install any rom. but make sure that you have a clean 2nd ext partition.
Click to expand...
Click to collapse
ok...ill try...i will use
v6 supercharger only

yup...its based on DXLC kernel. we do only a minor modification in init.rc and /sbin folder.

ok, downloading now..will give this a shot
BTW does increasing internal memory with this increase speed a little bit? coz the more internal memory the faster right?

internal memory space doesn't related to device speed. in fact, it will a little bit slower since ext3 partition is slower than rfs. nevertheless, the differences is not significant. and could only seen in benchmarking test.