After Factory Reset, I only Have 1.96GB
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 :((
#2 Updated by Wolfgang Wiedmeyer almost 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.
#5 Updated by Wolfgang Wiedmeyer almost 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. almost 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 almost 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
The output should look like this:
mkexfatfs 1.2.3 Creating... done. Flushing... done.
#9 Updated by A. S. almost 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.
#11 Updated by Jacob Bahn almost 2 years ago
- File fixing sdcard0 issue on R6.0.odt added
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.