Hey guys,i have one request for you.Did anyone can do a Rom with expanded system memory?To expand the 150mb of lg l3 to 500 or 1000mb.Please post is someone can do this,or say to me(step by step)how to do this.
[Request]Exapnding system memory.
Started by
bredwolf
, Mar 02 2013 07:34 PM
#1
Posted 02 March 2013 - 07:34 PM
#2
Posted 02 March 2013 - 08:39 PM
we have to change the base like zte blade with tpt
this is hard to dev and can brick easiely
this is hard to dev and can brick easiely
#3
Posted 02 March 2013 - 09:15 PM
change the cwm recovery fstab to recognise a new layout
create a new cwm recovery with new layout
flash it
create roms with new layout
flash them
stock mount points
new mount points
only one change made, but would change data partition from 150mb to 1024mb.
create a new cwm recovery with new layout
flash it
create roms with new layout
flash them
stock mount points
# mount point fstype device [device2] fstype2 /recovery emmc /dev/block/mmcblk0p17 /boot emmc /dev/block/mmcblk0p9 /cache ext4 /dev/block/mmcblk0p16 /data ext4 /dev/block/mmcblk0p21 /emmc vfat /dev/block/mmcblk0p20 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1 /system ext4 /dev/block/mmcblk0p14
new mount points
# mount point fstype device [device2] fstype2 /recovery emmc /dev/block/mmcblk0p17 /boot emmc /dev/block/mmcblk0p9 /cache ext4 /dev/block/mmcblk0p16 /data ext4 /dev/block/mmcblk0p20 /emmc vfat /dev/block/mmcblk0p21 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1 /system ext4 /dev/block/mmcblk0p14
only one change made, but would change data partition from 150mb to 1024mb.
#4
Posted 02 March 2013 - 09:17 PM
okay, this was new for me!
can you do that? is this save?
can you do that? is this save?
#5
Posted 03 March 2013 - 07:08 AM
hmm,i don`t know to do that...Maybe one developer will read hecatae`s post and will do that,or maybe hecatae will do if he has some time:D.Thanks.
#6
Posted 03 March 2013 - 08:20 AM
#7
Posted 03 March 2013 - 09:44 AM
hecatae, on 02 March 2013 - 09:15 PM, said:
change the cwm recovery fstab to recognise a new layout
create a new cwm recovery with new layout
flash it
create roms with new layout
flash them
stock mount points
new mount points
only one change made, but would change data partition from 150mb to 1024mb.
create a new cwm recovery with new layout
flash it
create roms with new layout
flash them
stock mount points
# mount point fstype device [device2] fstype2 /recovery emmc /dev/block/mmcblk0p17 /boot emmc /dev/block/mmcblk0p9 /cache ext4 /dev/block/mmcblk0p16 /data ext4 /dev/block/mmcblk0p21 /emmc vfat /dev/block/mmcblk0p20 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1 /system ext4 /dev/block/mmcblk0p14
new mount points
# mount point fstype device [device2] fstype2 /recovery emmc /dev/block/mmcblk0p17 /boot emmc /dev/block/mmcblk0p9 /cache ext4 /dev/block/mmcblk0p16 /data ext4 /dev/block/mmcblk0p20 /emmc vfat /dev/block/mmcblk0p21 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1 /system ext4 /dev/block/mmcblk0p14
only one change made, but would change data partition from 150mb to 1024mb.
can i use this mount points on editing ramdisk?
which file(s) should be edited? init.rc?
Edited by yayakuya, 03 March 2013 - 09:45 AM.
#8
Posted 03 March 2013 - 02:49 PM
so,yayakuya,you will try to do this?Please keep us at currency with all news,and when you need help please say:D.
#9
Posted 03 March 2013 - 05:50 PM
#10
Posted 08 March 2013 - 01:05 PM
this is for the partition structure created to use with link2sd (ie fat, ext, fat32)
REMOVE ALL SCRIPTS U ARE USING TO MOUNT EXT PARTITION AND MAKE A TITANIUM BACKUP OF ALL APPS
extract init.rc of boot.img and edit it.
do the following
1. search 'on fs'
on fs
comment out 'mount yaffs2 mtd@userdata /data nosuid nodev' with #
like this
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
#mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
now on 'on emmc-fs'
replace
wait /dev/block/mmcblk0p21
exec /system/bin/demigod_make_ext4fs -l 160M /dev/block/mmcblk0p21 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk0p21
mount ext4 /dev/block/mmcblk0p21 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
with
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
exec /system/bin/demigod_make_ext4fs -e /dev/block/mmcblk1p2 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk1p2
mount ext4 /dev/block/mmcblk1p2 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
save it
pack the boot.img and flash it using cwm
if u have any cwm flashable package with u then extract 'META-INF>com>google>android>updater-script' and edit it with notepad++
delete everithing it it and paste this
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("boot.img", "/tmp/boot.img");
assert(run_program("/system/bin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p9")=="0");
run_program("/sbin/busybox", "umount", "/system");
save it and drag and drop it to it's location, i.e. 'META-INF>com>google>android> here'
now drag and drop boot.img in the zip (no folder, the zip itself)
make a nandroid backup and flash this.
now, advance restore ONLY data using cwm recovery and reboot
if you want to mount external sd as internal sd do this in int.rc (this may have bugs)
search this
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
now remove all # from
# [START] LGE_USE_INTERNAL_FAT
#wait /dev/block/mmcblk0p20
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
#exec /system/bin/e2fsck -y /dev/block/mmcblk0p20
#mount vfat /dev/block/mmcblk0p20 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
to make it like to like like this
# [START] LGE_USE_INTERNAL_FAT
wait /dev/block/mmcblk1p3
exec /system/bin/resize2fs /dev/block/mmcblk1p3
exec /system/bin/e2fsck -y /dev/block/mmcblk1p3
mount vfat /dev/block/mmcblk1p3 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
add this above "mount vfat /dev/block/mmcblk1p3 /mnt/sdcard" if not mounting
unmount /dev/block/mmcblk0p20
save, pack, flash, enjoy.
and no need to do anything with the recovery. your backup of data will be huge now.
REMOVE ALL SCRIPTS U ARE USING TO MOUNT EXT PARTITION AND MAKE A TITANIUM BACKUP OF ALL APPS
extract init.rc of boot.img and edit it.
do the following
1. search 'on fs'
on fs
comment out 'mount yaffs2 mtd@userdata /data nosuid nodev' with #
like this
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
#mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
now on 'on emmc-fs'
replace
wait /dev/block/mmcblk0p21
exec /system/bin/demigod_make_ext4fs -l 160M /dev/block/mmcblk0p21 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk0p21
mount ext4 /dev/block/mmcblk0p21 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
with
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
exec /system/bin/demigod_make_ext4fs -e /dev/block/mmcblk1p2 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk1p2
mount ext4 /dev/block/mmcblk1p2 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
save it
pack the boot.img and flash it using cwm
if u have any cwm flashable package with u then extract 'META-INF>com>google>android>updater-script' and edit it with notepad++
delete everithing it it and paste this
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("boot.img", "/tmp/boot.img");
assert(run_program("/system/bin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p9")=="0");
run_program("/sbin/busybox", "umount", "/system");
save it and drag and drop it to it's location, i.e. 'META-INF>com>google>android> here'
now drag and drop boot.img in the zip (no folder, the zip itself)
make a nandroid backup and flash this.
now, advance restore ONLY data using cwm recovery and reboot
if you want to mount external sd as internal sd do this in int.rc (this may have bugs)
search this
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
now remove all # from
# [START] LGE_USE_INTERNAL_FAT
#wait /dev/block/mmcblk0p20
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
#exec /system/bin/e2fsck -y /dev/block/mmcblk0p20
#mount vfat /dev/block/mmcblk0p20 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
to make it like to like like this
# [START] LGE_USE_INTERNAL_FAT
wait /dev/block/mmcblk1p3
exec /system/bin/resize2fs /dev/block/mmcblk1p3
exec /system/bin/e2fsck -y /dev/block/mmcblk1p3
mount vfat /dev/block/mmcblk1p3 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
add this above "mount vfat /dev/block/mmcblk1p3 /mnt/sdcard" if not mounting
unmount /dev/block/mmcblk0p20
save, pack, flash, enjoy.
and no need to do anything with the recovery. your backup of data will be huge now.
Edited by SudeepDuhoon, 08 March 2013 - 01:21 PM.
#11
Posted 09 March 2013 - 12:39 AM
thanks for the info, will try to implement it too,especially with encryption ) By the way, anybody needs a flashable zip enabling ICS native encryption for us? I made a post in a big topic and can advance it with flash.
#12
Posted 09 March 2013 - 11:40 AM
hm, maybe someone, but I'm not interested in the encryption
make this sense? I mean, kernel 3.0 will came soon, and with that 4.1-4.2 will arrived
and encryption is a main feature of jellybean...
it woud be nice if you dev the ICS native encryption, but I don't want you to do something for nothing ;P
make this sense? I mean, kernel 3.0 will came soon, and with that 4.1-4.2 will arrived
and encryption is a main feature of jellybean...
it woud be nice if you dev the ICS native encryption, but I don't want you to do something for nothing ;P
#13
Posted 09 March 2013 - 11:57 AM
Native ICS encryption works, and it fails only because CWM format full data partition not leaving the footer of 16KB, and due to one commented string in init.rc
The chargerfix also uncomments it and a zip will contain a chargerfix bootimg and data repartition command I posted before.
Do you ever know if Jelly Bean supports encrypting SD cards along with conventional data encryption?
Do you ever know if Jelly Bean supports encrypting SD cards along with conventional data encryption?
Attached Files
Edited by gellmar, 09 March 2013 - 12:06 PM.
#14
Posted 09 March 2013 - 01:25 PM
Dumped mmcblk0 partitions and tried to parse what is what - http://www.modaco.co...t/#entry2099946
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account

Back to top










