A2SD Error? - Hero CDMA Q&A, Help & Troubleshooting

Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me

Don't know if this will work, but try this:
Go into an adb shell. Type this:
cd /data/data/com.android.vending/cache
rm -f *
reboot
This will clear the market cache and reboot your phone.
Let me know if that works.
kronik03 said:
Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me
Click to expand...
Click to collapse

Related

apps2sd working, but /data size increasing?

In short: When I install a new app, the app gets installed in /system/sd just fine (/data/app and /data/app-private symlinks work just fine) , but /data increases a little too.
before installing seesmic and pandora df shows:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197584 0 197584 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 110484 37996 74% /system
/dev/block/mtdblock5 200960 [B][COLOR="Blue"]62260[/COLOR][/B] 138700 31% [B]/data[/B]
/dev/block/mtdblock4 97280 39952 57328 41% /cache
/dev/block/mmcblk0p2 702873 [B]97721 [/B]567652 15% [B]/system/sd[/B]
/dev/block/mmcblk0p2 702873 97721 567652 15% /data/dalvik-cache
/dev/block//vold/179:1
14898512 827680 14070832 6% /sdcard
After installing seesmic and pandora df shows:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197584 0 197584 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 110484 37996 74% /system
/dev/block/mtdblock5 200960 [B][COLOR="Red"]62544 [/COLOR][/B] 138416 31% [B]/data[/B]
/dev/block/mtdblock4 97280 41280 56000 42% /cache
/dev/block/mmcblk0p2 702873 [B]100347 [/B]565026 15%[B] /system/sd[/B]
/dev/block/mmcblk0p2 702873 100347 565026 15% /data/dalvik-cache
/dev/block//vold/179:1
14898512 827680 14070832 6% /sdcard
Notice that /data increased by 300KB. Anyone know why?
why is my /data partition 31% used?
Yes, the size of the /data partition does increase even with apps2sd enabled... and from a quick analysis of the /data partition (with apps2sd enabled), I noticed this...
1. the applications are installed on the sd card and the /app & /app-private are symlinked
2. the application information is stored in /data/system/packages.xml (kinda like the windows registry)
3. some application data like shared prefs, extra libs (if any) are stored in /data/data
i guess this accounts for the usage size increase!!!
It looks like the apps are getting is installed to the sd card fine, but the app data still gets stored in the internal ROM
/data/data has 157 folders and is 52MB
/system/sd/app-private has 0 files and is 1K
Therefore it looks like either the apps2sd implementation is incomplete, or didnt get installed correctly.
Anyone tried moving /data/data to /system/sd/app-data and creating a symlink for it? (trying this now...)
darn it. after a reboot the OS removed my symlink, created a new /data/data folder, and apps are still writing to this folder now. lucky i made a backup.
... maybe while booting it saw that the /system/sd/app-data link was invalid (not mounted yet), and hence re-created the folder.

quick ? about arom's partition steps.

was running cm's newest rom but decided to try out kings new 1.9 rom that just came out.
booted into recovery, factory wiped, then i did the "wipe sd:ext partition. after doing this i did "partition sdcard", after that was done i did "ext2 to ext3" then "ext3 to ext4" as the rom suggested.
After this was done i rebooted recovery and connect the usb and installed the rom and flashed it. it runs good but the only thing is that the ap2sd will not work.
It shows me this:
total space: 6.88gb
available space: 6.81bg
SD card secondary:
total space: unavailable
available space: unavailable
internal phone storage:
available space: 81.84mb
where did i go wrong?
I'm not familiar with that rom but does it support ext4? You may need to use ext3.
You may need to re-partition again, something may have gone wrong... who knows.
Type this in terminal
Code:
busybox df -h
and post your results here when you have a chance.
filesystem size used available use% mounsted on
tmpfs 52.4m 0 52.4m 0 /dev
tmpfs 4.0m 0 4.0m 0 /sqlite_stmt
_journals
/dev/block/mtdblock3 90.0m 82.0m 8.0m 91% /system
/dev/block/mtdblock5 89.8m 15.5m 74.3m 17% /data
/dev/block/mtdblock4 30.0m 1.1m 28.9m 4% /cache
/dev/block/mtcblkop2 800.8m 46.1m 712.0m 6% /system/sd
/dev/block/mtcblkop2 800.8m 46.1m 712.0m 6% /data/dalvik-cache
/dev/block//vold/179:1 6.6g 708.0k 6.6g 0% /sdcard
this is what shows up. help? lol
/dev/block/mtcblkop2 800.8m 46.1m 712.0m 6% /system/sd
This is your apps2sd partition. Your next step is to download couple of big apps and check that again. If the your % went up - then it's working, just not showing up in the settings (I know few roms did a while ago, including CM cupcake roms). Remember, not everything goes on SD when you install an app, only and actual APK and dalvik-cache file. Other data stays in the phone so the phone's internal memory will go down a bit after install.
You can also try
Code:
ls /system/sd/app
ls /system/sd/app-private
ls /system/sd/dalvik-cache
to see what is in those directories before and after install. If you install an app and it shows up in one of the app dir's and in dalvik dir - then you're in the clear.
Good luck.
negative, i've installed a few apps and they all go to the internal memory. might be that the sd card is defective.

Need Some More Help Partitioned and loaded rom but internal mem is still under 32 sho

i used amon ra v1,5,2 because it is stable but i checked my internal mem and it says 32mb which is still regular phone mem
do i need ap2sd to get my 96mb or do i need to convert ex3 to ex4 or is there something im missing
What spl are you using?
Also, type
Code:
busybox df -h
in terminal and let us know the output.
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
DroidFreek said:
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
Click to expand...
Click to collapse
Doesn't look right . Your df -h output should look something like this
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.9M 12.0K 47.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 90.0M 66.4M 23.6M 74% /system
/dev/block/loop0 512.0K 512.0K 0 100% /system/modules
/dev/block/loop1 2.8M 2.8M 0 100% /system/xb
/dev/block/mtdblock5 89.8M 27.4M 62.4M 30% /data
/dev/block/mtdblock4 30.0M 24.1M 5.9M 80% /cache
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /system/sd
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /data/dalv
/dev/block//vold/179:1
6.9G 6.3G 670.3M 91% /sdcard
where /system/sd is your apps2sd partition (if you have it) and /data is your internal storage.
I have 62megs free in my data, I'm not sure where you hear 96 megs but its complete unnecessary to have that much space free. I've yet to experience any slowdowns or low mem warnings. Also remember.... some devs put parts of their rom on /data partition and that will decrease your available space.
Also, there's absolutely NO WAY you should be getting low mem warning with 34 megs free. That only happens when you have less then 10 megs available. Apps2sd is the obvious choice if you want to have as much phone mem available as possible.
Your a real geniuos ty I got it to work but what is the secondary sd for what does it store and how can I access it I am currently using estrongs explorer
Don't know about estrongs... never used it. Rule of thumb, if it asks for SU access the first time you run it - then it will be able to access it.
I'll break it down for ya
Internal memory:
/system - your rom
/system/app - system files (google apps, dialer, contacts etc)
/system/**** - extra stuff that our devs include (thanks to them)
/data/app - non-protected apps
/data/app-private - protected apps
/data/dalvik-cache - working files for all apps
/data/data - your settings
/system/sd - aka your secondary partition, aka apps2sd is a part of your sdcard. Only accessible in Linux or in terminal. When you have apps2sd set up, your phone will bypass /data/app, data/app-private and /data/dalvik-cache and forward those files to /system/sd/app, /system/sd/app-private and /system/sd/dalvik-cache. It will still use /data/data for all of your settings. I know it's a lot of slashes there but it will start making sense as you progress with Android hacking.
If you want to see what's on secondary sd just type this in terminal
Code:
ls /system/sd
This will give you a print-out of the apps that are on your sd.
Anything else I'm forgeting?
Ok this is the new output
$ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3**** 67.5M**** 61.8M***** 5.7M* 92% /system/dev/block/loop0
Is it possible you can give me a list of all the commands for terminal
http://www.droidforums.net/forum/droid-hacks/26036-linux-commands-android.html
Try this, some basics.
want to make exact image of my whole os and all apps in it
Is it possible to make an exact image of of my whole os including the apps web bookmarks and etc
sort of like the program iamgeburn does for pc
yea a nandroid back up. check your recovery for a back up option
So i just head to recovery and choose nanodroid then choose backup right
after soing so where does it save to and how can i retrieve it after a complete wipe of sd and system
saved on your sdcard under nandroid.
To use it, in recovery select restore and choose the nadroid that you want to recover. Your now back to exactly where you were when you created it.
easy peasy.

help needed please - JP3 problem...?

i just flashed to JP3 followind the useful guide from this forum. it all went well, seems verry snappy, bu i have one problem... if i try to install fifa 10 it says i`m out of space "clean up some space and try again". also, if i try to install NOVA for example, it goes thru with the installation but when it starts it says "an SD card with at least 7mb is needed to download" even after i preveously copied the game cache to the SD card....
i forgot to mention some things :
1. i dont have a "lag fix"
2. the external SD, the internal Sd and the phone memory, all have at least 2 GB of free space!
I cannot find a fix anywhere on he internet even know i tried to ...
thank you in advance and excuse my english
hm. make a
busybox df -h
please ...
I am also having problem installing game w update. anyone know why we having this problem?
same here. What I heard is that the 2.2 rom mount phone memory to /internal_sd instead of /sdcard and it causes the problem....
evermick said:
same here. What I heard is that the 2.2 rom mount phone memory to /internal_sd instead of /sdcard and it causes the problem....
Click to expand...
Click to collapse
that may be the case but i also have about 2GB of unused disk space on the internal sd, so it should work ...
jodue said:
hm. make a
busybox df -h
please ...
Click to expand...
Click to collapse
i have the same problem. just installed busybox + rooted
$ su
su
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 152.4M 0 152.4M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 152.4M 0 152.4M 0% /mnt/asec
/dev/block/stl9 275.8M 271.8M 4.0M 99% /system
/dev/block/mmcblk0p2 1.9G 68.1M 1.8G 4% /data
/dev/block/stl10 127.2M 10.9M 116.3M 9% /dbdata
/dev/block/stl11 30.1M 32.0K 30.0M 0% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/block/vold/179:1
5.8G 1012.9M 4.8G 17% /mnt/internal_sd
/dev/block/vold/179:9
7.6G 259.4M 7.3G 3% /mnt/internal_sd/externa
l_sd
/dev/block/vold/179:9
7.6G 259.4M 7.3G 3% /mnt/secure/asec
#
please help!
It is only the most reported bug in froyo.... Have you even tried to read the forum?
And no, there is no fix f for it.
Sent from my GT-I9000 using XDA App

[Q] app2SD - can't mount ext2 partition

Hi, I have an unlocked, rooted Milestone running 2.1-update1.
I am having some issues getting App2SD up and running.
Everything seems to be working fine except for one piece:
I can't mount the ext2 partition of my SDCard.
I have a 16gb sdcard, formatted with two primary partitions, 14.5gb for FAT32 and 1.5gb for ext2.
busybox was installed ok, all the shell scripts seem to have installed fine as well, however, in order for it to work, the "mount_sd.sh" script has to be able to mount the second partition in order to link /data/app to it - but the damn thing won't mount.
I have tried re-partitioning the SD card multiple times, using multiple different partitioners (gparted in Ubuntu, Minitool in XP, even fdisk in the Android shell itself...) but nothing seems to work - I always get the same error:
Code:
# mount -t ext2 /dev/block//vold/179:2 /system/sd
mount -t ext2 /dev/block//vold/179:2 /system/sd
mount: No such device
The device however, most certainly DOES exist:
Code:
# ls /dev/block//vold
ls /dev/block//vold
179:2
179:1
179:0
I have seen that some people use the /dev/block/mmcblk0 instead of /dev/block//vold/179 - I am unsure as to why (anyone know which one I should be using on the Milestone???) but I tried that as well:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Again, it tells me the device doesn't exist, when it clearly DOES:
Code:
# ls /dev/block/mmc*
ls /dev/block/mmc*
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
When I try to verify the partitions are there in the ADB shell, it looks like /dev/block//vold/179 doesn't exist or is some kind of special device (incidentally, does anyone know wtf the double slashes "//" are for?):
Code:
# fdisk /dev/block//vold/179
fdisk /dev/block//vold/179
fdisk: can't open '/dev/block//vold/179'
However, I CAN fdisk /dev/block/mmcblk0, and it gives me the following partition table:
Code:
# fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
...snip...
Disk /dev/block/mmcblk0: 16.0 GB, 16039018496 bytes
255 heads, 63 sectors/track, 1949 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1762 14153233+ b Win95 FAT32
/dev/block/mmcblk0p2 1763 1949 1502077+ 83 Linux
So, it looks like /dev/mmcblk0 is the correct block device, however, mount tells me this:
Code:
# mount
mount
...snip...
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=101
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
So, mount is telling me that the first partition is mounted onto /sdcard from /dev/block//vold/179:1
I am confused. The only thing left I need to do in order to get App2SD working on my Milestone, is to mount the bloody second partition of my SD card and link it to the file system, yet the damn thing refuses to mount.
Does anyone know where I am going wrong here?
Which is the correct block device I should even be trying to mount /dev/block/mmcblk0 or /dev/block//vold/179:2?
I don't want to flash to an unofficial 2.2 and I have everything else working just the way I want it, so I'd rather not reset either.
There MUST be a solution somewhere, but I am getting frustrated.
Thanks for any help you can give me!
Hello!
I'm having exactly the same problem... I've been trying to find a solution for this problem for the last 3 hours, but I can't figure out a way...
Can anyody give us a light??
Thanks!
Same question here. Partitioned more than a month ago, but then I reached a dead end. I don't know a reliable way to mount the ext2 partition. I'm familiar with Linux, and I have tried all kinds of crazy shell scripts, but the Android filesystem is still a bit alien to me.
By the way, what is this App2SD that you speak of? It's something different from the Apps2SD app on Froyo, right?
JoeDuncan said:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Click to expand...
Click to collapse
A shot in the dark would be ext2.ko is not insmodded ... ?
got this problem to on stock US froyo kernel for Samsung Galaxy 5. I also suspected ext2 was missing but it seems compiled into kernel.
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext2
nodev ramfs
vfat
nodev nfs
rfs
For the MS, you have to insert a ext2 Kernel module, look around here on the forums..
Depending on which module-version you're using try "-t auto" instead of "-t ext2"
Also you should use "/dev/block/mmcblk0p2" if this is your ext2 partition
Besides, there should be some packages available which contain the necessary scripts and files to install this automatically and at boot, applicable as OR-updates
It was my understanding that Apps2SD could not be used on 2.1, you needed 2.2 to use that app. Although I have the same issue with Links2SD which is suppose to work with 2.1. I can't get anything to see an ext2 or 3 or Fat partition.
My amator tries
Hy,
I've got the same problem on Cyanogen and Goapk roms:
mount -t auto /dev/block/mmcblk0p2 /sd-ext
doesn't work
I verified sd-ext was present
mkdir /sd-ext
Nothing changed.
My mount description is somethime using vold instead of mmcblk0p... I don't really understand.
However I succeeded to mount sdext by using busybox (on goapk rom)
busybox mount -r -w -t auto /dev/block/mmcblk0p2 /sd-ext
result mount:
rootfs / rootfs rw 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 /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=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,uid=1
000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
/dev/block/mmcblk0p2 /sd-ext ext2 rw,errors=continue 0 0
Just in case, If somebody can help me:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
*perl script are unable to decompresse boot.img, how to change init.rc in this case?
thanks
symlinks
lamidesbetes said:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
Click to expand...
Click to collapse
Symlinks can be removed with the rm command.
The "cross device link" error happens when one uses the ln command without the "-s" option (so attempting a hard link instead of symlink).

Categories

Resources