[Q] How to mount partition 2 (ext3) on SD card? - Droid Incredible Q&A, Help & Troubleshooting

[Q] How to mount partition 2 (ext3) on SD card? - Droid Incredible Q&A, Help & Troubleshooting

I used Amon-Ra's recovery to create a 1 GB ext3 partition on my SD card.
When I look at the card in a UNIX like OS the partition is there.
Ideally, I'd like to have partition's file system mount & unmount at /sd-ext
or /mnt/sd-ext programaticly. I've been trying to figure out what its /dev name is.
ADB's shell says partition 1 is /dev/block/vold/179:9 mounted on /mnt/sdcard.
There are 12 /dev/block/vold/179:?? (0-11) how do I find out which is
associated with partition 2?
Or is there another way to reach it? Is there a root app to mount / unmount
a file system? Do I need to use ADB or a local shell?

mouting and using tune2fs -l /dev/block/mmcblk0p2
tune2fs -l /dev/block/mmcblk0p2
you can use tune2fs -l and the block name to get the nitty gritty details of the partition or disk.
you can use df and or mount commands to get the details of your system
you can also cd into /dev/block/ and use ls to see all the files in there: below is my output with is use ls in /dev/block/
[email protected]_targa:/dev/block# ls
ls
dm-0
vold
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk1p27
emstorage
mmcblk1p26
userdata
mmcblk1p25
webtop
mmcblk1p24
preinstall
mmcblk1p23
cache
mmcblk1p22
system
mmcblk1p21
kpanic
mmcblk1p20
cid
mmcblk1p19
misc
mmcblk1p18
cdrom
mmcblk1p17
recovery
mmcblk1p16
boot
mmcblk1p15
mmcblk1p14
mmcblk1p13
mmcblk1p12
mmcblk1p11
mmcblk1p10
mmcblk1p9
mmcblk1p8
pds
mmcblk1p7
mmcblk1p6
mmcblk1p5
mmcblk1p4
mmcblk1p3
mmcblk1p2
mmcblk1p1
mmcblk1
mmcblk0p3
mmcblk0p2
mmcblk0p1
platform
mmcblk0
[email protected]_targa:/dev/block#
mmcblk0... is my external sd card, it has 3 partitions, mmcblk0p1 is the one recognized and mounted by android, mmcblk0p2 is the ext3fs, and mmcblk0p3 is a linuxswap file

This should mount the ext3 partition to /data/sd-ext. You will need to create the sd-ect folder before running the command in the terminal.
mount -t ext3 -o rw /dev/block/vold/179:10 /data/sd-ext

cmlusco said:
This should mount the ext3 partition to /data/sd-ext. You will need to create the sd-ect folder before running the command in the terminal.
mount -t ext3 -o rw /dev/block/vold/179:10 /data/sd-ext
Click to expand...
Click to collapse
and than how to use it with vold to mount to PC via USB?

purportex said:
and than how to use it with vold to mount to PC via USB?
Click to expand...
Click to collapse
I dont believe that is possible, at least as far as i know. It would probably require a modified ramdisk which is over my head, i wouldnt know where to begin.

Related

Difference between app2sd and standard app manager?

Hi Guys,
Im currently running oxygen RC7 on my Htc Desire. ok im a little confused as to how i have such little space. According to wikipedia the Desire has 512mb flash memory. But according to app2sd it has a total of 185.69MB and according to settings it has 148Mb. So which is it? Now im aware that the rom takes up some space now onto the second part of my question.
I also have partitioned my SD card to 512mb with rom manager, but this doesnt explain the random sizes both A2SD and system settings are saying. Also i dont understand what i achieved by partitioning my sd card i didnt see any difference in size on the storage settings am i just looking in the wrong place.
My understanding is that app2sd moves apps to the ext3 partition created by Rom manager and the stock application manager moves apps to the fat partition. My reasoning for this is that some apps can be moved to SD by the stock application manager and the same apps cant be moved by app 2 SD
Can anyone explain this to me?
Thanks

I don't know much about Apps2SD, A2SD or what ever you call it but I will give it a go anyway and hope that I help you out a little. I don't use it as I will explain why.
The 512MB size is the total size of the internal memory. That memory is split up into 3 main partitions. /system, /data and /cache. Other things like boot, recovery and so on goes somewhere else. The rom goes onto the /system partition, the apps go to /data partition and /cache is for temporary storage like when your downloading apps from the market.
Try not to do it with Rom Manager. It is a little buggy and doesn't work well. You can use something like gparted to format and partition your SD card.
As for A2SD. I understand that you install a script for it to work properly. By default, it will move apps to the ext partition on your SD card. Please note if your using widgets and the app is on the SD card, you won't be able to use the widgets.
Here is a A2SD script by DarkTremmor. Read up on it. Hope this helps.
I prob am wrong about this but this is my understanding of A2SD. Please update me guys if I am wrong or you have better info. I still don't understand A2SD properly. I will however try it out and see how it works.

If you use A2SD (the version with the ext) widgets will work. They only won't work when on the fat partition.

hey thanks for the reply. ok so this helps me understand it a bit better thanks googlejelly. But this still doesnt explain why a2sd has a different total size then the stock application manager?
Even if you say that by default App2sd moves it to ext partition and that is the reason for the different sizes it still doesnt match up as i created a partition of 512mb and got 185.69 which is a bit far off the mark.

Most proper way to know your free memory is Console. Connect phone, type adb shell and:
Code:
# mount
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.rovio.angrybirdsseasons-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/system - read only (s-off rules!) file system for your system files
/data and /cache rw partitions for application and data storage
next is SD-Card mount point
/mnt/secure - is hidden folders on SD-Card for storing data for native a2sd Android. You can see last line - it's Angry birds moved to SD mounted as independent partition. Don't move any apps to SD-card if you have custom a2sd+ script configured.
Code:
# df
Filesystem Size Used Free Blksize
/dev 203M 44K 203M 4096
/mnt/asec 203M 0K 203M 4096
/mnt/obb 203M 0K 203M 4096
/system 140M 126M 13M 4096
/data 272M 56M 215M 4096
/cache 25M 10M 14M 4096
/sd-ext 457M 189M 267M 1024
/mnt/sdcard 3G 2G 859M 4096
/mnt/secure/asec 3G 2G 859M 4096
Now sizes (i have custom partitions size, so your sizes will differ)
/data - where you install all apps.
/sd-ext - a2sd+ storage (on SD-Card)
And to check is a2sd word proper:
Code:
# ls -l data/
lrwxrwxrwx root root 2011-02-22 16:54 app-private -> /sd-ext/app-private
lrwxrwxrwx root root 2011-02-22 16:54 app -> /sd-ext/app
lrwxrwxrwx root root 2011-02-22 16:54 dalvik-cache -> /sd-ext/dalvik-cache
-rw-r--r-- root root 8447 2011-02-22 16:55 dta2sd.log
-rw-r--r-- root root 8447 2011-02-22 16:54 dta2sd.lg1
-rw-r--r-- root root 8576 2011-02-22 16:54 dta2sd.lg2
drwx------ system system 2011-02-22 16:55 backup
-rw-rw-rw- root root 376 2011-02-21 17:30 dtinstall.log
drwx------ system system 2011-02-21 17:32 secure
drwxrwxr-x system system 2011-02-23 15:08 system
drwxr-xr-x root root 2008-08-01 15:00 xbin
drwxr-xr-x root root 2011-02-21 17:32 local
drwxr-xr-x root root 2008-08-01 15:00 jit
drwxr-xr-x root root 2011-02-23 14:05 data
drwx------ root root 2011-02-22 16:54 property
-rw-r--r-- root root 1978 2008-08-01 15:00 changelog.txt
drwxrwx--- root root 2011-02-21 17:32 lost+found
drwxrwx--t system misc 2011-02-23 13:14 misc
drwxr-x--- root log 2011-02-21 17:32 dontpanic
you see "->" is symlink to SD-card. So any app you installed in internal memory of your phone actually goes to SD. But, there is on folder - data, which not moved to card with a2sd. Cause some restrictions or smth like this.
in /data/data/ app store their libraries etc. Now check which soft use storage:
Code:
# cd data/data
# du -shd1
3.0M ./com.adobe.reader
80.0K ./com.mhuang.overclocking
54.5K ./kz.mek.DialerOne
4.0K ./jp.r246.twiccaplugins.twitpic
17.5K ./com.anddoes.fancywidget
9.0K ./org.swiftp
.....
2.5K ./com.rerware.android.MyBackupRoot
15.0K ./ccc71.bmw
45.6M .
So total folder use 45.6MB of internal storage. all other is free for use. There another folders in data, but it not so heavy.
Stock Desire, according to alpharev, has - Bravo Sense: /system:180M /cache:40M /data:217M.
Main goal of using custom a2sd+ is that you install all apps in internal memory as your phone thinks. And all widgets work well. With stock a2sd you can't move apps with widgets to sd-card or it stop working.

crap i tried the app2sd script and it messed up my phone, now i cant install any app from the market it just starts and stops straight away. im after doing a factory reset on my phone and even restored backups.
can anyone help?

Why not to take any of existent rom with working a2sd?

thanks for the relpy (both of them) after doing a wipe via android itself, everything is back to normal now. So is it that all i have to do to get app2sd to transfer my apps to my ext3 partition on my sd is run a script (.zip file) in clockworkrecovery?
the one i tried is what messed everything up, i dont know if it was because some of my apps were on my sd (via the standard application manager) or that the script wasnt designed for the desire/the rom im running.
i have partitioned my rom correctly to ext3 so im nearly there :-(

With a2sd all apps should be installed in internal memory.
Check what show ls -l /data/ in terminal. If there is symlink to SD - everything is Ok!

Resize Nook STR Partitions

I wanted to increase the available space for my side loaded content and reduce the space for B&N downloads
First I used noogie to make a backup of the pristine nook at v 1.0.0, next I upgraded it to v1.0.1 and made another image
Then these commands on a linux box
Code:
[FONT="Fixedsys"]
dd if=/dev/zero of=new.img bs=1958739968 count=1
(
cat << _EOF
0,8,c,*
,2,c
,64,L
,,E
,128,L
,668,c
,32,L
,,L
_EOF
) | sfdisk -H128 -S32 -D -f new.img
kpartx -a mynookbackup.img
kpartx -a new.img
mkdir x z
cd x
mkdir boot cache data factory NOOK p5 rom
cd ../z
mkdir boot cache data factory NOOK p5 rom
cd ..
mkdosfs -H128 -t32 -F16 -n boot /dev/mapper/loop1p1
mkdosfs -H128 -t32 -F12 -n rom /dev/mapper/loop1p2
mkdosfs -H128 -t32 -F32 -n NOOK /dev/mapper/loop1p6
mkfs.ext2 -L factory /dev/mapper/loop1p3
mkfs.ext2 /dev/mapper/loop1p5
mkfs.ext3 -L cache /dev/mapper/loop1p7
mkfs.ext3 -L data /dev/mapper/loop1p8
cd x
mount /dev/mapper/loop0p1 boot
mount /dev/mapper/loop0p2 rom
mount /dev/mapper/loop0p3 factory
mount /dev/mapper/loop0p5 p5
mount /dev/mapper/loop0p6 NOOK
mount /dev/mapper/loop0p7 cache
mount /dev/mapper/loop0p8 data
cd ../z
mount /dev/mapper/loop1p1 boot
mount /dev/mapper/loop1p2 rom
mount /dev/mapper/loop1p3 factory
mount /dev/mapper/loop1p5 p5
mount /dev/mapper/loop1p6 NOOK
mount /dev/mapper/loop1p7 cache
mount /dev/mapper/loop1p8 data
cd ..
rsync -avP x/ z/
sync
umount x/*
umount z/*
kpartx -d mynookbackup.img
kpartx -d new.img
[/FONT]
after that I now have 1.4 GB for side loaded content.
Hope this helps someone.

Thanks for sharing. This is something that i have been wanting to do so I would not have to use an sd card.
Now I do have a question on this. the part
Code:
(
cat << _EOF
0,8,c,*
,2,c
,64,L
,,E
,128,L
,668,c
,32,L
,,L
_EOF
) | sfdisk -H128 -S32 -D -f new.img
what does this actually do?

It creates a new partition table on the file new.img using sfdisk I can script it instead of doing it manually
Here is the output of fdisk -l on both files
Code:
Disk mynook101.img: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders, total 3825664 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
mynook101.img1 * 32 155647 77808 c W95 FAT32 (LBA)
mynook101.img2 155648 188415 16384 c W95 FAT32 (LBA)
mynook101.img3 188416 577535 194560 83 Linux
mynook101.img4 577536 3792895 1607680 5 Extended
mynook101.img5 577568 1167359 294896 83 Linux
mynook101.img6 1167392 1658879 245744 c W95 FAT32 (LBA)
mynook101.img7 1658912 2150399 245744 83 Linux
mynook101.img8 2150432 3792895 821232 83 Linux
Disk new.img: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders, total 3825664 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
new.img1 * 32 32767 16368 c W95 FAT32 (LBA)
new.img2 32768 40959 4096 c W95 FAT32 (LBA)
new.img3 40960 303103 131072 83 Linux
new.img4 303104 3825663 1761280 5 Extended
new.img5 303136 827391 262128 83 Linux
new.img6 827424 3563519 1368048 c W95 FAT32 (LBA)
new.img7 3563552 3694591 65520 83 Linux
new.img8 3694624 3825663 65520 83 Linux

and here is the output of df to see where the space has been reallocated
Code:
Filesystem Type Size Used Avail Use% Mounted on
vfat 75M 9.8M 66M 14% /mnt/scratch/tmp/x/boot
vfat 16M 119K 16M 1% /mnt/scratch/tmp/x/rom
ext2 184M 106M 77M 58% /mnt/scratch/tmp/x/factory
ext2 279M 185M 92M 67% /mnt/scratch/tmp/x/p5
vfat 237M 171K 237M 1% /mnt/scratch/tmp/x/NOOK
ext3 233M 6.1M 224M 3% /mnt/scratch/tmp/x/cache
ext3 790M 42M 740M 6% /mnt/scratch/tmp/x/data
vfat 16M 9.8M 6.2M 62% /mnt/scratch/tmp/z/boot
vfat 4.0M 148K 3.9M 4% /mnt/scratch/tmp/z/rom
ext2 124M 106M 13M 90% /mnt/scratch/tmp/z/factory
ext2 248M 185M 51M 79% /mnt/scratch/tmp/z/p5
vfat 1.4G 212K 1.4G 1% /mnt/scratch/tmp/z/NOOK
ext3 62M 5.4M 54M 10% /mnt/scratch/tmp/z/cache
ext3 62M 30M 29M 51% /mnt/scratch/tmp/z/data

Thank you very much, it works very well
Here is what I did with comments of what I understood (might be useful for someone)
Code:
#First, we create a blank image (same size as the nook, mine is 1962934272)
#I used bs=1916928 count=1024 instead of bs=1962934272 count=1, I assume it is the same (or else I didn't have enough memory))
dd if=/dev/zero of=new.img bs=1916928 count=1024
#Then, we create partitions on it with sfdisk (I used a larger data partition to have more space for my apps)
(
cat << _EOF
0,8,c,*
,2,c
,64,L
,,E
,128,L
,620,c
,32,L
,,L
_EOF
) | sfdisk -H128 -S32 -D -f new.img
#We create partition mapping (or something like that) so that we can "access" them in /dev/mapper
kpartx -a mynookbackup.img
kpartx -a new.img
mkdir x z
cd x
mkdir boot cache data factory NOOK p5 rom
cd ../z
mkdir boot cache data factory NOOK p5 rom
cd ..
# We create the filesystems on the partitions (Your mkdosfs commands were invalid for me, so I did something like)
mkdosfs -F16 -n boot /dev/mapper/loop1p1
mkdosfs -F12 -n rom /dev/mapper/loop1p2
mkdosfs -F32 -n NOOK /dev/mapper/loop1p6
mkfs.ext2 -L factory /dev/mapper/loop1p3
mkfs.ext2 /dev/mapper/loop1p5
mkfs.ext3 -L cache /dev/mapper/loop1p7
mkfs.ext3 -L data /dev/mapper/loop1p8
#We mount them
cd x
mount /dev/mapper/loop0p1 boot
mount /dev/mapper/loop0p2 rom
mount /dev/mapper/loop0p3 factory
mount /dev/mapper/loop0p5 p5
mount /dev/mapper/loop0p6 NOOK
mount /dev/mapper/loop0p7 cache
mount /dev/mapper/loop0p8 data
cd ../z
mount /dev/mapper/loop1p1 boot
mount /dev/mapper/loop1p2 rom
mount /dev/mapper/loop1p3 factory
mount /dev/mapper/loop1p5 p5
mount /dev/mapper/loop1p6 NOOK
mount /dev/mapper/loop1p7 cache
mount /dev/mapper/loop1p8 data
cd ..
#We copy the content of the nook's partitions to the new ones
rsync -avP x/ z/
sync
umount x/*
umount z/*
kpartx -d mynookbackup.img
kpartx -d new.img
#Now we just have to "restore" new.img on the nook
For information, my partition table
Code:
Disque new.img*: 1962*Mo, 1962934272*octets
128 têtes, 32 secteurs/piste, 936 cylindres, total 3833856 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique)*: 512*octets / 512*octets
taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
Identifiant de disque*: 0x00000000
Périphérique Amorce Début Fin Blocs Id Système
new.img1 * 32 32767 16368 c W95 FAT32 (LBA)
new.img2 32768 40959 4096 c W95 FAT32 (LBA)
new.img3 40960 303103 131072 83 Linux
new.img4 303104 3833855 1765376 5 Étendue
new.img5 303136 827391 262128 83 Linux
new.img6 827424 3366911 1269744 c W95 FAT32 (LBA)
new.img7 3366944 3497983 65520 83 Linux
new.img8 3498016 3833855 167920 83 Linux
#The original one
Disque /dev/sdb*: 1962*Mo, 1962934272*octets
128 têtes, 32 secteurs/piste, 936 cylindres, total 3833856 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique)*: 512*octets / 512*octets
taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
Identifiant de disque*: 0x00000000
Périphérique Amorce Début Fin Blocs Id Système
/dev/sdb1 * 32 155647 77808 c W95 FAT32 (LBA)
/dev/sdb2 155648 188415 16384 c W95 FAT32 (LBA)
/dev/sdb3 188416 577535 194560 83 Linux
/dev/sdb4 577536 3792895 1607680 5 Étendue
/dev/sdb5 577568 1167359 294896 83 Linux
/dev/sdb6 1167392 1658879 245744 c W95 FAT32 (LBA)
/dev/sdb7 1658912 2150399 245744 83 Linux
/dev/sdb8 2150432 3792895 821232 83 Linux
#df
Sys. de fichiers Taille Util. Disp. Uti% Monté sur
/dev/mapper/loop0p1 75M 58M 17M 78% /home/mdall/x/boot
/dev/mapper/loop0p2 16M 120K 16M 1% /home/mdall/x/rom
/dev/mapper/loop0p3 184M 106M 77M 58% /home/mdall/x/factory
/dev/mapper/loop0p5 279M 194M 83M 71% /home/mdall/x/p5
/dev/mapper/loop0p6 240M 104M 137M 43% /home/mdall/x/NOOK
/dev/mapper/loop0p7 233M 14M 217M 6% /home/mdall/x/cache
/dev/mapper/loop0p8 790M 149M 633M 20% /home/mdall/x/data
/dev/mapper/loop1p1 16M 10M 6,0M 63% /home/mdall/z/boot
/dev/mapper/loop1p2 4,0M 150K 3,9M 4% /home/mdall/z/rom
/dev/mapper/loop1p3 124M 106M 13M 90% /home/mdall/z/factory
/dev/mapper/loop1p5 248M 191M 45M 82% /home/mdall/z/p5
/dev/mapper/loop1p6 1,3G 104M 1,2G 9% /home/mdall/z/NOOK
/dev/mapper/loop1p7 62M 13M 47M 21% /home/mdall/z/cache
/dev/mapper/loop1p8 159M 136M 16M 90% /home/mdall/z/data

For those of us tards who have no clue how to use linux and still wanna increase the size of our Nook Touch, is there a nice gui that will do the same thing?

Another helpful trick to add to this mix:
symlink /data/media to
/media so you can actually see the files BN is downloading to your device.
in adb shell or via ssh:
cd /data/media
rm -r *
cd ..
rmdir media
ln -s media /media
After doing this, the reader, etc. put their files where you can pick them up and archive them in Calibre, etc.

One more nook succesfully resized.
Thanks

is a step by step instruction possible......

Hi, I can see the you do not care about bootloader during the resize. Do you know what bootloader is used in nook? grub? (don't have my nook atm so I cannot check it)

cceerrtt said:
Hi, I can see the you do not care about bootloader during the resize. Do you know what bootloader is used in nook? grub? (don't have my nook atm so I cannot check it)
Click to expand...
Click to collapse
x-loader and u-boot, both located on the fat32 /boot partition.
This is the beauty of the omap3 platform

is it possible to create a script that does this automagically?

user4242 said:
is it possible to create a script that does this automagically?
Click to expand...
Click to collapse
If you have access to a Linux distro you can easily write one yourself based on the info posted in xda - B & N N T.
If you need more info I have a post here, just change the values to what you fell suits you

mdall said:
Thank you very much, it works very well
Here is what I did with comments of what I understood (might be useful for someone)
Code:
#First, we create a blank image (same size as the nook, mine is 1962934272)
#I used bs=1916928 count=1024 instead of bs=1962934272 count=1, I assume it is the same (or else I didn't have enough memory))
dd if=/dev/zero of=new.img bs=1916928 count=1024
#Then, we create partitions on it with sfdisk (I used a larger data partition to have more space for my apps)
(
cat << _EOF
0,8,c,*
,2,c
,64,L
,,E
,128,L
,620,c
,32,L
,,L
_EOF
) | sfdisk -H128 -S32 -D -f new.img
#We create partition mapping (or something like that) so that we can "access" them in /dev/mapper
kpartx -a mynookbackup.img
kpartx -a new.img
mkdir x z
cd x
mkdir boot cache data factory NOOK p5 rom
cd ../z
mkdir boot cache data factory NOOK p5 rom
cd ..
# We create the filesystems on the partitions (Your mkdosfs commands were invalid for me, so I did something like)
mkdosfs -F16 -n boot /dev/mapper/loop1p1
mkdosfs -F12 -n rom /dev/mapper/loop1p2
mkdosfs -F32 -n NOOK /dev/mapper/loop1p6
mkfs.ext2 -L factory /dev/mapper/loop1p3
mkfs.ext2 /dev/mapper/loop1p5
mkfs.ext3 -L cache /dev/mapper/loop1p7
mkfs.ext3 -L data /dev/mapper/loop1p8
#We mount them
cd x
mount /dev/mapper/loop0p1 boot
mount /dev/mapper/loop0p2 rom
mount /dev/mapper/loop0p3 factory
mount /dev/mapper/loop0p5 p5
mount /dev/mapper/loop0p6 NOOK
mount /dev/mapper/loop0p7 cache
mount /dev/mapper/loop0p8 data
cd ../z
mount /dev/mapper/loop1p1 boot
mount /dev/mapper/loop1p2 rom
mount /dev/mapper/loop1p3 factory
mount /dev/mapper/loop1p5 p5
mount /dev/mapper/loop1p6 NOOK
mount /dev/mapper/loop1p7 cache
mount /dev/mapper/loop1p8 data
cd ..
#We copy the content of the nook's partitions to the new ones
rsync -avP x/ z/
sync
umount x/*
umount z/*
kpartx -d mynookbackup.img
kpartx -d new.img
#Now we just have to "restore" new.img on the nook
For information, my partition table
Code:
Disque new.img*: 1962*Mo, 1962934272*octets
128 têtes, 32 secteurs/piste, 936 cylindres, total 3833856 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique)*: 512*octets / 512*octets
taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
Identifiant de disque*: 0x00000000
Périphérique Amorce Début Fin Blocs Id Système
new.img1 * 32 32767 16368 c W95 FAT32 (LBA)
new.img2 32768 40959 4096 c W95 FAT32 (LBA)
new.img3 40960 303103 131072 83 Linux
new.img4 303104 3833855 1765376 5 Étendue
new.img5 303136 827391 262128 83 Linux
new.img6 827424 3366911 1269744 c W95 FAT32 (LBA)
new.img7 3366944 3497983 65520 83 Linux
new.img8 3498016 3833855 167920 83 Linux
#The original one
Disque /dev/sdb*: 1962*Mo, 1962934272*octets
128 têtes, 32 secteurs/piste, 936 cylindres, total 3833856 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique)*: 512*octets / 512*octets
taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
Identifiant de disque*: 0x00000000
Périphérique Amorce Début Fin Blocs Id Système
/dev/sdb1 * 32 155647 77808 c W95 FAT32 (LBA)
/dev/sdb2 155648 188415 16384 c W95 FAT32 (LBA)
/dev/sdb3 188416 577535 194560 83 Linux
/dev/sdb4 577536 3792895 1607680 5 Étendue
/dev/sdb5 577568 1167359 294896 83 Linux
/dev/sdb6 1167392 1658879 245744 c W95 FAT32 (LBA)
/dev/sdb7 1658912 2150399 245744 83 Linux
/dev/sdb8 2150432 3792895 821232 83 Linux
#df
Sys. de fichiers Taille Util. Disp. Uti% Monté sur
/dev/mapper/loop0p1 75M 58M 17M 78% /home/mdall/x/boot
/dev/mapper/loop0p2 16M 120K 16M 1% /home/mdall/x/rom
/dev/mapper/loop0p3 184M 106M 77M 58% /home/mdall/x/factory
/dev/mapper/loop0p5 279M 194M 83M 71% /home/mdall/x/p5
/dev/mapper/loop0p6 240M 104M 137M 43% /home/mdall/x/NOOK
/dev/mapper/loop0p7 233M 14M 217M 6% /home/mdall/x/cache
/dev/mapper/loop0p8 790M 149M 633M 20% /home/mdall/x/data
/dev/mapper/loop1p1 16M 10M 6,0M 63% /home/mdall/z/boot
/dev/mapper/loop1p2 4,0M 150K 3,9M 4% /home/mdall/z/rom
/dev/mapper/loop1p3 124M 106M 13M 90% /home/mdall/z/factory
/dev/mapper/loop1p5 248M 191M 45M 82% /home/mdall/z/p5
/dev/mapper/loop1p6 1,3G 104M 1,2G 9% /home/mdall/z/NOOK
/dev/mapper/loop1p7 62M 13M 47M 21% /home/mdall/z/cache
/dev/mapper/loop1p8 159M 136M 16M 90% /home/mdall/z/data
Click to expand...
Click to collapse
copy-pasting this into the command line makes the process painless. It's ok as long as you take the time to read what's going on here, and mdall did a good job of explaining. I think 160MB for the data partition is a little big...but better safe then sorry: these are good numbers.

If you really wanted to do this, you might try asking around IRC in NookColor for a copy of the Partition Resize uRamdisk, with sufficient knowledge of uRamdisks/sh scripts, etc you could easily retool it to move around partition space on the N2E. Considering it was designed by BN's Devs for the sole purpose of changing Userspace into /data it shouldn't be hard to make it do the reverse. But something like this could be highly dangerous if it's not done right and there's always the risk of bricking your device if you mess up the script. Just some words of advice.

mkdosfs -H128 -t32 -F16 ....
Click to expand...
Click to collapse
I'm using the latest Knoppix (CD version) to do this, and my mkdosfs command didn't like the -H and -t options.
Are they heads and tracks, and are they important?
Other than that, I modified this line:
dd if=/dev/zero of=new.img bs=1958739968 count=1
Click to expand...
Click to collapse
dd if=/dev/zero of=new.img bs=244842496 count=8
because it complained about exhausted memory.
Did someone mention in this thread about how to write back to the NST?
dd if=new.img of=/dev/sdX
Well, I've updated mine to 1.1 and then did the partition resize, and everything seems to have gone smoothly.
Now, I've now moved on to nooting with TouchNooter v1.11.20, and that itself is a whole new kettle of fish, and for another thread.
ED: Oops... after installing some apps, it's complaining about low memory....
mdall said:
Thank you very much, it works very well
Here is what I did with comments of what I understood (might be useful for someone)
Code:
#Then, we create partitions on it with sfdisk (I used a larger data partition to have more space for my apps)
Click to expand...
Click to collapse
D'OH!!! *sigh* I'm redoing partition resizing by following mdall's script. Thanks mdall.

Hard work for me, but now it's all fine!! Good job!
My experience with Ubuntu 11.10:
Install kpartx: sudo apt-get install kpartx
Became root;
When make mkdosfs partitions, i haven't used flags "-H128 -t32" (thanks Mdall!).
Ex: mkdosfs -F16 -n boot /dev/mapper/loop1p1 instread of mkdosfs H 128 -f32 -F16 -n boot /dev/mapper/loop1p1 ...
when make all partiton with "mkdosfs" i've received this message:
"mkdosfs 3.0.9 (31 Jan 2010)
unable to get drive geometry, using default 255/63 " DON'T WORRY!
I have used a backup of fresh installation of salsichaNooter04, and the "data" folder of my backup image was "userdata", so i'have changed all "data" with "userdata".
Nice work, thanks a lot, sorry for english LoL

Here is another way to resize the partitions (maybe easier)
And I guess that we could also create something like that but for the Nook Touch (now that we have CWM)

A little question:
Can i rename my big new NOOK partition as "sdcard" ?
I use Dropbox and i would utilize my new partition instead of sd card.
It's possible?

I want to simply explain why resizing those partitions is... not clever....
You have those partitions on Your NOOK:
/rom (15.7MB)- self explanatory
/system (278MB)- as above
/data (790MB)- THIS is default internal storage in Android
/cache (232MB)- used for caching compiled java programs (in short way)
/media (240MB)- THIS is completely unnecessary partition
EXPLANATION:
What you really need is only internal storage, rom, system and cache. This is how it is done on most Android phones. B&N wants to block access to /data partition so they created special /media partition which is accessible from PC and you can put your files in there. That was easier for them. So /media partition is some kind of already inserted SD card.
If you have real SD card, probably much bigger, you really don't need another, very small partition to simulate SD card.
If you are not rooting it may sound good to have bigger /media partition and smaller /data partition. Maybe. This will cause many troubles but You can try.
IF you are rooting then making /data partition smaller is the most stupid thing I can imagine. In fact what you really want to do is to make /media partition smaller and make /data partition bigger! Or even better! Delete /media partition, make /data partition bigger and then just creater folder /media for compatibility. I didn't try, but this sounds good!
WHY not to scale /data down? Because /data partition is the place for everything in Android. And specially it is the place for APKs! Also this is the place for everything written by APKs. So when You will have smaller /data you may not install as many APKs as You want. This is not problem in Android 2.2 because You can install APKs on sdcard, but what we have here is Android 2.1.

[Q] Opps I formated my internal storage to ntfs

I formatted my internal storage drive on my htc droid incredible to ntfs (comes with 8gb internal flash and 2gb external microsd)
I did this with windows However when you un-mount you will not be able to get back into it in windows or your android os afterwards leaving you with minimal storage space left on your internal flash. Now I only have roughly 600mb internal and somewhere a huge partition formatted to ntfs that cannot be assessed by windows or android. DOH! I've spend a few hours trying to find answers so I'm posting for help!
Also I am running Jellybean 4.1.1 RC2 (rooted)
I tried to mount and format with CWM and did not work (no app2sd partition)
There has got to be a way to use adb to reformat the ntfs space back to fat32 It seems way to easy to mess a phone up just by formating a storage space with windows.. Really need help here !

Go to CWM, mounts and storage and select format emmc. Do you get any errors there? It should make it fat32 again or at least fat which should be picked up by windows.

tiny4579 said:
Go to CWM, mounts and storage and select format emmc. Do you get any errors there? It should make it fat32 again or at least fat which should be picked up by windows.
Click to expand...
Click to collapse
CWM version is 5.0.2.0
Messages:
Formatting /emmc...
Error mounting /emmc!
Thanks for a reply btw!

blown4x4 said:
CWM version is 5.0.2.0
Messages:
Formatting /emmc...
Error mounting /emmc!
Thanks for a reply btw!
Click to expand...
Click to collapse
You're welcome. Have you tried formatting internal storage in the ROM itself?
If that doesn't work can you run from adb shell in the ROM or recovery? Try ROM as I think it will more likely work.
Code:
umount /storage/sdcard1
mkfs.vfat /dev/block/vold/179:3
If umount fails with not mounted that's good. Any other error let me know. The mkfs.vfat command should hopefully succeed. I don't want to try as I don't want to wipe emmc but that's the internal device name of the internal storage.

tiny4579 said:
You're welcome. Have you tried formatting internal storage in the ROM itself?
If that doesn't work can you run from adb shell in the ROM or recovery? Try ROM as I think it will more likely work.
Code:
umount /storage/sdcard1
mkfs.vfat /dev/block/vold/179:3
If umount fails with not mounted that's good. Any other error let me know. The mkfs.vfat command should hopefully succeed. I don't want to try as I don't want to wipe emmc but that's the internal device name of the internal storage.
Click to expand...
Click to collapse
on the umount /storage/sdcard1 command in adb shell i get an error stating that there was an invalid argument

blown4x4 said:
on the umount /storage/sdcard1 command in adb shell i get an error stating that there was an invalid argument
Click to expand...
Click to collapse
emmc shouldn't be mounted then. If you've confirmed that emmc (internal storage - 8gb) is ntfs then run the second command.

tiny4579 said:
You're welcome. Have you tried formatting internal storage in the ROM itself?
If that doesn't work can you run from adb shell in the ROM or recovery? Try ROM as I think it will more likely work.
Code:
umount /storage/sdcard1
mkfs.vfat /dev/block/vold/179:3
If umount fails with not mounted that's good. Any other error let me know. The mkfs.vfat command should hopefully succeed. I don't want to try as I don't want to wipe emmc but that's the internal device name of the internal storage.
Click to expand...
Click to collapse
Shouldnt it be:
Code:
umount /mnt/emmc
mkfs.vfat /dev/block/vold/179:3
Then to remount:
Code:
mount -t vfat /dev/block/vold/179:3 /mnt/emmc
umoumt /storage/sdcard1 just says failed if i try to run it.

blown4x4 said:
on the umount /storage/sdcard1 command in adb shell i get an error stating that there was an invalid argument
Click to expand...
Click to collapse
Tiny, I also tried the second part of the commands and got this " mkfs.vfat lseek: value too large for defined data type "

Actually, cmlusco my umount /storage/sdcard1 worked fine as root for me. But umount /mnt/emmc should work across all ROMs.

blown4x4 said:
Tiny, I also tried the second part of the commands and got this " mkfs.vfat lseek: value too large for defined data type "
Click to expand...
Click to collapse
Couldent you just try an ruu
Sent from my Droid Incredible using xda app-developers app

Thanks for the reply guys!
I get an invalid argument when trying to unmount emmc

blown4x4 said:
Tiny, I also tried the second part of the commands and got this " mkfs.vfat lseek: value too large for defined data type "
Click to expand...
Click to collapse
Does this work:
Code:
su
mkfs.vfat /dev/block/mmcblk0p3
If not check post #17 in this thread, replacing mmcblk0p14 with mmcblk0p3:
http://forum.xda-developers.com/showthread.php?t=1647806&page=2
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
zachf714 said:
Couldent you just try an ruu
Sent from my Droid Incredible using xda app-developers app
Click to expand...
Click to collapse
It's a bit extreme for an improperly formatted partition.

I got the same result
" value too large for defined data type" Bolth methods
Again thank you for all your help guys!

This might be helpful?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>cd miniadb_inc
The system cannot find the path specified.
C:\Users\User>cd C:
C:\Users\User
C:\Users\User>cd C:/
C:\>cd miniadb_inc
C:\miniadb_inc>umount /mnt/emmc
'umount' is not recognized as an internal or external command,
operable program or batch file.
C:\miniadb_inc>adb shell
[email protected]:/ # umount /mnt/emmc
umount /mnt/emmc
umount: can't umount /mnt/emmc: Invalid argument
1|[email protected]:/ # mount -t vfat /dev/block/vold/179:3 /mnt/emmc
mount -t vfat /dev/block/vold/179:3 /mnt/emmc
mount: mounting /dev/block/vold/179:3 on /mnt/emmc failed: Invalid argument
255|[email protected]:/ # su
su
[email protected]:/ # mkfs.vfat /dev/block/mmcblk0p3
mkfs.vfat /dev/block/mmcblk0p3
mkfs.vfat: lseek: Value too large for defined data type
1|[email protected]:/ # #cat /proc/partitions
#cat /proc/partitions
1|[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 640 mtdblock0
31 1 4608 mtdblock1
31 2 3072 mtdblock2
31 3 253952 mtdblock3
31 4 640 mtdblock4
31 5 40960 mtdblock5
31 6 152576 mtdblock6
179 0 7757824 mmcblk0
179 1 778240 mmcblk0p1
179 2 204800 mmcblk0p2
179 3 6774776 mmcblk0p3
179 8 1931264 mmcblk1
179 9 1930240 mmcblk1p1
[email protected]:/ #

Try this:
/system/bin/busybox mkfs.vfat /dev/block/vold/179:3
Or
/system/xbin/busybox mkfs.vfat /dev/block/vold/179:3
Depending on where busybox is installed.

Thank you for the suggestion cmlusco! However I still get value too large for defined data type

Ok try
mkfs.vfat -F 32 /dev/block/vold/179:3
Or try formating it to something else first like ext2:
mkfs.ext2 /dev/block/vold/179:3

Try the post I linked, check post 17. Itt has a different busybox and you can push it to /data/local/tmp and run busybox according to the instructions there just replace /dev/block/mmcblk0p14 with /dev/block/mmcblk0p3. It may not work with your busybox version in the the ROM.

tiny4579 said:
Try the post I linked, check post 17. Itt has a different busybox and you can push it to /data/local/tmp and run busybox according to the instructions there just replace /dev/block/mmcblk0p14 with /dev/block/mmcblk0p3. It may not work with your busybox version in the the ROM.
Click to expand...
Click to collapse
Was just reading on google about newer busyboxes having lseek issues, so that will probably solve your issue. However i cant download the linked busybox.zip file from that thread. From the xda app it says failed to connect, and from the website it just sits there trying to load forever. Any idea what version of busybox will work, cant find that info anywhere.

cmlusco said:
Was just reading on google about newer busyboxes having lseek issues, so that will probably solve your issue. However i cant download the linked busybox.zip file from that thread. From the xda app it says failed to connect, and from the website it just sits there trying to load forever. Any idea what version of busybox will work, cant find that info anywhere.
Click to expand...
Click to collapse
I don't know the answer to that one. OP, try busybox 1.18.2 or 1.18.4. You can use stericson's busybox app to easily install an older busybox version but the free version is annoying with extra boxes that pop up. However once you install one that works you can uninstall the app. If you install busybox from there (wait for smart install to be ready but you can do normal), then you need to try the commands from the phone.

Who would like a 1GB System Partition???

THIS IS FOR DEVELOPMENT ONLY!!!! THIS IS ONLY A CONCEPt FORGETTING THE 1GB SYSTEM PARTITION.
30-Jan-13 update
Ok so using this method I now have a ported rom from the Samsung Galaxy S3 that has a 680+mb system booting on my G2. If any of you feel like helping me get it up and running PM me or you can download it from here http://sourceforge.net/projects/sgs3forg2/files/FJB4G2-orig-runtime.zip/download and see for yourself...
MAJOR EDIT: SO THE UPLOAD MUST HAVE BEEN CORRUPTED FOR THE EM1.zip. IT IS NON FUNCTIONAL. ALL CREDIT TO THE ONE I WILL PUT UP GOES TO FLINNY. I IN NO WAY DID ANYTHING TO CREATE THIS ROM JUST ALTERED THE MOUNTS TO GET THE 1GB SYSTEM PARTITION. THE FILE IS NAMED f10.zip. it is his 10.1 base.
Ok so I know its been a while but I have something I can not keep away from the community. Anyone want to get a 1GB System and 549MB Data partition??? Yes thats right we can swap the partitions. here is a link to some screen shots and another to, with the permission of nik3r, the modified Elitemod Rom. just go into recovery, format all partitions(sorry you will have to start over in order to swap the partitions, well for now that is), and flash the EM1.zip
http://www.mediafire.com/?ka8yq4hzs6upj
Ok so this all started after my wife got her new phone the samsung galaxy s3. in love with the phone and what it could do but unable to, due to financial constraints and TMobiles unwillingness to give me one for free like they did my wife, I set forth trying to find a way to port its OS to our G2. finally i have found a way, or at least now the space in which to put it. now will begin the porting phase. hence this thread, I bring you this solution to our space issue cause really is 1.3GB for G2 or 1GB for DZ partition for data really needed???
So here is what I did...
1. First I got android sdk all setup
2. Then I downloaded the android kitchen
3. Also downloaded the Elitemod Rom from nik3r's thread and set it up in the android kitchen
4. In the android kitchen I extracted the kernel and ramdisk from the boot.img
5. I editted all the init files in the BOOT-EXTRACTED/boot.img-ramdisk directory and changed the mount section of the init.rc to
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 /dev/block/mmcblk0p26 /system
mount yaffs2 /dev/block/mmcblk0p26 /system ro remount
mount yaffs2 /dev/block/mmcblk0p25 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
and the init.vision.rc mounts i also swapped
on early-fs
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
mount ext4 /dev/block/mmcblk0p26 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p25 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p27 /cache wait noatime nosuid nodev barrier=1
mount ext4 /dev/block/mmcblk0p28 /devlog wait noatime nosuid nodev barrier=1
6. now in order for it to boot right i had to get the files to go to the right place so i editted the updater-script and changed the mount for system to /dev/block/mmcblk0p26 (which as you know is the normal data partition) and the data mount to /dev/block/mmcblk0p25( normally system) now the files are going to places we want and the init files on boot remount the system on 0p26 and data on 0p25 (in reverse from normal) but it boots. so here we go lets get the life put back in this phone now we have the space.
Mad props to nik3r for his rom and permission to use it
UPDATE: For some reason the wifi got broken but to fix there is the MOD_Elitekernel zip found in the link at the top of this post that will fix that. I also put EdKeys wifi calling as well, have it running now on my phone so let me know if you find anything else.
UPDATE 2: I have put a hacked version of S Voice from the galaxy S3 in the link for the G2 *TO BE USED WITH THIS PROJECT ONLY*.
UPDATE 3: there must be some confusion with this. This is not a new rom with some timeframe to get it working. I have a fully opperational rom with no problems with apps or anything right now. This is about a mod that can be adapted to any rom or as brought up gapps which will be uploaded here tomorrow. My point is that any rom should be able to be altered this way.

So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?

WOW, Congrats man! Looking forward to this! As if the G2 will ever die! Pffft! And Kudos To nik3r for all his work towards this community!
BUT COME BACKKKKKK nik3r, we miss you!!

HTCDreamOn said:
So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?
Click to expand...
Click to collapse
working on one of those... not sure what it would take for multiboot... could look into it once my main task is done -> SGS3 to G2

So, this would allow me to install more apps and less moving apps to sd card? Noob question, but I really do not know the answer.
Sent from my HTC Vision using xda app-developers app

Less apps, lager rom, kinda like custom mtd partions for older devices. Probably would need to have an ext partition to hold apps if you need a lot... gotta say I've been waiting for something like this!
Sent from my HTC Vision using xda premium

So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?

Yes, the updater script just writes system to the data partition and since the init files are in the boot.img.they mount the "data" partition as /system and "system" partition as /data. Minor alterations to any rom would take advantage of this work around. And yes you can swap back and forth between a bacckup and this or any other altered rom but just remember in recovery(for now) formating system clears data and factory reset (clearing data) deletes the rom.
ineedone said:
So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?
Click to expand...
Click to collapse

Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?

It does take a min to boot... remember there's no cache. What does logcat say????
ineedone said:
Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?
Click to expand...
Click to collapse

I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549

ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app

EnZl said:
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
as i stated in the OP... yes i did change the mounting in the init.rc and init.vision.rc in the ramdisk. once the updater script sends the info tho the partitions i needed to edit those to make it boot with it making /dev/block/mmcblk0p26(originally data) the system mount. same for data mount is now the 0p25 partition

ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out

ineedone said:
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out
Click to expand...
Click to collapse
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what.
let me know
ok so an update I have gotten Flinny's latest 10.1 to work also but I will not put it out until/ if I get his permission to do so

[/SIZE]
OdiemanSAM said:
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what
Click to expand...
Click to collapse
Here is the output:
Partitions seem to change and i lose 500MB some how
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
1099608 18840 1080768 2% /system
/dev/block/mmcblk0p26
1099608 18840 1080768 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16812160 13289984 56% /sdcard
/dev/block/mmcblk0p26
562384 10216 552168 2% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
562384 10216 552168 2% /system
/dev/block/mmcblk0p26
562384 10216 552168 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16815296 13286848 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
also from previous recovery.log:
About to install:
EM1-1.zip
Continue install?
-- Installing: /sdcard/Download/EM1-1.zip
Finding update package...
I:Update location: /sdcard/Download/EM1-1.zip
Opening update package...
Installing update...
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Creating filesystem with parameters:
Size: 1143992320
Block size: 4096
Blocks per group: 32768
Inodes per group: 7760
Inode size: 256
Journal blocks: 4363
Label:
Blocks: 279295
Block groups: 9
Reserved block group size: 71
Created filesystem with 11/69840 inodes and 9114/279295 blocks
warning: wipe_block_device: Discard failed
Initiating EliteMod ICS 120728
================================
Designed for HTC Desire Z/G2
Applying AOKP m6 and gapps...
minzip: Extracted file "/...........................................
.....................................................snip
minzip: Extracted file "/system/xbin/su"
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
package_extract_file: no system/bin/modelid_cfg.sh in package
set_perm: chown of /tmp/modelid_cfg.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/modelid_cfg.sh to 777 failed: No such file or directory
about to run program [/tmp/modelid_cfg.sh] with 2 args
run_program: execv failed: No such file or directory..............................................
.......................
minzip: Extracted file "/data/local/postsetup/undervolt.txt"
Applying EliteKernel 120728...
set_perm: chown of /system/etc/init.d/04mountsddl to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/04mountsddl to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/11apps2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/11apps2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/61swap2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/61swap2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/64swapmarker to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/64swapmarker to 775 failed: No such file or directory
set_perm: chown of /system/xbin/virtuous_oc to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/virtuous_oc to 775 failed: No such file or directory
about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/tmp/dump_image"
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/mkbootimg.sh"
Extracting Kernel files...
minzip: Extracted file "/tmp/unpackbootimg"
minzip: Extracted file "/tmp/zImage"
Installing kernel...
about to run program [/tmp/dump_image] with 3 args
about to run program [/tmp/unpackbootimg] with 3 args
BOARD_KERNEL_CMDLINE no_console_suspend=1
BOARD_KERNEL_BASE 4000000
about to run program [/tmp/mkbootimg.sh] with 1 args
minzip: Extracted file "/tmp/vision_wipe_efs"
about to run program [/tmp/vision_wipe_efs] with 1 args
Backing up partition /dev/block/mmcblk0p13 to /sdcard/part13backup-1358877146.bin ...
Backing up partition /dev/block/mmcblk0p14 to /sdcard/part14backup-1358877146.bin ...
Wiping partition /dev/block/mmcblk0p13...
Wiping partition /dev/block/mmcblk0p14...
Successfully wiped partitions 13 and 14.script result was []
EliteMod ICS installed successfully!
Credits to all the amazing devs that made this possible! Thank You!
Install from sdcard complete.
..................................................................
it also seems like only some files get written to data partition around 200mb, nothing to system...

you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.

OdiemanSAM said:
you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.[/QUOTE
mounted them last time because they didn't show up in fist instance :silly:
output:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # dfFilesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
Click to expand...
Click to collapse

so is it working for you now???
UPDATED OP

Sorry , still on htc bootlogo
Only files seems to be written to data
Is there a way to view if/what data is written to the different partitions or boot ? Or do i need to install aditional gapps?

[Guide] Find7 9GB App storage and mount External SD-Card as SD0

In this Guide you will learn how to modify your system to handle the 9GB Partition 29 as Data (App-Storage) and use the external SD-Card as internal.
Don't be afraid, this is a lot of text mostly to explain the whole procedure, the steps are straight forward.
Thanks go to Kishd (oppoforums), Coldbird and alienmind (xdadevelopers)
Beside of the public made solutions i will do the following:
Instead of repartitioning the device i will change only the partition name of "sdcard" to "userdata", mount the external SD as internal and use the remaining 3GB Partition as external SD.
So partition 15 will become "sdcard1" and partition 29 will become "userdata"
On the Find7a you will have 9 gigs of application space and xx gigs for the internal sd (size of the sdcard).
This should work on Find7 too, someone has to check the partition layout if it is equal, than you will have 25 gigs of application space and xx gigs for the internal sd (size of the sdcard).
PRECAUTIONS:
If you mess around with partition table you could brick your device, so be careful!
Thes procedure worked for me, i am not responseable for any missing or mistyped commands/procedures, so THINK BEFORE YOU DO ANYTHING!
I am not an android Pro, nor an Develper. My Spare time is very limited so i can't help you out if something goes wrong!
I've done this with Gummy Rom, not tryed with ColorOS or another custom rom but it should work on all AOSP-based ROMS.
The swapped SD-cards do not belong to recovery, so the internal SD is accessed as before.
What do you need:
1.: Time: This is not done in 5 minutes, so please be patient.
2.: A Linux-PC with working ADB and Fastboot
3.: TWRP recovery image on your PC or installed on the device: http://techerrata.com/browse/twrp2/find7a (I used 2.7.1.0)
4.: An SD card with at least 16Gb inseted into your Find7a
5.: Fully charge your Device before messing around, some jobs will need a lot of time.
6.: A fitting custom ROM installed, i've done this with Gummy-M2.3-06-29-14-NIGHTLY-find7 which is suitable for find7 and find7a which can be found here: http://crackflasher.com/gummy-m2-3-06-29-14-nightly-find7-zip-oppo-find-7a-gummy/
7.: The zip-file of the custom rom on your local PC
What are we going to do:
0.: Boot into recovery and access the Device via ADB
1.: Format external SD to Ext4 Filesystem
2.: Backup the original partition layout and all partitions too
3.: Copy Data from internal SD to external
4.: Rename two partitions
5.: Format the new "userdata" partition and move all content of the old to the new location
6.: Format the new "sdcard1" partition
7.: Edit/replace fstab files in /etc to tell TWRP and System the new mountpoints
OK, let's do the trick
Step0.: Booting into recovery and accessing the Device via ADB-shell:
Put the phone into fast boot mode. (Power Volume Up simultaneously)
Open a terminal in your linux-PC and do the following as root (sudo -r):
#: fastboot devices ( check that fastboot is up and running)
#: fastboot boot openrecovery-twrp-2.7.1.0-find7a.img (or boot into TWRP if already installed)
The phone will boot into twrp.
Connect the phone and go into adb
#: adb shell
After entering the adb shell you should see the following in your terminal:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ #
Step1.: Format external SD to Ext4 Filesystem
First we have to write a new partition table as i dont know how your SD-card looks:
umount /external_sd (could cause errors if no filesystem is present on SD - dont mind)
parted /dev/block/mmcblk1 (you should see parted welcome message, no errors!)
mklabel msdos (this will write a new partition table on your sdcard)
mkpart primary ext4 1 -1 (this will make a ext4 partition which uses the whole sd)
quit
Now we are going to format the ext4 partition:
mke2fs -t ext4 -m 0 -L sdcard /dev/block/mmcblk1p1
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk1p1
mount /dev/block/mmcblk1p1 /external_sd (Mount the new formatted sd-card -- this should show no errors)
If all is done without errors, proceed to step2
Step2.: Backup the original partition layout and all partitions too
dd makes physical imagea of partitions so you can put it back if needed
While DD is copying you will see no progress bar or any output, so BE PATIENT!
Code:
mkdir /external_sd/backup
parted /dev/block/mmcblk0 print > /external_sd/backup/partitions (original partition Layout for later reference)
dd if=/dev/block/mmcblk0p1 of=/external_sd/backup/modem
dd if=/dev/block/mmcblk0p2 of=/external_sd/backup/sbl1
dd if=/dev/block/mmcblk0p3 of=/external_sd/backup/dbi
dd if=/dev/block/mmcblk0p4 of=/external_sd/backup/ddr
dd if=/dev/block/mmcblk0p5 of=/external_sd/backup/aboot
dd if=/dev/block/mmcblk0p6 of=/external_sd/backup/rpm
dd if=/dev/block/mmcblk0p7 of=/external_sd/backup/boot
dd if=/dev/block/mmcblk0p8 of=/external_sd/backup/tz
dd if=/dev/block/mmcblk0p9 of=/external_sd/backup/pad
dd if=/dev/block/mmcblk0p10 of=/external_sd/backup/modemst1
dd if=/dev/block/mmcblk0p11 of=/external_sd/backup/modemst2
dd if=/dev/block/mmcblk0p12 of=/external_sd/backup/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/external_sd/backup/oppostanvbk
dd if=/dev/block/mmcblk0p14 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/system.gz
dd if=/dev/block/mmcblk0p16 of=/external_sd/backup/persist
dd if=/dev/block/mmcblk0p17 of=/external_sd/backup/cache
dd if=/dev/block/mmcblk0p18 of=/external_sd/backup/recovery
dd if=/dev/block/mmcblk0p19 of=/external_sd/backup/fsg
dd if=/dev/block/mmcblk0p20 of=/external_sd/backup/fsc
dd if=/dev/block/mmcblk0p21 of=/external_sd/backup/ssd
dd if=/dev/block/mmcblk0p22 of=/external_sd/backup/misc
dd if=/dev/block/mmcblk0p23 of=/external_sd/backup/LOGO
dd if=/dev/block/mmcblk0p24 of=/external_sd/backup/DRIVER
dd if=/dev/block/mmcblk0p25 of=/external_sd/backup/reserve1
dd if=/dev/block/mmcblk0p26 of=/external_sd/backup/reserve2
dd if=/dev/block/mmcblk0p27 of=/external_sd/backup/reserve3
dd if=/dev/block/mmcblk0p28 of=/external_sd/backup/reserve4
dd if=/dev/block/mmcblk0p30 of=/external_sd/backup/grow
It is not urgently needed to make dd backups of userdata and (internal) sdcard but here for refernce:
Do a compressed multispan backup with dd so you can use the files on an FAT32 filesystem too:
dd if=/dev/block/mmcblk0p15 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/userdata.gz.
dd if=/dev/block/mmcblk0p29 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/sdcard.gz.
Example of restoring partition 29:
cat /external_sd/backup/userdata.gz.* | gzip -dc | dd of=/dev/block/mmcblk0p29
Step3.: Copy Data from internal SD to external SD:
cp -a -i /internal_sd/* /external_sd/ (this can take a while)
ls /external_sd/ (you should see a bunch of files here)
If nothing went wrong go to step4
Step4.: Rename partitions:
umount /internal_sd/
umount /and-sec/
umount /data/
parted /dev/block/mmcblk0
name 15 sdcard
name 29 userdata
print (should show you the renamed layout)
quit
If nothing went wrong go to step5
Step5.: Format the new "userdata" partition and move all content of the old to the new location:
mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p29
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p29
mount /dev/block/mmcblk0p15 /internal_sd
mount /dev/block/mmcblk0p29 /data
cp -a -i /internal_sd/* /data/ (this can take a while)
If nothing went wrong go to step6
Step6.: Format the new "sdcard1" partition:
umount /internal_sd/
mke2fs -t ext4 -m 0 -L sdcard1 /dev/block/mmcblk0p15
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p15
If nothing went wrong go to step7
Step7.: Edit/replace fstab.qcom file to tell System the new mountpoints:
Guide from Coldbird: http://www.oppoforums.com/threads/unpack-repack-find-7-a-boot-img.14538/
Unpack update.zip and make a working directory.
copy file boot.img from update.zip into this directory
download https://github.com/xiaolu/mkbootimg_tools
unpack bootimage:
mkboot boot.img extracted (this will create a folder "extracted" with the content of boot.img where you can find fstab.qcom
edit fstab.qcom co match your needs (i.e. swap internal and external storage as shown below)
pack bootimage:
mkboot extracted newboot.img (creates newboot.img)
test bootimage (via fastboot):
sudo fastboot boot newboot.img
flash bootimage (via fastboot):
sudo fastboot flash boot newboot.img
sudo fatboot reboot
This is how the original file looks:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337 wait
/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:29,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/xhci-hcd auto auto defaults voldmanaged=usbdisk:auto
Code:
This is the changed file:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
# Use internal sdcard as /data
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
#/dev/block/platform/msm_sdcc.1/by-name/sdcard /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
# CM11 hack: Swap sdcard1 and sdcard0 - both in ext4 and (internal)sdcard1 as emulated
#/devices/msm_sdcc.2/mmc_host auto vfat defaults voldmanaged=sdcard0:auto,noemulatedsd
#/dev/block/platform/msm_sdcc.1/by-name/userdata /storage/sdcard1 ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 defaults
#/dev/block/platform/msm_sdcc.1/by-name/sdcard auto ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 voldmanaged=sdcard1:29,nonremovable,noemulatedsd
# Original Entry of Gummy rom:
#/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:29,nonremovable,noemulatedsd
#/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:auto,noemulatedsd
# Working with switched sd-cards, Aut0mat3d:
/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:15,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:auto,nonremovable,noemulatedsd
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto

Reserved

Reserved1

This should work for most people until we fully unify the storage.
Good job there.

MrColdbird said:
This should work for most people until we fully unify the storage.
Good job there.
Click to expand...
Click to collapse
Thanks. without your Help with storage mounting i'd dropped the project

I really want to try it out but I fear that I screwed something up... I use the unofficial AOSB port. Could somebody check, if my modifications to the fstab.qcom file are correct?
Original file:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/devices/msm_sdcc.1/mmc_host auto ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 voldmanaged=sdcard0:29,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto vfat defaults voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto
And the new one:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/devices/msm_sdcc.1/mmc_host auto auto noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 voldmanaged=sdcard1:15,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard0:auto,nonremovable,noemulatedsd
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto
Did I miss something? I would really appreciate your help because I don't want to mess up my device...

looks pretty fine, just give it a try. If it doesnt work it will not damage your device.
alternatively you can use the following lines tested on Gummy and CM11:
Code:
/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:15,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:auto,nonremovable,noemulatedsd
For getting the job more easy i have made a AROMA installer that handles with partition renaming and flashing boot.img:
http://www.oppoforums.com/threads/a...rage-and-mount-external-sd-card-as-sd0.17852/

This can use on stock color OS?

vincent_smoox said:
This can use on stock color OS?
Click to expand...
Click to collapse
in principe: Yes
You have to modify fstab in boot.img to swap sd cards

I did it
Thanks a lot. It worked. Now I have a 128 GB SD Card in my Find7.
If anybody reads this and wants the Files needed for AOSB 1.3.6 - I uploaded the ROM including new boot.img and the boot.img alone to mega. Download here:
ROM+Boot.img
Boot.img only
I hope it works for you too

Everything was working fine until after 2 days, without warning, the screen went blank and then when I rebooted, I'm unable to save screenshots and gallery images are unavailable and external storage unavailable is the error. Sdcard0 is empty under /storage
Sent from my Find7 using XDA Free mobile app

Happened Again! Random reboot followed by corrupt partition. Cannot repair via TWRP also.

defective SD card?
Gesendet von meinem Find7 mit Tapatalk

Possible.
Sent from my Find7 using XDA Free mobile app

can you repeat step 7 again? I don't understand which zip file I have to download and how are the next small steps (command lines)?
Thank you very much for your help

jowar said:
can you repeat step 7 again? I don't understand which zip file I have to download and how are the next small steps (command lines)?
Thank you very much for your help
Click to expand...
Click to collapse
update.zip means the zip file of custom rom you have installed. next steps are in command line like steps before.

Aut0mat3d said:
In this Guide you will learn how to modify your system to handle the 9GB Partition 29 as Data (App-Storage) and use the external SD-Card as internal.
Don't be afraid, this is a lot of text mostly to explain the whole procedure, the steps are straight forward.
Thanks go to Kishd (oppoforums), Coldbird and alienmind (xdadevelopers)
Beside of the public made solutions i will do the following:
Instead of repartitioning the device i will change only the partition name of "sdcard" to "userdata", mount the external SD as internal and use the remaining 3GB Partition as external SD.
So partition 15 will become "sdcard1" and partition 29 will become "userdata"
On the Find7a you will have 9 gigs of application space and xx gigs for the internal sd (size of the sdcard).
This should work on Find7 too, someone has to check the partition layout if it is equal, than you will have 25 gigs of application space and xx gigs for the internal sd (size of the sdcard).
PRECAUTIONS:
If you mess around with partition table you could brick your device, so be careful!
Thes procedure worked for me, i am not responseable for any missing or mistyped commands/procedures, so THINK BEFORE YOU DO ANYTHING!
I am not an android Pro, nor an Develper. My Spare time is very limited so i can't help you out if something goes wrong!
I've done this with Gummy Rom, not tryed with ColorOS or another custom rom but it should work on all AOSP-based ROMS.
The swapped SD-cards do not belong to recovery, so the internal SD is accessed as before.
What do you need:
1.: Time: This is not done in 5 minutes, so please be patient.
2.: A Linux-PC with working ADB and Fastboot
3.: TWRP recovery image on your PC or installed on the device: http://techerrata.com/browse/twrp2/find7a (I used 2.7.1.0)
4.: An SD card with at least 16Gb inseted into your Find7a
5.: Fully charge your Device before messing around, some jobs will need a lot of time.
6.: A fitting custom ROM installed, i've done this with Gummy-M2.3-06-29-14-NIGHTLY-find7 which is suitable for find7 and find7a which can be found here: http://crackflasher.com/gummy-m2-3-06-29-14-nightly-find7-zip-oppo-find-7a-gummy/
7.: The zip-file of the custom rom on your local PC
What are we going to do:
0.: Boot into recovery and access the Device via ADB
1.: Format external SD to Ext4 Filesystem
2.: Backup the original partition layout and all partitions too
3.: Copy Data from internal SD to external
4.: Rename two partitions
5.: Format the new "userdata" partition and move all content of the old to the new location
6.: Format the new "sdcard1" partition
7.: Edit/replace fstab files in /etc to tell TWRP and System the new mountpoints
OK, let's do the trick
Step0.: Booting into recovery and accessing the Device via ADB-shell:
Put the phone into fast boot mode. (Power Volume Up simultaneously)
Open a terminal in your linux-PC and do the following as root (sudo -r):
#: fastboot devices ( check that fastboot is up and running)
#: fastboot boot openrecovery-twrp-2.7.1.0-find7a.img (or boot into TWRP if already installed)
The phone will boot into twrp.
Connect the phone and go into adb
#: adb shell
After entering the adb shell you should see the following in your terminal:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ #
Step1.: Format external SD to Ext4 Filesystem
First we have to write a new partition table as i dont know how your SD-card looks:
umount /external_sd (could cause errors if no filesystem is present on SD - dont mind)
parted /dev/block/mmcblk1 (you should see parted welcome message, no errors!)
mklabel msdos (this will write a new partition table on your sdcard)
mkpart primary ext4 1 -1 (this will make a ext4 partition which uses the whole sd)
quit
Now we are going to format the ext4 partition:
mke2fs -t ext4 -m 0 -L sdcard /dev/block/mmcblk1p1
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk1p1
mount /dev/block/mmcblk1p1 /external_sd (Mount the new formatted sd-card -- this should show no errors)
If all is done without errors, proceed to step2
Step2.: Backup the original partition layout and all partitions too
dd makes physical imagea of partitions so you can put it back if needed
While DD is copying you will see no progress bar or any output, so BE PATIENT!
Code:
mkdir /external_sd/backup
parted /dev/block/mmcblk0 print > /external_sd/backup/partitions (original partition Layout for later reference)
dd if=/dev/block/mmcblk0p1 of=/external_sd/backup/modem
dd if=/dev/block/mmcblk0p2 of=/external_sd/backup/sbl1
dd if=/dev/block/mmcblk0p3 of=/external_sd/backup/dbi
dd if=/dev/block/mmcblk0p4 of=/external_sd/backup/ddr
dd if=/dev/block/mmcblk0p5 of=/external_sd/backup/aboot
dd if=/dev/block/mmcblk0p6 of=/external_sd/backup/rpm
dd if=/dev/block/mmcblk0p7 of=/external_sd/backup/boot
dd if=/dev/block/mmcblk0p8 of=/external_sd/backup/tz
dd if=/dev/block/mmcblk0p9 of=/external_sd/backup/pad
dd if=/dev/block/mmcblk0p10 of=/external_sd/backup/modemst1
dd if=/dev/block/mmcblk0p11 of=/external_sd/backup/modemst2
dd if=/dev/block/mmcblk0p12 of=/external_sd/backup/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/external_sd/backup/oppostanvbk
dd if=/dev/block/mmcblk0p14 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/system.gz
dd if=/dev/block/mmcblk0p16 of=/external_sd/backup/persist
dd if=/dev/block/mmcblk0p17 of=/external_sd/backup/cache
dd if=/dev/block/mmcblk0p18 of=/external_sd/backup/recovery
dd if=/dev/block/mmcblk0p19 of=/external_sd/backup/fsg
dd if=/dev/block/mmcblk0p20 of=/external_sd/backup/fsc
dd if=/dev/block/mmcblk0p21 of=/external_sd/backup/ssd
dd if=/dev/block/mmcblk0p22 of=/external_sd/backup/misc
dd if=/dev/block/mmcblk0p23 of=/external_sd/backup/LOGO
dd if=/dev/block/mmcblk0p24 of=/external_sd/backup/DRIVER
dd if=/dev/block/mmcblk0p25 of=/external_sd/backup/reserve1
dd if=/dev/block/mmcblk0p26 of=/external_sd/backup/reserve2
dd if=/dev/block/mmcblk0p27 of=/external_sd/backup/reserve3
dd if=/dev/block/mmcblk0p28 of=/external_sd/backup/reserve4
dd if=/dev/block/mmcblk0p30 of=/external_sd/backup/grow
It is not urgently needed to make dd backups of userdata and (internal) sdcard but here for refernce:
Do a compressed multispan backup with dd so you can use the files on an FAT32 filesystem too:
dd if=/dev/block/mmcblk0p15 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/userdata.gz.
dd if=/dev/block/mmcblk0p29 | gzip -c | split -b 2000m -a 3 - /external_sd/backup/sdcard.gz.
Example of restoring partition 29:
cat /external_sd/backup/userdata.gz.* | gzip -dc | dd of=/dev/block/mmcblk0p29
Step3.: Copy Data from internal SD to external SD:
cp -a -i /internal_sd/* /external_sd/ (this can take a while)
ls /external_sd/ (you should see a bunch of files here)
If nothing went wrong go to step4
Step4.: Rename partitions:
umount /internal_sd/
umount /and-sec/
umount /data/
parted /dev/block/mmcblk0
name 15 sdcard
name 29 userdata
print (should show you the renamed layout)
quit
If nothing went wrong go to step5
Step5.: Format the new "userdata" partition and move all content of the old to the new location:
mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p29
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p29
mount /dev/block/mmcblk0p15 /internal_sd
mount /dev/block/mmcblk0p29 /data
cp -a -i /internal_sd/* /data/ (this can take a while)
If nothing went wrong go to step6
Step6.: Format the new "sdcard1" partition:
umount /internal_sd/
mke2fs -t ext4 -m 0 -L sdcard1 /dev/block/mmcblk0p15
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p15
If nothing went wrong go to step7
Step7.: Edit/replace fstab.qcom file to tell System the new mountpoints:
Guide from Coldbird: http://www.oppoforums.com/threads/unpack-repack-find-7-a-boot-img.14538/
Unpack update.zip and make a working directory.
copy file boot.img from update.zip into this directory
download https://github.com/xiaolu/mkbootimg_tools
unpack bootimage:
mkboot boot.img extracted (this will create a folder "extracted" with the content of boot.img where you can find fstab.qcom
edit fstab.qcom co match your needs (i.e. swap internal and external storage as shown below)
pack bootimage:
mkboot extracted newboot.img (creates newboot.img)
test bootimage (via fastboot):
sudo fastboot boot newboot.img
flash bootimage (via fastboot):
sudo fastboot flash boot newboot.img
sudo fatboot reboot
This is how the original file looks:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337 wait
/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:29,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/xhci-hcd auto auto defaults voldmanaged=usbdisk:auto
Code:
This is the changed file:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
# Use internal sdcard as /data
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
#/dev/block/platform/msm_sdcc.1/by-name/sdcard /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
# CM11 hack: Swap sdcard1 and sdcard0 - both in ext4 and (internal)sdcard1 as emulated
#/devices/msm_sdcc.2/mmc_host auto vfat defaults voldmanaged=sdcard0:auto,noemulatedsd
#/dev/block/platform/msm_sdcc.1/by-name/userdata /storage/sdcard1 ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 defaults
#/dev/block/platform/msm_sdcc.1/by-name/sdcard auto ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,nodelalloc,uid=1023,gid=1023,dmask=0007,fmask=0007 voldmanaged=sdcard1:29,nonremovable,noemulatedsd
# Original Entry of Gummy rom:
#/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:29,nonremovable,noemulatedsd
#/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:auto,noemulatedsd
# Working with switched sd-cards, Aut0mat3d:
/devices/msm_sdcc.1/mmc_host/mmc0 auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard1:15,nonremovable,noemulatedsd
/devices/msm_sdcc.2/mmc_host auto auto uid=1023,gid=1023,fmask=0007,dmask=0007 voldmanaged=sdcard0:auto,nonremovable,noemulatedsd
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbdisk:auto
Click to expand...
Click to collapse
Does this work with Color is 2.1.5?

unpack-repack-find-7-a-boot-img
Does anybody has unpack-repack-find-7-a-boot-img ? OppoForums are down. I need this file.

Develop Bugs

welcome