Database Info

Mozart not recognised by windows so can't backup please help!!

I was recently given a Htc mozart by a friend who had cracked the screen and bought a new phone, they said I could have it but would like their photos and vids off it so if I could back it up (easy as pie I thought!!!)
The phone charges and functions fine (I changed the digitzer) but when plugged into a pc it displays usb unrecognized error code 43 (malfunction?). I have tried multiple cables, laptops and even os (xp, 7 32bit/64bit and osx), I have searched the internet and have seen some suggestions on wiping the phone (but I don't want to do this until the data is backed up) also looked at reading the micro sd but found you can't by conventional methods.
I have also tried multiple apps - boxfiles, sendstuffnow,sharefile (they seem to allow one photo at a time but not videos), I also tried emailing them but again I can't email vids and the phone has over 500 pics! tried bluetooth and also yivosoft but it doesn't seem to be able to view the files (root access required??), tried a few other programs such as ftp and they just state the phone needs to be updated via zune (currently running 7.0.7004.0).
I was thinking of sticking another microsd card in and formatting it etc just to see if it is then recognised in windows and poss update the firmware then put the old micro sd back in? would this work or is the firmware stored on the micro sd card and also if not when I update would it then state the old micro sd needs formatting or something? If anyone has any suggestions on how I can get the pics and vids off it would be greatly appreciated! I am an android user and this is my first experience with a windows phone so if I am way off my apologies. Thanks again

For sure don't mess with the uSD cards. They're locked to the device (the "S" in SD stands for "Secure" and refers to a rarely-used ability to lock an SD card). Even if you managed to make the card usable again, the data on it would be gone. Also, yes, the OS is at least partially stored on the SD card, and your switch-update suggestion would not work.
WiFi sync would work, but if that's not already set up you'd need to connect the phone to Zune via the USB to set it up. There are some homebrew apps that would be able to lift the files easily enough, but unless you have something lile TouchXplorer or Advanced Explorer installed already, that's not an option (you need USB connection to install more homebrew).
Sorry, man. This is one of the reasons why I plug in my phone to my PC every day or two and sync it; the tiny amount of time it takes is worth the reassurance. I realize that doesn't help now, though...

GoodDayToDie said:
For sure don't mess with the uSD cards. They're locked to the device (the "S" in SD stands for "Secure" and refers to a rarely-used ability to lock an SD card). Even if you managed to make the card usable again, the data on it would be gone. Also, yes, the OS is at least partially stored on the SD card, and your switch-update suggestion would not work.
WiFi sync would work, but if that's not already set up you'd need to connect the phone to Zune via the USB to set it up. There are some homebrew apps that would be able to lift the files easily enough, but unless you have something lile TouchXplorer or Advanced Explorer installed already, that's not an option (you need USB connection to install more homebrew).
Sorry, man. This is one of the reasons why I plug in my phone to my PC every day or two and sync it; the tiny amount of time it takes is worth the reassurance. I realize that doesn't help now, though...
Click to expand...
Click to collapse
Thanks for the reply, know what you mean I back up regular also but my friend didn't. I can't believe its so difficult to transfer the files without the usb connection :S also can't believe the updates are no ota :S was hoping there might be a method of unlocking the phone for homebrew like there was with the iphone at one stage. Ah well back to the drawing board unless someone can come up with any other ideas!

Cannot access internal or external storage...

Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?

Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
Try to take out your SD card and put it in a Card reader, remember to do it while your device is off or unmount it from memory settings, try to swtich on your device later and connect it to your computer and check if it connect through USB or not.

Try some system tools?
Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
I'm guessing databaiz's suggestion to take out the card isn't an option because it's the internal sd card, right? If so, for the one-in-a-million chance that the external card is screwing with the bus, I'd take the external card out and reboot anyway, just to make sure; if it works OK then, I would check the external card as databaiz suggests. But assuming it still doesn't work, next question is, do you have a terminal app installed? Please try the 'mount' command and let us know what you see. One other question, will it still go into fastboot mode? Can you see it from your computer when in fastboot mode (the details of how to do this depend on whether you have windows or linux/macOS - I can maybe help with the latter, but not the former).

It could be bad card
It could be bad card.... Remove and test in card reader...

cannot access internal or external storage
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.

Brian44 said:
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.
Click to expand...
Click to collapse
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.

cannot access internal or external storage
urilabob said:
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.
Click to expand...
Click to collapse
Thanks, Urilabob. The command df had an effect!
Shows Filesystem with figures for Size, Used, Free, and Blksize (4096), next to each of the following:
/dev, /mnt/asec, /mnt/obb, /system, /data, and /cache. The figures are all different except Blksize.
/mnt/sdcard is not shown.
Does this tell you anything useful?
I have never been able to access the tablet from my laptop with Windows 7. My son’s laptop has an earlier Windows, so I checked today and found that his Windows Explorer finds the tablet (as 2 disks, A and F) and asks “Please insert a disk into Removable Disk H:” (and same for F.
By the way, this problem started when I downloaded the (automatic) firmware update direct to the tablet, not via laptop. But the wifi signal was weak, and files may have been corrupted. I have since downloaded the complete, latest firmware to the laptop (with strong wifi signal), but do not know how to get it into the tablet!
Have not yet done anything on adb or fastboot modes. Will Google adb tonight.
Not worried about losing data or apps.
Thanks again, Brian.

I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.

cannot access internal or external storage
SacTappingUni said:
I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.
Click to expand...
Click to collapse
Thanks for your thoughts. My tablet is not rooted. And I cannot enable USB debugging, because Settings freezes when I tap Developer Options to get to USB debug. I am just learning about Android - seems to be 2 partitions on the internal storage, one about 2.6GB with apps and other things on (which is accessible), and the other partition must be about 13GB, but has not been accessible since the automatic firmware update.

Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.

cannot access internal or external storage
MissionImprobable said:
Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.
Click to expand...
Click to collapse
Factory reset would be great, if it worked, but it does not function.

Can you exchange the device?
Brian44 said:
Factory reset would be great, if it worked, but it does not function.
Click to expand...
Click to collapse
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob

cannot access internal or external storage
urilabob said:
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob
Click to expand...
Click to collapse
Thanks, Bob for all your help. This seems like the end of the line with this tablet. I expected this might be the case, and emailed DinoDirect two days ago for a refund, as I am heading overseas next week and want to resolve the matter before I go. They responded that "we will contact our related department to process your case priority". I have been aware that any actions I might take could invalidate the warranty, and this has inhibited me a bit. I will forward your latest comments in support of my refund claim.
I learned some basics of Android from all this!
Good wishes, great talking to you.
Brian

Just for a great justice :victory:
Got same bug on my Gemei G6, guess it hapens after i connect dc cabel to a fully charged pad that was charged in off mode and turn on. So i just download last firmware fro Gemeitech.com, unzip it on SD card and tnen turn on pad with pressed Home and Power buttons that must be pressed untill robot with green rotating belly appears what mean start of flashin` Thats it.

Got the same issue in Huawei Ascend P-7, I just switched off the mobile, removed the SD card and turned it back on after 5 minutes ....... and that was it, all issues resolved. Just the thing was that once SD card was re-inserted, problem came up again. So i have decided to copy SD card data to PC via Card Reader and format it or get new SD card

[Q] 64gb SD micro sdxc not working

Hi, can someone please help. I have put a 64gb micro SD sdxc into my galaxy note pro 12.2, but unfortunately when I try to write to the card when inserted in the tablet, it craps out when I get to around 10gb of transfered data every time. The card works perfectly on a galaxy note 10.1 and when used on a PC. I read on the net that the card being in a sdxc format might be the problem, so I formated the card in to fat32 format. But when I put it back in to the tablet it says damaged SD card and says to reformat it. As I say the card works perfectly on other devices. I also have a 32gb sdhc micro SD card and that works perfectly in the galaxy note pro 12.2. I have returned the tablet thinking it was a fault with the tablet but I have exactly the same problem with the new one. It's really starting to p!ss me off especially after I found how they have restricted SD micro access in android 4.4.
Does anyone know of a fix for this as a 32gb card is nowhere big enough for me. I love the tablet but this issue is making me not want it anymore.
Thanks in advance for any help.
P.s. I wish to insert a 128gb card (as I have read they work) but don't want to buy one if the table won't read sdxc

I'm using two 64GB Sandisc MicroSDXC's interchangably with my 128GB Sandisc one on my P905, but I've never encountered such an issue.
All three are formatted as ExFAT, as FAT32 has a <4GB filesize limitation. Which is useless when it comes to 1080p films.
How are you trying to write to it? How do you eject it? This is the first Android device I have encountered that behaves like a Mac when it comes to external storage, if you don't unmount the card before disconnecting it, it starts doing all kinds of crazy sh*t. Damaged errors, mysteriously vanishing data...
Did you try formatting it inside the tablet through Android's own menu? It really doesn't like partitions formatted on Windows.

Have tried everything.
ShadowLea said:
I'm using two 64GB Sandisc MicroSDXC's interchangably with my 128GB Sandisc one on my P905, but I've never encountered such an issue.
All three are formatted as ExFAT, as FAT32 has a <4GB filesize limitation. Which is useless when it comes to 1080p films.
How are you trying to write to it? How do you eject it? This is the first Android device I have encountered that behaves like a Mac when it comes to external storage, if you don't unmount the card before disconnecting it, it starts doing all kinds of crazy sh*t. Damaged errors, mysteriously vanishing data...
Did you try formatting it inside the tablet through Android's own menu? It really doesn't like partitions formatted on Windows.
Click to expand...
Click to collapse
Hi, thanks for your reply. I've tried writing to it via drag and drop and via Samsung kies many times with the same result. Have always ejected the card via the unmount option in device settings. I have also tried formating it on my note pro and via many different formating programs on pc in both fat and exfat, but again none of it has sorted the problem.
It really seems to be a problem with the memory card its self but it works fine as storage when not in the device, and works fine in my old note 10.1 formatted to exfat.
It's a really strange issue and incredibly annoying.
Thanks again.

My wife has one of these and she purchased a 64gb Samsung micro that she will get next week (orange card).
I know this worked on my S5 back in the kitkat days https://play.google.com/store/apps/details?id=nextapp.sdfix
It's worth a try. Let us know if it worked buddy.

nicetucu said:
My wife has one of these and she purchased a 64gb Samsung micro that she will get next week (orange card).
I know this worked on my S5 back in the kitkat days https://play.google.com/store/apps/details?id=nextapp.sdfix
It's worth a try. Let us know if it worked buddy.
Click to expand...
Click to collapse
Unfortunately you need to root your device to be able to use the suggested app, but was worth a try.
Thanks.
Surely I can't be the only one to have this problem as it's the same on my returned note pro and the replacement. Time to harass Samsung a little I think.

Sorry, didn't think that was a rooted app, hard to keep track sometimes lol.
I'll let you know if the Samsung card has better compatibility with the device. Seems to work for in most part. It's only in transferring large amounts of data at once, right?
I had a bad Sandisk card that I had to RMA a while back. So in this case it was the card and not the device (S5 at&t rooted kk 4.4.2 at the time).
The card was a 64 GB microSDXC XC 1 class 10 variety. At about half way full I couldn't delete files from the card. It was able to read (for backup of pics and videos) but acted like it was frozen in time lol. The card has a lifetime warranty and Sandisk paid for shipping both ways. It took about 10 days for turnaround though, not great, but the new card has worked well so far.
There was a bad batch of cards made in early 2013 and this was a card carried over from an S4. I tried so many things via a PC and just finally gave up and Sandisk was quite understanding. I did have to send the old card back and asked if I could cut the card cause I couldn't delete my data and they agreed as long as they could read what type of card it was. I ended up just sending it back intact cause it was mostly family pics and vids and nothing sketchy.
I'll let you know once she gets it and put it through the paces.

dodgedabullet said:
Hi, thanks for your reply. I've tried writing to it via drag and drop and via Samsung kies many times with the same result. Have always ejected the card via the unmount option in device settings. I have also tried formating it on my note pro and via many different formating programs on pc in both fat and exfat, but again none of it has sorted the problem.
It really seems to be a problem with the memory card its self but it works fine as storage when not in the device, and works fine in my old note 10.1 formatted to exfat.
It's a really strange issue and incredibly annoying.
Thanks again.
Click to expand...
Click to collapse
Hm.... And when you copy paste it in groups of a few GB at a time? It might just be an MTP problem, that protocol is a nightmare.

nicetucu said:
Sorry, didn't think that was a rooted app, hard to keep track sometimes lol.
I'll let you know if the Samsung card has better compatibility with the device. Seems to work for in most part. It's only in transferring large amounts of data at once, right?
I had a bad Sandisk card that I had to RMA a while back. So in this case it was the card and not the device (S5 at&t rooted kk 4.4.2 at the time).
The card was a 64 GB microSDXC XC 1 class 10 variety. At about half way full I couldn't delete files from the card. It was able to read (for backup of pics and videos) but acted like it was frozen in time lol. The card has a lifetime warranty and Sandisk paid for shipping both ways. It took about 10 days for turnaround though, not great, but the new card has worked well so far.
There was a bad batch of cards made in early 2013 and this was a card carried over from an S4. I tried so many things via a PC and just finally gave up and Sandisk was quite understanding. I did have to send the old card back and asked if I could cut the card cause I couldn't delete my data and they agreed as long as they could read what type of card it was. I ended up just sending it back intact cause it was mostly family pics and 1vids and nothing sketchy.
I'll let you know once she gets it and put it through the paces.
Click to expand...
Click to collapse
If you could let me know that would be great, any info and help will always be handy.

ShadowLea said:
Hm.... And when you copy paste it in groups of a few GB at a time? It might just be an MTP problem, that protocol is a nightmare.
Click to expand...
Click to collapse
Yeah I've tried large transfers at a time and individual file transfers, even as small as 1 mp3 file at a time, but always the same outcome. I have the same Sandisk ultra 64gb micro sdxc in my galaxy S5 phone and that card works perfectly in that device. Unfortunately I can't remove that card to try it in the note pro as when I do all the game and app data I've transfered to it loses its link to the system files for the data and I have to reinstall it all again, which is a real pain in the arse when you've downloaded them over time and stupidly not kept track or copies of where they have come from. Lol.
Do you mind if I quickly go off topic and ask a question about the Samsung keyboard on the note pro. You seem to know what your talking about. Say I want to delete part of text like a url etc, when I delete it and start to type in different text the Samsung keyboard replaces the text I had just deleted so I end up having to delete it twice. It's not a huge problem but bloody annoying. Do you happen to know how to stop it doing that?
Thanks again.

dodgedabullet said:
Yeah I've tried large transfers at a time and individual file transfers, even as small as 1 mp3 file at a time, but always the same outcome. I have the same Sandisk ultra 64gb micro sdxc in my galaxy S5 phone and that card works perfectly in that device. Unfortunately I can't remove that card to try it in the note pro as when I do all the game and app data I've transfered to it loses its link to the system files for the data and I have to reinstall it all again, which is a real pain in the arse when you've downloaded them over time and stupidly not kept track or copies of where they have come from. Lol.
Click to expand...
Click to collapse
Very strange. It shouldn't be doing that. (No seriously. My 128GB MicroSD has 30MB free space. The rest is films, series, magazines, comics and music.)
Does it also happen when you transfer files internally to the MicroSD? Or just over USB?
What I do notice is that there seems to be some sort of timelimit to the MTP protocol. If it's attached for longer than around 5 minutes, be it in transfer or not, it starts lagging or even just randomly disconnecting. My Note 3 and S5 don't do that, but their USB system is different.
Ohhh, very familiar. I made that mistake once, good grief that took ages to fix.
Do you mind if I quickly go off topic and ask a question about the Samsung keyboard on the note pro. You seem to know what your talking about. Say I want to delete part of text like a url etc, when I delete it and start to type in different text the Samsung keyboard replaces the text I had just deleted so I end up having to delete it twice. It's not a huge problem but bloody annoying. Do you happen to know how to stop it doing that?
Thanks again.
Click to expand...
Click to collapse
I don't mind. Going off topic is a speciality of mine.
You should be able to turn that off under Settings > Controls > Samsung Keyboard (The gear icon behind it) > turn off Auto Replacement. (I know it says on pressing space, it's lying.)
Although it might be worth looking into Hacker's Keyboard or Swiftkey. (Both are free) I much prefer Hacker's Keyboard as it acts like a proper keyboard.

"You should be able to turn that off under Settings > Controls > Samsung Keyboard (The gear icon behind it) > turn off Auto Replacement. (I know it says on pressing space, it's lying.)"
That's great thanks, your a diamond. xxx .
Haven't tried hacker's keyboard before, will have to try that one.
"Does it also happen when you transfer files internally to the MicroSD? Or just over USB?"
As far as I was aware android 4.4 stopped allowing writing to micro sd from devices internal memory. (it seems a lot of hassle considering samsung advertise that the note pro will work with 64gb sdxc cards) And i haven't rooted my note pro yet as if i can't get larger than 32gb cards to work on it i may well take it back for a refund

dodgedabullet said:
"Does it also happen when you transfer files internally to the MicroSD? Or just over USB?"
As far as I was aware android 4.4 stopped allowing writing to micro sd from devices internal memory. (it seems a lot of hassle considering samsung advertise that the note pro will work with 64gb sdxc cards) And i haven't rooted my note pro yet as if i can't get larger than 32gb cards to work on it i may well take it back for a refund
Click to expand...
Click to collapse
Hm, it still works on mine. I'm on P905XXUANC3/XXUANA7/DBTANC3. (The newer update breaks it, I believe.) 5.0 brings MicroSD control back though; but I have no schedule on its release yet.
I can't rename anything though, that won't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ShadowLea said:
Hm, it still works on mine. I'm on P905XXUANC3/XXUANA7/DBTANC3. (The newer update breaks it, I believe.) 5.0 brings MicroSD control back though; but I have no schedule on its release yet.
I can't rename anything though, that won't work.
Click to expand...
Click to collapse
Just to let you know, it turns out it was a memory card problem. I took the risk and bought a 128GB card and it is working. It seems to be some weird of incompatibility issue as the original card works in everything else i've tried it in.
Unfortunately i'm having another strange problem with the memory card. I have come across the problem before but have never worked it out. The problem is, i copied over a 1.8gb file from internal memory over to memory card but the card capacity went down by 2.9gb. I checked the size of the file i copied to memory card when it was on the memory card and the file is definitely only 1.8gb. So wtf has happened to the other 1.1gb. lol.
The actual useable total memory on the card is 119gb, and when i checked the size of everything i've put on the card it comes to 109gb, but the system on my note pro is saying i have 7.1gb left when there should be roughly 10gb left. So i'm missing 3gb in total somewhere. Does anyone have any ideas how to retrieve the missing storage space?

K1: Post 1.3 OTA, paired/married SD causes tablet lock, bootloops, and a ton of heat.

This is a strange one for me. Stumped. Been working on it all night, no improvement. New one for me, long-ish description (with detail), but a TL;DR too.
Last night I applied the 1.3 OTA for the K1. Being my K1 was rooted, I followed the process I have always followed by restoring the system images to stock, applying the OTA via recovery, then re-rooting. Process:
Shutdown tablet
Swap married/paired SD card with temp SD containing flashables (OTA, SuperSU)
Boot to bootloader, fastboot (re)flash tablet's current system images (recovery was already stock but flashed again for good measure, boot, system, blob -> staging)
Boot to custom recovery using fastboot boot -recovery image-
Flash OTA from temp SD, wipe caches, apply SuperSU
Shutdown, replace married SD, boot, enjoy life
This time I didn't immediately apply SuperSU, as I thought I'd flash 1.3 and let it go fully stock a bit to ensure no other updates were pending (nVidia seems to like incremental updates, so flashing to 1.1 won't give you an OTA to 1.3 directly, but to 1.2 first, then 1.3). I've also followed this process with the K1 for every update since 1.1 without a hitch, and although there haven't been many OTAs, it has still worked perfectly every time. Because of this and because I've done this a billion times on a million different devices with zero issues ever, I didn't take a backup before the update. Woe is me.
When I rebooted this time after flashing the OTA (no root), it booted up seemingly fine to the "Android is upgrading" modal, so I left the tablet alone for a bit to let it do its thing. When I came back, the tablet was HOT, was at a completely black screen save for the status bar (no wallpaper/launcher besides the clock/wifi icon which showed a connection, that's it). I tried to interact with it and couldn't (totally locked up, also a first), then it rebooted on its own. Subsequent times, during troubleshooting, I noticed that it's totally locked -- NOTHING responds, unless you can get to it before it reboots and hold power to kill it.
First thought was a bad flash. NBD, so went back and reflashed, double-checking everything and carefully following the same process. No dice. I did use a newer TWRP recovery from April of this year initially, which was a recommended version for the K1 specifically, rather than a really buggy but working one from last year. To test I did I try using the older TWRP on one of the next flashes thinking maybe the new one borked the partitions, or at least wasn't writing the partitions/symlinks properly (and the older one was the TWRP I had used for previous updates, with no issues). But, no change..
It took me a long time and many reflashes and cache formatting and digging before I realized if I pulled the married SD out, it booted just fine. Weird, and gets weirder. After leaving the married SD out and booting, and having the tablet working just as expected (except for missing the SD), Android shows a notification saying to reinsert the married SD. Once the married SD is reinserted, things seem OK for a few seconds before the whole system goes unresponsive again, heats up, and begins bootlooping. Before it sh'ts the bed, the message on the status notification asking to reinsert the married SD card doesn't change, but in the Storage settings, it shows it's "checking" the card, followed by a sudden hot death spiral into non-function. If you select the SD from Storage settings to take a look around its contents, the tablet basically locks up instantly. Inserting other SDs works fine (for the most part, still some other weirdness), it's just the married SD that totally kills the device without fail.
Obviously I'd like to avoid wiping and reinstalling the whole thing if it can be avoided, not just because my dumb ass didn't take a backup so I'd lose a ton of app/game data, but also because it's a just huge pain. A lot of the sites that offered "fixes" for these types of problems say to just wipe data, which is not a solution and is the nuclear option (like telling someone to to replace a car due to a flat tire).
Ideas? Is this as simple as recreating some symlinks that somehow disappeared and refuse to come back after all the flashes, and if so, how? I've been looking for hours and haven't found anyone with this particular issue or steps to correct.
[size=+2]TL;DR[/size]: Applied K1 1.3 OTA, married/paired SD card is no longer recognized, causes tablet to hard-lock and enter bootloop when inserted (other SDs do not cause this issue).
Other potentially pertinent bits:
Initial flash was dirty, second and subsequent flashes included a wipe of system first
Installed 1.2 images first, then tried going back to 1.1.1 and taking nVidia's OTAs to get back up to 1.3
1.1.1 does not recognize the married SD but doesn't kill the tablet, while 1.2 and 1.3 kill the tablet when the SD is inserted
When married SD is not inserted, using shell or ES Explorer or otherwise, not seeing a /storage/emulated/0, or /sdcard, or /data/media, or any other familiar storage related directories
When married SD is inserted, it dies too fast to look around much or try to do anything to check/fix the SD itself
/storage is totally empty except for a folder called "self", and inserting a working SD creates a directory under /storage labeled with the SD's serial number (not an emulated/0 directory or anything similar)
Not sure if this is expected behavior since the SD was married -- do those directories/symlinks live on the SD now since it's married, and won't show up in the device filesystem until everything's properly mounted?
Tried following these steps, which although written in the N5 forum, still seemed relevant.. no change
Tried the referenced SD permissions update with the card inserted and not, in case of the directories it touches only being visible/available with the card inserted, no change
Noticed even within TWRP, going to the "mount" menu seemed flaky, labored, and didn't show what I expected, but this could be because there isn't a "proper" or official custom recovery for the K1 yet and things are just buggy
ES File Manager still seems to think an /sdcard directory exists and tries to open to it, and just spins in an open directory.. as expected
Going to /data in ES File Manager shows me an empty directory with a message stating the SD card is missing
Using a working, freshly formatted SD in the tablet and trying to point Titanium to a directory on the SD gives me messages about the directory being unwritable, no matter where I go on the SD
Titanium's app permissions (including r/w storage) are proper, SD is not write protected (freshly formatted on the tablet)
Tried using SDFix, which also gave me an error re: "platform permission file is invalid"
There's probably more I'm missing, but can't remember it all -- I have tried everything, I feel like, and have been at it for 13 hours now (apologies if this is written spotty, fighting to keep my eyes open).
So is it totally hosed, or is this recoverable? Is there a way to fix the tablet to recognize the SD, or fix the SD itself if that's the issue (but I'd wonder how it got corrupted in the first place, since it has only been removed once fully powered down)? Is there at least a way to check the married SD for corruption or issues?
Thoughts?
EDIT: Formatting

You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all

GtrCraft said:
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
Click to expand...
Click to collapse
And why is that? When the OS is running, sure, you can't. It'd be equivalent to just deleting /data while the OS was running. It seems pretty unlikely that removing and reinserting it while it's powered off, though, would make it suddenly unable to read the SD or forget its pairing. Adopted storage is "married" to the device via a generated encryption key, which is stored on the device's internal storage. It's all handled in software, not like the SD fuses itself to the device Removing the SD (while off) would not (and does not) break this pairing method, unless the internal storage or SD decides to spontaneously erase itself while the device was off.
The process outlined is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD

grivad said:
When the OS is running, sure. Maybe that is the case, but it seems pretty unlikely that removing and reinserting it while it's powered off would make it spontaneously unable to read the SD or forget its pairing.
This is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
Click to expand...
Click to collapse
Still, you better off formatting it
Sent from my XT1562 using XDA Labs

Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk

lafester said:
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Cool.
Regarding the YOU CAN'T REMOVE IT belief (which is categorically false), if this were a serious issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Also that I cannot write to a working SD with Titanium. These things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."

grivad said:
Cool.
Regarding the DON'T REMOVE IT belief, if this were an issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Both of those things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
Click to expand...
Click to collapse
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place

GtrCraft said:
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
Click to expand...
Click to collapse
It's not that I don't believe the solution, I don't believe the premise because it is provably false There is absolutely nothing unsafe about ejecting adopted storage, which is why the OS lets you do it, even while it's running and using the storage. Even less of a risk if the thing is off. The "solution" offered wasn't much of a solution, and in the OP it was stated that I wasn't looking for that answer (already know that's an option, which is why I mentioned in the OP).
I appreciate you trying to help, but simply saying "format it", again, is the nuclear option. Not what I'm looking for. Either information as to what's happening (if anyone else has dealt with this) with a justification as to why it's irrepairable, or things to try based on the information I gave. Spending a lot of time being thorough just to get a "format it" response, to be frank, isn't very helpful It's like telling someone to reinstall their entire OS because they can't figure out how to install a driver, or to raze their house because a painting fell off the wall.
The SD didn't spontaneously corrupt itself in the 5 mins it was out of the device. No gamma bursts or EM storms in my area that I know of, either Because the only thing that changed was installing the OTA, this really seems to be a software problem (albeit a bit bizarre, to me) so it should be fixable via software. The fact it's pegging the CPU when the SD is inserted makes me wonder if it's getting stuck in a loop, maybe due to partition changes (looking for a file or partition it can't find). If that's the case, again, that should be fixable via software, with instruction from someone knowledgeable on how the Android FS and mounts work.
Again thanks for trying to help. I know formatting is an option (the easiest one), but I'm looking for just that -- options.

You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?

lafester said:
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
Click to expand...
Click to collapse
True, the SD was out, however this is how I've both read to do it in multiple places, and how I've applied every OTA so far without issue (with the same adopted SD every time). As part of my troubleshooting, I did try flashing the OTA with the adopted SD inserted, though. It didn't make a difference.
I did try downgrading.. When I started the tablet was on 1.2, OTAd to 1.3. Every time I'd reflash I would do so to 1.2. I did try flashing down to 1.1.1 (the "recovery OS image") and OTAing back up, and like I mentioned that allowed me to use the device with the SD inserted, but it wouldn't recognize it as the adopted storage.. just kinda did nothing, as if the card wasn't inserted at all. This happened in 1.2 as well (OTAd from 1.1.1), and once it got up to 1.3 from 1.2 it all started all over again.
I'm creating an image of the SD right now (using dd) to try restoring it to another SD. I've read that doing this preserves the pairing information, so if it's a bad SD, this would hopefully fix it. I also wanted to try flashing directly to 1.3, but the images aren't available yet Only 1.2 and 1.1.1..

Honestly I would divorce the card before update then redo it after this whole method is janky anyway no reason to remap the data links like they do and all it would be required is if app devs were forced to comply with a data space method... The feature of installing to SD card should be available to non married storage.

Old thread, haven't been on in a while, but thought I'd post an update.
The problem ended up being a hardware issue. I contacted nVidia after absolutely nothing I tried resolved the issue (different SDs, different OS versions, different process to set up, etc.). I simply explained the problems I was having and my troubleshooting attempts, asked if it was a known issue or if they had any suggestions, and they immediately responded with RMA info, no questions asked. The replacement turnaround time was very fast (within a week IIRC), and the new K1 has had zero issues.

SDCard gets into a "Read only" state on random time intervals

Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?

Did you REALLY need a poll for this? Seriously?
Did you look for information on this? There are at least a dozen threads on SD card issues on the Moto G 2015 just on XDA, much less the dozens of other threads everywhere else... Here is a quick summary, assuming you have tried clearing the cache partition, factory reset, etc:
50% of the time, it's the SD card itself that is bad, or there is a compatibility issue... Try a different brand, size, speed, etc. The most compatible cards seem to be Samsung EVO+ or EVO Plus series (they are different), PNY Elite series, Lexar 633x or 1000x series, and Sandisk Extreme or Ultra series but again this varies by individual handset. Kingston cards are hit and miss, some people have good luck, others not so much.
40% of the time it's a hardware defect or damage inside the device, nothing you can do but replace the microSD socket which requires micro soldering... Probably best to leave it to professionals.
10% of the time, it's a mixed bag... sometimes a couple layers of scotch tape on the back of the card will help (increases tension on the contact fingers slightly), sometimes it's counterfeit cards (don't kid yourself, this is a HUGE problem, use SD Insight to check), sometimes a U3 card helps, or who knows what else.
The point is, about half the time switching to completely different card fixes the issue, and since microSD card are cheap, especially at the 16GB-32GB card size, so it's a good place to start.

+1
replace card.

frenchiveruti said:
Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?
Click to expand...
Click to collapse
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.

reactorcoremeltdown said:
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.
Click to expand...
Click to collapse
I finally found someone with the same problem as me! (well, that's bad news for you and me bad at least I'm not the only one with this problem)
So, you tried everything like me and yet no way to make it work? I couldn't test a different "brand" of SDCard but I did try different ones and checked if they were fake ones and still I have the same annoying problem. Damn...
I think yeah I'll have to go down to an android 5 if there's no way to fix this.
I'm wondering if a custom kernel can solve this, but it's really difficult to know the "why" is this happening, and the logcat doesn't help that much to be honest, at least not from the side of knowing where or what to read that could be causing the issue.