I have seem to have found the issue and solution to this problem that many of us have been experiencing. If you have encountered issues like myself, there is a thread dedicated to the description of this problem; MAJOR LAG, RANDOM REBOOTS, the phone won't boot up and goes into a screen where you read:
----Mmc_failed failed boot---
After searching for about a month, it seems to be an internal SD issue. Many have reported to having these issues after they root, others upgrading to the non reversible DOK2 FIRMWARE. Others were stock with out root and had this issue as well.
**THE PARTITION OF THE INTERNAL SD CARD IS CORRUPTED**
Could be corrupted files, that stick to the phone EVEN AFTER ODIN FLASHING STOCK MANY TIMES.
(I Odin 5 times back to back to fix and the partition was still corrupted)
People thought "well, if Odin doesn't work, it's a hardware issue" I thought that myself, and it was not.
My friends, I have found something that has worked for me and would like to share with you guys. I hope this fixes your device like it did mine. I've been so close to throwing this Note 4 against the wall, running it over with my car, or smashing it with a hammer. I had no way to return my device as many have suggested to do because I left T-mobile a while back. Plus, rooting my phone voided my warranty. Yada, yada, yada, let's get into it.
*Since the internal partition to the SD card is messing up, we need to repair it.
**In order for this to work, you will need to be ROOTED.
*Download an app called "AParted SD Card Partition." Hope I don't violate any rules, but here is the link to it on Google Play.
https://play.google.com/store/apps/details?id=com.sylkat.AParted
Once the app gains root access, you will be brought to the main screen. Click the tab that says tools. Once that screen pops up, you will see
Part 1 FS: fat32 . Size 31914 MB
Part 2
Part 3
Part 4
Please note that the size to Part 1 may be a different number. That is what mine read.
*You will now click Part 1
*After doing so, at the bottom where it says create, click it and replace it with REPAIR.
*Hit apply, and you're all set.
*Turn off phone, pull battery out for 10 seconds, as well as external SD card and Sim. (They hold small amounts of electric current which may prevent the phone to do a proper boot) I usually hold both volume buttons, power button, home button, and pull the s spen out for 10 seconds simultaneously, then put it all back together and boot up.
*******Also, I used the app to delete the partition, and creating it again to avoid problems from a faulty repair. So if you want to do that, click Part 1. Instead of repair, click delete. Once done, click Part 1 again, then click create. Hit the Fat32, and start it. Once it's created, you shouldn't have issues. In case you're worried, pictures and videos will not be erased.******
I HAVE NO AFFILIATION WITH THE DEVELOPER, BUT HE SAVED MY DEVICE WITH THIS APP. PLEASE, PLEASE, PLEASE DON'T FORGET TO THANK HIM AND HIT THE LIKE BUTTON IF THIS WORKED FOR YOU AS WELL. LEAVE COMMENTS AND QUESTIONS BELOW, AND IF YOU SEE PEOPLE TALKING ABOUT THE PROBLEM IN OTHER THREADS, RE- DIRECT THEM TO THIS THREAD.
This is what I got when repairing the partition. You should have a message as well.
um... if they can't start up the device, how are they going to download it from the play store and install to run it? Thanks!
Are you able to go into DOWNLOAD MODE AND FLASH FIRMWARE? I had the Mmc_failed screen and my phone would not turn on until I took everything out the phone; battery, both cards and s pen, then hold all the buttons down.
Try this to reboot like I described up at top.
Turn the phone off. Pull the battery out, s pen out, SD card and SIM CARD.
PRESS AND HOLD ALL HARDWARE BUTTONS FOR 10 SECONDS WITH EVERYTHING OUT THE PHONE. I CLICK ALL THE BUTTONS SEVERAL TIMES TO GET ANY ELECTRIC CURRENT OUT THE PHONE. IT WON'T BOOT UP IF YOU DON'T DO THAT. I'm assuming it messes with the boot up process. Anyways, Re assemble and boot. When I was having this mmc_failed crap, it would take several times doing these steps so that the phone could boot. Don't get frustrated and try again until it boots up. Sometimes it would sit on the NOTE 4 screen, other times it would boot up to the Android logo with the mmc_failed screen. It takes several attempts since the PARTITIONS TO THE SD CARD ARE CORRUPTED. IF YOU ARE ABLE TO ODIN FLASH FIRMWARE, FLASH THE FIRMWARE TO HELP YOU BOOT UP. FLASH TWRP, THEN ROM, then you will have root.
If you still get the mmc_ boot after repairing it, erase the partition, and create it again. I updated the guide on top on how to do that. Haven't had a single hiccup or Mmc_failed bs since then. Good luck guys.
Please report back if it worked for you.
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
mtran1977 said:
I will try this as soon as I can. The t-mobile store I went to was unhelpful and only wanted to sell me a new phone, even though I've only had the phone for 1 yr and 1 week. The problems started 2 weeks ago. Thank you for giving me hope.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
No problem. Save everything important from your sd card and formatt it. That also helps. Try booting up your phone without your sd card. You know what mmc is? An sd card. Google it. Ive seen corrupt sd cards prevent phones from booting up.
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
What does it fix??
I tried using this application and the first partition that came up was a 61240 Mb partition. I thought it has to be my external SD card. Then i pulled out the external sd card and ran this application again. This time it did not find any partition.
Is this what its suppose to do? If not can you post a screenshot of your partition list.
Thanks
thiennvbk said:
Now I can't turn on the phone to fix like you. This morrning I'n in stock DOK2 and have all of error like you. I flash TWRP and flash cook rom, hope can fix like you. But after flash TWRP succesfull, I'm flash cook rom but the phone turn off and can't turn on. when it turn on, it go in to download mode and notice MMcC read fail. I try many time but it still like that. I use odin to load DOK2 Stock firwame but it FAIL. try many time still FAIL
now I don;t know anything need to do to save my phone. lol
Click to expand...
Click to collapse
After flashing TWRP AND THE COOKED ROM, TURN OFF THE PHONE. TAKE THE BATTERY OUT....SIM CARD OUT...TAKE THE SD CARD OUT AND THE S PEN PUT.
THEN WITH ALL THAT OUT, PRESS AND HOLD POWER FOR 20 SECONDS. THEN TRY TURNING ON THE PHONE. HAD THE SAME ISSUE AND IT TURNED ON AFTER A FEW TRIES.
U may need tp try to do that a few times until you get it to power on.
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
It does not fix internal SD
Willy318is said:
This is Kinda confusing, we are talking about the INTERNAL STORAGE here, Right? If so, How on earth an App can Format the Internal Storage while its being used obviously by the OS itself? and How can it NOT erase any Media files? It seems very unrealistic approach? unless we boot the system using external boot device then wipe the affected partition, think "Ultimate Boot CD" or "Hiren" for Windows.
What you are saying is like this: Boot Windows laptop/Desktop normally, then Format C: from within Windows !!!
I know you mentioned REPAIR PARTITION, that would/might be OKAY, but to Re-Create the Partition of the MMC (Internal Storage), this sounds crazy, and not even doable.
Please Shed some more lights into this !
Click to expand...
Click to collapse
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
rajatkuthiala said:
If you take out the external SD card, the app does not detect any partition. So this means that we are never fixing the internal memory, just the external one.
Click to expand...
Click to collapse
So all of this lengthy post and RED Promises are all BS?
I thought so !
Willy318is said:
So all of this lengthy post and RED Promises are all BS?
I thought so !
Click to expand...
Click to collapse
I am still waiting @notufatjesus to reply.
---------- Post added at 03:09 PM ---------- Previous post was at 02:37 PM ----------
I was wondering, could this issue be related to eMMC like they had on earlier galaxy series. These symptoms are pretty much similar.
created new thread with real solution
Ashwin Prabhunerurkar said:
created new thread with real solution
Click to expand...
Click to collapse
I have the same problem and also hope have a way to repair this error. Now very difficult to use the phone.lol
Mine works fine
@dannygoround
My hopes went up then got nuked as I read the comments lol
Related
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .
what about adb ? Did tried it ?
a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair
bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen
workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.
I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.
Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks
I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.
Hello everyone, i just got the nexus one just to mess around with, its already rooted but no rom installed. My problem is that when I put my SD card in the phone and boot up the phone I get the message "SD card blank or has unsupported file system". I know theres threads on the topic but they seem not to work, I've also reformatted thesd card and nothing. Its a 32gb
Not sure of the brand, ill look and post it.
Try using a program like sdformatter and did you format to FAT32?
Try a different sd card to see if maybe it's the card itself that's bad
Yeah I tried sdformatter, yeah I tried formatting to Fat32, no the SD isn't bad,the computer recognizes it. Idk what's wrong
with sdformatter did you use full erase and size adjustment ON
i am not sure but a card may be able to be recognized and still can't be formatted or may be bad--again, not sure
Yeah I tried full erase but not with size adjustment on though, ill give it a try though. I know the SD card isnt bad because after trying to have the nexus read it, and I get the blank SD card error, I plug it into my computer and it will automatically ask me if I want to format the SD card because its corrupt, after I select yes the computer reads it just fine. I think it just might be the phone itself, I've tried countless solutions people have posted in other threads, and the phone is what, about 2 years old, it just might be slowly dying
understand--good luck
rugmankc said:
understand--good luck
Click to expand...
Click to collapse
i got it to work, i flash rcovery, phone reboots and the same problem again ...i think this phone is done.
didn't see in your posts, but did you try another card
707BeastMode707 said:
Hello everyone, i just got the nexus one just to mess around with, its already rooted but no rom installed. My problem is that when I put my SD card in the phone and boot up the phone I get the message "SD card blank or has unsupported file system". I know theres threads on the topic but they seem not to work, I've also reformatted thesd card and nothing. Its a 32gb
Not sure of the brand, ill look and post it.
Click to expand...
Click to collapse
Does N1 support 32 gb cards?
The N1 does support 32gb SD cards, I've gotten lucky and it read it, but after booting the phone up again I got the same message in the status bar, I think the problem might be with the rom on phone I don't know what rom its running but it looks like its a completely stock rom, or it could be the way the way the person rooted the phone, and I don't have a clue on how to unroot the phone. Yes I know its rooted I'm able to get superuser permissions.
you didn't say, unless i missed it, did you try another card
if so, and it is rooted can you tell what recovery is on phone clockwork or amonra
Sorry about that, yeah I tried and still am trying a 4gb SD card, I didn't root the phone, but when I got the memory card to work I flashed clockworkmod, I was going to reboot into recovey but when I pressed powered button I could only power off the phone, so I did and was going to boot into recovery through hboot, but when I selected recovery it just showed the picture of the android with the black background, so I rebooted the phone and kept on getting the error message, idk what I did to get the phone to read the SD card, I guess just luck.
Do you have the android sdk installed on pc do fastboot flash amonra 2.2.1 or maybe clockwork has that option. If it it the first time you may need to delete a couple files to have amonra stick. Clockwork 3+ did have some issues for some. Or you can check wiki and flash the correct passimg and go back to stock and start over. If you have means back up what you can. Not sure of your problem--sorry
Well it looks like the N1 is done, it won't even boot any more, looks like I'll be phone less for a while...the problem wasn't because it was rooted, I got it unrooted back on 2.2.1 then it updated to 2.3.? And it still had the sd card problem, I guess it was a sign that the phone was dying...r.i.p. n1 lol
Thank you ruggmankc for trying to help save my n1
sorry to hear that--
bright side is great phones are coming out this year and N1's can be bought at good prices if interested
---------- Post added at 01:35 AM ---------- Previous post was at 01:34 AM ----------
i snuck my post in ahead of yours--but you are welcome--
Basically anything I can make calls and text on will do until I can afford and high end android phone
good luck on it--
OK so heres my story of what happened to my Captivate. I plan on getting an SIII sometime in the next couple of weeks, but it would be nice to get my Captivate up and running again in case I need it sometime in the future.
So I was running CM9 on my phone, not sure which build, not sure if it matters. Phone was still in my pocket when I went swimming. Left it in a bag of rice, and it booted up. I got the message that said Encryption failed...reset phone or whatever. I figured it would just format it and didnt know that it would lead to more problems. So based on what I have read on the site, now my internal SD is fried im assuming. Now I tried following some guides for using an external SD card but I couldnt get it to partition from ClockworkMod, and I couldnt get into download mode for a few days because something probably got messed up internally from water damage. I managed to get into download mode today and tried running an Odin One-Click to see if it would help at all. Now my phone brings up the AT&T World Phone screen, then shuts off as soon as the screen normally transitions into the next step of the boot process.
So thats my story. I just want to know if anyone knows if this is still a problem with the SD card or if my phone is completely beyond repair. Thanks a lot to anyone that tries to help
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
robm1911 said:
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
Click to expand...
Click to collapse
Ya that was the guide I tried but my external SD card wont partition, at least not through clockworkmod. When i press the button to partition, the partition process is instant, and i know it just has to skip it because there is no way it would partition that fast.
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
mrhaley30705 said:
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
Click to expand...
Click to collapse
I think with the EU bug its just trashed. JTAG won't even fix it. There are a few stories of them coming back to life on their own, but no promises.
Hi we offer a work around re-map to have the partitions run on you external sdcard. Pm me if you need any help with this.
Sent from my GT-I9300 using xda premium
First, let it be known that I'm an idiot. I'm not new to the scene but I did some really noobish things and I've really screwed myself into a corner. So, first the background info. I have a Samsung Galaxy S Captivate, on Rogers (Canada), and I was running CM 10.2 (if I remember correctly). I set an alarm at night and woke up the next day to a recovery loop. I tried a number of ways to recover and reflash and one by one they failed, and piece by piece, I unmounted, erased and formatted everything (I know, I know). So I've got to an interesting point and I'm not sure what to do next as most method seem inaccessible. So, here's the list of broken things (that originally worked but I broke):
- No recovery/no ability to boot to recovery. All attempts cycle a boot loop.
- no internal sdcard. Can't see it or mount it. I've tricked my phone into thinking the external is the internal. This however, means I can't download anything or even copy anything to my phone. No cloud or internet files.
- no usb. I can connect and it recognizes it, but there's no sdcard (so it thinks) so there's no connection made.
- no download mode. Here's where it gets funny. I managed to flash a stock kernel with odin (YAY!) but I flashed an AT&T version and guess what? No download mode anymore. I've tried numerous combinations. I haven't yet tried a jig which is what I'm assuming everyone will say I have to do. I have no idea what I'm doing from there.
- almost unusable phone. I can't even make calls as the SIM is meant for Rogers, not AT&T
- my bank account. I'm short on cash so I can't just go and buy a new fancy phone even though I really, really want to.
I seem to be the prime example of what not to do and I brought it all upon myself. However, I've heard that as long as the phone turns on, there's hope. My goal is to get back to a CM firmware (or something else if you hate it) and maybe recover from the damage I've caused. So, am I screwed?
tl;dr Everything is broken and I'm stupid and desperate. :good:
Jig... to get into Download mode.
Then flash an Odin Stock firmware for Rogers here... http://forum.xda-developers.com/showthread.php?p=18371028 Post #4.
But not sure how that will work out for ya since ur internal memory is messed up.
---------- Post added at 12:18 PM ---------- Previous post was at 12:08 PM ----------
If all fails and u don't mind spending some money when ya can...check out mobiletechvideos.com for the repair.
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Val D. said:
I think the main problem here is failed internal memory. At one point the system lost the access to internal memory -> reboot -> can't read data -> reboot, etc. This is why you found the phone in a bootloop that morning. Android 4.3 (CM10.2) is still in beta, but it's not the cause of the failure. No software fix for a hardware problem, unfortunately. I know some people use external SD as internal, but I never needed to study this workaround.
Click to expand...
Click to collapse
It's using the external as the internal right now. If I remove the external and try to boot, it will show the boot logo and shut down. Seems like the jig is the next step.
sometime ago my sdcard kept being unexspectly removed, a friend of mine had a theory that it might be a software problem.
So he tried to install cyanogenmode on it coming from whatever system I had before.
Suddenly the SDcard worked, and I could get the new OS on.
now on cyanogenmode it can't decide whether it wants to work or not, it seems to stop working whenever i'm doing something with video.
The SDcard always comes to work again when my phone completely runs out of power, but then after sometime it stops.
my friends theory is now that the sdcard might be bricked, how do I unbrick?
i tried formatting the sdcard and this is the rom that i'm using
[ROM][CM10][4.1.2]CyanVivo X Reborn![Buttery Smooth][15/07/2013][3.0.86]
http://forum.xda-developers.com/showthread.php?t=1996570 - link to rom
cophenague said:
sometime ago my sdcard kept being unexspectly removed, a friend of mine had a theory that it might be a software problem.
So he tried to install cyanogenmode on it coming from whatever system I had before.
Suddenly the SDcard worked, and I could get the new OS on.
now on cyanogenmode it can't decide whether it wants to work or not, it seems to stop working whenever i'm doing something with video.
The SDcard always comes to work again when my phone completely runs out of power, but then after sometime it stops.
my friends theory is now that the sdcard might be bricked, how do I unbrick?
i tried formatting the sdcard and this is the rom that i'm using
[ROM][CM10][4.1.2]CyanVivo X Reborn![Buttery Smooth][15/07/2013][3.0.86]
http://forum.xda-developers.com/showthread.php?t=1996570 - link to rom
Click to expand...
Click to collapse
Your sdcard is not bricked. Just take off the back cover, take the sd card out. Blow gently on sd card and slot and then put sd card back in. Normally the problem goes away.
072665995 said:
Your sdcard is not bricked. Just take off the back cover, take the sd card out. Blow gently on sd card and slot and then put sd card back in. Normally the problem goes away.
Click to expand...
Click to collapse
It doens't, also that's like one of the first things i tried, way before I even thought about getting a new OS.
bump.
SD card problem
Did you fix your phone or not.
After I made factory reset on my phone I faced with same problem. There were nothing wrong with phone before factory reset. !! strange