Asking for my girlfriend who has an international s7 edge. Twice now her /data has been corrupted which resulted in a complete wipe needed before it would function and she's not rooted... Has anyone experienced this?
Related
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Try re-loading recovery via Odin.
Check out this thread close to your issue
I am attempting this now. I did not realize that you meant stock recovery when I first wrote this post.
czahrien said:
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Click to expand...
Click to collapse
I'm having this same issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! Did you ever fix it? - http://forum.xda-developers.com/showthread.php?t=2563695
hi not sure if this is just me or others have same problem i have had my tab since june 2013 i have rooted cwm twr and flashed many different
roms.
lately the tab is locking up and being unresponsive when doing the simplest of things even on boot with the boot logo it lockup
does this also when running any rom i have tried about 6 or 7 of the best roms all with the same results..
i have wipe the whole device meaning i have formatted /system /data /internal sdcard
has any one else had this problem and was you able to fix this unresponsiveness, locking up
im thinking of reflashing stock update from nov 2013 and seeing if this maybe resets what ever it thinks is wrong
is there some thing else im able to do
then re-rooting and re-flashing my costume rom
i would like to avoid all of that and see if any one has a faster fix then that
i came across this posting which seems like just what i have locking up
seems there was no fix as well
http://forum.xda-developers.com/showpost.php?p=32005650&postcount=1
video of the lockups
video of the lock up
http://youtu.be/Xrb_QKxK1lU
I've see this before, try to flash the tablet again and wipe all data including the cache (most important). I used to see flickering on my galaxy tab 8.9 and weird unresponsiveness, usually cache wipe is enough. Most people with those problem didn't wipe the cache before a new flash.
I have Verizon Note 3, with Jasmine Rom and TWRP recovery.
I have posted a question about my phone started showing some sh** dialog over and over about facebook app not responding.
Till now i havent found any solution to it. So, seems as last resort, i will flash again with jasmine rom (if there is anyother better do tell me). But before that, i want everything (EVERYTHING) to be backed up, text messages, my games data, my installed softwares, cracked versions, everything. Is this possible???
Anyone coming to save the day????????
First you need to state whether you have a safestrap ROM or a unlocked bootloader and real custom recovery. Huge difference.
You should also bear in mind that if you are suffering from a corruption issue somewhere, a "complete" backup and restore merely records the corrupted data and restores the same corrupted data. What exactly would you gain that way?
Your hypothesis suggests you think a fix could be acheived by "refreshing" just the ROM (i.e. the /system mount). If you have any customizations in there, they will be lost unless you can identify them and re-create them after you have "refreshed" the /system mount. If you are unable to do that, you will lose them.
If you thought that you were unable to identify those changes and were going to plunge ahead and try anyway, theoretically you would get the same result by just flashing /system only and wipe the /cache mount without doing any backups at all. EXTREMELY RISKY MOVE THOUGH IF SOMETHING GOES SIDEWAYS. (You should always assume that something will go wrong and make backups... and get those backups off the phone in case the entire device needs to be wiped in a "start from scratch scenario)
Note that your apps have been under constant update all this time since Jasmine's release while it (Jasmine) has been standing still. There's no guarantee that what you are observing are not merely bugs in Jasmine uncovered by new application code.
A Herculean, careful and diligent backup & restore operation might fix nothing.
Hey, I'm in a very strange situation. The thing is I left my phone to charge overnight just like usual (made it reboot before doing so), when I woke up today I've noticed that it was bootlooping like crazy along with being very hot to the touch, like it was about to go off :x. Rebooting resulted in nothing, phone still bootloops. After entering TWRP and trying to look for my backup I also noticed that it shows "Internal storage (0mb)", what is totally weird considering that I've been doing absolutely no software modifications lately (I'm on Lineage). I also cannot mount data in "Mount" section, backing it up is also not an option.
I havent't tried yet to restore my full back up I've made around a month ago, is there any way I can revive the data partition?
Ok, since my backup is missing I've decided to reinstall the rom. But I can't format the Data partition at all . TWRP just goes "Failed to mount '/data' (Invalid argument), Unable to wipe /data). What should I do? Is the phone internal memory dead or what?
OK SOLVED. I entered erecovery and formatted my data. Now I reinstalled Lineage and everything works again... apart from photos of my doggy lost . Damn, I have completely no idea what caused that Data partition failure
Hi
Have been having battery issues with my phone and read where wiping cache partition may help. I started the process about 2.5 hours ago and it is still 'wiping cache'. Is there any way that I can stop the process without damage?
Really need to use the phone atm . Have googled as much as I can in the last hour and cannot find an answer. Saw where one guy took out his battery to stop and now phone won't work. Really appreciative of any advice.
Thanks in advance
It should be fine just to take the battery out (although don't quote me on this one). Wiping the cache should be very quick as its a much smaller partition compared to lets say the data partition.
Could be recovery frozen, corrupt partition, either way it is a very unlikely occurrence. In TWRP, try formatting cache partition manually (advanced wipe options). If that doesn't help, go to TWRP settings, tick the box that uses "rm /rf instead of format", then wipe again.