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...
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.
At the lag fix recovery screen, there is an option for disabling lag fix... I was wanting to know if that will disable any of the lag fixes that you selected, I selected the last overkill option, just because I read in a post that it would repartition your internal SD card. I was one of the unlucky ones whos got wiped. It did repartition it. So am I ok to undo the lag fix? Will it un-repartition my card if I do? Im pretty sure I made that word up.
Hey guys. Got a question here.
I recently installed litening rom with ke7 kernel and it seems that if i use mass memory mode to access my phone while in usb debugging my phone willl reboot when disconnecting.
I never had that problem before. I need usb mass storage mode but what I dont need is for my phone to reboot when I use it. lol.
Anywho ... just wondering if anyone else has that prpblem or if anyone knows a solution
Thanks.
I haven't had that problem at all. Only two hardware things I can think of that can cause that problem though. Either you have a defective phone or you have a defective microSD-card.
Could of course also be an issue with the custom rom you installed or a bad flash.
Hmm, I was thinking it had something to do with the custom rom since it started doing it after I flashed and started messing with the framework and build.prop files.
It freezes after the media scanning completes.
I dont have a memory card in it, just using internal memory.
Wondering if I should backup the internal memory, format it - then copy everything back.... might be a problem with the internal memory.
Its just not remounting properly.
I truly hope its not damaged memory....
Another thing that could be causing issues is Titanium backup.
I froze allot of bloatware.
More than likely the rom test with a stock rom .
jje
ya, I found the problem - corrupted internal memory. It just would not re-mount due to a srewed up file system.
I just copied everything to my PC, reformatted it - then copied everything back - rebooted and it works now.
Seems that the ROM and some memory optimizations I did screwed up the apps2sd part of Gingerbread. Some of the apps that transferred duplicated so there was problems mounting....
Thanks so much for the help guys,
SBS_ said:
I haven't had that problem at all. Only two hardware things I can think of that can cause that problem though. Either you have a defective phone or you have a defective microSD-card.
Could of course also be an issue with the custom rom you installed or a bad flash.
Click to expand...
Click to collapse
Thanks! I faced the same issue. In USB debugging mode, it wasn't a problem when connecting the USB storage. Only after disconnecting the USB storage, the phone auto-rebooted.
This is what that happened that caused that: Unfortunately while flashing the last restore, my phone dropped on the floor. The USB was connected, battery hadn't fallen out and I saw that CWM was still running. So I thought luckily nothing bad had happened. After restoring the phone rebooted normally and everything was fine. BUT after that incident my phone started rebooting every time I disconnected USB storage.
I was searching for this issue in xda and came across this thread. When I read the phrase "bad flash", it struck me what the problem was. I restored the same good restore copy and that auto rebooting problem has gone away.
UPDATE: The issue is still not fixed, the auto reboot is happening again. Please help.
Is anyone else having problems Mounting their sdcard / adb'ing their phone on EC09? I cant seem to ever get it to work. I want to theme, and since most people are switching to this new rom I want to theme it and not ed04 which doesnt give me problems.
Borked SD cards are one of the issues with EC09. Both Nitro and TSM are working on ROMs based on the EC09 leak, so I recommend holding out until UKGB and/or Evil Fascination GB ROMs come out. Perhaps TSM or Nitro (yes, he has a DX2 AND a Droid Charge, but he pm-ed me saying he'll have a EC09 EF release within a couple of weeks) will find a way to fix or bypass the SD card bug. Both Navenedrob and JPTech have posted warnings on their threads against flashing their ROMs until this issue is resolved. I think the number of users who choose to flash anyway, despite seeing the warnings right where the download links are, will be limited (and with a borked SD card, they won't be in a position to flash anything for a while, let alone a GB theme ).
Another Fascinating post by my XDA app...
SD Card isnt broken, Phone just wont mount. I just went to ED04 and it mounted fine.
TheMuffStuff said:
SD Card isnt broken, Phone just wont mount. I just went to ED04 and it mounted fine.
Click to expand...
Click to collapse
The borked SD cards only happen to some of those who flash EC09 apparently. Some have been able to recover their cards using various methods, but some have not been able to recover yet.
Another Fascinating post by my XDA app...
the two *Major* problems are the sdcard freak outs and usb debugging/adb on boot
i find you can toggle debugging and unplug ur cord and get the card to mount with the computer (its much easier in ubuntu than windows...for me at least)
but the major problem is with adb only working randomly while the phone is booting its really hard to logcat issue and for sbrissen to debug the various mods he does
but ive been able to theme/mod ok...just its a headache i wish we didnt have
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.