Related
I use a 1gb sd with a fat32 and a ext2 partition.
It doesn't want to install, tried also the eclair version. Same problem.
Please help me .
This is my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 988 KB for FAT
Attempting to allocate 988 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (201623) not correct (201622)
Fix? yes
Next free cluster in FSInfo block (50390) not free
Fix? yes
9 files, 403244 free (201622 clusters)
sh: 1: unknown operand
Using partitioned system
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p2 is mounted
ext2: clean, 11/120832 files, 15402/481950 begin_of_the_skype_highlighting**************15402/481950******end_of_the_skype_highlighting blocks
Creating a new Data store
256+0 records in
256+0 records out
mke2fs 1.38 (30-Jun-2005)
mke2fs: cannot determine if /sdcard/andboot/data.img is mounted
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 11/65536 files, 8286/262144 blocks
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
Click to expand...
Click to collapse
Also adding a third partition as linuxswap makes this install not even see the ext2 partition, thats why I did not add a linuxswap, do I need to?
Try installing it without an ext2 partition, there really is no benefit from using an ext2 partition on a haret install, in fact it may be the cause of your problems, a swap partition may help however, around 64-96 MB is usually more than enough.
The error messages may indicate that the Fat32 partition is not the first partition on the SD card, it depends what you used to partition the SD, some utilities are no good for android SD partitioning, since they may create the partition wrongly, ( as far as android is concerned).
Hello...
Due to the corruption of the Data partition, i've installed android with System on NAND, data on SD Partition. Now, this leaves a few megs of space on NAND unused.
I've used atools, configured as i thought it would work:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yet upon install and boot, i find out the System is on mtdblock2 (i do have mtdblock0 and mtdblock1). No swap partition mounted.
Could any of you kindly advise ? have I done something wrong ? Is this procedure... inadvisable ?
sry for OT.. but which batt do you have?
daedric said:
Hello...
Due to the corruption of the Data partition, i've installed android with System on NAND, data on SD Partition. Now, this leaves a few megs of space on NAND unused.
I've used atools, configured as i thought it would work:
Yet upon install and boot, i find out the System is on mtdblock2 (i do have mtdblock0 and mtdblock1). No swap partition mounted.
Could any of you kindly advise ? have I done something wrong ? Is this procedure... inadvisable ?
Click to expand...
Click to collapse
I dunno why that wont work. If I were you I would just use Sys on nand, and then put data on an ext2.img and then swap on a swap partition of the SD card.
Michga said:
sry for OT.. but which batt do you have?
Click to expand...
Click to collapse
2800 mAh. Cameron Sino.
aceoyame said:
I dunno why that wont work. If I were you I would just use Sys on nand, and then put data on an ext2.img and then swap on a swap partition of the SD card.
Click to expand...
Click to collapse
And all that NAND waisting ? Why not use it as swap... its faster than any SD you put there... We're already slowed down by having DATA and Dalvik Cache on SD...
how about this ;
/system and /data on Nand.
/data/app and /data/app-private on sd ext partition (symlink)(a2sd)
reduce the wasting space.
vellowax said:
how about this ;
/system and /data on Nand.
/data/app and /data/app-private on sd ext partition (symlink)(a2sd)
reduce the wasting space.
Click to expand...
Click to collapse
Shared preferences would still be on data.... dalvik would still be on data...
Data... would still corrupt.
I referred WASTED space, by having Data on SD (being it in a partition or a img), and all that NAND... empty... unused.
Why not repartition the NAND. I would have it then be 100% DATA and then nand and swap on SD. I just don't think we have swap working with the nand yet.
aceoyame said:
Why not repartition the NAND. I would have it then be 100% DATA and then nand and swap on SD. I just don't think we have swap working with the nand yet.
Click to expand...
Click to collapse
You sentence makes no sense. 100% dATA and NAND AND SWAP on SD ?
as for the last sentence... NAND... is a block device... we can write to it with DD no ? we can format a block device, as we see fit.
What you can argue... is that NAND was not meant/planed... for highly changing and volitile... SWAP drive.
I meant with the slider in a tools. Like for instance, I have mine set to 100% system right now with the build I am testing. I am saying it almost sounds like you want as little as possible in system with as much as possible in data. That is why I suggested sys in sd. That way once you boot everything else that you want to run is on nand in /data. The only reason I am saying swap my not work on nand is just due to the way things are mounted on our kaiser. We are not using a traditional way to mount our file systems. They get mounted through a script as it is right now.
aceoyame said:
I meant with the slider in a tools. Like for instance, I have mine set to 100% system right now with the build I am testing. I am saying it almost sounds like you want as little as possible in system with as much as possible in data. That is why I suggested sys in sd. That way once you boot everything else that you want to run is on nand in /data. The only reason I am saying swap my not work on nand is just due to the way things are mounted on our kaiser. We are not using a traditional way to mount our file systems. They get mounted through a script as it is right now.
Click to expand...
Click to collapse
Linux boots with a complex list of scripts. look at conf.d in any major distro...
or perhaps sysconfig... doesn't matter. We can mount the filesystems from a script, or form a script parsing /etc/fstab and running the appropriated mount.fs_here to mount it.
I understand what you say, but what HAS me more confused... is that i said Atools SYS on NAND partition 2, SWAP on partition 3.
I got system on mtdblockp2, there was p1 and p0 for reasons... i don't know.
Now, let me get this straight, to clear doubts.
We can only have, as of yet, RO filesystems on NAND, or filesystems i don't care what they contain.
Data.. is mounted RW, frequently altered. It would be obvious to have it on NAND, for speed, but to to the data corruption issue, we must have it on SD.
We can have System on NAND, its mounted RO, very rarely changed... so it SHOULD be safe. And we can have SWAP there too, i really don't care its condition after a reboot/crash
In another way of thinking... perhaps the Kernel devs can enlighten me here.
for the MicroSD card, i have in /dev/block/
mmcblk0 ; mmcblk0p1 ; mmcblk0p2 ; mmcblk0p3
but for mtd... i only get mtdblock0 ; mtdblock1 ; mtdblock2. Where's the "mother device" ? When we plug a usb card to a linux system, we get a perhaps, /dev/sdc. each partition will be sdc1, sdc2, sdc3 and so on.
Now, for the NAND, mtdblock... i don't get a mother device (don't know better term). I can fdisk -l the microsd, but not the nand...
daedric said:
Linux boots with a complex list of scripts. look at conf.d in any major distro...
or perhaps sysconfig... doesn't matter. We can mount the filesystems from a script, or form a script parsing /etc/fstab and running the appropriated mount.fs_here to mount it.
I understand what you say, but what HAS me more confused... is that i said Atools SYS on NAND partition 2, SWAP on partition 3.
I got system on mtdblockp2, there was p1 and p0 for reasons... i don't know.
Now, let me get this straight, to clear doubts.
We can only have, as of yet, RO filesystems on NAND, or filesystems i don't care what they contain.
Data.. is mounted RW, frequently altered. It would be obvious to have it on NAND, for speed, but to to the data corruption issue, we must have it on SD.
We can have System on NAND, its mounted RO, very rarely changed... so it SHOULD be safe. And we can have SWAP there too, i really don't care its condition after a reboot/crash
In another way of thinking... perhaps the Kernel devs can enlighten me here.
for the MicroSD card, i have in /dev/block/
mmcblk0 ; mmcblk0p1 ; mmcblk0p2 ; mmcblk0p3
but for mtd... i only get mtdblock0 ; mtdblock1 ; mtdblock2. Where's the "mother device" ? When we plug a usb card to a linux system, we get a perhaps, /dev/sdc. each partition will be sdc1, sdc2, sdc3 and so on.
Now, for the NAND, mtdblock... i don't get a mother device (don't know better term). I can fdisk -l the microsd, but not the nand...
Click to expand...
Click to collapse
Hm, not sure how you have yours setup, but I have mtdblock0-3 under /dev/block, and even have mtd0(ro)-3(ro) under /dev/mtd... Did you leave the Alter system and data checked? Mine's at the default 101MB for /system and rest for /data, as I can't change mine anyways, as it can't mount mtdblock3 cause the device cannot be found for some odd reason.
Basically here is what I'm currently doing with my 2.6.32 kernel with both system and data on NAND. I install apps and odex every single app in /data/app partition (this enables me to remove dalvik-cache on /data partition). Then I use Ubuntu and open my androidinstall.tgz and move all the apps that I odexed to /system/app fill up my partition to about 99 meg (Warning: not all /data/apps are functional in /system/app folder). Then I reinstall androidinstall.tgz with a full system partition. What ever app that can't be installed in system/app, I install again in my /data/app and odex it. This will fill up your system folder and you will have a lot of space in /data folder. I currently have 60mb free in my /data partition which is great, no errors for 4 days (1st day reboot, 2nd day battery pull, 3rd and fourth day running continously).
So basically, I maximize the use of the system partition by adding odexed apps, then remaining apps in data partition and odex it. BTW, the rom I'm using is odexed so I have no need of dalvik-cache thus freeing up a lot of data partition space
daedric said:
for the MicroSD card, i have in /dev/block/
mmcblk0 ; mmcblk0p1 ; mmcblk0p2 ; mmcblk0p3
but for mtd... i only get mtdblock0 ; mtdblock1 ; mtdblock2. Where's the "mother device" ? When we plug a usb card to a linux system, we get a perhaps, /dev/sdc. each partition will be sdc1, sdc2, sdc3 and so on.
Now, for the NAND, mtdblock... i don't get a mother device (don't know better term). I can fdisk -l the microsd, but not the nand...
Click to expand...
Click to collapse
Bad Naming? or is this like the diff between a primary and extended partition?
the mtd hasn't a "mother device" so there is this type of naming
Krazy-Killa said:
Hm, not sure how you have yours setup, but I have mtdblock0-3 under /dev/block, and even have mtd0(ro)-3(ro) under /dev/mtd... Did you leave the Alter system and data checked? Mine's at the default 101MB for /system and rest for /data, as I can't change mine anyways, as it can't mount mtdblock3 cause the device cannot be found for some odd reason.
Click to expand...
Click to collapse
I did Alter the system and data partition. Look at the screenshot in 1st post.
clemsyn said:
Basically here is what I'm currently doing with my 2.6.32 kernel with both system and data on NAND. I install apps and odex every single app in /data/app partition (this enables me to remove dalvik-cache on /data partition). Then I use Ubuntu and open my androidinstall.tgz and move all the apps that I odexed to /system/app fill up my partition to about 99 meg (Warning: not all /data/apps are functional in /system/app folder). Then I reinstall androidinstall.tgz with a full system partition. What ever app that can't be installed in system/app, I install again in my /data/app and odex it. This will fill up your system folder and you will have a lot of space in /data folder. I currently have 60mb free in my /data partition which is great, no errors for 4 days (1st day reboot, 2nd day battery pull, 3rd and fourth day running continously).
So basically, I maximize the use of the system partition by adding odexed apps, then remaining apps in data partition and odex it. BTW, the rom I'm using is odexed so I have no need of dalvik-cache thus freeing up a lot of data partition space
Click to expand...
Click to collapse
This, this is one of the things everyone should do. On every release. 'course that's my opinion. But its pointless to the question.
l1q1d said:
the mtd hasn't a "mother device" so there is this type of naming
Click to expand...
Click to collapse
Is there a chance, that the partition is being created correctly, but the dev or block/dev simply not being created ??
update: indeed there is. I removed the Alter tables check, and now i have mtdblock0 through 3. System is mtdblock2.
I would assume, usually data would be on mtdblock3. yet 'swapon /dev/block/mtdblock3' gives me 'Input/Output Error'
you need to mkswap to the nand partition but it isn't a good idea because the nand has a limited number of read/write cycle
l1q1d said:
you need to mkswap to the nand partition but it isn't a good idea because the nand has a limited number of read/write cycle
Click to expand...
Click to collapse
every device has a read/write limit. NAND is specially LOW.
What i did:
mkdir /nand3
touch /dev/loop0
mount --bind /dev/block/loop0 /dev/loop0
mount /dev/block/mtdblock3 /nand3
dd if=/dev/zero of=/nand3/swapfile.img bs=1M count=100
losetup /dev/loop0 /nand3/swapfile.imf
mount -t swap /dev/loop0 swap
I got my swap on nand... i still have to deal with yaffs, but that might have its advantages, in reducing writes do the nand (against a pure swap partition)
After that i edited /system/bin/userinit.sh to reflect those commands. Should be enough for now...
daedric said:
Data... would still corrupt.
Click to expand...
Click to collapse
shutdown.d ?
vellowax said:
shutdown.d ?
Click to expand...
Click to collapse
Please explain.
daedric said:
Please explain.
Click to expand...
Click to collapse
Sorry mate, don't take it too serious. its just our impression for unclean shutdown ( if we have init.d, why don't we create shutdown.d )
But, why /system/bin/shutdown not really done its job.
s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey,
I have ext4 with 1024MB but i still get the "insufficient memory" message
I found that my a2sd partition is tiny!!! so what are the correct sizes if i want ext4 and good a2sd size?
i set partition 1 >> 1024 with ext4, and then partition 2 >> SKIP, then swap >> skip (Using 4EXT recovery to partition a 16 Gigs Class 10 MicroSD)
For starters, don't use the xscript on stock.
Sent from my HTC Runnymede using XDA Premium App
Partition should be the free space, why did you skip it? Or do I get something wrong?
Sent from dGB with Transparent XDA App
cronus101 said:
For starters, don't use the xscript on stock.
Sent from my HTC Runnymede using XDA Premium App
Click to expand...
Click to collapse
I didn't know that -______- Damn...
How did you know i did O_O
MatDrOiD said:
Partition should be the free space, why did you skip it? Or do I get something wrong?
Sent from dGB with Transparent XDA App
Click to expand...
Click to collapse
I used 1024 for ext4
so i didn't know why i have to use the 2nd partition and just skipped it :/
Apparently i have to re-partition and re-flash.... Oh man...
You need to have an ext4 partition with at least 1024 MB and the rest FAT32.
Sent from dGB with Transparent XDA App
MatDrOiD said:
You need to have an ext4 partition with at least 1024 MB and the rest FAT32.
Sent from dGB with Transparent XDA App
Click to expand...
Click to collapse
That's what i did!
What am i doing wrong...
That was just a pain.... i switched to the beloved CyanogenMod... i just don't have time for these hackey stuff to try and make them work...
Now i have re-partitioned to :
1024 ext4 SD-EXT1
1024 ext4 SD-EXT2
and the rest 13 Gigs Fat32... i'll see how this works...
Why do you have two ext4 partitions. One should be absolutely enough.
Sent from dGB with Transparent XDA App
That amarullz script is switched between /data and /sdext.
And store the application on /sdext and keep the dalvik cache on /data.
If you see the picture that your a2sd partition is low. That is actually your /data partition is low.
So you can't install any other app.
And for this script is better to use cm7r2 HBOOT that have bigger /data partition.
This script only need one ext4 partition.
2 ext partition is for ownhere data2ext script.
Sent from my HTC Runnymede using xda premium
hi!
last few days i had big problems with my desire. i had miui but after snowboarding it just stopped working. so i decided to install ICS 4.0.3. after big problems with s-off and install of clockworkmod recovery touch today I succeeded. with big smile on my face i rebooted in recovery and made sd card partition. 1st 2048mb and 2nd (first attempt) 0mb and when it rebooted I opened terminal and typed this
su
a2sd install
then i get something roughly as this in terminal
using /dev/block/mmcblk0p2 for block device
setting flag a2sd
would you also like to move dalvik-cache? (y/n) y
setting flag dc2sd
delvik-cache will be moved to /sd-ext on reboot
would you also like to move appdata (y/n) y
setting flag ad2sd
app data will be moved to /sd-ext on reboot
yout apps will be moved to /sd-ext on reboot
reboot
Click to expand...
Click to collapse
after that in titanium backup i have internal 154MB and 152 MB free
sd card (a2sd) 1.91GB and 1.79 GB free
but when i go to install first program from google play i get " insufficient storage available "
latter i tried with 1st partition 2048mb and 2nd 512mb but i get the same resoult
my last attempt was to when i'm in terminal to do this:
using /dev/block/mmcblk0p2 for block device
setting flag a2sd
would you also like to move dalvik-cache? (y/n) n
would you also like to move appdata (y/n) y
setting flag ad2sd
app data will be moved to /sd-ext on reboot
yout apps will be moved to /sd-ext on reboot
reboot
Click to expand...
Click to collapse
then i think i can install apps but internal memory is something like 154MB and 70+ MB free
so i went to terminal again and typed
su
a2sd cachesd
but i just get using /dev/block/mmcblk0p2 for block device and nothing happeneds.
what am I doing wrong?
please helo cos this is 4th day that i'm struggling with desire to make everything normal again and it's really starting to get on my nerves.
tnx.
Code:
SOLVED - had to partition ext3 to ext4
I've had BusyBox Free on my Nexus for many months... only there to keep me on the latest version. Well, yesterday it told me about 1.20.2 so I let it install that but it was a big mistake.
The memory is locked at read only now. I can even see last files written to it were...
busybox-stericson
toolbox-stericson
It crashes if I don't quickly put it in airplane mode, for example. I can push and delete files via adb, but that's only fake because once the buffer fills with backlogged changes, the phone crashes. In fastboot, erasing userdata, etc. doesn't really erase anything. Locking/Relocking the bootloader doesn't reallly take effect either, and neither does reflashing recovery. Formatting the internal memory doesn't have an effect, and while restoring a recovery backup goes through the motions, it complains at the end about the memory being read only.
I wrote the BusyBox Free developer an email last night but didn't get a response yet.
I don't know how this is possible.
BusyBox doesn't change anything to read only, except for /system, which is suppose to be read only anyways.
Besides this point, anything Busybox would have done, in regards to remounting partitions to rw, ro, or whatever a reboot would reset these to their defaults.
I suspect something else is going on. Maybe an applet or something of the like has been replaced that is causing this issue, but I have never heard of my installer causing an issue like this.
also, those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.
Stericson said:
... those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.
Click to expand...
Click to collapse
The Galaxy Nexus lumps all its memory in one 32GB pool (internal with SD) which is normally great compared to all my other Android devices. Regardless, writes to any of the filesystems don't appear to get committed from a buffer.
Anyways, thanks for the response. I'm gonna' have to do some more research and hope there's nothing wrong at the hardware layer (eg. write-enable/disable trace on chip). Physically, my phone is pampered and in mint condition.
I would say that's pretty dang good response time from the dev, and on the forum, even.
:good:
consultant.ben said:
I would say that's pretty dang good response time from the dev, and on the forum, even.
Click to expand...
Click to collapse
I agree, Ben. I have to remember this is more of a volunteer effort here, unlike at work where I'm a product engineer with certain response time criteria.
Hmmm, even with the memory being all internal I don't change any of the write permissions on the external storage...
Did you replace any applets?
Did you use smart install or normal install?
Maybe some applet got replaced that otherwise shouldnt have been...
If you run a logcat, do you notice any weird errors....if so, what are they stating?
Also, when your phone crashes, can you give us the actual logcat of the crash?
Also, I try to respond as quick as possible, but I have so little time to dedicate to my own personal applications nowadays
I didn't replace any applets, and have never used your applet manager. Also, normally I wait for your smart install to scan, but I remember I did something abnormal that day and impatiently hit install (ie. normal install) while it was doing its smart scan. It reported successfully installing 1.20.2 though.
Per your request... adb logcat -d -v time > logfile.txt
I put that file on my website at http://ErichMoraga.com/logcat.txt
I pulled the SIM card so I wouldn't have to put it into airplane mode, and got the logcat once the OS loaded after a crash. At first I thought this part was curious...
07-08 12:18:01.234 I/SystemServer( 186): Mount Service
07-08 12:18:01.234 D/MountService( 186): got storage path: /mnt/sdcard description: Internal Storage primary: true removable: false emulated: true mtpReserve: 100 allowMassStorage: false maxFileSize: 0
07-08 12:18:01.234 D/MountService( 186): using emulated external storage
But then I searched on the Internet and noticed other people had that too. This logcat didn't appear to catch the actual crash (I don't see how it could if I'm having a read only memory problem).
I understand we both don't have much free time, being technical people. Normally I'm analyzing logs for customers, so it's frustrating 'shooting my own device. I do appreciate any insight anyone has, and am concerned this could happen to other people too.
Well, I bought myself another Nexus so I'd have something to keep me going. I also disassembled my faulty one to inspect the module with the 32GB Sandisk memory, but couldn't see anything wrong with it. If I can find a replacement, I can easily swap modules I suppose...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
-Snags
Snags697 said:
What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
Click to expand...
Click to collapse
Thanks for the response, Snags. I uploaded output to that here...
http://ErichMoraga.com/color.txt
I haven't scoured that for yet for missing programs, dead links, etc. Mount seems to be there...
lrwxrwxrwx 1 0 0 19 Jul 5 2012 mount -> /system/bin/busybox
Since there's so much BusyBox redirection going on there, it still supports my theory that the BusyBox installation was the root cause of the read only memory issue.
I'm sure there is a way to debug the Nexus in real-time. I'll have to find out the command for that (ie. dump threads, etc. as they occur to my PC via USB). A reliable way to crash the phone is to wait about 5 seconds into the scan at... Settings > Storage
I also noticed other people have similar problems not being able to write any of their memory...
http://forum.xda-developers.com/showthread.php?t=1756111
I'm a Linux guy and just learning Android. My first impression would be to double-check with a known writable directory. If you can't write in the /data/local directory (adb push anyfile /data/local/), check the mount status of everything: adb shell toolbox mount should do that with the native toolbox instead of busybox. Each entry should list either "rw" or "ro" amidst the gibberish. If /data is "ro", remounting from a root prompt (toolbox mount -o remount,rw ... /data) (Note: no space before rw, and replace ... with whatever was listed before /data in the list of mounted filesystems above) may give you write access to /data/local.
Then again, I think this is pointless, because if fastboot can't write to the internal SD (like the link you posted), something hardware-related or partition-related must be going on. Maybe the partition table got fried. Fastboot is only willing to write whole partitions that are genuine, I think. So if the partitions are messed up, it may prevent fastboot from doing anything. To see the partition table, you'd need root (there's a hole in the bucket...) and from a root prompt, run: parted /dev/block/mmcblk0 then from the (parted) prompt, type print. Quit or exit should get you out of there. Compare the output to "Need a copy of a stock GSM Nexus partition table" (Google it, I can't post links yet).
Of course, if you don't have root, this all doesn't help.
-Snags
Well, Snags, let's just say great minds think alike :good:
Also, I have root, and bought another Nexus that should arrive this week to play with that I'll flash with a nandroid backup from a couple weeks ago. The mount output looked fine...
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
none on /acct type cgroup (rw,noatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,noatime,cpu)
/dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system type ext4 (rw,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs on /factory type ext4 (ro,noatime,barrier=1,data=ordered,noauto_da_alloc)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /mnt/sdcard type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/sbin # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 31.9GB 30.7GB ext4 userdata
I've also included some other stuff...
</etc/fstab>
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 rw
</etc/recovery.fstab>
# mount point fstype device
# there is no actual sdcard in this thing...
#/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system
/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
/data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc
/boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
/sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl
/xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader
/radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio
Bear in mind I have a Verizon CDMA phone, so the partition table is different than GSM's (32GB vs. 16GB). Oddly enough, I couldn't locate the CDMA version online. Here is one of the the GSM versions I found...
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
The only differences were the specification of ext4 in mine under 11 & 12, as well as the size in 12. I also noticed Koush documented the recovery.fstab to have "auto" for /data instead of ext4 like mine. Worst case, I can run some comparisons between my 2 phones when the new one arrives. It won't be hard to push the correct changes if found.
Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.
If you don't mind the fact that it'll result in a full wipe including internal storage, you could try:
Open up any Google official ROM and extract the userdata img file.
Go into fastboot and flash that img. Reboot. Let it go through the full reboot process.
If something went wonky with how the partition is configured, that should set it straight. If it's a hardware problem you are still boned.
ErichMoraga said:
Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.
Click to expand...
Click to collapse
So yes, it seems i have a pretty similar problem with mine : nothing can be written anymore on the internal memory, whatever i can try : in recovery, in windows or with a file manager in the phone. Plus it is in bootloops constantly.
But i haven't touch at Busybox at all ; i mean it comes with Trinity kernel i use, so i don't bother to install or update it....Problem appeared just after this procedure :
- Downloaded a new Rom
- Rebooted to recoverry (TWRP)
- Made a Nand
- Wiped cache/dalvik/data
-Flashed new Rom/ gapps
-Rebooted...in the old configuration, just as if i've done nothing ! O_O......then i knew something was getting really bad....
As i said in the other thread (http://forum.xda-developers.com/showthread.php?t=1756334&page=2) i've just sent it to Samsung for repair under warranty...so i'll tell you in about 2/3 weeks when they'll return it, if they accept it, becaused even if I relocked the bootloader, it is still rooted.....but as it is surely a hardware problem, the warranty should work.
Anyway, i read somewhere that people had experienced this kind of issue after a "bad nandroid", or EMMC (?)....i'm not sure of what it means though....
Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.
ErichMoraga said:
Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.
Click to expand...
Click to collapse
Yeah, that's not surprising me...let's them repair their **** after all....
Samsung was pretty quick with the repair. There was a status update yesterday...
"The unit has left the technician. SOLUTION: Replaced Component - PRL Updated - S/W Updated - Passed"
I assume they replaced the module that holds the SIM slot and SANDISK chip. I'm sure I'll receive the phone soon, although I've been using a backup i515 I bought on eBay earlier.
I hesitate to even say anything since I got reamed out once already, but it's getting ridiculous now. I JUST finished installing and using Link2SD, and before I rebooted I saw my usable space had gone up from 85.76 MB's to like 1.20 GB's, so I thought I was making some progress in the bigger picture. Well, I just rebooted and have the "storage space running out" notification showing. I did not add anything, and I thought I actually seemed to move some things. I cannot understand (first of all) how after moving something off, all of a sudden I have NO space left on the internal. But, the bigger question is, how can it be remotely possible that there is anything that could be using the 8 or 9 GB's of alleged remaining space? I don't fully get what Link2SD does, but even if the using of it only "virtually" moved the apps, how the flock can that process have INCREASED the data on the internal? There's something wrong. There's like NO data/files/media on it that I put on. Does anybody understand this mess and how to resolve it. When I was *****ing and moaning the other day it was kindof theoretical, now it's like I can't even install any apps. Any guidance is greatly appreciated.
EDIT: OK, can someone explain what legacy and emulated mean in simple terms? Nothing specific to the S4 when Googling. I just went in to clockworkmod in sdcard, deleted the "0" folder and now I have 8.61 GB's free. Everything seems to work??? Very strange.
Not so sure on the legacy/emulated setup of the ExtSD on the S4 but what link2SD is doing is what Windows would call a "symbolic link". Link2SD is using the same mechanic (it's a single line unix command) and what it does is when the OS is looking on the "internal sd" for an apk, the OS will be forwarded to the directory on the External SD. Just imagine it like a shortcut that can forward the OS to look in a specific location.
Either way, the following thread shows a way to move extremely large apps to SD and works properly on the S4 (just did it last night w/ no problem). The FolderMount application is only required when a game uses "additional data" downloads in addition to the apk.
http://forum.xda-developers.com/showthread.php?t=2285221
Emulated/legacy, as my limited understanding, are for applications that haven't been updated to JB mount points. Running a 'mount' command shows that the 0 folder you deleted was pointing to /data/media, aka your internal 'sdcard'. Probably don't want to delete that in the future.
If you're using CWM...have you done backups? I had some hiding in a random CWM folder mounted as (if I remember correctly) /storage/emulated/ClockworkMod/<stuff>.
thehelios said:
Not so sure on the legacy/emulated setup of the ExtSD on the S4 but what link2SD is doing is what Windows would call a "symbolic link". Link2SD is using the same mechanic (it's a single line unix command) and what it does is when the OS is looking on the "internal sd" for an apk, the OS will be forwarded to the directory on the External SD. Just imagine it like a shortcut that can forward the OS to look in a specific location.
Either way, the following thread shows a way to move extremely large apps to SD and works properly on the S4 (just did it last night w/ no problem). The FolderMount application is only required when a game uses "additional data" downloads in addition to the apk.
http://forum.xda-developers.com/showthread.php?t=2285221
Click to expand...
Click to collapse
Cool. I'm now up to 8.83 GB's after doing what you suggested. I can definitely live with that, along with a 32 GB external. You may have kept me from bringing it back. I had 2 days left, I think this is all do-able now.
Toleraen said:
Emulated/legacy, as my limited understanding, are for applications that haven't been updated to JB mount points. Running a 'mount' command shows that the 0 folder you deleted was pointing to /data/media, aka your internal 'sdcard'. Probably don't want to delete that in the future.
If you're using CWM...have you done backups? I had some hiding in a random CWM folder mounted as (if I remember correctly) /storage/emulated/ClockworkMod/<stuff>.
Click to expand...
Click to collapse
Exactly. Last night I was fishing around and somehow found what appeared to be a double backup on the CWM folder on the internal card. I got rid of it and gained quite a bit of space.
wbexpress said:
Exactly. Last night I was fishing around and somehow found what appeared to be a double backup on the CWM folder on the internal card. I got rid of it and gained quite a bit of space.
Click to expand...
Click to collapse
Under cwm, go to backups and restore, and select clear unused backup data. That's gets rid of the stuff you no longer need.
Sent from my SGH-M919 using Tapatalk 4 Beta
---------- Post added at 02:11 AM ---------- Previous post was at 02:05 AM ----------
Btw, i found this. Looks VERY promising. Seems to be right up your ally too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems android keeps allocating memory when it's not being used. For some reason it's showing up that way.
Any idea?
Sent from my SGH-M919 using Tapatalk 4 Beta
joshua.justice said:
It seems android keeps allocating memory when it's not being used. For some reason it's showing up that way.
Any idea?
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thats how it is on my S3 running CM10.1 too. Im guessing its needed for something.
elesbb said:
Thats how it is on my S3 running CM10.1 too. Im guessing its needed for something.
Click to expand...
Click to collapse
Mine did the same thing on stock.
I think it's an issue with the s 4.
elesbb said:
Under cwm, go to backups and restore, and select clear unused backup data. That's gets rid of the stuff you no longer need.
Sent from my SGH-M919 using Tapatalk 4 Beta
---------- Post added at 02:11 AM ---------- Previous post was at 02:05 AM ----------
Btw, i found this. Looks VERY promising. Seems to be right up your ally too.
Click to expand...
Click to collapse
Cool. Every little bit helps. Thanks.
joshua.justice said:
It seems android keeps allocating memory when it's not being used. For some reason it's showing up that way.
Any idea?
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Most of those, the 910Mib portions at least, are likely pointing to the same mount point. It's only counting the 'main' mount point toward your storage allocation.
edit: Doing a df shows all of those are just tmpfs mounts (ram disks), so they're not counting against any storage at all, unless you're concerned with memory. No idea if this is what you're asking, I'm just having fun messing around in a terminal
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 910.8M 80.0K 910.7M 0% /dev
tmpfs 910.8M 0 910.8M 0% /mnt/secure
tmpfs 910.8M 0 910.8M 0% /mnt/asec
/dev/block/dm-0 2.0M 72.0K 1.9M 4% /mnt/asec/com.keramidas.TitaniumBackupPro-1
tmpfs 910.8M 0 910.8M 0% /mnt/obb
/dev/block/mmcblk0p26 8.8M 4.1M 4.7M 46% /persdata/absolute
/dev/block/platform/msm_sdcc.1/by-name/system 2.6G 1.5G 1.2G 55% /system
/dev/block/platform/msm_sdcc.1/by-name/userdata 9.7G 6.3G 3.4G 65% /data
/dev/block/platform/msm_sdcc.1/by-name/cache 2.0G 32.4M 2.0G 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/apnhlos 86.0M 8.8M 77.2M 10% /firmware
/dev/block/platform/msm_sdcc.1/by-name/mdm 86.0M 49.5M 36.5M 58% /firmware-mdm
/dev/block/platform/msm_sdcc.1/by-name/efs 13.4M 4.2M 9.2M 31% /efs
/data/container 9.6G 6.3G 3.3G 66% /mnt/shell/container
/data/media 9.6G 6.3G 3.3G 66% /mnt/shell/emulated
tmpfs 910.8M 0 910.8M 0% /storage/emulated
/dev/block/vold/179:33 59.4G 50.3G 9.0G 85% /storage/extSdCard
/data/media 9.6G 6.3G 3.3G 66% /storage/emulated/0
/data/media 9.6G 6.3G 3.3G 66% /storage/emulated/0/Android/obb
/data/media 9.6G 6.3G 3.3G 66% /storage/emulated/legacy
/data/media 9.6G 6.3G 3.3G 66% /storage/emulated/legacy/Android/obb