Android OS Forum banner
1 - 20 of 306 Posts

·
Developer
Joined
·
339 Posts
Here are a some fixes that should help with some (most?) of those having
'sdcard' issues (or hoping to avoid them):

The first fix should be applied by everyone. It fixes the fsck_msdos
program. This program is used to check your 'sdcard' for errors before
using it. This program can also correct many of these errors. After
this fix is applied, you should see a notification after booting:

Preparing SD card
Checking for errors.

This notification will last until it is done checking. That will last
around 30 seconds (can vary greatly depending on size of 'sdcard' and
number of files on it, etc.). If this notifcation is replaced with
one that states 'Damaged SD Card', then the fsck_msdos was unable
to correct the errors. Hopefully, with this fix (barring some other
major incident), all of the minor errors on the 'sdcard' will get
fixed before they become major errors that it cannot fix.

The fsck_msdos fix: http://www.mediafire...g52q4zr03c3z1gx
Apply with your favorite recovery software.

NOTE: The fsck_msdos fix should be applied before any of the other fixes.
Also, you should boot at least once after applying the fix to allow
it to check/fix the 'sdcard'.

The other fixes are not true fixes, but work-arounds for the 50+
apps on sdcard issue. One of them allows you to increase the size
of your 'Internal storage' so you do not have to move apps to the
'sdcard'. The other allows you to move these apps back to the
'Internal storage' after you have encountered the 50+ issue.

After the "Preparing SD card" notification goes away, after about
a minute (can vary), do you see the following notification:

Removed SD card
SD card removed. Insert a new one.

If so, that (most likely) means that you have encountered the
50+ issue. To fix it, you will need to move apps back from
the 'sdcard' to the 'Internal storage' (or 'phone').

The next fix/workaround allows you to 'stash' some of the apps
on the 'sdcard' so that the 50+ issue does not come into play.
This will allow you to move apps back from the 'sdcard' without
encountering the "Removed SD card" error while attempting to do so.
Each time you apply this 'fix', it will 'stash' all but 40 of
the apps on the 'sdcard'.

So, apply this fix once. Then move apps back from the 'sdcard' to
the 'phone' (or 'Internal storage'). Note that apps that have been
'stashed' might show with a greyed-out icon with an 'SD Card' symbol
and the letters 'SD' -- do not attempt to move these. After you
have moved the apps from the 'sdcard' back to 'phone' (those that
haven't been 'stashed'), you apply the fix again. Applying the
fix the second time will 'unstash' the remaining apps (remember
that it will not allow more than 40 apps to be 'unstashed') thus
allowing you to move them off the 'sdcard' too.

Get it here: http://www.mediafire...4n3fhag1d33127q
Apply with your favorite recovery software.

The last fix/workaround allows you to increase the size of your
'Internal storage'. This will allow you to store more apps on
your 'Internal storage' and avoid having them on the 'sdcard'.

To check your current 'Internal storage' space, go to
Settings/Storage and note the values under 'Internal Space'.
If the size of the 'Available Space' is not enough to hold
all the apps you are moving back from the 'sdcard' (or apps
that you will install in the near future), you will need
to increase the size of your 'Internal Space'.

You can increase the size of your 'Internal space' (or /data)
in increments of 256MB, 512MB, 1024MB and 2048MB. You apply
these 'fixes' with recovery software (tested with CWM and TWRP),
however, please note the warnings below.

********** PLEASE READ ALL WARNINGS BELOW **********
********** PLEASE READ ALL WARNINGS BELOW **********
data_plus_256mb: http://www.mediafire...gxqjki8s255lwpw

data_plus_512mb: http://www.mediafire...wh83t6urhnf82ad

data_plus_1024mb: http://www.mediafire...zaeh4fd3pjinaga

data_plus_2048mb: http://www.mediafire...xyxdx7xscee6mex
********** PLEASE READ ALL WARNINGS BELOW **********
********** PLEASE READ ALL WARNINGS BELOW **********

WARNINGS:

1) BACKUPS. BACKUPS. BACKUPS. As always, and especially when you
are resizing filesystems, you should have backups. This means
backups of all data (that you would care about losing) on the
Touchpad. These backups should be stored off of the Touchpad.

2) Before attempting to resize your 'Internal space' make sure
you have enough free space on your 'sdcard' to do so. Check
this from Settings/Storage/SD card/Available Space. You should
have enough space plus a very healthy 'safety margin'.
DO NOT ATTEMPT TO TAKE ALL (OR CLOSE) AVAILABLE SPACE FROM SDCARD.

3) Before applying this 'fix', make sure you have plenty of charge
on your battery.

4) Do not reboot, reset or otherwise interrupt the touchpad while
applying this 'fix'.

5) As soon as this 'fix' is complete, use the recovery software's
reboot command to reboot the system. Do not do anything else
in recovery after applying this 'fix'. This 'fix' does things
that recovery software are not designed to do and does not
expect to happen. REBOOT IMMEDIATELY AFTER APPLYING FIX.
 

·
Registered
Joined
·
30 Posts
Excellent to see an alternative method to increase the internal partition size that is far more accessible, kudos for the post. About the fsck_msdos fix: What is the fix changing? Adding/changing command flags, using a different version, etc? Always curious before I apply any changes. Thanks.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #6 ·
Excellent to see an alternative method to increase the internal partition size that is far more accessible, kudos for the post. About the fsck_msdos fix: What is the fix changing? Adding/changing command flags, using a different version, etc? Always curious before I apply any changes. Thanks.
It was found that the original Android version of fsck_msdos did not work well with how webOS wrote data to the filesystem, so it was disabled.
The version that webOS uses (actually dosfsck from dosfstools) was tried, but the version that webOS uses (2.11) is fairly old and it did not port
over to the Android libs very well. The latest version of dosfstools (3.0.12), however, ported over to the Android libs much better. I used that
and modified the command-line parameters and return values so that they are more consistent with what Android expects from fsck_msdos.

This version has been in 'limited testing' for the last week (137 downloads currently) and seems to be working quite well. There were a couple
revisions prior to this one that didn't have the return values/parameters quite right (it can be difficult to uncover these issues until you get it
out to people with filesystem errors to test).
 

·
Registered
Joined
·
37 Posts
First, thanks, JC for some excellent work on cm7 and the fixes you have developed. They are greatly appreciated. I installed your fschk fix and see that the touchpad checks the file system at each boot. That part worked great. I then attempted to install the 1024 system. Space increase but it failed. I am using TWRP 2.0 instead of CWM for flashing and cannot get a screenshot of the failure but this is the output from TWRP:

Preparing tools
Checking media
Media : 10896 =>9872 cm-data : 1536 => 2560
Media_fs tot = 10885 sz=3034 free = 7851
Checking cm-data
Fsck cm-data failed rc=4
>>FAILED
 

·
Developer
Joined
·
339 Posts
First, thanks, JC for some excellent work on cm7 and the fixes you have developed. They are greatly appreciated. I installed your fschk fix and see that the touchpad checks the file system at each boot. That part worked great. I then attempted to install the 1024 system. Space increase but it failed. I am using TWRP 2.0 instead of CWM for flashing and cannot get a screenshot of the failure but this is the output from TWRP:

Preparing tools
Checking media
Media : 10896 =>9872 cm-data : 1536 => 2560
Media_fs tot = 10885 sz=3034 free = 7851
Checking cm-data
Fsck cm-data failed rc=4
>>FAILED
This means it is refusing to do the resize because it found 'uncorrectable errors' on the /data partition.
It will automatically fix errors that are deemed 'always safe to fix'. However, it will not attempt to fix
those that are not 'always safe to fix'.

There is another mode that can be used that will attempt to fix anything it can. Fix, in this sense,
means that the filesystem is in a consistent state. That could mean that some files that are not
in a consistent state are removed. However, if it remains in an inconsistent state, worse could
happen. If you would like to perform this 'more aggressive' filesystem check/fix, you can do
so with this update: http://www.mediafire...vfrwbox4a9i6y2o This update does not try to
resize the filesystem, it only performs the more aggressive check. If you go ahead with it (and
it does not fail), you can then try the resize again.

UPDATE/WARNING:
Since this 'more aggressive' filesystems check/fix may remove files, you may need to recover
from backups after running it.
 

·
Android Beginner
Joined
·
35 Posts
This means it is refusing to do the resize because it found 'uncorrectable errors' on the /data partition. It will automatically fix errors that are deemed 'always safe to fix'. However, it will not attempt to fix those that are not 'always safe to fix'. There is another mode that can be used that will attempt to fix anything it can. Fix, in this sense, means that the filesystem is in a consistent state. That could mean that some files that are not in a consistent state are removed. However, if it remains in an inconsistent state, worse could happen. If you would like to perform this 'more aggressive' filesystem check/fix, you can do so with this update: http://www.mediafire.com/?vfrwbox4a9i6y2o This update does not try to resize the filesystem, it only performs the more aggressive check. If you go ahead with it (and it does not fail), you can then try the resize again.
Tried the methods in the first post & nothing happened. Then I tried this 'more aggressive' filesystem check/fix & it crashed! I couldn't boot at all. Kept restarting at the end of the boot animation. Trying a Nandroid restore now; nothing else seems to make it work.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #11 ·
Tried the methods in the first post & nothing happened. Then I tried this 'more aggressive' filesystem check/fix & it crashed! I couldn't boot at all. Kept restarting at the end of the boot animation. Trying a Nandroid restore now; nothing else seems to make it work.
Humm, 'nothing happened': specifically, which of the 'methods' did you try? they did not install? you received no output at all? Please explain.

The 'more aggressive' filesystems check was suggested to someone receiving a specific error. When did the crash you mention happen?
Did it crash while in recovery installing the 'update' or some other time? As stated above, it is possible that if you run the 'more aggressive'
check that files could be removed. Sounds like you did have some corruption on /data and as part of correcting that, it removed some files.
Also, those files being removed prevented the system from fully booting.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #12 ·
I applied just the first patch for the fixed fsck_msdos from clockworkmod and now when I turn the screen off then back on, it reboots. Nothing appears in logcat either. Any way to reverse your patch? Or a fix for this? Thanks


EDIT: Running alpha 3.5
Sounds like a coincidence to me. Nobody else has mentioned anything like this regarding this fix.

However, if you wish to remove the filesystems check (which I strongly discourage), you can do
so with this: http://www.mediafire.com/?6l5wziw3huqzawu
 

·
Android Beginner
Joined
·
35 Posts
Humm, 'nothing happened': specifically, which of the 'methods' did you try? they did not install? you received no output at all? Please explain.

The 'more aggressive' filesystems check was suggested to someone receiving a specific error. When did the crash you mention happen?
Did it crash while in recovery installing the 'update' or some other time? As stated above, it is possible that if you run the 'more aggressive'
check that files could be removed. Sounds like you did have some corruption on /data and as part of correcting that, it removed some files.
Also, those files being removed prevented the system from fully booting.
Applied the first fix.
Installed. Rebooted. Got the notification: Preparing SD card. Checking for errors. It finished without any errors. I have less than 50 Apps on the SD, so I didn't get the "SD card removed. Insert a new one." error.
Next I tried the last fix/workaround allows you to increase the size of your 'Internal storage'. More specifically, the 2048MB fix.
Rebooted as soon as it was done. But the internal storage did not change. That is what I meant by: Nothing happened.

Next I tried the
'more aggressive' filesystems check/fix. As soon as I rebooted from recovery after applying that; it got stuck in a loop; wouldn't go past the boot animation, it just kept restarting at the boot animation. There was no crash otherwise.
The Nandroid backup-restore fixed it.
 

·
Developer
Joined
·
339 Posts
Applied the first fix.
Installed. Rebooted. Got the notification: Preparing SD card. Checking for errors. It finished without any errors. I have less than 50 Apps on the SD, so I didn't get the "SD card removed. Insert a new one." error.
Next I tried the last fix/workaround allows you to increase the size of your 'Internal storage'. More specifically, the 2048MB fix.
Rebooted as soon as it was done. But the internal storage did not change. That is what I meant by: Nothing happened.

Next I tried the
'more aggressive' filesystems check/fix. As soon as I rebooted from recovery after applying that; it got stuck in a loop; wouldn't go past the boot animation, it just kept restarting at the boot animation. There was no crash otherwise.
The Nandroid backup-restore fixed it.
OK. When you installed the 2048MB update, what output did you get? In particular, did you get ">>> SUCCEEDED <<<"
or ">>> FAILED <<<"? I will assume from what else you mention that it failed due to the errors on /data.
Since those should be corrected now, you could try it again.
 

·
Android Beginner
Joined
·
35 Posts
OK. When you installed the 2048MB update, what output did you get? In particular, did you get ">>> SUCCEEDED <<<"
or ">>> FAILED <<<"? I will assume from what else you mention that it failed due to the errors on /data.
Since those should be corrected now, you could try it again.
No! The output was: >> FAILED <<
Trying it out now again.
Just as a thought; suppose I connect the TouchPad to the computer & use the Windows Disk Checking utility on it; will that correct any of these errors?

EDIT: Yeah, same result as before. After the Nandroid restore; applied the first fix. It says Preparing SD Card: Checking for errors. No further output after that. Reboot into recovery & applied the 2048MB fix, this is the output:

media: 26248 => 24200 cm-data: 1536=>3584
media_fs tot=26242 sz=13585 free=12657
Checking cm-data...
fsck cm-data failed rc=4
>> FAILED <<
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #16 ·
No! The output was: >> FAILED <<
Trying it out now again.
Just as a thought; suppose I connect the TouchPad to the computer & use the Windows Disk Checking utility on it; will that correct any of these errors?

EDIT: Yeah, same result as before. After the Nandroid restore; applied the first fix. It says Preparing SD Card: Checking for errors. No further output after that. Reboot into recovery & applied the 2048MB fix, this is the output:

media: 26248 => 24200 cm-data: 1536=>3584
media_fs tot=26242 sz=13585 free=12657
Checking cm-data...
fsck cm-data failed rc=4
>> FAILED <<
First, I would suggest to NEVER use Windows to check/correct/format/etc. the filesystem on the Touchpad.
Second, this is the /data partition and Windows cannot see it or know what to do with the filesystem on it.

Which recovery are you using?

Before running the update, make sure that /data is not mounted by the recovery:
In CWM, from Mounts and Storage, if it has a "unmount /data", select it.
In TWRP, from Mount, if it has "Unmount Data", select it.

Also, and maybe most important, when you ran the "more aggressive" check,
did it say it SUCCEEDED or FAILED? If it failed, then your /data partition is really
messed up and you probably need to reformat, reinstall and restore first.
 

·
Android Beginner
Joined
·
35 Posts
First, I would suggest to NEVER use Windows to check/correct/format/etc. the filesystem on the Touchpad.
Second, this is the /data partition and Windows cannot see it or know what to do with the filesystem on it.

Which recovery are you using?

Before running the update, make sure that /data is not mounted by the recovery:
In CWM, from Mounts and Storage, if it has a "unmount /data", select it.
In TWRP, from Mount, if it has "Unmount Data", select it.

Also, and maybe most important, when you ran the "more aggressive" check,
did it say it SUCCEEDED or FAILED? If it failed, then your /data partition is really
messed up and you probably need to reformat, reinstall and restore first.
OK. I'm using CWM. Yeah, /data was always unmounted.
When I ran the 'more aggressive' check; the output was: >> FAILED - REBOOT NOW <<

So I formatted /data & tried again. Same results. Keeps failing. Any more suggestions?
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #18 ·
OK. I'm using CWM. Yeah, /data was always unmounted.
When I ran the 'more aggressive' check; the output was: >> FAILED - REBOOT NOW <<

So I formatted /data & tried again. Same results. Keeps failing. Any more suggestions?
Don't know what you used to format, but that should have worked (assuming it does a real format
(actually, mkfs) and not just remove files).

Regardless, using ACMEUninstaller and then re-install should do it.
 

·
Android Beginner
Joined
·
35 Posts
Don't know what you used to format, but that should have worked (assuming it does a real format
(actually, mkfs) and not just remove files).

Regardless, using ACMEUninstaller and then re-install should do it.
I formatted the /data partition through CWM. That didn't work out,
Anyways; uninstalled through ACMEUninstaller & reinstalled. Then applied the fixes. Worked out great! Thanks!
 

·
Gadget Freak
Joined
·
194 Posts
Hi JC,

I just applied the first fsck_msdos fix and it seemed to go well. I saw the notification for preparing SD card, checking for errors and there was no dialog suggesting errors.

I was thinking about doing the fix to expand internal storage, so I went into Settings/Storage to see how much space I had. I set my TP aside while I was reading this thread and my screen timed out as usual after 2 minutes. When I pressed power to bring it back up, I got a FC message. This FC seems to be just in Settings/Storage and is repeatable. I get the FC whether my screen times out, or I press power to shut off the screen. I also tried bringing the screen back up with the "hard" home button and still get the FC.

It's not really a big deal because I'll hardly ever be in the storage screen but I figured I would let you know. Thanks.

Btw, I cleared data in settings but the issue still persists.

Edit: I'm not so sure that this wasn't already an issue with 3.5, maybe just a coincidence that I happened to see it after installing the fix???

Mike T
 
1 - 20 of 306 Posts
Top