Hey guys, I have one quick question here.
Today I updated my Vanilla RB from 2.8 - > 2.9. All went ok until I updated DorimanX from 7.0 -> 7.1.
Now I'm unable to get past the boot animation.
Normally I would just wipe/factory reset and install a fresh rom. But this time I don't have a backup of my recent appdata.
I am nearly at the point of wiping anyway but then I thought if I could format /system or /data without harming my apps and appdata?
TL;DR: Does formatting /system or /data affect application data?
SynGates said:
Hey guys, I have one quick question here.
Today I updated my Vanilla RB from 2.8 - > 2.9. All went ok until I updated DorimanX from 7.0 -> 7.1.
Now I'm unable to get past the boot animation.
Normally I would just wipe/factory reset and install a fresh rom. But this time I don't have a backup of my recent appdata.
I am nearly at the point of wiping anyway but then I thought if I could format /system or /data without harming my apps and appdata?
TL;DR: Does formatting /system or /data affect application data?
Click to expand...
Click to collapse
1. /system does not have anything to do with your data, so formatting it wont affect your data. However, if you format /system, then you have to flash a ROM, hence, your device wont boot.
2. /data contains all your application data, settings, messages etc. formatting it will sure delete the same.
I'll advise you to format /system and flash ROM again. Your data will be intact and your device should boot now.
yesyes that was my intention; to format /system and flash the ROM again.
Thank you
edit: not working, guess I'll just wipe
Related
On a fresh AOKP installation (r31) I performed a restart then the tablet freezes during boot animation. Tried to reboot it multiple times - same result. I wanted to wipe everything and restart but I cannot format /data partition in recovery: it will stay on "Formatting /data ..." for 2-3 minutes and then will reboot :-(
Any idea?
I suspect something in the data partition is corrupted, may be the partition table. Is there a chance to re-create the partition table?
Thanks.
Problem solved:
Using Odin I flashed the stock recovery then wipe data/factory reset.
Flashed back CWM 4.0.0.4, performed /data format
Flashed CWM 5.5.0.4 installed rom, rebooted, wipe data, format data, format system, adb push aokp rom, flashed AOKP. I lost my sdcard data but now the system is working.
I think we can close this topic.
So after years of flashing roms, installing apps, saving junk to my phone I think it is time to completely wipe it. I've searched and come across a few threads but I want to look at some of the CWM Mounts and storage options to be sure. Here is one I came across:
http://forum.xda-developers.com/galaxy-s2/general/ref-cwm-clockworkmode-menu-options-t1542857
If I wanted to do a compete wipe including all internal SD data, but not lose Root, I would do the following???
wipe data / factory reset
wipe cache partition
wipe dallvik cache
format /system
format /cache
format /data
format /preload (unsure about this one, can't find info)
format /storage/sdcard0
install rom then from my ext sdcard1
install gapps then from my ext sdcard1
reboot into a clean phone and start installing stuff again.
That should be enough correct? I'm not sure where CWM Recovery lives but I would assume that would be on the /boot partition and that is the one section that I don't want to format, correct? I'm also not sure of where the modem is set/installed and would that need to be reinstalled again?
With this device, recovery lives with the kernel in the boot partition. Everytime you install a kernel, a fresh image is installed to the partition.
I'm not sure what your actual goal is, but the process you've outlined process is very redundant.
factory reset wipes /data & /cache (which includes dalvik-cache)
A factory reset plus manually wiping /system (and /preload if using samsung-based firmware) promises a clean installation of ANYTHING.
jackal2001 said:
[...]
If I wanted to do a compete wipe including all internal SD data, but not lose Root, I would do the following???
wipe data / factory reset
wipe cache partition
wipe dallvik cache
format /system
format /cache
format /data
format /preload (unsure about this one, can't find info)
format /storage/sdcard0
install rom then from my ext sdcard1
install gapps then from my ext sdcard1
reboot into a clean phone and start installing stuff again.
That should be enough correct? I'm not sure where CWM Recovery lives but I would assume that would be on the /boot partition and that is the one section that I don't want to format, correct? I'm also not sure of where the modem is set/installed and would that need to be reinstalled again?
Click to expand...
Click to collapse
I want to have a fresh install. Basically wipe everything including whatever junk is installed on the SD card. Like a new phone pulled out of the box. I'm sure there is tons of junk on the SD card due to apps being installed/uninstalled over the years.
Yes I understand some of the options may be redundant, but it only takes a second.
So as long as I don't "format /boot" you saying that should be OK?
If you prefer to take the extra steps, then I don't see any harm in your procedure.
It may seem obvious, but make sure you have everything you'll need on that ext-sd card, before you format /system.
mr.cook has some scripts that will format preload, if the option isn't present in your recovery.
jackal2001 said:
I want to have a fresh install. Basically wipe everything including whatever junk is installed on the SD card. Like a new phone pulled out of the box. I'm sure there is tons of junk on the SD card due to apps being installed/uninstalled over the years.
Yes I understand some of the options may be redundant, but it only takes a second.
So as long as I don't "format /boot" you saying that should be OK?
Click to expand...
Click to collapse
A couple weeks ago my carrier, Ringplus, went out of business, so I decided to switch to Tello. I couldn't do this because I couldn't do a carrier reset on Cyanogenmod 13, so I backed up my system with TWRP Backup, restored to stock (XT1526 Surnia Boost 5.0.2), successfully did a carrier reset. Then I tried restoring back to my original Cyanogenmod 13 backup, but it won't work, after the restore is complete, the phone won't boot. When I try rebooting after the restore is done, the phone crashes at the WARNING BOOTLOADER UNLOCKED screen. It can boot into Fastboot or TWRP, but it won't boot into the restored backup.
Is there anything I can do to get my Moto E 2015 Surnia XT1526 phone to boot once I restore from my backup?
regularcarrot said:
A couple weeks ago my carrier, Ringplus, went out of business, so I decided to switch to Tello. I couldn't do this because I couldn't do a carrier reset on Cyanogenmod 13, so I backed up my system with TWRP Backup, restored to stock (XT1526 Surnia Boost 5.0.2), successfully did a carrier reset. Then I tried restoring back to my original Cyanogenmod 13 backup, but it won't work, after the restore is complete, the phone won't boot. When I try rebooting after the restore is done, the phone crashes at the WARNING BOOTLOADER UNLOCKED screen. It can boot into Fastboot or TWRP, but it won't boot into the restored backup.
Is there anything I can do to get my Moto E 2015 Surnia XT1526 phone to boot once I restore from my backup?
Click to expand...
Click to collapse
Wipe system data and try restoring again
Or
Wipe system data and flash any custom ROM
oppodi said:
Wipe system data and try restoring again
Or
Wipe system data and flash any custom ROM
Click to expand...
Click to collapse
Here's what I'm doing: (I'm writing it out since I'm not allowed to link to pictures I took of the process)
On the Wipe/Advanced Wipe screen, I select the following partitions to wipe:
Dalvik / ART Cache
System
Data
Internal Storage
Cache
The wipe process goes as follows:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting System using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Wiping internal storage -- /data/media...
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Restore
Select Backup from Micro SDCard
2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e
Restore
Backup made on Mon Feb 13 00:40:34 2017
Name:
2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e
Select Partitions to Restore:
System (checked)
Data (checked)
Boot (checked)
Enable MD5 Verification of Backup Files (unchecked)
Restore Complete
Successful
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/TAO9800XCQ/2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e'
Skipping MD5 check based on user setting.
Calculating restore details...
Restoring 3 partitions...
Total restore size is 4944MB
Wiping System
Formatting System using make_ext4fs...
Restoring System...
[System done (66 seconds)]
Wiping Data
Wiping data without wiping /data/media ...
Done.
Restoring Data...
[Data done (249 seconds)]
Restoring Boot...
Flashing Boot...
[Boot done (2 seconds)]
Updating partition details...
...done
[RESTORE COMPLETED IN 325 SECONDS]
After that, the phone now doesn't boot beyond the WARNING BOOTLOADER UNLOCKED screen. I even tried leaving it on for 2 hours, and only got that screen.
I'm hoping that someone knows a way that will allow me to successfully restore from this backup, and that I won't have to flash to a new custom rom rather than restoring from my backup, since that would mean setting up the phone from scratch again.
regularcarrot said:
Here's what I'm doing: (I'm writing it out since I'm not allowed to link to pictures I took of the process)
On the Wipe/Advanced Wipe screen, I select the following partitions to wipe:
Dalvik / ART Cache
System
Data
Internal Storage
Cache
The wipe process goes as follows:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting System using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Wiping internal storage -- /data/media...
Formatting Cache using make_ext4fs...
Updating partition details...
...done
Restore
Select Backup from Micro SDCard
2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e
Restore
Backup made on Mon Feb 13 00:40:34 2017
Name:
2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e
Select Partitions to Restore:
System (checked)
Data (checked)
Boot (checked)
Enable MD5 Verification of Backup Files (unchecked)
Restore Complete
Successful
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/TAO9800XCQ/2017-02-13--00-39-33_cm_surnia-userdebug_6.0.1_MOB30R_aeb84f171e'
Skipping MD5 check based on user setting.
Calculating restore details...
Restoring 3 partitions...
Total restore size is 4944MB
Wiping System
Formatting System using make_ext4fs...
Restoring System...
[System done (66 seconds)]
Wiping Data
Wiping data without wiping /data/media ...
Done.
Restoring Data...
[Data done (249 seconds)]
Restoring Boot...
Flashing Boot...
[Boot done (2 seconds)]
Updating partition details...
...done
[RESTORE COMPLETED IN 325 SECONDS]
After that, the phone now doesn't boot beyond the WARNING BOOTLOADER UNLOCKED screen. I even tried leaving it on for 2 hours, and only got that screen.
I'm hoping that someone knows a way that will allow me to successfully restore from this backup, and that I won't have to flash to a new custom rom rather than restoring from my backup, since that would mean setting up the phone from scratch again.
Click to expand...
Click to collapse
Have you tried flashing a custom ROM? And what version recovery are you using?
Android_noob17 said:
Have you tried flashing a custom ROM?
Click to expand...
Click to collapse
I was originally using CyanogenMod 13 for Moto E LTE, found here on this forum. That's what my backup is, my CM13 system.
Android_noob17 said:
And what version recovery are you using?
Click to expand...
Click to collapse
I tried both TWRP 3.0.0r2 and 3.0.2r5, both produced the exact same issue.
regularcarrot said:
I was originally using CyanogenMod 13 for Moto E LTE, found here on this forum. That's what my backup is, my CM13 system.
I tried both TWRP 3.0.0r2 and 3.0.2r5, both produced the exact same issue.
Click to expand...
Click to collapse
Did you try flashing back to stock? Did you try any newer roms?
Android_noob17 said:
Did you try flashing back to stock? Did you try any newer roms?
Click to expand...
Click to collapse
I temporarily flashed back to Stock to do a carrier reset, which couldn't be done with CM13 for some reason. But flashing back to stock meant losing the apps and data and settings I had previously, so I wanted to backup using TWRP, temporarily flash back to stock and do the carrier reset, then restore back to CM13 using TWRP, so that I could keep my apps and data and settings. I flashed back to stock successfully but couldn't restore back to CM13 using the backup.
regularcarrot said:
I temporarily flashed back to Stock to do a carrier reset, which couldn't be done with CM13 for some reason. But flashing back to stock meant losing the apps and data and settings I had previously, so I wanted to backup using TWRP, temporarily flash back to stock and do the carrier reset, then restore back to CM13 using TWRP, so that I could keep my apps and data and settings. I flashed back to stock successfully but couldn't restore back to CM13 using the backup.
Click to expand...
Click to collapse
That's unfortunate man. Next time you should use titanium backup.
I switched from TWRP to OrangeFox recovery, move backup from TWRP folder to Fox folder and restored the data, then my phone can boot normally
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
aleksandar9999a said:
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
Click to expand...
Click to collapse
I didn't just suggest to format anything...
The important thing is to reflash twrp via fastboot.
The point is that after doing this you might even be able at all again to format data...
If you follow the further steps I think you're good to go and don't need to change any file system.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
Thats because maybe on a backup you select another storage that nota the internal storage....maybe you select otg storage ir something....put the selection on Internal storage....and it resolves
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Stonner_99 said:
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Click to expand...
Click to collapse
me either, my problem. RRD. pls anyhelp?
Hutabarat said:
me either, my problem. RRD. pls anyhelp?
Click to expand...
Click to collapse
Hi, I had the same problem. (Redmi Note 4, Mido)
But after installing RedWolf (Build 27)
with adb/fastboot and everything works fine - without formating everything.
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
solution about unable to mount data on s7 edge
Hi,
Make sure to do a backup of your data, all data will be erased
after many attempts to find the solution
i tried to go to recovery latest twrp:
go to wipe
select data
for me i choosed ext3 and make repair
than i select Fat and again ext3
you can choose another file system
Thank you
Thanks this worked for me
This is the best answer to solve the problem:
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Thanks to you I was able to recover my wife's Redmi 5. Cheers :good:
could not mount data and unable to find crypto error
Good morning guys im using Xiaomi Redmi note 4x(mido) i installed LineageOS 15.1 then the gapps, but the google photos and other google apps keep crashing and recommended me to uninstall and install again. so i wen to twrp and installed the gapps again, then it keeps crashing again. so what i did is to wipe in twrp then installed linneage and the gapps but when rebooting it asked my password then after than i can't no longer boot it keep sayingf could not mount/data and unable to find crypto. i tried all the steps and fix i found here and in other sites but it does not work when i try changing it to other file system it says mke2fs -t ext3 -b 4096 /dev/block/mmcblk0p49, and error 64. Please help thank you
Still not able to mount storage.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
I tried everything that is:
-changing file system also gives "unable to mount storage " in every format like fat, ext2, ext3, ext4.
-factory reset also gives same error "unable to mount storage"
-I also tried different recovery.
Please someone help me!!!
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Format data solved everything. But before format data, you better backup all your files. Because all of it will be erased like new.
Thank you.
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
I LOVE YOU!!! U saved me when nothing worked. Ty so much !!
Hey King,
I do not use a Redmi Note 8, yet I had the same problem with my Moto G5 Plus.
Until I read your post and now my phone works.
Thank you!
Hi, i have TWRP 3.6.0 installed on my mi 11 lite (courbet), and then it shows "unable to mount /data". I know, formatting helps, but what to do if i don't want to format it, only i want to update the rom?
I have a LeMax2, I was running the ROM PixelExperience, I updated the rom for the last time in February, and when I tried to update the rom to the latest a few hours ago messages like "unable to find crypto footer" "error:7" showed, and when I tried to wipe cache "failed to mount '/data' (no such process)" and "unable to mount storage". Then I looked in youtube and changed the format first to EXT2 and go back to EXT4, and the only thing I did is to delete the data of my phone without making a backupp (my fault). What can I do now to install any ROM? Thank you so much.
Heyyo, first off, please ensure you have the latest version of TWRP. To install Oreo ROMs you need TWRP 3.2.1-0 or higher.
Next? I'd recommend reformatting your data partition to remove any form of encryption like this:
Wipe > Format Data > yes > reboot to recovery.
Then using a PC or USB flash drive copy and install your ROM of choice. :good: