Hello
I've been googling for some time but so far I haven't found proper solution.
Since today I have Vernee Thor (MT6753, 3GB RAM, 16GB internal storage) and I've faced few problems.
The phone freezes randomly or is either having huge lags, like 2-3s. Same thing was happening on a STOCK and updated ROM, now I have ported MIUI (MIUI_8.3_EPIC_ROM_v7.3.23) along with TWRP. It installed properly, at least it seemed to.
After rebooting phone I have message with error: "Internal memory is corrupted. Your data is not safe." (translated, may be slightly different from original in English).
I've tried wiping stuff from memory, reinstalling rom but at the end there is no effect.
I thought about re-partitioning phone memory or checking for badblocks or similar stuff that may cause any errors. What should I do to fix that? I'm running out of ideas and it's sad because I haven't found anyone with similar problem.
Related
I've read upon the DAMAGED SD CARD problem with android, but most of the phone becomes virtually unusable, mine says it's damaged but market works, and I can install apps to phone memory, even with APPS2SD enabled. If I try and copy my files to the computer, it stops halfway with 'perimeter incorrect', glad I did a backup like 1 week ago. Funny thing is, in recovery the SD card is fine, I can make backups, I even tried to repair SD Ext Partition, no luck.
Its probably Android thinking it's damaged without it really being so. Totally confused since I warning/error is on the ongoing notification. Also when I go into the SD card & phone storage shows information as unavailable and SD information widgets can't read it either. I don't mind formatting and copying everything over, but it kinda works, but android thinks it's corrupted or something. Very weird. Also I did nothing out of the ordinary, but with computers or machines random errors can occur. I had the partition in place for a 3 weeks now, installed MCR 3.1 couple of weeks ago and using it pretty much like this, but since the WIFI hanged (kept saying it's turning off but being stuck) I rebooted and the message came up.
Is it possible to fix it how it is? Or shall I just re-format and copy everything again. I'm just worried it may happen again.
Hi everyone,
First things first, sorry if this was covered somewhere else in the forums, I really didn't find this question anywhere so I "had" to post this.
I got my Samsung GT-I9003 4GB a month ago, and everything was working perfectly until 3 days ago. It starts showing an "Internal SD card unexpectedly removed" error whenever the phone goes standby, then it forces me to terminate processes one after another, and finally it shuts down. I hadn't done any kind of ROM flashing nor rooting the device until the problems arose, so I don't know where the problem comes from.
I've tried to re-flash froyo 2.2.1 in my device, but the problem keeps showing up.
I found in this forums this thread (http://forum.xda-developers.com/showthread.php?t=1088474) covering the possibility of swapping both internal memory and external SD. It works great, but I still had problems with the "external SD card" being "unexpectedly removed"...
It crossed my mind if it was possible to modify the vold.fstab file further to only detect the external SD card as the internal memory and ignore the internal memory, as if it wasn't even on the phone. I don't know if that's even possible (since I don't know much about file systems nor Android), but I'd appreciate your thoughts on the matter.
same issue
eikur said:
Hi everyone,
First things first, sorry if this was covered somewhere else in the forums, I really didn't find this question anywhere so I "had" to post this.
I got my Samsung GT-I9003 4GB a month ago, and everything was working perfectly until 3 days ago. It starts showing an "Internal SD card unexpectedly removed" error whenever the phone goes standby, then it forces me to terminate processes one after another, and finally it shuts down. I hadn't done any kind of ROM flashing nor rooting the device until the problems arose, so I don't know where the problem comes from.
I've tried to re-flash froyo 2.2.1 in my device, but the problem keeps showing up.
I found in this forums this thread (http://forum.xda-developers.com/showthread.php?t=1088474) covering the possibility of swapping both internal memory and external SD. It works great, but I still had problems with the "external SD card" being "unexpectedly removed"...
It crossed my mind if it was possible to modify the vold.fstab file further to only detect the external SD card as the internal memory and ignore the internal memory, as if it wasn't even on the phone. I don't know if that's even possible (since I don't know much about file systems nor Android), but I'd appreciate your thoughts on the matter.
Click to expand...
Click to collapse
Was having the exact same problem with a further twist, the issue occured almost every half an hour at office and very rarely at home. Tried a factory reset and also GB update via Kies. Problem was still present, so have given it to samsung service and the service rep informed me that it was most likely a motherboard issue.
Recently one of my friends had the same issue. Samsung service center replaced the motheboard and the issue seems to be resolved.
Check this out to recover from a broken (but not fully broken) internal sd card ->http://forum.xda-developers.com/showthread.php?p=30195720
There is no fix. It happens when you have a corruption.It's not a bug.
It's a feature to help recover a bad partition. It just happened to be your SD that became corrupted. This kind of issue has always happened to other partitions and caused bootloops in all versions. ICS tries to correct the issue. Corruption is not new. It just rarely happens to internal storage.Also most of these issues ate happening after Odin. I'm sure you'll notice that if a poll is done.This even happens on official OTA updates to ICS on many devices.Another little tid-bit
Most of the other's having issues, are /data issue
The majority of those, have flashed Lindroid. After doing so Lagfix was enabled, and was not disabled before flashing an ICS ROM
-ICS PASSION DEVELOPER NELSON(FACEBOOK)
http://www.facebook.com/groups/icspassion/427030800664449/?notif_t=group_comment
The real question is what is causing the corruption?
no **** theres no fix, thats why people make threads about it...
I got it fixed. Here is my topic. The weird things is that now, i can not access my phone storage anymore ( both internal sd, external sd card) when connect to my PC.
http://forum.xda-developers.com/showthread.php?p=24585226#post24585226
read the whole thing again...
Hi all,
My i9100 seems to suffer from some memory corruption problems, in either the internal flash, or the internal memory. Sometimes it'll reset, and part, or all of my accounts are gone. It does this regardless of with software I have installed on it, and I tried the whole range of stock, CM11 Mx, and now on CM12. So I was wondering if there was some program (or module for CWM perhaps) which can check the RAM and/or internal SD for issues. Don't quite know where to begin looking though, so I thought this was a nice place to start.
Thanks in advance!
Hans
Updating apps through google playstore causes my rooted phone (Redmi1s) running a customized Cynogenmod 13 to bootloop. I think the internal storage is flaky and is causing updates to start bootlooping. Is there a tool for testing internal storage like disk drive scanning utilities?
When I tried to update the apps one by one, I thought I narrowed it down to a single problem app but when the bootloop issue happened again and I narrowed it down to a common app (Degoo 100Mb) so I think the internal storage could be faulty. I tried disabling xposed modules and uninstalling the xposed framework but it doesn't help.
What could be causing the bootloop problem during updates and does it make sense that the internal storage could be faulty?
edit:
I think the issue is caused by the customized rom not throttling the cpu well enough and the overheating will cause a crash/bootloop while updating many apps at once. Running updates manually on a few apps and fstrim will help avoid the issue but it looks like going back to stock rom is best thing to do.