Issue #1798: After Factory Reset, I only Have 1.96GB - Replicant

Actions

Copy link

Issue #1798

open

After Factory Reset, I only Have 1.96GB

Added by Edgar Jones almost 7 years ago. Updated about 3 years ago.

Status:

New

Priority:

Normal

Assignee:

Wolfgang Wiedmeyer

Category:

Website and wiki content

Target version:

Replicant 6.0

Start date:

05/05/2017

Due date:

% Done:

Estimated time:

Resolution:

Device:

Galaxy S 2 (I9100)

Grant:

Type of work:

Unknown, Wiki editions

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 :((

Files

Download all files

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

Actions

Copy link

Updated by Edgar Jones almost 7 years ago

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

Actions

Copy link

Updated by Wolfgang Wiedmeyer almost 7 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.

Actions

Copy link

Updated by A. S. almost 7 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?

Actions

Copy link

Updated by Wolfgang Wiedmeyer almost 7 years ago

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

Actions

Copy link

Updated by Wolfgang Wiedmeyer almost 7 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.

Actions

Copy link

Updated by A. S. almost 7 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.

Actions

Copy link

Updated by Wolfgang Wiedmeyer almost 7 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.

Actions

Copy link

Updated by Wolfgang Wiedmeyer almost 7 years ago

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

Actions

Copy link

Updated by A. S. almost 7 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.

Actions

Copy link

#10