I just purchased a Samsung Galaxy S9 + in April, replacing my Samsung Galaxy S5. I was using a 32 Gig SanDisk SD card which I encrypted in the S5. I decrypted the SD card in the S5 and inserted it into the new S9+. No problems, it was recognized and I could read/write to it.
2 weeks ago, I decided to encrypt the SD card in the S9+. I went into Security, and Encrypt SD Card. A short while later, the phone displayed a message that my SD card was now encrypted. Nice! I re started the phone, etc...
The next day, I decided to verify the encryption. I removed the SD card and popped it into my laptop. (phone not connected in any way to the computer) I was shocked that I could read all the data! I put it back into the phone and sure enough, the phone said that the SD card was encrypted.
I then re formatted the SD card in my laptop, tried again encrypting it in the phone. Phone displayed that it was now encrypted, but NO, I could still read the data from my laptop. I even tried from a different laptop. I have restored the phone back to factory defaults maybe 5 times, testing the encryption, still each time the phone says the SD card is encrypted, but it is still readable from any computer.
I drove to the T-Mobile Store and let them know. They verified that I did everything correctly, but said I needed to call Samsung. Samsung sent me to see the Samsung rep in a Best Buy about 40 minutes from my house. Not pleased, but I went. The rep had no answer for me. Said I needed to go back to T-Mobile to get a new phone.
I called Samsung again. They asked me what kind of SD card I was using. I said it was a SanDisk, but it is working fine, I could read and write to it. He insisted that Samsung suggests the Samsung EVO Class 10 SD cards.
So I went out and purchased a Samsung EVO Class 10 64 Gig SD card. Again, restored the phone to default, encrypted the card, but still readable from my laptop!
I went back to T-Mobile and demanded a new phone. It was a real battle because it has been 45 days or so. They wanted to send my NEW phone out for "repair". Not going to happen, give me a new phone. They did.
Put the new SD card into the phone, encrypted it, took it out and tested it on my laptop, ALL DATA STILL READABLE!
I called Samsung again, (3rd call) After much discussion, the woman called their support service center. She came back and said that they are getting reports of this and that they are working on an update and it will be released in the future. I asked when??? She could not tell me. And when it is released, how soon will it roll out to T-Mobile users?
She could not tell me. She transferred me to another tech. He asked me to send it in for repair. I told him I did not want to do that, it was a brand new phone, both of them! I asked him to call the service center. He did and came back and said it was not a common issue and my phone needed to be repaired.
!??? I said that I have two brand new phones, right out of the box, 45 days apart, and I just happened to get the two phones with this problem?
He then said that I needed to send my new phone to a 3rd party vendor, that is not even a Samsung company. ( "u break, we fix" or something like that ) Then gave their phone number so I can call, get an appointment, call them for a shipping label etc. I was shocked!!!
*** To ANYONE that has an SD Card that you "think" is encrypted, test it! Take it out of your phone and see if you can read the data from a computer. If it is readable, call Samsung, or your other phone manufacture. This is not an isolated case. I just by sure luck did not get the only two Samsung S9 + phones with this problem, 45 days apart!
I said to Samsung, can you imagine how Samsung is opening themselves up to liability? There are thousands and thousands of people (probably) who have SD cards in their phones, that their phone says is encrypted, but it's really not!
I have a brand new S9+, that I can't trust to use it.
Does anyone have any ideas?
Please also post your message to the phone boards so hopefully they will take notice.
You might want to try that again. In a previous test I did, the whole card isn't encrypted, but the files themselves were. You can still see the directory structure and such, but try and open a JPG or MP3 file on the card and it won't work. Each file is hashed in some way that it can't be read in any useful way by the computer.
did test as suggested...
Averix said:
You might want to try that again. In a previous test I did, the whole card isn't encrypted, but the files themselves were. You can still see the directory structure and such, but try and open a JPG or MP3 file on the card and it won't work. Each file is hashed in some way that it can't be read in any useful way by the computer.
Click to expand...
Click to collapse
I took your suggestion and can confirm that I could not actually open any "file". Though I could see the complete file structure, folders and subfolders, and individual filenames. But I could not open any files.
It shocks me that NO one from T-Mobile or Samsung suggested looking into this.
While this is of some comfort, I still feel that this is a huge security and privacy issue. After reading your reply, (by the way, a huge thank you) I saw this:
---snip---
General-purpose file systems with encryption
Unlike cryptographic file systems or full disk encryption, general-purpose file systems that include filesystem-level encryption do not typically encrypt file system metadata, such as the directory structure, file names, sizes or modification timestamps. This can be problematic if the metadata itself needs to be kept confidential. In other words, if files are stored with identifying file names, anyone who has access to the physical disk can know which documents are stored on the disk, although not the contents of the documents.
---snip---
This is probably what Samsung is doing. Again, I still feel that this is a huge security and privacy issue.
Thank you again…
I agree this revelation is a bit disturbing.
ingenious247 said:
I agree this revelation is a bit disturbing.
Click to expand...
Click to collapse
I mentioned in my reply that the the fact that a file in a folder was not readable was of some comfort. I have thought about it a lot today and I have to say it is NOT of any comfort. The fact that any encrypted drive or file is readable is not acceptable or secure. Imagine this, if you are like me, I end up taking pictures or scanning receipts and saving them to my phones memory card.
Why not, it's encrypted and secure!
What if a Samsung Galaxy S9+ was stolen or lost, OR if someone at work or even a family member took a phone and popped out the sd card and put it in their computer, imagine what they may find just by looking at the folder and file names? They do NOT have to open the actual end file to find out so much about you?
What if your "encrypted sd card" file structure was like this:
Medical > Cancer Screening > Test Results > MakingAWill.doc
Local Funeral Homes.htm
Survivor Benefits. pdf
Does it really matter that you can't open or read "MakingAWill.doc" or "Local Funeral Homes.htm" ???
No! What good is a so called encrypted drive if you can just pop out the sd card and view all the folder and file names? Where is the security!???
Has anyone else tested this and verified their sd card / expanded memory encryption? If so, could you please post your results? Can you read the file and folder names / file system?
Samsung REALLY needs to address this. This is a huge privacy and security issue.
Related
I plugged in my Vibrant through it's stock cable and click "yes" so I could copy some photos into my Vibrant but when I turned off the mass USB storage, Avatar was no longer there.
I did NOT touch the SD card or even opened it up in Windows so I have no clue as to why it's not showing up, it looks like the SD card has all of it's free space available though. Is there someway to re-download avatar? I got my phone yesterday but this sucks if I can't.
Not sure but u could try and ask a new phone lol like buyers remose
Sent from my T-Mobile G1 using XDA App
you can't get it back, just go to the tmobile store and say that the movie never worked. don't tell them you did anything, that it came like that and they have to give you a replacement SD (they did to me when I messed up my avatar movie tryin to copy it to another SD)
Awww.. Also where can I find the 9 digit BAN to fill the rebate form? I have thebox and the papers T-Mobile printed out as my receipt
I had this happen to me too. Good thing I backed it up to my computer when I first bought the phone. But also, I have noticed that for some reason, this phone will delete files on its own sometimes. I've had pictures & video's gone missing without me doing anything.
dq13 said:
you can't get it back, just go to the tmobile store and say that the movie never worked. don't tell them you did anything, that it came like that and they have to give you a replacement SD (they did to me when I messed up my avatar movie tryin to copy it to another SD)
Click to expand...
Click to collapse
i just copied the avatar movie to another sd with no problem. i wonder how that happen to you
Could it have been an ID-10-T error?
I work at a t-mobile store. I had enough customers come in with issues concerning that movie file that I ended up making a copy of it to provide an easy remedy. Some people don't realize that the movie is on the SD to begin with and they toss it in exchange for a larger one. I figure that its simpler to just copy the movie to the new card instead of hassling with exchanging phones/sd cards out.
Anyway, I would just go in to your local store and see if anyone working that day has a vibrant with them (if not see if they have one that was returned). If they're nice/competent, perhaps you can just have them make a copy for you.
As for your BAN, it is normally printed on the receipt (listed as account number or similar iirc). If not, you can get it through the online account management or by calling 611.
Hello all. Iam new to this, but I am hoping someone can help me out.
I have a Samsung Galaxy Note II from Verizon. I have installed a San Disk 32gb MicroSD card. I used the phone to format the card. I then created folders for music, photos, videos, etc. Next I set these new folders as the defaults for these file types, so that any music and photos, ect, will be stored on the external MicroSD card.
Now my problem: I copied all of my music files (about 1400, all in MPG3 format) to the music folder on the MicroSD card. However, when I attempt to play the music, a song will play for a second or 2, then jump to another song. It keeps doing this. If I play the song (stored on the phone) on my laptop (phone is connected via USB) it does the same thing. It will play a second or so, then stop.
I have deleted and recopied the music several times, I have turned the phone off then back on, nothing seems to help. Sometimes, after attempting to play music on the phone, and it reacts this way, I'll go back to the music folder, and suddenly it shows about 330 songs, not 1400 that were there before. A little while later, it will show all 1400 songs, but they still won't play properly.
I don't know if there is something I need to do with the phone, or the MicroSD card. I also noticed that 4 of my photos in my "images" folder would no longer display on the phone. After re-starting the phone, the 4 image files were gone completely.
This is driving me CRAZY!!! Someone please help!!
Thank you all very much for your support.
Bob
Oops!! I titled this thred as "MicroDS" instead of "MicroSD". Sorry
Is it a new card? One from Ebay or other unreputable seller? If so, you may have been scammed. Google "h2testw", it is a free program used to verify USB memory. It wirtes the entire drive full of data and then attempts to read it back. It will quickly uncover a fake SD card.
If that is not the case, then I don't have any ideas. The symptoms sure sound like a fake card though. The really crappy thing about the fakes is a lot of people loose valuable data when they move stuff to one of these cards. It all looks like it is there, but nothing beyond a few Kb transfers. Most of the time these are 4gb or smaller cards that have had some hacking done to display themselves as much larger. After the actual memory size is full, the file index continues to register files written, but they are physically not there at all.
Good Luck,
Jason
jacampb2 said:
Is it a new card? One from Ebay or other unreputable seller? If so, you may have been scammed. Google "h2testw", it is a free program used to verify USB memory. It wirtes the entire drive full of data and then attempts to read it back. It will quickly uncover a fake SD card.
If that is not the case, then I don't have any ideas. The symptoms sure sound like a fake card though. The really crappy thing about the fakes is a lot of people loose valuable data when they move stuff to one of these cards. It all looks like it is there, but nothing beyond a few Kb transfers. Most of the time these are 4gb or smaller cards that have had some hacking done to display themselves as much larger. After the actual memory size is full, the file index continues to register files written, but they are physically not there at all.
Good Luck,
Jason
Click to expand...
Click to collapse
Hi, I really need help with this. I have the exact same issue except that I've tried 3 different 64gb sd cards now (from 2 different sellers on eBay) and have had the same results. I've tried different methods of transfer and different file types, same thing every time. The h2testw program doesn't detect my phone (phone mem or sd card) so I can't use that.
Now, I will say, all of these cards were ~$30 but were bought from high-rated sellers. Did I just happen to buy 3 hacked cards in a row?
SpizNastee said:
Hi, I really need help with this. I have the exact same issue except that I've tried 3 different 64gb sd cards now (from 2 different sellers on eBay) and have had the same results. I've tried different methods of transfer and different file types, same thing every time. The h2testw program doesn't detect my phone (phone mem or sd card) so I can't use that.
Now, I will say, all of these cards were ~$30 but were bought from high-rated sellers. Did I just happen to buy 3 hacked cards in a row?
Click to expand...
Click to collapse
Same here bought my from ebay 35 bucks first day popped into phone was fine phone read the card. Then i rebooted to flash aosp rom no go with card trued different computers some read card some dont and tryingbto format i get errors or cant complete action. In read on line you can format with a digital camera to UN corrupt the card will try later and report back . I you can try before that would be nice. I have 9 hrs left at work so.
Sent from my SCH-I605 using xda app-developers app
Get a micro SD USB adapter and do H2Wtestw. The phones only mount MTP or PTP, you cannot run the test on the card in the phone, it has to be mounted as a USB mass storage device on the PC, and yes, I have no doubt that you got three hacked cards in a row. Virtually every high capacity card on ebay is fake. Most people see it mounts as the listed size and leave good feedback, it's too late to adjust your feedback when it eats all your data. Do some research, it is well documented out on the internet as to how many counterfiet cards are out there on eBay.
Later,
Jason
I have had similar problems with a lexar 32GB card. I noticed that when I copied files using the phone to transfer the files that many were incomplete. To verify this open a file browser and check the file sizes. I have another problem with my MicroSD as well. I randomly get an error stating that the card is damaged and needs formatted. I changed the format to exFat which has slowed the problem but it still does this occasionally. I an going to RMA the card and see if another card will perform better. I hope it isn't a problem with the phone because I don't feel like wasting time dealing with returning it to stock and setting up new one.
Is there a a good brand to buy like samsung ..also what does the card(say 64gb) need to be formatted to??
mobius0322 said:
Is there a a good brand to buy like samsung ..also what does the card(say 64gb) need to be formatted to??
Click to expand...
Click to collapse
Samsung, Sandisk, etc. The key is ONLY buy it from someone reputable, i.e. direct from Amazon, NOT one of their resellers, and NOT from eBay. There is no free lunch. A 64GB Class 10 will cost you $50-$60, if its less do NOT buy it, its a knock-off.
Sandisk comes preformatted as exFAT. This is compatible with Samsung Touchwiz and TWRP recovery. It allows very large file sizes.
CM, ASOP roms, and CWM recovery do not support exFAT. You will need to format to Fat32 if you plan to use them. There is a file size limit of 4GB, and you will need third party software to format 64GB on Windows.
micro sd
alistairs1 said:
Samsung, Sandisk, etc. The key is ONLY buy it from someone reputable, i.e. direct from Amazon, NOT one of their resellers, and NOT from eBay. There is no free lunch. A 64GB Class 10 will cost you $50-$60, if its less do NOT buy it, its a knock-off.
Sandisk comes preformatted as exFAT. This is compatible with Samsung Touchwiz and TWRP recovery. It allows very large file sizes.
CM, ASOP roms, and CWM recovery do not support exFAT. You will need to format to Fat32 if you plan to use them. There is a file size limit of 4GB, and you will need third party software to format 64GB on Windows.
Click to expand...
Click to collapse
Ok thank you.i found out the hard way about the ebay cards.I'm running jellybeans 12 and TWRP recovery.
First, sorry for my bad English. Hope I make myself clear enough for you to understand me.
Second, to the moderators: feel free to move this topic if I posted it on the wrong session. But as you will see reading the following, I believe that the issue I will describe is directly related with the Neatrom - correct me if I'm wrong, but I have reasons to believe that.
So, here it goes:
I have a Samsung Galaxy S2 (i9100), running XXLSJ Neatrom Lite v4.0, and this kernell: 3.0.31-Siyah-s2-v6.0b4+
In december 2012, I bought a MicroSD card (model Sandisk Ultra 32Gb class 10) to install in my i9100, and it rocks.
But 4 weeks ago, when I was playing some games on the phone, I ignored the first battery low warning messages, and kept playing to a point that the phone simply turned off. Completely. I recharged the battery and, after powering the phone on again, it showed a message saying something like "blank sdcard" or something. I had many pictures and important movies on that card, so I decided to not format it; instead, I searched for a way to fix it.
I tried to access the files from my computer - on Windows, no success; on Ubuntu, no success; on Mint, no success. Windows and Linux showed the icon representing the sdcard, but when I tried to open it under Windows, it showed a message saying "this disk is not formated. Do you want to format it?". Linux didn't show any message, and didn't opne a single window to show its content. Nothing. Nada.
Then, my cousin (a geek genius) took my card to test it on his own notebook. He made some long research on the net, and installed a software called TestDisk (http://www.cgsecurity.org/wiki/TestDisk - linux version) to try to recover the partition (or the MBR, I don't know exactly the tech name of this stuff...). He even entered on the software the number of cylinders, sectors and all that stuff to try to achieve sometuing... But after almost two hours reading tutorials, and trying hard to bring that card back to life with no success, he finally gave up, telling me to RMA the sdcard.
Then, I took the card from his hands, and put it aside, giving up too. Half an hour later, accepting the fact that my files was gone forever, I decided to try to format the card on my phone, to see if it would work after being formated. So, I put the card on the phone again, and powered the phone on... And, for my surprise, the card was back to life! For no reason, it decided to work again! With all the movies, all the pictures, all the games, everything was there, untouched!!!!
So, it worked great in the last 4 weeks, fast and nice - recording long HD movies, taking hundreds of pictures, installing huge data games, etc. It worked fine - until two days ago.
Because, two days ago, I was playing again, and again I ignored the low battery warnings, and it happened again! In the middle of the game, the battery ran out, and the phone turned off. Guess what? Yeah, after recharging it and turning it on again, there came that same message, telling me that my sdcard was blank! Again, no success trying to access it from Windows or Linux. And no geek cousin nearby...
(Of course, I had a backup of my files, created just after that first "death").
so, I sent an e-mail to my cousin, asking him about the software he used, and how it used it. He told me about that testdisk software. I downloaded the Windows version of the software, and give a try - no success. The program didn't recognize the drive letter of my "blank" sdcard, because the filesystem was simply not listed by the program. So, I went to the site, and I read that, under Linux, it was possible to force Testdisk to try to repair filesystems that was not shown in the list, by using a command line telling the software to look for the device through this mounting point (a folder inside /dev/). Linux stuff, I wont go any deep on this here.
So, I decided to restart my notebook, to boot on Linux to try that method. Guess what again? Suddenly, Windows recognized the sdcard again! I just ran the TestDisk utility, with no success - no command was used, I just ran the program, and since it didn't recognize the card, I closed the program. Nothing was done.
But, given the fact that the card was dead twice in the exact circumstantes (battery wearing completely off), and given the fact that the card came back to life after a simple run of the software TestDisk, I refuse to believe that it was a simple coincidence; I am not a geek, not a linux or android expert, nor a hardware wizzard, but my little experience tells me that it is possible that the android system locked the SDcard filesystem in a way that, after a sudden energy cut, it needed some sort of "logical shock" (made by TestDisk, even without any changes or command being called by the user, thats me).
I believe that this issue is part NeatRom's (or maybe kernell's) fault, because in stock roms, the system would close the app and close all sdcard access before turning the phone off to prevent issues like this one.
Again, I must repeat: I am not a technician, not an expert, so chances are I am wrong - very wrong. But I believe that my suspicions makes some sense, and woths to be investigated - or cleared out. And, of course, chances are that the card is deffective - and I already called RMA service from Sandisk. And I made another backup right now. But, I insist: everything is working: no movie corrupted, not a single file is corrupted... So, I still have a doubt here: was this issue cause by a deffective card, or was it cause by the sudden turn-offs?
Before you ask: no, I didn't test playing to the end of battery using another sdcard. By the way, I will never play to this point anymore. And yes, the card is still working!
Sorry for the VERY LONG POST. But I think that this testimonial may be of some value to the rom and kernell developpers.
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Galaxy s2 said:
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Click to expand...
Click to collapse
Not the rom itself, but possibly some "features" of this or any other rom related to how it handles battery. I will try to make myself as clear as possible...
I know that in stock roms it is not possible to shoot photographs using flash when battery level is under 15% - this is to prevent sudden turn-off of the phone. And I know that some roms uses some tweaks that allows the user to take pictures using flash under this 15%. This is a thing that most users can think is an improvement - but we know that it is dangerous to use battery in a not-so-controled way. The history I told on the first post is a prove of it!
So, my suspictions is that, in some way, some rom configurations (or kernell configurations) may be allowing the user to play a high-power-demanding game or app to the end of battery charge - when, instead, it should close all the apps after the first warning, and before shutting down the phone. In other words, some roms let the decision up to the user - and if the user is (like me) distracted with some game, and forgot or bypass the first warning, he becomes a victim of this own distraction, wearing all the juice without thinking about closing the apk and shuting down the phone in the correct manner.
So, the question is: are there some rom tweaks that could POSSIBLY be the reason for this kind of issue?
Hope I made myself clear now, despite my horrible "engrich"...
I've tried pretty much everything so far. Suddenly, it doesn't allow any more writes. Any songs and files currently present work with no issues. Anything downloaded/pushed through adb is either corrupted (songs are out of sync, music is all fuzzy) or just won't open altogether (parsing error).
Deleting any file works, until the card is reset. After that, all the deleted files are restored. Any pushed files will also be deleted after a remount.
I'm trying chkdsk right now but I can't format it in any possible way, and the write protected switch on the SD card adapter is OFF.
SD card is sandisk ultra, class 10.
Any ideas what else to try? To format I've tried windows, guiformat and SDformatter.
SD card is 64GB, FAT32 and 32KB allocation size.
Also, anything copied from the SD card to windows works just fine.
In fact, the last recorded files are some photos, dated 13/4 (13 of april). I have no idea why it has suddenly stopped the write cycles.
If formatting through phone, it'll 'format it successfully', but instantly after it'll show that the same space is used as before, so no rewrite actually happened.
It's driving me insane now.
Search exact same post and the answer .
jje
JJEgan said:
Search exact same post and the answer .
jje
Click to expand...
Click to collapse
I'm not sure what do you mean, for I have searched high and low and tested a lot of the 'solutions'.
Could you please point me to another solution before I decide the card is trashed altogether?
JJEgan said:
Search exact same post and the answer .
jje
Click to expand...
Click to collapse
OK, @JJE, your post doesn't help at all. It would make a lot more sense if you took a few extra seconds to specify WHICH POST (like add the link) so we can get to the solution you're talking about.
@Choristav: I had the exact same problem, with the exact same MicroSD card, went through the same motions of attempted fixes and frustration. Ultimately, I had to just return the card under warranty (and that too, physically go to the location so I could see them destroy the card since it contained private data that just wouldn't go away!). I decided to exchange for 2 x 32GB cards instead for use on cameras/handicams.
I had another new MicroSD card of the same make which I used successfully thereafter for about 6 months, but the same problem has resurfaced! That just leads me to think that these Sandisk Ultra Class 10 Micro SDXC cards have a problem, at least while using on smartphones.
So in short, I hate to say this, but I think the card has gone defective so your solution may lie in just availing the warranty for it. Before I return my second card though, I will spend some time looking around, over the next couple of days, to see if I find a simpler solution (like if there's some way to successfully "unlock" and format the card) and if I find it, I will post the link to the solution. Cheers!
I had the same problem with my SanDisk card.. After being so frustrated, I bought a new sd card, this time from Samsung and it's working fine. Btw the SanDisk support is crap: they asked me if I know how to insert the card in my pc or how to open it and I was like.... Shut up ?
Crappy model... needs to be recalled!
lil11b said:
I had the same problem with my SanDisk card.. After being so frustrated, I bought a new sd card, this time from Samsung and it's working fine. Btw the SanDisk support is crap: they asked me if I know how to insert the card in my pc or how to open it and I was like.... Shut up
Click to expand...
Click to collapse
Yes, SanDisk support was asking me dumb questions too and sending me through some scripted routines, but my response cut them short and they approved the RMA... I said, "I've already tried all the suggested solutions, this is a well-known problem with this particular model, you should look up forums on the internet to make yourselves aware. aaand BTW, you guys may want to be smart and either recall this product, or hand out an advisory that this model shouldn't be used on smartphones, cuz given the large number of folks who have lost data and time with this product, you may be exposing yourselves to a class action lawsuit. Just sayin'..."
RMA approved. I insisted on replacement with 2 x 32GB cards.
New to the forum, I did a search but came up empty, I have a rooted LG G# 35B rooted stock rom. it has a 128gb samsung sd card I had it for at least 6 months, no issues, last week it started unmounting my SD card by itself and unless I restart the phone it wont mount again, I did a factory reset and formated the card 3 times then mounted the card on the phone again and same issue, it will not go away also starts crating and deleting .txt files one called SNP_LOG .txt because of the modified nature of the phone I cannot do the OTA I have the 5.1.1 lollipop, also I have put on an 8G SD card and a 32GB same issue.
Try downgrading via the 10B TOT to try to verify if the problem is software or hardware. By your description I'm wondering of software but that's just a guess.
http://forum.xda-developers.com/showthread.php?p=67945841
http://forum.xda-developers.com/showthread.php?p=68040923
http://forum.xda-developers.com/showpost.php?p=68098895&postcount=1470
ilanpro said:
New to the forum, I did a search but came up empty, I have a rooted LG G# 35B rooted stock rom. it has a 128gb samsung sd card I had it for at least 6 months, no issues, last week it started unmounting my SD card by itself and unless I restart the phone it wont mount again, I did a factory reset and formated the card 3 times then mounted the card on the phone again and same issue, it will not go away also starts crating and deleting .txt files one called SNP_LOG .txt because of the modified nature of the phone I cannot do the OTA I have the 5.1.1 lollipop, also I have put on an 8G SD card and a 32GB same issue.
Click to expand...
Click to collapse
My wife's stock phone had this issue on 48A. I downgraded it to 10B and then took OTA's back up to 35B. It still had the issue. Went back to 10B and still had the issue. IIRC there is a post about this issue on the main LG G3 forum in case you are interested.
I have the insurance on my devices so 3 replacement devices later she got a phone that works again. Good luck!
I'm on 46A and had a similar issue with a Samsung 64 GB card I have been using for about a year. Recently it started unmounting and remounting out of nowhere. Eventually, the phone claimed that it was corrupted. I opened up a file viewer and it seemed as though it had reformatted it. Since I backed it up at the start of all this, I put it in my computer to restore the data. However, all of the files that were on there before were still there and in-tact. I tried a 16 GB card I had sitting around to no avail. After doing some Googling, it seems that these symptoms are apparently a relatively common hardware issue with the G3 (which sucks, because this phone was still doing great after 2 years).
TL;DR - you may want to try different SD cards if you have any. That will help narrow down the issue and whether or not it's software or hardware. If I find any more info on the similar issue I'm having, I'll post it here.
Has anyone tried something like deoxit on the sd card when they start going bezerk?
I wonder if the card or the slot contacts get dirty or microscopic corrosion.
I use deoxit on alot of contacts and it works well.
Brian
still cannot get it to work, also I keep getting this messages for creating an snp_log.txt and then deleting the file I search for it and erase it and it keeps doing it, also a DelMe file 1-21 keeps pooping up
running lg g3 35b-xdeb sdcard formated exfat, I had this issue happening 6 months ago with a 64gb sandisk card till the card become "unwriteable" to any device or pc. I can no longer write to the card and it is readable but pretty much useless. I replaced with a 128gb sandisk card and all went well. Problem is starting again. everytime I reboot the phone and use a passcode to log in, it unmounts and mounts once. I removed xposed and many other apps still to no avail. I did read somewhere that the card needs a "label" on the volume for lollipop. .I did noticed my card was unlabled. I placed a label on my sdcard but it still is happening. I have also read that backing up the card and doing a complete "non quick" format my help out. doing a backup on my card now. let ya know the results. I did place another 128gb card in my phone and the problem still existed. I tried formatting another card to ext4 but it still was happening. I do feel my issue is software related.
incase your unsure if this is happening to you all you need to do is launch the camera app and it will ask you to "save photos to sdcard" whenever it unmounts the sdcard.
Does anyone know any log files i can examine? since my phone can be rebooted and sit for hours and then when I log in with a passcode it unmounts perhaps I can see which app if it is an app that may be doing this. I am on lollipop but I did run the sdcard fix for kit kat on it. maybe a script still exists. I really like this phone and would love to sovle this. I'm wondering if it is an issue with the internal memory that is causing an unmounting and remounting of volumes. would love to solve this.
update:
So I tried backup the sdcard to a hardrive using windows 10. kept failing on files. I decided to try backing up using a linux-ubuntu dist. when it would fail on the files it would actually unmount the whole drive. can't remember the error exactly something to do with no enpoint. I started select directories one by one to copy. I came to an assumuption. the only directories with corrupt files were files that I copied from the internal memory to the sdcard. my tool of choice used to be using es-file explorer. I hate making blind assumptions especially if i'm wrong but that was definitely a common denominator.
So I kept getting "sdcard unmounted" and "sdcard mounted" after reboot and login. I decided to do a full wipe but not before doing a backup of my rom. (just for testing purposes and data backup) I tried nandroiding to the internal memory which had 18gig left and it kept failing saying not enough space. so I backed up to external_sd which worked fine. I then decided to do a format of internal memory from twrp. restored backup and an earlier backup and still mounting issues. I then installed latest stable of cm12.1 and it... worked. don't know why but I decided to install xdabeb 3.1.1 6.0 mm stock image. wow does it work great. all my needs were met. xposed for 6.0 sdk23, tether, g3 toolbox mmbeta. awesome slim down stock. no sdcard mount issues with original card. I actually think the external_sd mount issue is actually a byproduct of an issue with the internal memory. and I believe cm12.1 install might have done some kind of fsck(filesytemcheck) my pipe dream? my incorrect guess? prolly. give it a try. cm12.1 installs so quickly it can't hurt.
WARNING!
DO NOT FORMAT INTERNAL MEMORY IF YOU HAVE NOT COPIED /TWRP BACKUP FOLDER FROM INTERNAL MEMORY TO A SDCARD OR USBDRIVE IF YOU NEED IT.
you were warned (sorry bout the caps....felt it was needed)
I'm seeing this problem as of yesterday, and it started after I took the 49A OTA, but I do not believe that was the issue. I'm wondering if it's more because the phone is almost 2 years old? I don't take the SIM nor the SD Card out at all. I did drop my phone last week. It was in a case and it landed flat on it's back, but I wonder if that still might have caused an issue and it just happen to coincidentally rear it's ugly head yesterday when I took the 49A OTA? 10B and all subsequent OTAs exhibit the same issue.
Going to take it into Cell Phone Repair today and get an estimate to see how much it will cost to get it fixed. Would like them to fix the USB port as well as it appears to be loose and I have numerous connect/disconnect issues with the PC so I have to be VERY careful when flashing so as to not bump or jostle the cable or phone while connected to the PC.
Cell Phone Repair gave me a quote to replace the SIM/SD Card slot of around $90 USD. They did say there was a 50% chance that the phone might not turn on if they do the work and that would be the end of it. I'm going to leave it alone.
Now, one thing I have noticed is, the card ejects usually when I launch an app. From what I can tell, it only appears to happen once for the app. Yesterday, the Facebook app seemed to do it. Today, my Twitter app did it.
I'm wondering if it's due to permissions? I wonder if the OTA changed something in regards to the access allowed to the external SD card and that's causing it to eject the card, and then remount it with the proper permissions? Usually, it seems to take a bit of time to remount, but it usually does, and then from that point, I don't see it happen for that app anymore.
Any ideas on this?
UPDATE: I just launched Twitter again and it didn't eject the card. I launched Facebook as well and same thing, no dismount. But I then launched Google+ app and it ejected the SD card. Still waiting to have it remount the SD card. Like I said, sometimes it's quick. Other times, it takes some time to remount the card. But this seems to be the issue and I'm wondering if that's normal? It happens with any SD card I put in.
iBolski said:
Cell Phone Repair gave me a quote to replace the SIM/SD Card slot of around $90 USD. They did say there was a 50% chance that the phone might not turn on if they do the work and that would be the end of it. I'm going to leave it alone.
Now, one thing I have noticed is, the card ejects usually when I launch an app. From what I can tell, it only appears to happen once for the app. Yesterday, the Facebook app seemed to do it. Today, my Twitter app did it.
I'm wondering if it's due to permissions? I wonder if the OTA changed something in regards to the access allowed to the external SD card and that's causing it to eject the card, and then remount it with the proper permissions? Usually, it seems to take a bit of time to remount, but it usually does, and then from that point, I don't see it happen for that app anymore.
Any ideas on this?
UPDATE: I just launched Twitter again and it didn't eject the card. I launched Facebook as well and same thing, no dismount. But I then launched Google+ app and it ejected the SD card. Still waiting to have it remount the SD card. Like I said, sometimes it's quick. Other times, it takes some time to remount the card. But this seems to be the issue and I'm wondering if that's normal? It happens with any SD card I put in.
Click to expand...
Click to collapse
My wife's SIM slot stopped working about a month ago. I got an RMA on LG's site to send it to them for a repair quote. They wanted about $75 to repair or $150 for a complete refurb. We didn't have it repaired and then sent it back. We're hoping to buy two new non-contract unlocked phones in the near future. Probably the HTC 10 Unlocked or the Google Pixel XL 128 GB, but that latter isn't too likely given the very high price combined with its unavailability.
My wife is unfortunately using her old flip phone for now.
Mainly wanted you to know LG's quote as I'd be more comfortable having LG repair it than someone else, I just didn't want to put more money into phones that I'll be looking to replace soon anyway, and with the Swappa selling price of the G3 being only $50 more than that repair cost.
roirraW "edor" ehT said:
My wife's SIM slot stopped working about a month ago. I got an RMA on LG's site to send it to them for a repair quote. They wanted about $75 to repair or $150 for a complete refurb. We didn't have it repaired and then sent it back. We're hoping to buy two new non-contract unlocked phones in the near future. Probably the HTC 10 Unlocked or the Google Pixel XL 128 GB, but that latter isn't too likely given the very high price combined with its unavailability.
My wife is unfortunately using her old flip phone for now.
Mainly wanted you to know LG's quote as I'd be more comfortable having LG repair it than someone else, I just didn't want to put more money into phones that I'll be looking to replace soon anyway, and with the Swappa selling price of the G3 being only $50 more than that repair cost.
Click to expand...
Click to collapse
Thanks. $150 is what Verizon quoted me for a replacement G3. My issue is, I do not want to buy another phone. I actually love this phone. I'm comfortable with it and it does what I need. And with one daughter in college and the other getting ready to start college next year, I need to save money and I do NOT want to be paying more money a month for a new phone. With this phone just having gotten off contract, by VZW bill dropped $20/month which is nice. That's $240 saved over the course of a year. Might seem like peanuts to some, but for me, every little bit helps.
I've flashed back to 10b again to test out the SD card because it's really annoying that right after the 49A OTA, it started happening. I just can't see that it was already bad but never showed, or that the 49A OTA caused the issue to show up. I'm just wondering if there's something with the 49A OTA that causes this issue. Other people have reported to me that they experienced the exact same issue as me with the SD card constantly ejecting. Maybe the slot IS bad, but it's not as sensitive to it except with the 49A.
I had thought I saw the same issue on 10b, but now for the past couple of hours, I've ran on 10b and haven't seen one issue with the SD card. So, I'm now slowly going up the OTA chain until I can get back to 48A where it last worked without any issues and see what happens there.
I have verified that the SD card is fine. Or at least, it appears so. I copied all the files off of it, did a format, chkdsk, etc and nothing comes up bad about the card.
So, the drama continues on with my phone!
Well, it's been confirmed via another user where vzw told him the latest 49a ota is not compatible with our phone in some instances in regards to the SD card. Last night I flashed back to 10b and I'm back on 48a now and no SD card issues. Zero. I've been going over 12 hours now and not a single unmount. Thanks Verizon. Nice testing. ?
I'm curious if those on 49a not expediting issues with their SD cards if they are on the K or non-k model of the g3?
Sent from my VS985 4G using Tapatalk