My phone started bootlooping whenever I booted it up and the first examination determined the problem went away when I took out the MicroSDXC card. I have seen many threads about corrupted cards causing this problem. Why does the card cause this?
I thought the card must have been corrupted - reformats / removing files from it did not even solve the problem. so I went and bought another card. Put the new card in the phone and no more bootlooping. Copied the old card on a PC reader to my PC, then copied the same information back to the new card. Put the new card in the phone: the boot looping started again.
It turns out this bootlooping is not caused by the card but is a Samsung bug. So many of the cards that people have that they think are corrupted, ARE NOT CORRUPTED!
To fix the problem:
1. Turn off phone, remove battery
2. Remove memory card
3. Replace battery, turn on phone
4. Go into Settings
5. Tap on the left side on the "WiFi" line, the list of your memorized connections is shown
6. Tap the MENU button
7. On the pop up menu that appears, select "Advanced"
8. Make sure the check box for "Always Allow Scanning" is UNchecked
9. Turn off your phone, remove battery
10. Replace the memory card
11. Replace the battery
13. Turn on phone
- No more boot loops!
Sent from my Galaxy Note III; Previous owner/hacker of Galaxy S III, Galaxy Nexus, Droid X, HTC HD2, HTC Touch Pro 2, HTC Tilt, HTC 8525, O2 XDA II, O2 XDA.
After getting the 128GB memory card recently, I inadvertently turned the setting back on. Bootlooping started again. Started thinking the card was corrupted, then remembered my own post. Followed the inductions and the issue went away. Whew (these cards are hard to replace).
Sent from my Galaxy Note III; Previous owner/hacker of Galaxy S III, Galaxy Nexus, Droid X, HTC HD2, HTC Touch Pro 2, HTC Tilt, HTC 8525, O2 XDA II, O2 XDA.
Related
Hi there,
I have an xda neo which has the following problem.
If an SD card is installed (either a real card or the dummy), an i have the phone switched off from the power button, while the setting is onlz to turn on when pressing the on/off, if I apply a soft presure in the region of the sd card, the phone turns on. I believe its a mechanical/electrical error of the phone so does O2 but since I want be around to get the phone fixed in the next 2 weeks I wondered if there is an registrz kez I can change in order to disable the autodetection of the SD card internally, since I believe that that is the problem.
If installed a registry viewer, but I can't find anzthing in the gregistry that seems to me as an appropriate key.
Can anybody help?
Anyone ever had a problem with their O2 XDA Mini S not recognising a mini SD card?
I got a 512MB one on Thursday (not a cheapo one, a SanDisk bought from the O2 shop), and when I put it in (with the device on), nothing happened. If I went to Settings > System > Storage Card, it said "Not inserted".
Ok, I thought, maybe it needs formatted somehow. Couldn't find an option for that. So I thought maybe reseting the device, but that didn't work either. I took the card out and put it back in, and it instantly showed up this time.
Anyway, all was fine over the next 2 days, till last night - I was messing about with TomTom 6 (which is on my SD card) before I went to bed last night, and all was ok. I exited the app, I put the phone on charge and when I got up this morning and started TomTom I got "No maps found". This was because when I checked Memory > Storage Card, it said "Not inserted". Popped the card out, put it back in, works fine.
Any seen this behaviour before, and do you think it's more likely to be a problem with the device or the card?
Cheers
I had the same problem with a 2GB MiniSD after checking with varius programs I just removed and re-inserted the card. It was detected immediately and has worked fine since (if it has not I've just done the remove and re-insert thing).
Was it an expensive one or a cheap one? I've read on here people have had issues with really chep Mini SD cards. My O2 was a little unstable for a bit when I got my 2GB card. But then I paid £45 for 2 of the blighters from eBay so it wasn't surprising. Currently it seems OK though.
2nd line of my post:
"not a cheapo one, a SanDisk bought from the O2 shop"
markmcrobie said:
2nd line of my post:
"not a cheapo one, a SanDisk bought from the O2 shop"
Click to expand...
Click to collapse
I had this same problem. I fixed it by removing the miniSD card from the wizard. Then soft reset the device. THen turn it back on. Wait for it to fully boot back up and re-insert the card. Also, do you have a card reader you can test the card on to make sure its the phone, not the card?
Seems ok in my card reader, but then it was only in it for 5 mins.
Hi,
yesterday evening, just when I wanted to set the alarm and go to bed, I suddenly noticed an alarming sign on top of my display. The message that came along with it was that my sd card has been removed which definitely wasn't the case. I tried several thing to let the device know that the card is still there but none of them worked:
- re-entering the card
- rebooting the device (with and without card inserted)
Afterwards I inserted an old 2gb card and the device noticed it at once. Then I tried to use the probably one with an SanDisk Card Reader on my Computer but it didn't either - it didn't show up.
Is there anyone who experienced the same or has a clue what may have happened? The phone is vodafone branded an bought in early August. I never updated the ROM nor did I try any risky tasks ;-)
Hey everyone, I'm trying to figure out the possible cause to my issue. I have a Samsung Galaxy S5 with stock rom. I also have a samsung class 2 micro sd card that I've had for quite some time. (I believe I got it back with my S3 or possibly before that in the Mytouch days).
I started having the issue when I would click on a photo in my gallery and it started lagging and then it wouldn't open any of them as the drive appeared to be corrupted. Then I attempted to restart then device and had no luck there as it would freeze on the carrier screen as it was turning off. So the only way to turn it off was to remove the battery. I played with this issue for a minute trying to figure out the cause and eventually device I was just going to do a master reset. However again once I went to turn the phone off to do the master reset the phone once again froze up and was unable to turn off due to being on the carrier screen. Then I just went directly into the bios of the system by holding the pwr volume and home buttons to do the reset from there. That did work and I got the phone all back up and running. However SD card was still not working So i went to go power it down but it again froze so I took the battery out and removed the sd card as well as the battery and with the sd card out everything functions fine. I plugged the SD card into my computer and it proceded to check it for errors because it couldn't find any data on the drive. It checked for the errors then after the check was done it came back with nothing. But all the data was intact. So I put it back in my phone. Everything worked fine, I was able to view my sd card files on my phone and computer, then I went to sleep. Put the phone on the charger. I woke up to my phone being off and not wanting to turn on. So again popped out the battery and was able to get it started but same issue sd card is not being seen by the device but its causing it to not turn off or restart properly.
Does anyone have any idea if this is just a corruption issue with just the card it self? Or is it possibly a virus that got into the micro SD card? Everything was working fine prior to last night. The sd card had been used in multiple phones as well as the Galaxy S5 that I've had for about a month.
Thanks
Crashin1775 said:
Hey everyone, I'm trying to figure out the possible cause to my issue. I have a Samsung Galaxy S5 with stock rom. I also have a samsung class 2 micro sd card that I've had for quite some time. (I believe I got it back with my S3 or possibly before that in the Mytouch days).
...
Does anyone have any idea if this is just a corruption issue with just the card it self? Or is it possibly a virus that got into the micro SD card? Everything was working fine prior to last night. The sd card had been used in multiple phones as well as the Galaxy S5 that I've had for about a month.
Thanks
Click to expand...
Click to collapse
There isn't a virus. You CANNOT get viruses on android without installing an APK (99% of the time). It's most likely a bad SD card. Why are you using a class 2? I would just upgrade to a class 10 samsung / sandisk card and see if the problem still exists.
"SD Card Damaged : Try reformatting" and SD card randomly unmounting itself.
I'll start from the beginning. I purchased the phone on 2/14/16 from Best Buy for a $1 upgrade fee. The phone worked fine from day one with the Sandisk 64gb Ultra card I have had installed and running in my three prior phones (Samsung Galaxy S3, Samsung Galaxy Note 3, and LG G3) with no problem. Basically just used the card to hold music I had downloaded off of Google Play Music. I believe I used about 40-45gb of the available space.
This past Monday, the phone was at 20% battery when I went to bed so I powered the phone off and charged it overnight with it off to get the most charge before work. When I powered it on Tuesday morning, I had a notification that said "Damaged SD Card: Try Reformatting." Upon seeing this, I attempted a reformat and nothing happened. Tried again and again to nothing happening. Being rather upset, I dealt with the lack of a SD Card for the day until I could get to Best Buy and see what they had to say.
Stopped by Best Buy after work and their "tech guys" told me they had no clue, attempted a few fixes (all to no avail) and ended by telling me I should buy a new SD Card and give that a shot. Being it was close to closing time, I grabbed the 128gb Samsung Evo + which, per a few internet searches, was the "best SD card in 2016." Drove home, powered off the phone, pulled the SIM/SD tray, installed the new card, popped the SIM/SD tray back in, powered up and...nothing.
The phone wouldn't recognize that there was a SD card in it. Read a few articles from a few Google searches and pulled the card and verified that it was working by putting it in my Chromebook. The Chromebook recognized it, my Lenovo PC recognized it, the phone would not. I tried reformatting it on the PC and reinstalling it just for it to recognize the card and have the card unmount itself literally within two minutes of being recognized.
Frustrated, I called Verizon and asked what they could do. They overnighted me a replacement phone. Get home from work today, try the new phone and ...nothing. Same issue. I read a few threads on this forum that stated that Motorola doesn't want to take responsibility for the issue but I don't see how it isn't the phone's fault. My Chromebook can use the card. My PC can use the card. The previous three phones I had could use the 64gb Sandisk card. What gives?
Sadly, looking around Google, I don't see many articles or forum posts about my issue so I have yet to find a solution. Can anyone shed some light on this? Is there a way to fix this? Is my best option to get irate with Verizon until they replace this phone with yet another replacement to which has the same problem? Do I wait for the Marshmallow update and hope for the best? Do I continue being irate with Verizon in hopes that they'll replace this phone with a different model by a different manufacturer? What is my best options?
TL;DR - SD Card will mount in phone but will unmount itself immediately after powering on. Lack of Google results. Is there a fix?
Try to format sd card with your phone. I had similar problem with my previous phone.
I have exactly the same sd card as you and works flawlessly in my Force.
Sent from my XT1580
I've tried numerous times. When I hit "Erase everything" it starts and reads "Unmounting SD" for like a minute then gives me the error that the SD card was removed before it could finish though it hasn't. I don't know what the problem is.
Sent from my XT1585 using Tapatalk
Try removing the Micro SD-Card and use Windows to run "Error Checking" on it (right click drive, click on properties, click on "Tools" tab").
This fixed my SD-Card concerns.