When I press gallery it says my SD card is unmounted. I powered off, removed card, cleaned card and phone, then I restarted it and it worked but now I'm getting it again. Pretty annoying. Also, is this the type of issue covered by the warranty?
I ran a search on Google and nexus one general forum before posting, thanks in advance for any help...
oh wow....i just unmounted the card, then i powered down. when i powered on it said the card was damaged and i may need to reformat it.
So i put it in my laptop and it says it needs to be formatted.
Have i lost all of the stuff on my card and, if so, what could have caused this? its kind of devastating for me.
The ONLY thing i did today that was out of the ordinary was install zumodrive on the phone.
its a class 6, A Data 8 gig and ive had it for a matter of 6 months, im guessing it was the phone or an app that caused it?
Unless you were constantly removing the card while a device was in the middle of writing to it, I dont think the phone it self would have caused much damage... I'm thinking it was more likely a defective card...
s4yunkim said:
Unless you were constantly removing the card while a device was in the middle of writing to it, I dont think the phone it self would have caused much damage... I'm thinking it was more likely a defective card...
Click to expand...
Click to collapse
bummer, so i probably should just trash it as opposed to formatting it and using it again?
i have had a card fail on me, and was able to get it back and it worked fine. seemed to be just a tad bit slower the second time around, but nonetheless it worked.
it was weird thought, windows wouldnt detect it, and my phone wouldnt either. i had to go into drive management and it was seen there. once i got that squared away and go tit formatted all worked well.
as far as saving your files, im not sure... i try to backup my sdcard about once a week (simply overwrite any files that havent changed). you may be able to use a disk recovery utility, such as the ones that are used to retrieve files from dead HDD's.
i had this problem on stock
i ended up putting my sd card in the pc and backing everything up (everything was fine even after the phone showed it was corrupted)
reformatted my sdcard
tested and still got the error
so i pulled the sdcard back out, started the phone up without any sdcard inserted. after putting card back in and booting up never had the problem again
since rooting, i've never run into this problem either
Hey everyone, I really need your help.
my 16GB microsd died last night, here's what happened:
I had gotten google music beta on wednesday, last night i was showing it to a friend, then clicked home. I have Watchdog installed, which told me music was taking up a lot of CPU, so i went in and killed it. instantly, android notified me that the sdcard had been ejected. then it popped up and told me that a blank card had been inserted. I was confused at first, but didn't do anything with the card, I took it out, reseated it with the phone off, started backup, same issue. I put the card into a card reader on my win7 pc, no luck, the card really is dead. It shows up with a drive letter, but notifies me that the card needs to be formatted.
Does anyone have experience recovering data from flash drives? I always backup my roms to the card, and apps using titanium, but I never ever thought of backing up the entire contents of the sdcard elsewhere. HELP!?
http://www.piriform.com/recuva
Use that on windows, it worked when my sd got messed up. This is assuming the files are still on the sd and not gone completely. You could try the repair option in windows if you have Vista/7, not sure about macs or linux.
Thanks but right now windows is telling me that the drive is not accessible. recuva is also saying "the parameter is incorrect". I can't see anything on the card. I think i need some low level scan type stuff, but I have no idea what program goes that deep.
phuzznut said:
Thanks but right now windows is telling me that the drive is not accessible. recuva is also saying "the parameter is incorrect". I can't see anything on the card. I think i need some low level scan type stuff, but I have no idea what program goes that deep.
Click to expand...
Click to collapse
Sorry, don't know of any software like that. You may need to format if you can find no solutions.
I had the same problem a couple of weeks ago, but the last application that I used and caused the card's premature death was some FM radio app.
Since it is not recognized in any device whatsoever, I don't see any software that can help you even attempt to recover, fix or format the card.
But I learned a lesson: I always used to do backups once in a while, but when the card fubared I just learnt the hard way that I wish I had made backups more frequent...
(BLACK SCREEN OF DEATH)
OK, I have a dead Nook on my hands - non-responsive completely. A coworker of mine bought one of those CM7 cards off of Ebay and it worked fine, but had some connection issues, so I suggested he make a move to PA. Of course, I was the one that was going to do this, so I installed CWR to the EMMC, rebooted, hit N, and booted to EMMC recovery no problem.
Here's where things got stupid:
In recovery, I attempted to install PA without removing the sd card and used the internal SD Card to grab the image. Yeah, I know... Browbeating not necessary... It was taking too long and appeared stuck, and then suddenly the unit just appeared to power down. That was it. No more recovery, the card no longer worked, NOTHING!
Hooked it up to my PC and for a second or two when you hook it up, you can see in the device manager, the Motorola device pops up (I own a Motorola phone, so I assume the drivers are kicking in), and then it goes away. Long press power, do it again, same results. Still no screen, no nothing.
So I figure the 16GB CM7 card (Sandisk SDHC) still has to be useful for creating a recovery card, right? After all, whoever created it originally was able to stuff a bootloader on there, right?
So here's what I tried in terms of tools:
win32diskimager .1 r15
win32diskimager .7
WinImage 8.5
with these, I have tried the following images:
16gb_clockwork-3.0.2.8.img
generic-sdcard-v1.3.img
TWRP-2.1.8-bootable-SD.img
And I used MiniTool Partition Wizard to remove the partitions after each attempt and reformat back to its full 16GB.
The only time a burn was unsuccessful was on the 16GB clockwork with Win32DiskImager - it gave an error stating it couldn't find sectors at 99%. I tried an 8GB image too, but while it burned successfully, no dice.
Alright, so here we are, me at the end of my wits, you reading this tale of woe, and a coworker without a functioning device. The device has charged all night. I owned an NC for years and was mod-happy during that time, and although I had BSOD, I was able to fix it easily. This is a 1 year old BNRV200 (pretty sure they didn't switch up the models).
Help? Advice? WT%#$%^?
EDIT: ADB does not recognize the device when connected.
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Go to my NC partition repair thread linked in my signature and follow the procedures there.
Use SDFormatter free on the web for formatting your card before burning one of my bootable CWM images. Don't use partitioning software. The NC is real finicky about how cards are burned. Look at my NC Tips thread and read item A9.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
majorpay said:
OK, so I used SD Formatter v3.1, size adjustment ON, Full Format (Erase)
Then I used win32diskimager v.7 with CWM-6.0.1.2-bootable_SD - still no boot.
Went back to SD Formatter, rinse, repeat.
Then I used win32diskimager v.1 r15 with same image - still DOA.
Anything I'm missing? I'm going to try 5.5.0.4 in the meantime, but I have my doubts that it will make a difference.
Click to expand...
Click to collapse
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
reply
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
majorpay said:
I'm running W8 on all my PCs (doubt that matters?)
Tried 5.5 - no luck.
Switched to a 512mb SD Card, no luck.
Switched to an external card reader (crap one), no luck.
Switched to using external reader without sd-microsd adapter, no luck.
Running out of options here. I gave my old Nook to my dad, so maybe I can go pick it up for sanity checking... I may try these cards in that one just to verify this isn't a full on hardware issue. That would seem strange and highly suspect given this just so happened to occur when I was attempting to install PA. If I can nail it down to that, I suspect it's somehow my fault, and I will need to replace it. If I can't, then I will need to buy a new CM 7 card from Ebay for the guy.
How do you own a Nook for years with never a single problem you couldn't fix, and the one time you touch someone else's, it goes all to hell?
Click to expand...
Click to collapse
dajmaa said:
brother what to tell you my nook color is also dead similarly since last 3 weeks.i also tried everything under the roof like bootable sd card.i also opened a topic in help section but did not get a single reply.i wrote to lepinllair also but even he does not know what to do . i miss my nook everyday. i appeal to nook community to please help us get out of this mess. i also get similar trying to search divers issue when attached to a laptop.also mine is getting charged fully .so i guess both of us have a similar issue. brother please let me know if you find solution .thankyou
Click to expand...
Click to collapse
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
SHOOTEMUP2.0 said:
Well looks like their is Three of Us. I have been trying to fix my daughters Nook Color for about 2 weeks now. I have tried 6 different sd cards, my internal card reader and 2 external ones. I have used every version of cw recovery and twrp i can find. I have tried alot of guides. At least the ones that the downloads are still there for.
Heres to pulling your hair out.
Click to expand...
Click to collapse
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
majorpay said:
Well, here's what I can say (which may be saying nothing):
Back in the day when I had a BSOD on my old device, I was able to fix it by using TheCube's methods. I don't think he hangs around these parts anymore, but I know it was a specific sized SD card you had to have, and a pretty old version of CWR you were flashing onto the card. I remember there was only ONE version of win32diskimager that would work and it was one of the V 0.1 variants (r?). Technology has changed, people have come and gone, and this may mean absolutely squat now. I just know I had this problem on my old one and I was able to fix it that way.
All the links to those items are gone, all the files have been long since lost, and the server I used to use to house those files has long since become a thing of the past.
Maybe B&N has set trip-wires for the modding community in their "newer" revisions? I cut the red wire, and the whole thing blew up.
Click to expand...
Click to collapse
Story of my life. always a Dollar Short and a Day Late. Well in this case a couple years late.
leapinlar said:
sometimes difficult, keep trying.
Edit, are you following advice in A9, like using external USB card reader?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
majorpay said:
Leap... Have you tested these methods? If so, can you give me a lead as to which SD reader you used? I'm not above believing that the problem is the multiple readers I have (one is internal, the other is a Chinese plastic knock-off).
I was not able to get over to my parents house to test on their Nook yet.
Click to expand...
Click to collapse
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I use an external USB card reader made for micro SDs so I need no micro to SD adapter. A little red or grey one. I got it on eBay for $2. In fact, I bought several since they sometimes quit working. Then I use win32diskimager with no other windows open. Someone said they even had to update to the latest version (0.7, I think) from sourceforge. Any number of things could make it not boot. NCs can sometimes be very temperamental. But I have never had one I could not eventually get to boot to SD.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Scratch that...
I found the files, but now I have an entirely different issue.
My copy of Win32DiskImager back then was very size specific, and although I have a copy of the 16gb_clockwork file I used back then, I can't burn it because Win32DI says the card isn't the right size..
Ugh... I'll keep you all posted.
majorpay said:
Alright... Well here's where we are at this point:
Bought a Dynex 7 in 1 with specific port for MicroSD - burned v6 cwr bootable to 16GB SanDisc C4 SD using Laptop - Didn't work
Switched to main PC and burned 5.5 to 512mb Nokia C4 SD - didn't work.
Both were attempted with latest Win32DiskImager (.7) from SourceForge.
At this point, I'd lean towards a hardware failure, BUT... it's too coincidental that this occurred during a standard CWR install of a ROM. My understanding is that the Nook is supposed to ALWAYS check the SD slot prior to booting internally. Now whether there is a partition block that tells it to do this or not, I've never dug that far, but I'd have to say that this sure makes it look that way.
If that's the case, then the "unbrickable Nook" (which I once believed to be true) is a fairy tale. The fact that several others around here have met with the same fate, I'm almost inclined to believe it. I'm going to go on a hunt for the original files that fixed my first nook. If only I could remember what the heck I did with them.
Click to expand...
Click to collapse
It is possible that it is a hardware failure of the SD slot. Have you tried cleaning it? The booting to SD is built into the OMAP chip and is not effected by what you have in emmc. It automatically looks at the SD slot first to see if a bootable SD is there. But it looks for specific features of the SD found there to be sure it is bootable. If it is not bootable, it tries the emmc boot partition and if valid boot files are not there, it won't turn on.
Sent from my Nook HD+ running CM10.1 on emmc.
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
majorpay said:
Alright, I ended up flashing the old image I used on my last Nook with the same version of win32diskimager I used back then, and still no signs of life.
Unlike the previous issues I had on my first Nook, this one shows no signs of life. No backlit deep black that you can see in the dark, nothing. So I plugged it into my tower PC and held the power for 10 seconds. The install for the OMAP 36xx processor drivers went through the process, but when done, you could not find it in the device manager. So I held the power again for 10 seconds, it showed up for a second, then went away. I repeated this process several times, and same thing each time.
Just to make sure I wasn't leaping to assumptions, I unplugged it and plugged it back into the PC, and no response. Not until I held the power down for 10 seconds again.
So what can we conclude from this? Well, either it is normal for the Nook to show up for a split second on Windows, or the Nook is powering on, then down almost instantaneously. I'm inclined to believe the latter as ordinarily holding the power down for a few seconds wouldn't *reboot* the device, but instead, it would power it down, or power it up (if it was off). Also, unplugging and replugging it in to the PC should have activated the device driver if it was staying on (assuming that isn't a momentary thing on initial startup).
What's the missing piece of the puzzle? I don't know if it's the same for all the other users that have commented, but I don't have the original cable for this device, so I cannot fast charge. A dead Nook will power on, even if drained, when the fast charge cable is used (I believe?). This is something else I will have to try when I get my hands on my dad's Nook. Is it possible that a trickle charge doesn't work below a certain point?
This was kind of my thoughts back when this first occurred - that perhaps the Nook simply lost juice during the install.
Grasping at straws? Perhaps, but straws are all I'm seeing at this point.
Click to expand...
Click to collapse
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
I think what you are seeing is the device powering on with the screen off (like it normally does), looking for boot files in SD and emmc and when seeing none, immediately powering off. That is why the brief driver showing in windows. Ordinarily if it finds those boot files, it turns the screen on and continues the boot.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Bit the bullet and grabbed my dads. It's confirmed, the SD card I recently burned works - CWR booted right up. Now for the stock cable test.
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
I'm done...
I'm beat. Cable turned green again, and no dice. This Nook is headed for the scrap pile (unless I get a wild hair and tear it apart to re-solder some joints).
majorpay said:
Stock cable confirms that the Nook will not power up at all - cable is green indicating full charge. This Nook is toast - so just coincidence that it was during flashing PA? Hard to believe, but haven't I ruled every other possibility out?
EDIT - moved the cable and it turned orange. Coworker confirmed that his Nook charger he was using wouldn't even charge a phone I loaned him. May be on to something here. I'll wait until the cable turns green.
Click to expand...
Click to collapse
I went back to your OP and re-read. It is very common for an installation to screw up and lock up, leaving the boot partition borked. But usually the user can boot to a bootable CWM and re-flash and it repairs it. Ordinarily I would say that the slot could have been messed up for a long time too, since a lot of users have CWM on emmc and would not know it until they needed a bootable card. But in your case the slot was working right up till after you put CWM on emmc. And your using internal memory to flash the zip from and leaving the SD in the slot is usually of no consequence. But it is remotely possible since you left the SD in and the software was running amouk, that it did something to the SD and the slot, like overcurrents or some such nonsense. I still think the not booting from SD is a slot hardware issue since your card boots on other devices and the booting code is in chip firmware.
Sent from my Nook HD+ running CM10.1 on emmc.
Hello All,
Im Hoping Someone Would Be Able to Help me with an issue....
ive got the samsung galaxy s5 SM-G900I with telstra here in Australia, on the 26th of last month i went to my fathers wedding, i was taking photos on my phone with the camera it spent most of its time on the camera app (once closed itself down prob due to inactivity) anyways after a while it stopped taking pictures.... the capture button on screen was grayed out but i could still see through the camera.... i though ok weird and closed the app down and opened it with the same result... then a popup came up that said "Camera Failed" when i pressed ok the camera app closed.... tried to bring it up again and it was a no go so i decided to reboot my phone..... it shut down properly but never turned back on so i though ok maybe it turned itself off so i tried to turn it back on and got nothing..... i pulled the battery out and put it back in and the phone turned on and the camera was working perfectly fine again so i though oh ok glitch but all good.... anyways i went back to taking and i found that all the pics i had taken that day were gone from the SD card...
it took me a minute to relize that all the photos on my card were gone.... i went to investigate and say that the card wasnt mounted under storage and i though all good again and hit mount and nothing happened.... then i saw a notification saying either an unformatted card or an unsupported file system... i checked in another phone with it and got the same issue and it seemed the card had gone bad, anyway i got home that night and plugged the card into my computer and found that the card was reading up as a raw file system.... so i went stright to data recovery but before the data recovery could finish scanning the card all of a sudden there was my sd card reading up perfect in my laptop... which was weird to me as i havnt seen that happen before, so i backed up everything on my card to my computer and plugged the card back into my phone and it came up with a different error i think it said something about the card maybe being corrupt.... so i put it back into my computer and ran a chkdsk on it and it showed that everything on the card was corrupted..... so i decided to wipe the card and start again and i transfered everything back onto it and everything was working perfectly fine as if nothing had happened...anyway fast foward to monday this week and i went to take some photos and recorded a video on my phone (went stright to the SD card) and i checked it afew hours later because i got busy and i had found that everything i had done that day had corrupted and photos that i had taken about 4 or 5 days ago were also corrupted... images that i had seen to be working fine.... so i backed up my SD card again and though ok im gunna have to buy a new sd card and i redirected the save location for photos back to internal storage.... anyway today my SD card was still in my phone... all of my music is on it still and i was listening to music while i was heading out to the shops.... and i noticed that afew of my songs were playing for a second or 2 then skipping to the next or just pausing and throwing an error about the song being corrupt...
so i put the SD Card into my Samsung Galaxy Tab S and the songs that were "Corrupt" on the SD Card were working fine on the tablet..... so i am wondering.... is it the SD Card or the Phone?
thanks Help would be amazing!
paul118 said:
Hello All,
Im Hoping Someone Would Be Able to Help me with an issue....
ive got the samsung galaxy s5 SM-G900I with telstra here in Australia, on the 26th of last month i went to my fathers wedding, i was taking photos on my phone with the camera it spent most of its time on the camera app (once closed itself down prob due to inactivity) anyways after a while it stopped taking pictures.... the capture button on screen was grayed out but i could still see through the camera.... i though ok weird and closed the app down and opened it with the same result... then a popup came up that said "Camera Failed" when i pressed ok the camera app closed.... tried to bring it up again and it was a no go so i decided to reboot my phone..... it shut down properly but never turned back on so i though ok maybe it turned itself off so i tried to turn it back on and got nothing..... i pulled the battery out and put it back in and the phone turned on and the camera was working perfectly fine again so i though oh ok glitch but all good.... anyways i went back to taking and i found that all the pics i had taken that day were gone from the SD card... it took me a minute to relize that all the photos on my card were gone.... i went to investigate and say that the card wasnt mounted under storage and i though all good again and hit mount and nothing happened.... then i saw a notification saying either an unformatted card or an unsupported file system... i checked in another phone with it and got the same issue and it seemed the card had gone bad, anyway i got home that night and plugged the card into my computer and found that the card was reading up as a raw file system.... so i went stright to data recovery but before the data recovery could finish scanning the card all of a sudden there was my sd card reading up perfect in my laptop... which was weird to me as i havnt seen that happen before, so i backed up everything on my card to my computer and plugged the card back into my phone and it came up with a different error i think it said something about the card maybe being corrupt.... so i put it back into my computer and ran a chkdsk on it and it showed that everything on the card was corrupted..... so i decided to wipe the card and start again and i transfered everything back onto it and everything was working perfectly fine as if nothing had happened...anyway fast foward to monday this week and i went to take some photos and recorded a video on my phone (went stright to the SD card) and i checked it afew hours later because i got busy and i had found that everything i had done that day had corrupted and photos that i had taken about 4 or 5 days ago were also corrupted... images that i had seen to be working fine.... so i backed up my SD card again and though ok im gunna have to buy a new sd card and i redirected the save location for photos back to internal storage.... anyway today my SD card was still in my phone... all of my music is on it still and i was listening to music while i was heading out to the shops.... and i noticed that afew of my songs were playing for a second or 2 then skipping to the next or just pausing and throwing an error about the song being corrupt... so i put the SD Card into my Samsung Galaxy Tab S and the songs that were "Corrupt" on the SD Card were working fine on the tablet..... so i am wondering.... is it the SD Card or the Phone?
thanks Help would be amazing!
Click to expand...
Click to collapse
Whoa. That would be painful to read. Can you break that into paragraphs?
.
fffft said:
Whoa. That would be painful to read. Can you break that into paragraphs?
.
Click to expand...
Click to collapse
sorry about that.... not the best when it comes to that lol, i just edited it i hope it makes it easier to read
I'm not trying to give you a hard time, but that is still hard to read. If I got the gist of your post, you had a camera failed message and apparently SD card corruption.
There isn't enough information (or maybe it's in the middle of those paragraphs) to tell what happened. Probably just a temporary glitch, but you could have anything from an actual camera failure to a physical SD card defect.
Try clearing your system cache. I wouldn't worry about the failed camera message if it doesn't recur. If it does, search for the camera failed threads, Samsung was providing warranty replacements for some early production camera failures.
If you are searching for photos, see if your phone put them on the internal sdcard (since the external SD wasn't accessible). Otherwise you could consider a data recovery app to see if photos can be recovered from your external SD card.
Is your external SD card bad? We don't have enough information to know yet? Do a search for an app to test the card integrity or you can probably use the fsck command to test the card and correct (if possible) filesystem errors, followed by reformatting and remounting the card. The fact that the card was readable on another device doesn't differentiate between an marginal or unstable card and a sound card. You'll have to test and reformat the card to really tell.
.
fffft said:
I'm not trying to give you a hard time, but that is still hard to read. If I got the gist of your post, you had a camera failed message and apparently SD card corruption.
There isn't enough information (or maybe it's in the middle of those paragraphs) to tell what happened. Probably just a temporary glitch, but you could have anything from an actual camera failure to a physical SD card defect.
Try clearing your system cache. I wouldn't worry about the failed camera message if it doesn't recur. If it does, search for the camera failed threads, Samsung was providing warranty replacements for some early production camera failures.
If you are searching for photos, see if your phone put them on the internal sdcard (since the external SD wasn't accessible). Otherwise you could consider a data recovery app to see if photos can be recovered from your external SD card.
Is your external SD card bad? We don't have enough information to know yet? Do a search for an app to test the card integrity or you can probably use the fsck command to test the card and correct (if possible) filesystem errors, followed by reformatting and remounting the card. The fact that the card was readable on another device doesn't differentiate between an marginal or unstable card and a sound card. You'll have to test and reformat the card to really tell.
.
Click to expand...
Click to collapse
thats ok i know your not trying to give me a hard time on it im sorry that its so dificult to read, ill see if i can try this alittle better
on the 26th of last month i was taking photos for my fathers wedding when the camera stopped working, it wouldnt let me take photos so i closed the camera app and opened it again thats when i got the camera failed message
i tried to reboot my phone but it froze during the reboot and didnt start up again so i pulled the battery out and put it back in, when the phone started up again the camera was working perfectly fine but the SD card was coming up as unreconized file system or unformatted,
i got the SD card to my Laptop and the File System Read up RAW i started data recovery and while it was scanning the card everything started working again and i got all my photos back without the need for using data recovery
put the SD card back into my phone and it read corrupt so i reformatted it and restored everything back into it and the card worked fine,
Fast Foward to Monday This Week and i recorded a 10 minute video at 1GB size and took some photos.... and they corrupted.... no issues with the camera or anything like that.
Today i Was Listening to Music that was stored on my SD Card (64GB Class 10 Transcend) and it skipped a song about 2 seconds into it and another song it tried to play and failed coming up with an error about it being corrupt, ive taken the SD Card out of my phone and put it into my Samsung Galaxy Tab S and the songs that were "Corrupt" worked perfectly fine on my tablet
so im wondering if it could be the SD Card or the Card Reader in the Phone? the System Cache in the phone has been cleared.
Thanks i hope thats helped you able to understand it better and again i am sorry for my poor writeing skills
paul118 said:
Today i Was Listening to Music that was stored on my SD Card (64GB Class 10 Transcend) and it skipped a song about 2 seconds into it and another song it tried to play and failed coming up with an error about it being corrupt, ive taken the SD Card out of my phone and put it into my Samsung Galaxy Tab S and the songs that were "Corrupt" worked perfectly fine on my tablet
so im wondering if it could be the SD Card or the Card Reader in the Phone? the System Cache in the phone has been cleared.
Click to expand...
Click to collapse
Thank you for going through that again.
The basic question or mystery that we are trying to solve is why does the external SD card only appear to have problems in your phone and not the tablet? And how can we tell if it is a card issue or something other aspect of your phone?
While it could be some problem with your phone e.g. bent or damaged SD card slot, corrupt driver or other causes.. it would be hard to track down without further hints. i.e. there are so many possible causes that we need to narrow it down.
So it's easier to tackle this by elimination. Lets test the hell out of the card because that is easier to do.. and despite the fact that it appears to work in your tablet, it's still more likely to be a card problem. Why would it only affect your phone and not the tablet if it is a card problem? There are lots of reasons, but just to give one example.. it could be a problem on just one area of the card.. and that happens to be where your phone is preferentially storing files.
If that makes sense so far.. then the plan is to see if we can identify a card defect. So.. grab an app that will check for file system errors (chkdsk, fsck, etc), check partition structure and do extended read /write tests on the card. At a glance perhaps one of these apps: Lewy or Dewy.
Most likely you have some bad clusters which fsck or chkdsk could repair. But it's best to run an extended card test.. that may take a few hours but it's still a lot quicker than trying to search for all the possible causes of phone problems. If your card passes with no issues.. I'd be inclined to back up your phone and then install a brand new, 100% fresh and stock firmware temporarily. That should in one swoop tell you if it is a hardware or software issue. Again, we are looking for expedient ways to narrow down the possible causes.
.
i will give u a hint ... try to make your topics, in your case, a loooooot less than your post so a lot more people would help you.
fffft said:
Thank you for going through that again.
The basic question or mystery that we are trying to solve is why does the external SD card only appear to have problems in your phone and not the tablet? And how can we tell if it is a card issue or something other aspect of your phone?
While it could be some problem with your phone e.g. bent or damaged SD card slot, corrupt driver or other causes.. it would be hard to track down without further hints. i.e. there are so many possible causes that we need to narrow it down.
So it's easier to tackle this by elimination. Lets test the hell out of the card because that is easier to do.. and despite the fact that it appears to work in your tablet, it's still more likely to be a card problem. Why would it only affect your phone and not the tablet if it is a card problem? There are lots of reasons, but just to give one example.. it could be a problem on just one area of the card.. and that happens to be where your phone is preferentially storing files.
If that makes sense so far.. then the plan is to see if we can identify a card defect. So.. grab an app that will check for file system errors (chkdsk, fsck, etc), check partition structure and do extended read /write tests on the card. At a glance perhaps one of these apps: Lewy or Dewy.
Most likely you have some bad clusters which fsck or chkdsk could repair. But it's best to run an extended card test.. that may take a few hours but it's still a lot quicker than trying to search for all the possible causes of phone problems. If your card passes with no issues.. I'd be inclined to back up your phone and then install a brand new, 100% fresh and stock firmware temporarily. That should in one swoop tell you if it is a hardware or software issue. Again, we are looking for expedient ways to narrow down the possible causes.
.
Click to expand...
Click to collapse
Im Sorry it took so long to reply to you, The 2 apps u suggested did not work they wouldnt detect the SD Card, i put it into my laptop and backed up my data and i ran a chkdsk on it and it came back clean said nothing was wrong with it, i have hard disk sentinel installed on my laptop and ive run a surface scan on it that is doing read write read test selection on 2 passes and has been running all day.... the first pass came back clean on it but the second pass has picked up 4 bad blocks near the end of it... its come up "7/08/2014 9:43:09 PM ! Verify error, Sector: 99480300" afew times with different sectors on it, im wondering if the camera issue i experenced could have caused my card to screw up like this? or even the phone not booting back up without taking the battery out first after the camera issue happened? would you consider Transcend a good brand for SD Cards? mine was a Transcend Premium 300X Class 10 Micro SD Card 64GB, im thinking of getting a 64gb Samsung Pro Micro Sd Card now... are those good?
Hey mate! finally i have someone who has the same issue as me! this happened to me last week. i was going through my photos and they looked to be all corrupted. i didnt take much notice as i didnt really need them. i was at the gym and my music was all gone. it was all saved to my samsung 32gb SD card. i got home and there was a message saying SD card is damaged. i lost everything. i did a format and nothing happened. it still said SD card failed.
i went and bought a new Samsung Evo 32gb SD card and it is doing the same thing. i plug it into my laptop it works fine. when i chuck it back into my s5 it says its corrupt. i have no idea whats going on. SD card reader in the phone maybe damaged somehow? i dont i have ever dropped my s5. its driving me mad.
My wife's 64GB card is now doing the same. Formatted and working twice. Images all saved to cloud but a pain waiting for it to happen again.
Ordered a new 64GB card today. Hoping that sorts the issue. If not its return to store time. Happy knox is intact.
Sent from my Galaxy S5 running NeatRom 0X1
my galaxy S5 does not read SD card also..
i think most likely is the software issue.
Just wanted to chime in here. I have a hardware failure with my s5 SD reader, and it was my fault. I had to replace my digitizer, hence putting My Straight talk sim into a temp phone for a fee days.
I cut my sim down to nano size for the temp phone, then stuck the now nano sim back in the s5 after repair, I didn't have a sim converter, and ended up bending pins. Thankfully the sim still works but I toasted my SD slot. Not only will it not read any SD card, it breaks any working one i put in it. I'm a hardware guy, so I'm going to give a go at fixing it, but I'm pretty sure the whole assembly is soldered to the board, no replacing this assembly. At least I don't believe so.