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.
Related
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.
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..
Works on 2.3.7 upto 4.2.2(At least thats all I have tested).
Hi,Guys this is an awesome app here let me start by stating.
Advantages of Odexed Rom.
1.Better Battery life
2.Better app performance.
3.lower ram usage.
Disadvantages of Odexed Rom.
1.no themes can be applied(and i mean at all).
2.Lower /system space.
How to Install -Guide-
1) make sure you have a custom rooted rom / kernel with init.d support (scripts must be able to run at boot: it is a folder in /system/etc). It is very important or it won't run pre-boot scripts.
2) make sure that you don't have any themes applied before odexing or you will loose your themed apps after odexing.
3) simply put the apk in /system/app folder with a file browser like "Root Explorer" and ofcourse give correct permissions rw-,r--,r-- and reboot.
4) do a nandroid backup(just added safety) and/or a titanium backup of all user apps and system data
5)Start ODEX ME app
6) follow the onscreen instructions.
7)your device will boot several times or even boot for a long time(Its all normal).
8)to see if you rom is odexed go to /system/app partition and you will see a whole lot of .odex files.
Credit :
paulobrien : for the app.Original Thread : http://forum.xda-developers.com/showthread.php?t=1215271
Dark Passenger : for testing the app and sharing.
NOTE : doesnt work with any app2sd script that moves system dalvik cache to /sd-ext eg.INT2EXT4+
copy paste already share in galaxy mini section,anyway nice
fitranger said:
copy paste already share in galaxy mini section,anyway nice
Click to expand...
Click to collapse
hello this is no copy paste work.
yes there may be a shared thread in mini section but here i posted to share the app as I thought it might be useful for fit users.
Dark Passenger said:
Hi,Guys this is an awesome app here let me start by stating.
Advantages of Odexed Rom.
1.Better Battery life
2.Better app performance.
3.lower ram usage.
Disadvantages of Odexed Rom.
1.no themes can be applied(and i mean at all).
2.Lower /system space.
How to Install -Guide-
1) make sure you have a custom rooted rom / kernel with init.d support (scripts must be able to run at boot: it is a folder in /system/etc). It is very important or it won't run pre-boot scripts.
2) make sure that you don't have any themes applied before odexing or you will loose your themed apps after odexing.
3) simply put the apk in /system/app folder with a file browser like "Root Explorer" and ofcourse give correct permissions rw-,r--,r-- and reboot.
4) do a nandroid backup(just added safety)
5)Start ODEX ME app
6) follow the onscreen instructions.
7)your device will boot several times or even boot for a long time(Its all normal).
8)to see if you rom is odexed go to /system/app partition and you will see a whole lot of .odex files.
Credit :
paulobrien : for the app.Original Thread : http://forum.xda-developers.com/showthread.php?t=1215271
Dark Passenger : for testing the app and sharing.
Works on 2.3.7 upto 4.2.2(At least thats all I have tested).
Click to expand...
Click to collapse
How to make nandroid backup if I not have Amon-RA, than CWM5?
ZmisiS said:
How to make nandroid backup if I not have Amon-RA, than CWM5?
Click to expand...
Click to collapse
I think all recoveries support backup options(that is nandroid backup)
else backup all user apps and system data using titanium backup.
Partial odexing from fixes themes
Sent from my GT-S5570 using Tapatalk 2
Tried it!! It's Working!!!:thumbup::thumbup: Odexed my Cyanmobile rom without any issues. Thanks for sharing this ONE-CLICK-ODEX app. I really needed it.
Pls. tell if this app can odex 2.3.6 custom rom (like Razodroid,creeds...etc), I've read the heading already but just curious.
Thnks Again
Sent Via XDA™ Premium
Galaxy_Rohit said:
Tried it!! It's Working!!!:thumbup::thumbup: Odexed my Cyanmobile rom without any issues. Thanks for sharing this ONE-CLICK-ODEX app. I really needed it.
Pls. tell if this app can odex 2.3.6 custom rom (like Razodroid,creeds...etc), I've read the heading already but just curious.
Thnks Again
Sent Via XDA™ Premium
Click to expand...
Click to collapse
yes.
Looks interesting will try it!!
For me in CM 10.1 Setting.apk removed and it has disappeared in the menu.How to solve it?
Android Daymon said:
For me in CM 10.1 Setting.apk removed and it has disappeared in the menu.How to solve it?
Click to expand...
Click to collapse
Huh what sorry are you saying that you placed the apk in /system/app partition gave it permission rw-,r--,r-- rebooted , clicked on the app icon from the app drawer of odex me. choice odex now let the phone remain aside till it stabalised about 5 min max. and then your settings app is not there.
what did you do cause I am using latest release and nothing happened.
Yes,I do what you say.but my settings disappeared.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
Doesn't it work with INT2EXT4+?????
Android Daymon said:
Yes,I do what you say.but my settings disappeared.
---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------
Doesn't it work with INT2EXT4+?????
Click to expand...
Click to collapse
OH MY did you do the steps I mentioned after flashing int2ext4+ no wonder go into /system/app and tell me if there is a file called settings.apk and settings.odex
for most safe and best result always run first any script. mod .anything you need done then flash any app2sd script.
Sry... but I can't odex official cyanogenmod (2.3.7). It goes to bootloops. (Cyanmobile, Razodroid etc. were odexed successfully by your mentioned method but not this one)
Sent Via XDA™ Premium
Galaxy_Rohit said:
Sry... but I can't odex official cyanogenmod (2.3.7). It goes to bootloops. (Cyanmobile, Razodroid etc. were odexed successfully by your mentioned method but not this one)
Sent Via XDA™ Premium
Click to expand...
Click to collapse
I'm using cm7 official odexed so what exactly did you do is your dalvik cache moved to /sd-ext cause that will explain the boot-loop.
sol. don't use any app2sd solutions till after you have odexed k.
Dark Passenger said:
I'm using cm7 official odexed so what exactly did you do is your dalvik cache moved to /sd-ext cause that will explain the boot-loop.
sol. don't use any app2sd solutions till after you have odexed k.
Click to expand...
Click to collapse
I use Link2SD. I also used Link2SD on Cyanmobile too but no bootlooping in that while odexing.
So, do I've to unlink all the links of Link2SD & then try odexing??
If Yes, then I'll give it a try...
Sent Via XDA™ Premium
Galaxy_Rohit said:
I use Link2SD. I also used Link2SD on Cyanmobile too but no bootlooping in that while odexing.
So, do I've to unlink all the links of Link2SD & then try odexing??
If Yes, then I'll give it a try...
Sent Via XDA™ Premium
Click to expand...
Click to collapse
that doesnt make any sense link2sd moves only user installed apps not system so should give no problem....? but you can try and unlink from link2sd and see how it goes.
After I installed this OdexMe, in system/app, I have only 4,96 MB free.
ZmisiS said:
After I installed this OdexMe, in system/app, I have only 4,96 MB free.
Click to expand...
Click to collapse
hmm thats actually not really any problem or bug the app converts the dex files to odex files and stores the file onto /system/app basically the dalvik cache of system apps is moved to the /system/app directory. Hence the lower space.
Dark Passenger said:
hmm thats actually not really any problem or bug the app converts the dex files to odex files and stores the file onto /system/app basically the dalvik cache of system apps is moved to the /system/app directory. Hence the lower space.
Click to expand...
Click to collapse
I know, but now I can't install some applications.
Is there a possibility that I can remove .odex files, and that I do not again install ROM?
hi i am riyaz from Inida i got i997 from customer hang on samsung it was emmc fault so i remove emmc now phone is starting ok but cant use camera so i want original or modified vold.fstab which swap internal storage to external thanks
wbr
What kernel / rom are you running?
Typically this is set up by the custom kernels. The GB custom kernels update this file on every boot. If running GB, try both Entropy DD and Infusion-Z - they handle vold.fstab differently. You can get either kernel from the Infuse Toolkit (see link in my sig). If running a stock kernel rooted you can edit /system/etc/vold.fstab and change the last part of the last line before the "end line" from "mmc_host/mmc2" to "mmc_host/mmc1" (or perhaps the reverse depending on your setup). [edit] - Or, with a GB kernel, you can rename the vold.fstab file at the location above, reboot phone, and the kernel will reinstall a clean copy of the file. The edit above may still be needed.
Here are the files used by the common custom firmwares on the Infuse:
JB (CM 10.1): https://github.com/scotthartbti/android_device_samsung_infuse4g/blob/cm-10.1/prebuilt/etc/vold.fstab
ICS - https://github.com/TeamRefuse/android_device_samsung_infuse4g/blob/ics/vold.fstab
GB1 - https://github.com/ZenArcade/initramfs_sgh-i997r-z/blob/master/voodoo/extensions/vold/vold.fstab (mmc1)
GB2 - https://github.com/Entropy512/initramfs_sgh-i997r/blob/master/voodoo/extensions/vold/vold.fstab (mmc2)
thanks for replay i am using
(I997UCLB3-CWM-root-deodex.rar ) this firmware
cdma-india said:
thanks for replay i am using
(I997UCLB3-CWM-root-deodex.rar ) this firmware
Click to expand...
Click to collapse
That package includes Entropy's DD kernel. You can use the GB2 file linked above, or you can delete the existing file and reboot. Either should get you a working vold.fstab file and access to your external SD card from the phone OS. At present neither kernel offers the ability to read the external SD card from CWM recovery.
If after this you still cannot see /sdcard/external_sd, try the GB1 file or make the edit I described above.
This is not a guide for noobs or a step by step guide, but it is extremely easy for devs who have knowledge of all the things mentioned here.
As always, do anything at your own risk.
Require things+knowledge of:-
1. MTK Device's boot.img and custom recovery.img (CWM/TWRP/etc)
2. Windows PC with Cygwin and MT65xx .img unpack/repack scripts
3. Notepad++
4. A Class 6 or better Micro SD Card+a good card reader (lower than class 6 will give you lags/phone freeze, but, it'll work)
5. Mini tool partition wizard
6. Working roms for your device
7. A compression tool (i use 7zip)
8. Mobile uncle tool (google play, apk) installed in phone (or sp flash tool in pc, if you want it this way )
Steps:-
1. PARTITIONING MEMORY CARD:
Plug your memory card using card reader and copy everything from it to PC as we are going to partition it.
All partitions are PRIMARY
Select your card in mini tool and delete the partition. Partition it as follows-
First Partition-FAT32 (total memory card size-1924mb) <----- SD CARD
This is the space you will see as your memory card (external sd) in both of your roms.
Second Partition-EXT4 (550mb) <------ SYSTEM
This is System Partition of Second Rom
Third Partition-EXT4 (1024mb) <----- DATA
This is Data Partition of Second Rom, apps will go here
Fourth Partition-EXT4 (350mb) <----- CACHE
You can reduce it a bit more if you want to.
2. PREPARING SECONDARY ROM'S ZIP:
Get the updater-script of the rom you want to dual boot and open it up in notepad++
Press ctrl+F in notepad++ and go to replace tab.
Find what-mmcblk0p3 (may differ for different devices, look for "mount("ext4", "EMMC", "/dev/block/mmcblk0p3");" in updater script to know)
Replace with-mmcblk1p2
Save it and move it back to its location in zip (META-INF\com\google\android)
Note: if there is data folder in rom's zip then you also have to replace data partition block with mmcblk1p3, like: mmcblk0p5--->mmcblk1p3
3. PREPARING SECONDARY ROM'S BOOT.IMG:[/COLOR]
Unpack boot.img of the rom you want to dual boot using mt65xx tool and cygwin.
Open notepad++ and drag and drop all files of ram-disk to notepad++
Once again, find and replace:
Find what-[email protected]
Replace with-mmcblk1p2
Find what-[email protected]
Replace with-mmcblk1p3
Find what-[email protected]
Replace with-mmcblk1p4
Save all and pack the ram-disk with kernel to dualboot.img
4. PREPARING SECONDARY ROM'S RECOVERY (OPTIONAL IF YOU DON'T WANT TO CHANGE THE SECONDARY ROM EVER):[/COLOR]
Unpack recovery.img like your unpacked boot.img and open 'etc\recovery.fstab' with notepad++
Edit from this-
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/cache ext4 [COLOR="red"]/[email protected][/COLOR]
/data ext4 [COLOR="red"]/[email protected][/COLOR]
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/emmc vfat /[email protected]
/system ext4 [COLOR="red"]/[email protected][/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto [COLOR="red"]/dev/block/mmcblk1p2[/COLOR]
to this
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/cache ext4 [COLOR="red"]/dev/block/mmcblk1p4[/COLOR]
/data ext4 [COLOR="red"]/dev/block/mmcblk1p3[/COLOR]
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/emmc vfat /[email protected]
/system ext4 [COLOR="red"]/dev/block/mmcblk1p2[/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
#/sd-ext auto [COLOR="red"]/dev/block/mmcblk1p5[/COLOR]
Save and pack the edited one as dualrecovery.img.
5. MAKING UPDATE.ZIP FOR BOOT.IMG:
Download Boot.zip, copy it once, open Boot.zip with 7zip and place your Primary Rom's boot.img (replace the dummy one) in it with meta-inf folder.
Rename the Copy of Boot.zip to DualBoot.zip and place Secondary Rom's boot.img (the one you edited in step 3) in it with meta-inf folder.
6. SETTING UP IN MEMORY CARD:
a. Move all initially copied files back to your card
b. Create 2 folders with names:
"1Primary Rom"
"1Secondary Rom"
In "1Primary Rom" copy/move-
a. Boot.zip
c. Primary Rom.zip (not required)
In "1Secondary Rom" copy/move-
a. DualBoot.zip
b. Secondary Rom.zip
7. FLASHING/SWITCHING ROMS:
Just reboot to recovery and flash the Secondary rom from "1Secondary Rom' folder and after that flash "DualBoot.zip"
You will be rebooted to secondary rom automatically.
To Switch Roms, Reboot to recovery and flash Boot.zip for primary and DualBoot.zip for secondary rom.
8. SYNC DATA OF APPS BETWEEN ROMS:
Like in my case, if you want to test/use both rom at the same time or want to use features of both roms at the same time, consider making a filter in primary rom's titanium backup, of user apps which are common in both the roms, and export the list to clipboard.
Create a widget of ti backup up to 'backup all modified data' and use the filter you just created.
Open any file explorer (i use es file explorer) and create a new text file and past the list of apps (you exported to clipboard in ti backup), save it.
Reboot to secondary rom, open that text file, copy everything, open ti backup, create filter, import from clipboard, save and create a widget same way.
Restore date of this filter in secondary rom.
Whenever you want to switch rom, tap the widget, reboot to secondary/primary rom, restore filter.
For contacts, calender, browser bookmarks, etc, use google account to sync in both roms.
Notes:
1. By this folder preparation in memory card, you will get these two folders at the top in cwm recovery, this is for ease only.
2. If you want to use data on sd kind of thing, use mmcblk1p5 instead of mmcblk1p2 (not tested if data on sd will work or not with secondary rom)
3. If you want to apply any update to secondary rom, check the updater-script of the update if there is a need to edit mount path (mmcblk0p3-->mmcblk1p2)
4. Recovery for secondary rom should be flashed using mobile uncle tools/sp flash tool before flashing secondary rom, second time. As this time we will need to wipe data, cache, dalvik-cache and system if required.
Now Press THANX And Subscribe
My Work:
Mods For Lg L3 E405 Dual
Micromax Canvas Music Kernel Development Thread
How to mod lewa os PIM.apk (sms)
Multi Boot MTK Devices
Custom recoveries for Canvas Music A88 and Canvas 2 A110
Micromax Canvas Music Custom Rom's Patches
MT6577 Auto Focus Fix
Will try this out when i get to go back in win7. Thanks for sharing this bro!
Sent from my H120 using Tapatalk
AMAZING MAN!!!
Will give it a try!!
dnle71 said:
Will try this out when i get to go back in win7. Thanks for sharing this bro!
Sent from my H120 using Tapatalk
Click to expand...
Click to collapse
Shivam Bhalla said:
AMAZING MAN!!!
Will give it a try!!
Click to expand...
Click to collapse
i was still editing it when you replied. i guess there was a huge need of this.
Sudeep Duhoon said:
i was still editing it when you replied. i guess there was a huge need of this.
Click to expand...
Click to collapse
As you know buddy there's nothing much happening for MTK devices we didnt have Cyanogen Mod we didnt have source codes for our devices and there are so much development in other sections of other devices but nothing for us. So each and every new thing is very precious for our MTK devices.
Again Thanks for this tutorial !!! :good:
Looks good, thanks
This looks like the same mod i did for my old ZTE Blade, from the MoDaCo forum.
Great MOD.
Will try it on the next weekend :good:
superdragonpt said:
Looks good, thanks
This looks like the same mod i did for my old ZTE Blade, from the MoDaCo forum.
Great MOD.
Will try it on the next weekend :good:
Click to expand...
Click to collapse
I have never had a zte blade, but i did got a lg optimus. I got inspired from data on sd mod and tried system on sd, got success. Tried the same on canvas music and not to my surprise, worked again.
Will edit more to make this better.
Sent from one and only Canvas 4 unnamed rom for canvas music
Sudeep Duhoon said:
I have never had a zte blade, but i did got a lg optimus. I got inspired from data on sd mod and tried system on sd, got success. Tried the same on canvas music and not to my surprise, worked again.
Will edit more to make this better.
Sent from one and only Canvas 4 unnamed rom for canvas music
Click to expand...
Click to collapse
You mean by tassadar? From p500 forum?
Sent from my H120 using Tapatalk
dnle71 said:
You mean by tassadar? From p500 forum?
Sent from my H120 using Tapatalk
Click to expand...
Click to collapse
I don't remember as it's around 6 7 months now.
Sent from one and only Canvas 4 unnamed rom for canvas music
Sudeep Duhoon said:
I have never had a zte blade, but i did got a lg optimus. I got inspired from data on sd mod and tried system on sd, got success. Tried the same on canvas music and not to my surprise, worked again.
Will edit more to make this better.
Sent from one and only Canvas 4 unnamed rom for canvas music
Click to expand...
Click to collapse
Yeah the base MOD and the principal is the same, well done for porting to our platform
Just tested, so far so good ; )
This is something i will use, still, maybe i (we) can improve this MOD
Class! Space for improvements, in terms of switching and all that. Well done man!
Woah... Dual boot.... Wish i still had my xolo a1000... But then again I got a lot of followers who are willing to test it for me here in my country... Will try this soon .. Great job... Thanks. For sharing it
Sent from my GT-I9070 using xda app-developers app
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
Btw... This just came to my head... Since external sdcard requires class 6 or greater.. Have you tried using the internal sdcard if it yields good results???
Sent from my GT-I9070 using xda app-developers app
---------- Post added at 12:51 PM ---------- Previous post was at 12:51 PM ----------
Btw... This just came to my head... Since external sdcard requires class 6 or greater.. Have you tried using the internal sdcard if it yields good results???
Sent from my GT-I9070 using xda app-developers app
thirdzcee said:
Woah... Dual boot.... Wish i still had my xolo a1000... But then again I got a lot of followers who are willing to test it for me here in my country... Will try this soon .. Great job... Thanks. For sharing it
Sent from my GT-I9070 using xda app-developers app
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
Btw... This just came to my head... Since external sdcard requires class 6 or greater.. Have you tried using the internal sdcard if it yields good results???
Sent from my GT-I9070 using xda app-developers app
---------- Post added at 12:51 PM ---------- Previous post was at 12:51 PM ----------
Btw... This just came to my head... Since external sdcard requires class 6 or greater.. Have you tried using the internal sdcard if it yields good results???
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I am using internal sd in data partition for primary rom and moved apps to external s de for secondary rom, so i can't try. And it will be a bit difficult to partition internal sd according to our wish.
This way i get,
For primary rom-
580mb system
2.5gb data
50mb internal sd
26.76 gb external sd
For secondary rom-
550mb system
1536mb data
200mb cache
26.76 gb sd
Sent from one and only Canvas 4 unnamed rom for canvas music
Demo please.
Why don't you guys take a video and post its link? Atleast those who were not able to follow the OP can enjoy seeing the instructions in action. A fantastic idea and a fantastic guide as it is apparently working.
Thank you all once again.
hariks0 said:
Why don't you guys take a video and post its link? Atleast those who were not able to follow the OP can enjoy seeing the instructions in action. A fantastic idea and a fantastic guide as it is apparently working.
Thank you all once again.
Click to expand...
Click to collapse
The famous restriction with me-limited data.
Can't upload vid.
Sent from one and only Canvas 4 unnamed rom for canvas music
A video speaks a million words.
Sudeep Duhoon said:
The famous restriction with me-limited data.
Can't upload vid.
Sent from one and only Canvas 4 unnamed rom for canvas music
Click to expand...
Click to collapse
Any other takers ?
awesome idea
great guide !!!
I enjoyed going through the guide very easy had a few minor adjustments for my star s7189 (mt6582) worked great thanks !"!!!
billyfraser93 said:
I enjoyed going through the guide very easy had a few minor adjustments for my star s7189 (mt6582) worked great thanks !"!!!
Click to expand...
Click to collapse
what are the changes youve made?
@OP, I've a class 4 SD-CARD. Are you sure they'll there will be freezes?
Regards.