Project

General

Profile

Issue #1798

After Factory Reset, I only Have 1.96GB

Added by Edgar Jones about 2 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Category:
Website and wiki content
Target version:
Start date:
05/05/2017
Due date:
% Done:

0%

Resolution:
Device:
Galaxy S 2 (I9100)

Description

So I had Replicant 4.2 installed and I had full disk encryption on and had all of my 16GB. I had to do a wipe of the device so I did a factory reset via the recovery (CWM). After that wipe I only have 1.96GB. This isn't what I have left over as some people tell me, this is defiantly in total how much the phone has.

Have I broke it? Can it be fixed. I just got this phone too :((

fixing sdcard0 issue on R6.0.odt (33.8 KB) Jacob Bahn, 06/24/2017 01:14 PM

fixing sdcard0 issue on R6.0.odt (34.3 KB) Jacob Bahn, 06/24/2017 07:58 PM

History

#1 Updated by Edgar Jones about 2 years ago

Oh shite, just realised this isn't the forums. Sorry

#2 Updated by Wolfgang Wiedmeyer about 2 years ago

  • Category set to Recovery
  • Status changed from New to Feedback
  • Assignee set to Edgar Jones

Is this issue still there with Replicant 6.0, specifically with the recovery for Replicant 6.0?
Please follow the installation instructions and check how much storage is displayed then.

#3 Updated by A. S. about 2 years ago

Yes, it's there with the Replicant 6.0 stable release. I used the 6.0 recovery image to perform a factory wipe.

Where during the installation do you mean that we should check available storage?

#4 Updated by Wolfgang Wiedmeyer about 2 years ago

  • Status changed from Feedback to New
  • Target version changed from Replicant 4.2 to Replicant 6.0

#5 Updated by Wolfgang Wiedmeyer about 2 years ago

I meant checking the available storage after installation in the menu. So is this issue the same as the issue reported in the forum? Does the same error happen?
As I already explained there, logs are needed.
I doubt that this issue is specific to Replicant. The same error should also happen with LineageOS/CyanogenMod, unless they have a fix for this in a later version after 13.0 which would be good to know.

#6 Updated by A. S. about 2 years ago

So is this issue the same as the issue reported in the forum? Does the same error happen?

Yes, it's the same issue with the exact same error. Just like Edgar, I've upgraded from an encrypted Replicant 4.2 installation.

The same error should also happen with LineageOS/CyanogenMod unless they have a fix for this in a later version after 13.0 which would be good to know.

OK, so I guess that I should try the following:

1. reinstall Replicant 4.2 and enable encryption;
2. install CyanogenMod/LineageOS 13.

Should the issue remain I will:

3. go through step 1 again
4. install LineageOS 14.

#7 Updated by Wolfgang Wiedmeyer about 2 years ago

  • Assignee changed from Edgar Jones to Wolfgang Wiedmeyer

You could try the following to fix this in Replicant 6.0, either with ADB or with the terminal app on the device.

For ADB, make sure that it's correctly set up and running as root, as explained in the wiki.
Then run this command:

adb shell mkfs.exfat /dev/block/vold/public\:179_11

For the terminal app, you need to enable it first. Make sure root access is enabled. You can enter a root shell by entering su in the terminal app.
Then run this command:

mkfs.exfat /dev/block/vold/public\:179_11

The output should look like this:

mkexfatfs 1.2.3
Creating... done.
Flushing... done.

#8 Updated by Wolfgang Wiedmeyer about 2 years ago

After formatting the storage with this command, a reboot is needed for the changes to take effect.

#9 Updated by A. S. about 2 years ago

Wolfgang, I did what you suggested using the ADB method and it worked. Many thanks!

Under sdcard0 it no longer says "damaged" but "5.28 MB of 11.51 in use." I also tried to take a picture and it worked.

Now, I wonder what I need to do to encrypt this new-won storage because I had already encrypted the device (when I had only 2 GB available) and that seems to be a one-time thing in this OS.

#10 Updated by Jacob Bahn almost 2 years ago

YES - SUCCESS

Thanks for this advice which solved the issue similar to A.S.'.

#11 Updated by Jacob Bahn almost 2 years ago

One problem I often encounter with technical instructions is that I lack the overview of

  • multiple options being presented intertwined, and
  • multiple (partial) instructions being spread over several pages.

I have tried to make a 'total' guide for fixing the 'sdcard0 corrupted on Replicant 6.0' issue, comprising each and all steps (on a Debian-based OS).

Comments and corrections are most appreciated.

#12 Updated by Jacob Bahn almost 2 years ago

It is crucial to give rot access to 'Apps and ADB'. 'ADB only' doesn't work. I imagine it is because the terminal emulator is an app!?

I have edited the 'fixing the sdcard0 issue' guide

#13 Updated by Denis 'GNUtoo' Carikli 3 months ago

  • Category changed from Recovery to Website and wiki content

#14 Updated by Denis 'GNUtoo' Carikli 3 months ago

Do you want wiki editor access to add that a tutorial on how to do that on the wiki?

Denis.

#15 Updated by Denis 'GNUtoo' Carikli 3 months ago

  • Priority changed from High to Normal

Also available in: Atom PDF