Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/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/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).
Chickenmarkus said:
Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/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/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).
Click to expand...
Click to collapse
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.
crossfire77 said:
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.
Click to expand...
Click to collapse
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.
Chickenmarkus said:
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.
Click to expand...
Click to collapse
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Sent from my HTC Wildfire S A510e using Tapatalk 2
crossfire77 said:
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Click to expand...
Click to collapse
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:
Chickenmarkus said:
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:
Click to expand...
Click to collapse
i guess a2sd+ works same as link2sd.it will mount downloaded apps,dalvik cache and cache to sd-ext.system will remain untouchable.
read this here
Related
How can I tell if I am running ext~4? THANKS
Sent from my SPH-D700 using XDA App
sandman512 said:
How can I tell if I am running ext~4? THANKS
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I've been trying to help you out as much as possible, but you really should post this in the q&a or general. You also could have just asked in the cwm3 thread rather than starting a completely new thread...
To answer your question: Just reboot into recovery and it should be orange. However, if you do this make sure you have a compatible kernel ready. If you odined using the deodexed cwm3 version I sent you too then you are good to go and can reboot no problem the kernel is compatible. If you used the one click cwm method then you will need to download an ext4 compatible kernel such as Twilight or Genocide.
sandman512 said:
How can I tell if I am running ext~4? THANKS
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Two ways:
If you have the SDK set up and know how to use adb, do this:
Code:
adb shell
mount
If not, you can go to the market, download "Terminal Emulator" (there's a chance whatever ROM you are on came with it) and open in up and type this:
Code:
mount
Both are going to spit out a lot of data. Just look for:
Code:
/dev/block/stl9 /system ext4 <MORE STUFF>
/dev/block/stl10 /data ext4 <MORE STUFF>
/dev/block/stl11 /cache ext4 <MORE STUFF>
If it says rfs instead of ext4, then you have rfs.
Dnathan, first thanks you have been extremely helpful. I did an all in one stock flash, root with cwm 3.0. So I want to make sure I'm good to go for my first Rom. I did not use a kernel or anything, but so far so good.
Sent from my SPH-D700 using XDA App
Thanks Devin. It looks like it says both?
export PATH=/data/local/bin:$PATH
$ $mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,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,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,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.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Sent from my SPH-D700 using XDA App
sandman512 said:
Thanks Devin
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
If you have thanks left use them when people help you, if you don't then just try to hit them up later. I know it can be scary, but you will get the hang of all this.
sandman512 said:
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
Click to expand...
Click to collapse
Yeah it looks like it didn't fully convert you. Data and cache should also be ext4.
Interesting, I just booted into cwm and the phone just started doing stuff. I then checked again and got this.
$ export PATH=/data/local/bin:$PATH
$mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,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,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,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.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Sent from my SPH-D700 using XDA App
sandman512 said:
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
Click to expand...
Click to collapse
Looks like that fixed it...clockworkmod 3.0.0.5/6 will convert automatically to ext4 when you first enter recovery
EDIT: Can theimpaler747 or another moderator move this thread to Epic 4G Q&A please?
Moved to Q&A. Please post in the correct section. Thank you.
Total SpaceA few weeks ago I have a problem with memory SD
when I install any version (JPU, JPI, or JPY) but when boot on the
Android Sytem recovery <3e> displayed the following message:
update,media, please wait
E:can't mount /dev/block/mmcblk0p1
(no sucho file or directory)
E: copy_dbdata/media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
After that flash with ODIN and speedmod-kernel-k12k-500hz
Then the phone starts NORMALLY, but it shows me two pop up:
Preparing internal SD, SD CARD IS DAMAGED, after that I go to:
SETTING/SD card and phone storage and shows me:
SD card and phone storage
Total Space
00
Available Space
00
Unmount SD card
Format SD card
Internal SD card
Total Space
Unavaible
Available Space
Unavaible
Format SD card
Format (erase) the SD Card
Internal phone Storage
Available space
00b
So I try to format both SD card, and nothing happens.
Connect the phone to pc, open SuperOneClick v1.91 and click ROOT
Width the phone rooting i go to adb :
c:\Program Files (x86)\Android\android-sdk\platform-tools\
1____I first put the phone in Debbuging mode,
2____Second fixed if the phone is attached:
adb devices >>>
List of devices attached
100012044e6e device
3____Go to adb shell> su > mount, and show me:
# mount
mount
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#
In this case try to find a route to the internal and external sd:
external : /dev/block/vold/179:9
internal: ????????????????
I add to this thread, images with different situations.
I read the following post but to no avail:
http://forum.cyanogenmod.com/topic/6...ernal-storage/
And millions of post that talk of SD brick
PLEASEEE HELLPPP MEEE!!!!!!!!!
Read allgamer's sticky.
Insanity cm - superaosp kernel.
This question should be in Q&A, please contact moderator to get it moved also watch this
http://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player
Insanity cm017/glitch v10c
Does anyone know if we have the ext2.ko or any of the ext file systems on our nooks? If not how hard would they be to add? As previously mentioned I'm clueless about the Android system.
Yes the Nook2 supports and uses ext2 ++
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block//vold/179:6 /media vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Thanks, I tried using linktosd and formated the first partition of SD card using fat32 and second part using ext 2. It formated correctly but nook kept stating the disk was damaged.
I'm using the MerrukTechnology Kernel 2.0 PRE-FINAL (2.6.35.7 [email protected]), Android Version: 2.3.6, Base Version: S5360BUTLC1, ext4 partitions, tried Darktremor app2sd, custom made (http://forum.xda-developers.com/showthread.php?t=832799), and etc.
Nothing works right, i used this custom on my G5 and works Just fine.
But on SGY not works well, sometimes works, sometimes not, sometime works and on next reboot stop, even can mount ok but apps not works.
Sometimes works perfect, but when i restore my Titanium backups, on next restart stop working.
This is the Script i'm trying:
/system/etc/init.d/02app2sd:
PHP:
#!/system/bin/sh
LOG=/data/app2sd.log
echo "$(date) mounting..." > $LOG
mount -o rw -t ext4 /dev/block/vold/179:2 /sd-ext 1>>$LOG 2>>$LOG
mount -o rw -t ext4 /dev/block/mmcblk0p2 /sd-ext 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/app /data/app 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/dalvik-cache /data/dalvik-cache 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
I already tried almost everything, somebody know some working script?
and what your log said?
irfanbagus said:
and what your log said?
Click to expand...
Click to collapse
pastebin.com/bih8vtiU
I wipe, i put script, restore backup and next restart stop all stop work even logcat said waiting device!
And app2sd.log:
# cat /data/app2sd.log
cat /data/app2sd.log
Tue May 15 15:40:26 BRT 2012 mounting...
mount: Device or resource busy
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437
0 0
/dev/block/stl11 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=or
dered,noauto_da_alloc 0 0
/dev/block/stl10 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=o
rdered,noauto_da_alloc 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /merruk tmpfs rw,relatime,size=32k 0 0
/dev/block/vold/179:2 /sd-ext ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/app ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/dalvik-cache ext4 rw,relatime,barrier=1,data=ordered
0 0
Tue May 15 15:40:29 BRT 2012 mount finished
Click to expand...
Click to collapse
you can try repencis. it has a2sd support but you'll need to change your partition into ext2.
kurotsugi said:
you can try repencis. it has a2sd support but you'll need to change your partition into ext2.
Click to expand...
Click to collapse
I don't like custom themes
I tried the DarkTremor too, but stops working too.
you can replace the theme with stock one. the one you need is the a2sd script in /system/bin and /system/xbin. everything else could be replaced with stock rom.
Not works anyway, even i tried the ChobitsDigitalis and i wipe, flash and when reboot it show the stock room not the custom rom
nexbr said:
I don't like custom themes
Click to expand...
Click to collapse
Try terma kernel but make sure a2sd script install 1st b4 the kernel.
Actually u can custmz ur stok kernel so can run a2sd.
Hi,
I formatted my external SDCard with 2 partitions, so I could use it with Link2SD. Since I am on a Mac I only could format the first one, which is FAT32. Now I need to format the 2nd with ext4 but I can only do this from inside the phone. Which is no problem, except I do not understand where I can find the device, I need to format. So, to sum it up: I have already a 'linux' type partition on the SDCard, unformatted, however. And I have a FAT32 partition on it, which gets mounted by Android already. What do I need to issue to the mke2fs command as input?
This is what I get, when issuing 'mount'.
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=771,uid=1000,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:32 /mnt/emmc 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:66 /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:66 /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
[email protected]:/ $ ls /mnt
asec
emmc
obb
sdcard
secure
[email protected]:/ $ ls /dev/block/vold/
179:0
179:1
179:10
179:11
179:12
179:13
179:14
179:15
179:16
179:17
179:18
179:19
179:2
179:20
179:21
179:22
179:23
179:24
179:25
179:26
179:27
179:28
179:29
179:3
179:30
179:31
179:32
179:4
179:5
179:6
179:64
179:65
179:66
179:7
179:8
179:9
[email protected]:/ $
In the recovery under mounts or advanced
Sent from my One V using Tapatalk 2
Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.
zmix said:
Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.
Click to expand...
Click to collapse
you sure??? i've formated my 8GB one with CWM5 before.....try TWRP or CWM6
Could be, that it offers 8 GB as well. I don't remember. But this is a 32GB card I have in use. What I'd need is two primary partitions, one around 6-8GB/ext4, the other one takes the rest as FAT32.
Can I install a different recovery mod, without resetting/erasing the phone? Is it as simple?
Ok, I updated CWM to v6 and re-checked. The max size is still 4096. Also I noted this:
After I left "advanced/partition" and turned on the log this shows up each time I select "show log"
Code:
When opening the log I get I: Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblkp1
and the "advanced/partitions" menu item is gone. "parted" in normal boot said, that I have overlapping partitions on the sdcard, which I doubt, since I did the partitioning with a special partitioning utility. Anyways, going to boot up a Linux VM now, should have done so much earlier It's just always so messed up with getting external volumes on USB to recognized.
I'll sort this ASAP thank you for bringing it to my attention
Sent from my One V using Tapatalk 2
Thanks for trying so hard. Greatly appreciated
On a side-note... I tried with a VM, but whatever way I tried to connect the SD card to the Linux guest, I did not succeed. So I am here again, no way to create an ext4 filesystem from inside the phone. Currently I play with the thought about installing a minimal, chrooted debia in my phone. But then I still have the problem with parted moaning about "overlapping partitions", which must be invisible to me, since I just checked the partition table with OS X' fdisk and all numbers seem in sequence. Okay, going to the other thread