Database Info

Phone reboots while copying high res pictures

As title says, I have a problem copying high resolution images (say 2569x1600) into my phone. While copying files from PC phone turns off or screen goes black and touch sensitive buttons at the bottom blinks.
I thought it is problem with my sd card, so I reformatted it but still couldn't resolve it. To get over this problem I even tried reflashing, still no luck. I think it shouldn't be a problem copying HighRes images as phone itself captures images at the resolution of 3264x2448!
Anyone else with similar issue? Please help!

How are you copping the files (usb, wifi)?

3rdstring said:
How are you copping the files (usb, wifi)?
Click to expand...
Click to collapse
I tried both way but same problem occurs.
Have you had this kind of problem?

Sometimes i have similar issues. The problem is faulty sdcard (or at least faulty in the phone).
I proved the sdcard + phone combination as faulty this way:
1. Boot in openrecovery and issue adb shell to the phone
2. Simulate some sdcard activity (i was using dd to read and write to a file over the sdcard)
Look for "dma" errors in the dmesg output. if that happens usually you can do something with the phone, but nothing which access somehow the card
Alternatively:
From normal mode, connect via adb to the phone. Copy the files, phone will "freeze", but the linux in it will be alive again you can see dma errors in the dmesg output Your shell will be alive (even if it will be necessary to issue another adb shell command), but the phone framework will be freezed
If somebody is curious the sdcards, which make the phone freeze are realy faulty, but not so obviously. e.g. you can use them normal with other devices and pc. But if you go deep and run some test (divide card in logical parts, then compare the read speed of this parts) you will see that the card is gone to gone...
Anyway, i think that even problematic sdcard dosen't have to make the phone freeze. but .... moto decision (or moto fail)

jackfrost3821 said:
I tried both way but same problem occurs.
Have you had this kind of problem?
Click to expand...
Click to collapse
I have had this problem, although it wasn't when it was connected to PC. I will get it sometimes when I an downloading off the internet directly to the phone.
What happens with me is the download gets interupted for some reason and then when I try to reset it back to Home screen it never goes. I soft touch the power button and then that is when I see only the 4 lights at the bottom light up and black screen.
I have to do a battery pull and then when I am fully booted up is when I can fix the issue. Something in the interuption causes the SD card to unmount and you get a corrupted file on there. Let's say I was downloading a picture and this happened. Once I do battery pull and reboot, if I go into the media.apk and see my pix, there will be one that is grey and has a ! in it and also I'll get a notificiation that could not read/write to SD card. Find that file, Delete it, go into settings and unmount SD card and then remount it. You will lose whatever pix it was but my SD card is now mounted again.
Sorry for the long description but it has happended to me a number of times and I even started a thread about it. Moral of the story os that a connectiong was broken during download. Either USB came slightly unplugged or BT signal was interupted, or (this happende to me once) the screen timed out and if you have JuiceDefender it will cut your connection.
Find the corrupted file and deleted it, un-remount SD card (in phone) and maybe try transfering smaller batches over at a time.

peshovec said:
Sometimes i have similar issues. The problem is faulty sdcard (or at least faulty in the phone).
I proved the sdcard + phone combination as faulty this way:
1. Boot in openrecovery and issue adb shell to the phone
2. Simulate some sdcard activity (i was using dd to read and write to a file over the sdcard)
Look for "dma" errors in the dmesg output. if that happens usually you can do something with the phone, but nothing which access somehow the card
Alternatively:
From normal mode, connect via adb to the phone. Copy the files, phone will "freeze", but the linux in it will be alive again you can see dma errors in the dmesg output Your shell will be alive (even if it will be necessary to issue another adb shell command), but the phone framework will be freezed
If somebody is curious the sdcards, which make the phone freeze are realy faulty, but not so obviously. e.g. you can use them normal with other devices and pc. But if you go deep and run some test (divide card in logical parts, then compare the read speed of this parts) you will see that the card is gone to gone...
Anyway, i think that even problematic sdcard dosen't have to make the phone freeze. but .... moto decision (or moto fail)
Click to expand...
Click to collapse
Thanks mate. Now I guess, I have to resize images to lower resolutions to get rid of this problem. Again thank you for the help!

Woodrube said:
I have had this problem, although it wasn't when it was connected to PC. I will get it sometimes when I an downloading off the internet directly to the phone.
What happens with me is the download gets interupted for some reason and then when I try to reset it back to Home screen it never goes. I soft touch the power button and then that is when I see only the 4 lights at the bottom light up and black screen.
I have to do a battery pull and then when I am fully booted up is when I can fix the issue. Something in the interuption causes the SD card to unmount and you get a corrupted file on there. Let's say I was downloading a picture and this happened. Once I do battery pull and reboot, if I go into the media.apk and see my pix, there will be one that is grey and has a ! in it and also I'll get a notificiation that could not read/write to SD card. Find that file, Delete it, go into settings and unmount SD card and then remount it. You will lose whatever pix it was but my SD card is now mounted again.
Sorry for the long description but it has happended to me a number of times and I even started a thread about it. Moral of the story os that a connectiong was broken during download. Either USB came slightly unplugged or BT signal was interupted, or (this happende to me once) the screen timed out and if you have JuiceDefender it will cut your connection.
Find the corrupted file and deleted it, un-remount SD card (in phone) and maybe try transfering smaller batches over at a time.
Click to expand...
Click to collapse
I have exactly same problem as you described. I did battery pull, deleted all the corrupted files and then copied them again but as you said connection gets disconnected and black screen appears. Is this problem with MIUI too, because that's the last option I have left with.

jackfrost3821 said:
I have exactly same problem as you described. I did battery pull, deleted all the corrupted files and then copied them again but as you said connection gets disconnected and black screen appears. Is this problem with MIUI too, because that's the last option I have left with.
Click to expand...
Click to collapse
I wouldn't say it was anything with the ROM you are on, but main the quantity of material you are transfering at one time. Maybe try to cut it down and do small batches and see if that works.
Btw, I am on Kahl's v4 Epicsteelblue ROM.

Are you overclocked? Perhaps your vsel is too low.

If you're using WiFi make sure to set the WiFi sleep policy (or set your screen not to turn off)
Settings >> Wirless & Networks >> WiFi settings >> (menu) >> Advanced >> WiFi sleep policy >> Never off

it is just the sdcard.
before proving within openrecovery, have tried stock clocks and vsel (e.g. not loading overclock.ko)
also was in doubt about vsel, so tried in openrecovery at 250MHz (suppose the vsel was the standard 39 or 32 don't remember exactly).
So it is not the vsel (or at least vsel alone, may be combination of vsel and frequency )

Woodrube said:
I wouldn't say it was anything with the ROM you are on, but main the quantity of material you are transfering at one time. Maybe try to cut it down and do small batches and see if that works.
Btw, I am on Kahl's v4 Epicsteelblue ROM.
Click to expand...
Click to collapse
I tried copying single file but it happened!
Mioze7Ae said:
Are you overclocked? Perhaps your vsel is too low.
Click to expand...
Click to collapse
Previously I used to run MilestoneOverclock @1Ghz with 65Vsel. Last night I tried reflashing , phone wasn't rooted, no overclock module, no Setcpu - phone was completely at stock values and still same thing happened.

3rdstring said:
If you're using WiFi make sure to set the WiFi sleep policy (or set your screen not to turn off)
Settings >> Wirless & Networks >> WiFi settings >> (menu) >> Advanced >> WiFi sleep policy >> Never off
Click to expand...
Click to collapse
That could be the solution but when plugged with USB cable, phone behaves in same weird manner.

Because that happen only when you copy image, so i think your gallery (or another image software contain error when it make the thumb of image). Have you tried remove gallery and copy to see what happen?

jjackichan said:
Because that happen only when you copy image, so i think your gallery (or another image software contain error when it make the thumb of image). Have you tried remove gallery and copy to see what happen?
Click to expand...
Click to collapse
No, I didn't try that. After reflashing to stock there shouldn't be any problem, right? It still happens. Really annoying problem. So what I do now is resize images to 854x480.

jjackichan said:
Because that happen only when you copy image, so i think your gallery (or another image software contain error when it make the thumb of image). Have you tried remove gallery and copy to see what happen?
Click to expand...
Click to collapse
You could try creating a folder with a file named .nomedia inside it (that will prevent media scanning) and see if you can transfer the image into that folder.

Mioze7Ae said:
You could try creating a folder with a file named .nomedia inside it (that will prevent media scanning) and see if you can transfer the image into that folder.
Click to expand...
Click to collapse
Make sure you google .nomedia and read about it before you do that. There are some bugs and issues that "can" come along with that. If it works great, but if not
It worked for me on a few folders but I didn't push my luck with it.

Woodrube said:
Make sure you google .nomedia and read about it before you do that. There are some bugs and issues that "can" come along with that. If it works great, but if not
It worked for me on a few folders but I didn't push my luck with it.
Click to expand...
Click to collapse
Can you be more specific about what google search I should use? What I find for ".nomedia" doesn't seem unexpected...

Mioze7Ae said:
Can you be more specific about what google search I should use? What I find for ".nomedia" doesn't seem unexpected...
Click to expand...
Click to collapse
I got these
http://www.droidforums.net/forum/rescue-squad/117253-nomedia-problems.html
These two are for Droid X but .nomedia is .nomedia
http://www.droidxforums.com/forum/d...cture-thumbs-not-opening-nomedia-problem.html
http://www.droidforums.net/forum/droid-x-tech-issues/97843-nomedia-ignored-gallery.html
I am just saying to make sure whoever doesn't put in a .nomedia where it can do some real frustration. "Hey it worked for this folder, why not try it on this folder."

Funny thing is happening on my xt. If i put 16gb class 6 sd card, and when I am on phone call I get random scrambled noise. Until yesterday I thought that it is some kind of hardware failure, but after replacing sd card with provided one with xt (8gb/class 2) everything is working fine...
Sd card is sandisk....
Sent from my MotoA953 using Tapatalk

Apps disappearing after reboot?! [CM6]

Ive had a weird problem the last day or so, when I reboot my device, apps mysteriously go missing. Each time I reboot, like 5 or 6 different apps disappear. This only happens to SD card apps though. This started happening a few days ago but yesterday it got alot worse AFTER I had reformatted my card. Could there be something wrong with my SD card? The apps still appear to be installed in "manage applications" but they look like "com.aac.cachemate.demo" as the name of the app, instead of "Cachemate" and etc...?

did you use link2sd ?

com....whatever in manage applications usually means, that the apk file is missing, while the application data is present
the mess as described, can be seen if your ext partition is mounted too late ...
nadlabak has some fix about it
https://github.com/nadlabak/android...mmit/e5b9b3195687e04af7a7929f8637e77e1efae9a1
but i can't remember where is part of setting the property, after checking and mounting the whole card ...

nikctsh said:
did you use link2sd ?
Click to expand...
Click to collapse
I did not, I used the standard apps2sd built into CM6. Every time I reboot, different apps are missing and then some come back that were missing the time before...They all still appear in manage applications though so they might be intact but I'm not sure if all are, they show up with the default generic android icon, and weird names. "mobi.mgeek.tunnybrowser." (Dolphin Browser) and "net.flixter.android" (Flixter) etc...The storage sizes of the missing apps appear to be different then they are supposed to be. (Maybe)

(This might have something to do with it) Yesterday for hours (before I reformatted) the phone was stuck at "Preparing SD card, checking for errors" so I went online and followed the suggestion an xda member who suggested in another thread to delete the "fsck_msdos" file from "system /bin" which disables the SD card check to see if the SD card has been properly mounted and checked. It seemed to fix my other SD card issue for the rest of the day. could this be related?

Just share my experience , when I was in 2.1 , I used link2sd , and if I boot without sdcard , all my linked apps will happen like that , I think maybe this is the same case as apps2sd . So , what I do is just uninstalled all those apps , and reinstalled some of it ( it's quite annoying to reinstall over 100 apps ) . As you said , all those apps remained as it's package name , so I'm kinda sure our case is almost the same . But when I was in 2.2 , once I booted with sdcard inserted , but after boot completed , all my user apps dissapear , yes , ALL . But anyway , after scan for sdcard problem in OR , all my apps recovered , with no force close , just like nothing happen during the last boot . So also , try to scan for sdcard problem in OR .

It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....

donovanx3 said:
It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....
Click to expand...
Click to collapse
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).

Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
Ok I will run a chkdsk when I get some time to sit down at the computer later. I think it probably is corruption.

Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
SD card fixed with error checking in windows!! Thanks!

Fast Boot option may be the culprit
The advice about checking SD card on Windows or Linux sounds good and I will keep it in mind, but I did not need to fix this sort of problem. I am not familiar with CyanogenMod (CM) in any version, but if it has a fast boot option, read on...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:

Sorry for opening up old thread. My HDC Note3 clone phone having the same/similar issue. The phone have 8G ROM which partition into 2 different name, internal phone (1G) and SD card (5G). Whatever Apps that I install on the SD card will disappear from home menu every-time I re-boot using the power button. However, it it still there when the phone do their own reboot due to something
I try unchecked "Fast Boot" but disappearing act still happen. Any suggestion to resolve the issue?

[Q] USB storage says it mounts, but it doesn't really. It lies!

I have moved an SDCard to a new phone with Android 4.4.
Since that time I cannot see the camera files when connected mass storage in a windows 7 machine. The files that are visible on the computer are from last year, before the move of the card to a new phone. They are all on the SDCard, removable. I removed the SDCard from the phone and all the old files are there.
The camera app is apparently saving new pictures to internal storage. Which does not mount USB.
I should say, a while ago my internal storage got full and I went through and selected "Move to SDCard" on most apps. I don't think that is related, but I am no expert.
I have two camera items in gallery. I can see all the files, new and old, and can send any of them with an SMS message. No problems. When I removed the SDCard gallery only had one camera item.
So to troubleshoot, I have downloaded ESFileExplorer. That can see all the files.
But when I connect to USB and enable USB storage, I can only see the removable card. To test I removed the SDCard from the phone and installed it in a card reader, I can see all the files now.
I do notice one difference now, when I connect the phone to USB with no SDCard installed I get the usual message to enable USB storage, and I click the button, it chuggs, and goes back eventually to the same message, and the USB storage is indeed not mounted. So the stock phone with no SDCard will not mount USB storage, though it offers to.
I have two notifications in the notification pane, one "USB connected" with the robot and the button "turn on usb storage".
I also have a different notification "connected as mass storage" which when selected has four entries, SDCard, which is selected, and PTP, MTP and Charging.
But it seems even though SDCard in checked, it's not actually mounted for some reason.
Any ideas, or is the idea of putting an SDCard in an android phone now a bad idea because of this?
My reading indicates this might be a problem introduced with the permissions changes with KitKat. If so, they really need to fix that. But judging on all the fighting on security issues on Bugzilla which results is just plain wrong development decisions, well, I get it. But I just had to ask you guys who probably actually know.

Firstly, try to be more concise when have problems, post the things you have tried in numbers or columns so somebody who might want to help can quickly know what you have tried and suggest something.
I did not read past your 2nd paragraph.
Secondly, I had a problem with my own sdcard, a kingston 16gb, in the past. Long story short, it became unreadable in my phone. Try to connect it to a PC, if you have an adapter, and back your files there.
The only solution for me was formatting it in my PC. After the format, it works for now.
I also switched phones, formerly a phone running CM11, now a phone running stock Sony 4.4 firmware.
Lastly, it might have to do with the fact that, whatever phone you switched to, some folder naming causes issue for the OS to read.
Again, back your files up, format the SD card.

shadowcore said:
Firstly, try to be more concise when have problems, post the things you have tried in numbers or columns so somebody who might want to help can quickly know what you have tried and suggest something.
I did not read past your 2nd paragraph..
Click to expand...
Click to collapse
Hmm.. Well, then thanks for the response.
shadowcore said:
Secondly, I had a problem with my own sdcard, a kingston 16gb, in the past. Long story short, it became unreadable in my phone. Try to connect it to a PC, if you have an adapter, and back your files there.
The only solution for me was formatting it in my PC. After the format, it works for now.
I also switched phones, formerly a phone running CM11, now a phone running stock Sony 4.4 firmware.
.
Click to expand...
Click to collapse
As I said, the card is readable on a pc, and on the phone. It's hard for me to think that is the answer. I did all that, and posted it.
shadowcore said:
Lastly, it might have to do with the fact that, whatever phone you switched to, some folder naming causes issue for the OS to read.
Again, back your files up, format the SD card.
Click to expand...
Click to collapse
Now that's an idea.
Before I try that I will see if anyone else has any ideas.
But that doesn't explain why the USB storage does not mount when I connect USB with the SDCard removed from the phone. It tries but never mounts. I think that is a clue.
I was gonna post a link to esr's "how to ask questions the smart way", but I don't have enough rep to post the outside link to catb.org.
I do try to follow that approach, and though I am new here I am NOT new to forums. I have been doing this, well, longer by far than most. A lot.

Well, still no change. I may just get another SDCard, put that in and see if that one exhibits the problem.

Virtual?
I did get another SDCARD, no difference.
I need to find the issue here.
I noticed I have two camera items in gallary, one has a camera icon and one has a folder icon.
The one with the camera icon only contains old pictures, from before migration.
The one with a file folder icon contains current pictures, taken by this phone.
When I plug into a computer as USB storage, only the old one mounts, the one with the camera icon. The new pictures (folder icon in gallery) do not mount.
Clearly this seems like a virtual filesystem that has it's pointers slightly wrong.
The camera app is saving it's photos in a directory that is not mounted when USB storage is used. It's not in the SDCARD, but it is in the internal memory.
The camera subdir that is a folder icon should be the one mounting as USB storage, and the other folder should be virtualized as a part of that.
I guess the problem is Kitkat does not save camera pictures on the SDCARD if available, as previous android versions did.
Can anyone suggest steps to isolate this problem?

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.

[SOLVED] Apps suddenly unable to access SD card for seemingly no reason

SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Click to expand...
Click to collapse
Solution answer
So this one is weird.
Everything was working fine untill I rebooted my phone earlier today.
For some reason, since this reboot, apps are unable to access my SD card storage. As far as I know, no update was applied with this reboot. I do not recall tinkering or changing anything related to this recently.
Symptoms
SD card is still visible in the storage tab of the settings (there is no available option to unmount or eject it) or in select cases when choosing a folder from an app, however the content does not show up past the root.
My music player (Oto music) sends an error message "Cannot play this file" while trying to play a song from the SD card
File explorer will not show the SD card directory at all
Resillio Sync has a synced folder on the SD card. It now says "Can't open the destination folder". If I try adding a new synced folder on the SD card and select the root of the SD card, I get the message "Android OS restricts access to this folder"
Google file is stuck in a loop trying to get permissions to access the card
SD card works just fine on another phone.
Other SD cards have the same problem with my phone, not just this one
SD card does not show up when using file transfer with a Windows PC
Rebooting the phone did nothing
Removing the card and putting it back in again did nothing
Formatting the card did nothing
I factory reset the phone. It worked, but the problem came back at the first reboot.
Current state of investigations I have reset the phone a second time and reboot it every time I install an app, uninstall or disable a system app or change some settings. So far the SD card is still accessible so I know what it's not:
it's not the fault of disabling system apps
it's not related to using a work profile (Insular)
still haven't found an app that causes it
Apps I have not tried re-installing on my second reset and that might be the curlprit:
Shizuku (I have my suspicions on this one, let me know if this one is known for causing similar bugs) Not Shizuku per se but a developper option needed for it (see solution answer)
I have no idea what could cause this, all I know is it's related to my phone in particular and it appeared out of nowhere.
I am using Android 13 on ColorOS.
Thanks to anyone who can help.

Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.

blackhawk said:
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
Click to expand...
Click to collapse
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?

Iune said:
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Click to expand...
Click to collapse
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.

blackhawk said:
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
Click to expand...
Click to collapse
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.

SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.

Iune said:
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
Click to expand...
Click to collapse
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.

blackhawk said:
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
Click to expand...
Click to collapse
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help

Iune said:
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Click to expand...
Click to collapse
Yay! Well done. So many settings...
Traditionally a hard reboot is killing the power to the mobo... I believe, or maybe I just watched too many sci-fi movies You do it by holding the power button (or combination of buttons) down for 20-30 seconds.
On cams and older phones you simply remove the battery for a few seconds. It clears any volatile memory settings in the chipsets or semiconductors by cutting to power to everything.