Database Users

Insufficient Space Available

Ok, so I was rocking Thedude's 1.1a and new a2sd method on a 1 gig SD card. I recieved my 16 gig card in the mail yesterday, so I backed up my /system/sd/app and /system/sd/app-private, rebooted the phone with the new card in, partitioned it (500MB ext2), copied the directories back over to the SD and everything worked dandy.
Until, that is, I needed to install an application. First, it was LatinIME.apk. The app was acting goofy for my beforehand, but I was waiting until I got the new SD card to try fixing it. I removed the apk from /system/sd/app but the app still worked, so I had to uninstall it from the settings menu. I then tried installing it from the apk using appsintaller, but got the error message:
"Android Keyboard could not be installed on this phone."
Great.. I tried reboot etc, but nothing. So I try to ADB install it:
"INSUFFICIENT_SPACE_AVAILABLE" (or something to that extent, didn't write it down)
Alright, whatever. I physically copied the apk into /system/sd/app and it worked out beautifully.
Now, when I try to install an app from the market, I get an error:
"Installation error: Insufficient storage available"
which is complete BS because I can (using adb shell) put any file I want into /system/sd/app and there's 470 MB remaining.
I searched for this problem, but all I found were people with the same problem on A2SD old method, and they had to symlink app-private to their SD card too. I have app-private and app in /system/sd, so I'm not too sure what the problem is. When I remove my new card and use the old card, same problem. When I remove my card and try to have it install to /system/intmem, same problem. Does anyone have any ideas?

Ooglez said:
Ok, so I was rocking Thedude's 1.1a and new a2sd method on a 1 gig SD card. I recieved my 16 gig card in the mail yesterday, so I backed up my /system/sd/app and /system/sd/app-private, rebooted the phone with the new card in, partitioned it (500MB ext2), copied the directories back over to the SD and everything worked dandy.
Until, that is, I needed to install an application. First, it was LatinIME.apk. The app was acting goofy for my beforehand, but I was waiting until I got the new SD card to try fixing it. I removed the apk from /system/sd/app but the app still worked, so I had to uninstall it from the settings menu. I then tried installing it from the apk using appsintaller, but got the error message:
"Android Keyboard could not be installed on this phone."
Great.. I tried reboot etc, but nothing. So I try to ADB install it:
"INSUFFICIENT_SPACE_AVAILABLE" (or something to that extent, didn't write it down)
Alright, whatever. I physically copied the apk into /system/sd/app and it worked out beautifully.
Now, when I try to install an app from the market, I get an error:
"Installation error: Insufficient storage available"
which is complete BS because I can (using adb shell) put any file I want into /system/sd/app and there's 470 MB remaining.
I searched for this problem, but all I found were people with the same problem on A2SD old method, and they had to symlink app-private to their SD card too. I have app-private and app in /system/sd, so I'm not too sure what the problem is. When I remove my new card and use the old card, same problem. When I remove my card and try to have it install to /system/intmem, same problem. Does anyone have any ideas?
Click to expand...
Click to collapse
I hate to be devil's advocate here but do you know how much space is available on /system/sd/intmem? Could be that it's seeing that there isn't enough space there and so won't let you install.

[email protected] said:
I hate to be devil's advocate here but do you know how much space is available on /system/sd/intmem? Could be that it's seeing that there isn't enough space there and so won't let you install.
Click to expand...
Click to collapse
busybox df -h: (or at least the relevant parts)
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock5 74.8M 28.6M 46.2M 38% /system/intmem
/dev/block/mmcblk0p2 535.5M 27.8M 480.4M 5% /system/sd/
unionfs 535.5M 27.8M 480.4M 5% /data/app
unionfs 535.5M 27.8M 480.4M 5% /data/app-private
Also, I have tried wiping and reflashing the phone, then reinstalling the latest a2sd method (replacing both init.rc and a2sd.sh).. so I'm really at a loss :-/

i think there might be two explanations
one is that there is some other file system error, but the app installer is not designed to cope with that, so it mistakenly reports no space.
or the installer is hardcoded to check the /data partition instead of the mount point /data/app is in.

billc.cn said:
i think there might be two explanations
one is that there is some other file system error, but the app installer is not designed to cope with that, so it mistakenly reports no space.
or the installer is hardcoded to check the /data partition instead of the mount point /data/app is in.
Click to expand...
Click to collapse
I think it may be the first one. When I connect my SDcard to the computer using the pull down menu and mount (which worked on the 1 gig,) upon disconnecting, the phone crashes trying to "prepare the SD card" and will reboot. What's goin on, eh?

For troubleshooting purposes, this is what I get from
busybox df -h:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 64.4M 25.6M 72% /system/
/dev/block/loop0 836.0K 836.0K 0 100% /system/modules
/dev/block/loop1 3.5M 3.5M 0 100% /system/xbin
/dev/block/mtdblock5 89.8M 29.8M 59.9M 33% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
/dev/block//vold/179:1
7.4G 3.5G 3.9G 47% /sdcar
Using Dude's 1.2, I DO NOT want apps2sd, so do not have ext2 partition on my SD card. I like to just be able to install apps to internal memory.

Ooglez said:
I think it may be the first one. When I connect my SDcard to the computer using the pull down menu and mount (which worked on the 1 gig,) upon disconnecting, the phone crashes trying to "prepare the SD card" and will reboot. What's goin on, eh?
Click to expand...
Click to collapse
Sorry, wasn't concentrated enough the first time. I saw that using the unionfs method, you mounted the internal data partition on /system/intmem , so what is data now? Is it mounted at all? Because if it's not mounted, it is just a directory of the ramdisk image, which is read-only and indeed has no free space. Could you explain to my why it is necessary to mount mtdblock5 this way?

what is the output of :
ls -l /system/sd
It's a permission issue I think .
try
chown -r 1000:1000 /system/sd
chmod -r 755 /system/sd

I really do believe poeple need to read that sticky. Please people do a search before posting.

maybe the 2 100%'s in the chart?
Haven't tried ADB on my pc but trying to install from market gets me same from above, " insuffcient storage space available. This is what I get from busybox
$ busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock. 367.5M 64.4M 3.1M 95% /system
/dev/block/loop0 836.0K 836.0K 0 100% /system/modules
/dev/block/loop1 3.5M 3.5M 0 100% /system/xbin
/dev/block/mtdblock5 74.8M 34.3M 40.5M 46% /data
/dev/block/mtdblock4 67.5M 1.5M 66.0M 2% /cache
/dev/block//vold/179:1
3.8G 3.4G 412.7M 89% /sdcard
I do not have A2SD mainly because I don't care for it. I am well aware that 1.2 of dude's bill carries bugs and I would revert back to 1.1 or something of similar likes but being unable to install a file manager and not being able to access a pc has left me with an eternally stock g1...

reverted to dude 1.1
That solved it now I'm on cyanogen's build works great. I'm ditching dude till he fixes it...

What DID WORK on the other hand was removing the entire app directory under /data/data.
So for instance for "Network Discovery" app that would not update due to
"insufficient storage available" i did:
cd /data/data
rm -rf info.lamatricexiste.network
The app would then install from Market as usuall.

apider said:
cd /data/data
rm -rf info.lamatricexiste.network
Click to expand...
Click to collapse
That's strange, I have this issue from time to time, developing from eclipse, when pushing update of my app to the device (N1).
Network Discovery does not have any special thing that could end to this behavior, using only the sdk..
Let me know martindjr88 if you are using "Network Discovery" too.

Cant push update to SD

So last night I installed the newest JAC Hero build and it was forcing close on google maps and a few others. In the thread it said to format your ext2 partition so I used paragon and I thought I formated it but now It wont get past the HTC screen. I can go to recovery and fastboot but when i try to push any new update it just updates to the hero rom again. Also if I use ls to list the files it shows nothing in /sdcard but obviously it has stuff since it still will flash the hero rom fine. How can I make a new update override this one when I push it to the phone? I dont have a card reader so I have to use my phone.

You must have your FAT32 partition first, the big one,where you put your update.zip and then a ext2 or ext3 partition of ≈500mb.
have you respect this order ?

Yes, I have a 1gb card and my 600mb fat32 is first then a 400mb ext2.

When you are in adb your ext2 partition is /system/sd
More than likely you need to do this part from my post here: http://forum.xda-developers.com/showthread.php?t=517874
Delete existing apps on SD
Code:
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/app-private

imfloflo said:
≈500mb.
Click to expand...
Click to collapse
You have 500mb of bacon?!?!

When I try those commands it says no such directory or file for both.
EDIT: I just got it fixed with these commands from brandenk's thread:
adb shell mount /sdcard
adb shell rm /sdcard/update.zip
adb push *filename* /sdcard/update.zip

Charbo said:
When I try those commands it says no such directory or file for both.
Click to expand...
Click to collapse
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd

phantasm714 said:
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
Ok, so I thought it was fixed but it was stuck at the android screen. Im guessing because of my apps still on the card? When I tried your command it said no such file or directory also so I did mkdir /system/sd and tried again and it said invalid argument.

I got it into android now with the sd card out when i turned it on. So now is there any way i can completly wipe the sd card of all partitions from in windows so I can start over?
EDIT: Got it formatted from the sd card settings on the phone lol... now I can start over thanks for all your help.

I'm hoping someone could help me with loading JAC's 2.2 Hero rom
I've never had any problems updating, but I had never tried a hero rom before
When trying to update i get this error
"Copying files...
E:Can't chown/mod /system/xbin
(No such file or directory)
E:Failure at line 12:
set_perm_recursive 0 2000 0755 0
6755 SYSTEM:xbin
Installation aborted"
Anyone know whats causing this?
There's a handful of people also experiencing this issue

How to I run repair ext filesytems

I tried everything possible to install jachero and I continually get a bootloop in the HTC opening intro. Ive used unbuto , pargon partition manager to make , format the ext2/ ext3 partitions. But whenever I try to install I always get a bootloop. I don't know what the hell is wrong but i spent hour upon hour trying to get this to work.. Im usuing Cyanogenmod 1.2 and am trying to repair the ext filesystems and then it says,
Erro checking filesystem! Run e2fsck maually from console! can someone give me exact instructions on how to run e2fsck and do what has to be done so i can install Jachero.

Stuck in the same boat as you... I get to the Hero/HTC bootloop and I've tried what you have. In the recovery do this: Alt+X to get to console then type: e2fsck /dev/block/mmcblk0p2 to run the fix. I tried that, but still boot looping, maybe you'll have better luck with it...

Bootlooping, I had that issue after I tried to link my /data folder back to my SD. Didnt like that. Is your data folder there?

ok first of all, are you running the latest Radio and SPL? Access fastboot (Camera and Power OR Back and Power) and post the info you get here.
for the command to e2fsck try running this
e2fsck /dev/block/mmcblk0p2 <--- For ext2
e2fsck /dev/block/mmcblk0p3 <--- For ext3

nephron said:
e2fsck /dev/block/mmcblk0p3 <--- For ext3
Click to expand...
Click to collapse
I should point out that this block here could also be the linux-swap partition for alot of people and that the 2nd one could be ext3 if its been converted.

jhood99 said:
I tried everything possible to install jachero and I continually get a bootloop in the HTC opening intro. Ive used unbuto , pargon partition manager to make , format the ext2/ ext3 partitions. But whenever I try to install I always get a bootloop. I don't know what the hell is wrong but i spent hour upon hour trying to get this to work.. Im usuing Cyanogenmod 1.2 and am trying to repair the ext filesystems and then it says,
Erro checking filesystem! Run e2fsck maually from console! can someone give me exact instructions on how to run e2fsck and do what has to be done so i can install Jachero.
Click to expand...
Click to collapse
I fixed this by using a different SD Card

DDMS Error

When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?

Mdawg112 said:
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Click to expand...
Click to collapse
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.

smw6180 said:
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
Click to expand...
Click to collapse
Ha, I feel stupid now.

Mdawg112 said:
Ha, I feel stupid now.
Click to expand...
Click to collapse
Happens to everyone at times. Don't sweat it

So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/

jubi23 said:
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
Click to expand...
Click to collapse
Good question. Unfortunately I have no idea. Never seen it fail. theoretically there's a command line you can run in adb shell to mount the FS read/write, but I can't remember it off the top of my head.
Something like mount -o rw /dev/m3blk (as I said I can't remember the exact filesystem name). I'd do a search for 'mount -o' on the forums. It's been posted more than once and I'm too lazy to find it for you

I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw

Yeah, I'm having the same problem as you sometimes. Other times it works. It's very strange! It annoys me. Anyone have any idea on a fix?

jubi23 said:
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Click to expand...
Click to collapse
Yeah that's the one, thanks.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Sounds like you've checked anything else I would have thought of...wish I could help.

Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Click to expand...
Click to collapse
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying

jubi23 said:
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
Click to expand...
Click to collapse
That could be it. ext4 doesn't play nicely with ext3 based stuff. It's 'semi' backward compatible (meaning you can mount ext4 as ext3) but it seems to have some serious inconsistencies that way. I'd recommend a re-partition and then upgrade ext3->ext4 AFTER you install the new ROM.
Heh. I had all KINDS of problems restoring an ext3 based nandroid after upgrading to ext4. Had to repartition and then restore the nandroid to get it to work.

well, loaded recovery, re-partitioned my sdcard, upgraded to ext3 and left it there, still nothing

the sd card wouldnt have any bearing on the ability to adb remount.
the /system partition is stored on the phone itself, so the mount -o ..yadda yadda
remounts the /system partition in this case /dev/block/mtdblock3.
the only reason a sd card would come to play is if youre runnign a2sd, in which case it makes symlinks (shortcuts) to the sdcard, if the sdcard is formatted improperly then a2sd will either cause a bootloop, or crash and then youre phone should boot normally but you wont have access to your ext4 partition (the partition with your apps).
im not sure how to fix a problem with adb remount, perhaps try a new version of the SDK or just a clean one.
good luck

I'm wondering if there is something wrong with my mounting
When i'm in the shell
if i cd /sdcard
then do a ls
nothing is returned
I've also directly copied the recovery image from my computer to the sdcard, and attempted to run the flash_image command and it says no such file or directory
I do have usb debugging enabled and am selected to mount the sdcard, is there some other step or something i'm missing?

nenn, i had actually just a little bit ago downloaded the latest sdk on a completely different machine and still same results

Alrite, so I was able to copy the image recovery from
explorer and flash from.terminal on my phone
Although I'd prefer to work from the pc, anyone have any other possible ideas?! I'm at a loss
-------------------------------------
Sent from my HERO200

Mounting storage manually

With no questions asked ask to why I'm asking, I need to know how to manually mount the sd card so my device can use it while booted.
The following works via adb shell to mount the internal storage on /emmc at boot:
echo "" >> /system/bin/sysinit
echo mount /dev/block/mmcblk0p3 /emmc >> /system/bin/sysinit
Perhaps it's as simple as figuring out which partition on /dev/block is the sd card? Any help is greatly appreciated.

While booted using the device normally, the sdcard should already be mounted rw without doing anything.

xvenom89 said:
Perhaps it's as simple as figuring out which partition on /dev/block is the sd card? Any help is greatly appreciated.
Click to expand...
Click to collapse
Noob here. So don't have a clue. However, I do know you can just run the mount command with no parms to get a list of the partions. Please ignore if that was already obvious.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

krelvinaz said:
While booted using the device normally, the sdcard should already be mounted rw without doing anything.
Click to expand...
Click to collapse
It doesn't, this is why:
http://forum.xda-developers.com/showthread.php?t=754929
It mounts fine on stock Eclair and did fine on the Froyo leaks, but after deleting the stupid VZW partition I'm left with this issue.

rigman said:
Noob here. So don't have a clue. However, I do know you can just run the mount command with no parms to get a list of the partions. Please ignore if that was already obvious.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)
Click to expand...
Click to collapse
The partitions are as follows:
~ # ls /dev/block/
mmcblk0 mmcblk0p2 mmcblk1 mmcblk1p3 mtdblock1 mtdblock3 mtdblock5
mmcblk0p1 mmcblk0p3 mmcblk1p1 mtdblock0 mtdblock2 mtdblock4 mtdblock6
I just don't have a clue as to which is for what, except that mmcblk0p3 is for the phone's 8GB of internal storage.

Mount command shows
/dev/block/vold/179:9 /mnt/sdcard vfat
Does that help at all?
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

Not yet, no. I'm trying to mount it and emmc from recovery and they are still listed as "unavailable" under settings. Could you upload your /system/bin/sysinit for me? Perhaps that is what I need.

xvenom89 said:
Not yet, no. I'm trying to mount it and emmc from recovery and they are still listed as "unavailable" under settings. Could you upload your /system/bin/sysinit for me? Perhaps that is what I need.
Click to expand...
Click to collapse
File /system/bin/sysinit doesn't exist. I searched /system and all subdirectories and no such file exists.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

Edit: Deleted text. It was a dumb comment. I understand now that I read your other post.
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)

rigman said:
From home screen when I go menu>settings>sd & phone storage, it shows my sd card total space and available space. Also gives an option to unmount the sd card. Which means it must be already mounted, right?
________________________________
Unrevoked forever
SkyRaider 2.5.2 Sense
Hrdra kernel ocuv_ov_v10 (#2)
Click to expand...
Click to collapse
Yes, that's what normally happens. The problem is described in my thread here; I can choose to mount them from the notification bar when connected to my computer, but they do not mount. From Menu -> Settings -> SD & Phone Storage, the SD Card and Internal Storage are listed as Unavailable and the options to Format and to Mount are grayed out. The SD Card mounts fine in Clockworkmod Recovery, but not when I boot the system.