My brand new Vox is continously rebooting. The only way I can get it to boot is to take out the microsd card, then put it back in after it boots. The microsd card works fine afterwoods, but its really annoying.
Anyone else have this problem?
Looks like you installed something which the Vox doesn't like.
Perhaps facade? (see http://forum.xda-developers.com/showthread.php?t=307378)
Had the exact same problem. Removing the microSD worked also.
Afterwards it was working fine. The problem started after installing
BatMonitor on the device. Removing it solved the problem permanently.
I would suggest you go through the programs you installed and check
to see wich one is causing the issue.
Thanks guys, I have a feeling you are both right and it is a programs I have installed. I wonder if it's newsbreak as my data file is on my microsd card. I guess I should wipe the device and start over....
For a temporary fix, remove the MicroSD, boot, then put the MicroSD back on.
For a more permanent fix: Install SKTools Lite and run the "Notifications Queue" tool. Then Press ACTION > Mark Duplicates. If you scroll down you will see some duplicates checked. Next press ACTION > Delete marked.
That should keep you running for a while. If the problem re-appears in the future, repeat this procedure.
Thanks. I read that post on Modaco too, but it didn't work for me. For now I just remove the microsd card when I reboot. I guess I will wipe the device and start over at some point...just had everything I wanted loaded right
ayan said:
For a temporary fix, remove the MicroSD, boot, then put the MicroSD back on.
For a more permanent fix: Install SKTools Lite and run the "Notifications Queue" tool. Then Press ACTION > Mark Duplicates. If you scroll down you will see some duplicates checked. Next press ACTION > Delete marked.
That should keep you running for a while. If the problem re-appears in the future, repeat this procedure.
Click to expand...
Click to collapse
Had the same problem. Thought it was the Facade, but it turns out not. I don't know what it is but I basically did a hard reset. Put everything I wanted back into the phone and than turned on without MSD card. Once it rebooted, I put the card back in. Since than no reboot problems so far.
I had the same problem, although I am not sure if it is related to installing any particular program. Initially the phone was fine and then it started re-booting on startup. I saw a suggestion of running SKtools and removeing duplicates in the Notification table, this worked for a while, then it came back again.
At first the only cure appeared to be to re-boot without the sd card inserted - inserting it again after the phone was running (I even had the same problem if a blank sd card was card inserted)
I then read about someone putting the phone in Flight mode before turning it off - this also solved the problem - better than removing the card each time.
Mike
yep, this happened to me, although i have no programs installed on my S710! (tho it did have a nasty drop onto the ground - which shouldnt realli affect it)took out the card, and it booted up fine! i keep my phone on 24/7 normally but had run outta battery!
Cheers!
Formatting the MicroSD card worked for me
Problem came back again today, and sett flight mode did not fix it, then i found this http://www.modaco.com/Continuous-reboots-t256186.html
which suggested renaming omap850_sdhc.dll to omap850_sdhc.dll.ol
but in my S710 I only have omap850_sdhc_mux.dll and that file is in rom and I can't copy or rename it.
Looks like it might be a sd card driver bug.
Mike
wizgnome said:
Problem came back again today, and sett flight mode did not fix it, then i found this http://www.modaco.com/Continuous-reboots-t256186.html
which suggested renaming omap850_sdhc.dll to omap850_sdhc.dll.ol
but in my S710 I only have omap850_sdhc_mux.dll and that file is in rom and I can't copy or rename it.
Looks like it might be a sd card driver bug.
Mike
Click to expand...
Click to collapse
have you tried to edit the file with a copy of total commader??? sorry if it's such an obvious question...
I did try this with Total Comander!
Looking around at other posts/forums it looks like it is a WM6 problem. Probably related to the SD card driver.
At the moment the only consistant suggestion, is to reboot with the SD card removed and insert it when the phone is back up and running.
I managed to get the phone to boot with the SD card inserted!
I know that when booting that I do not run any applications which are installed on the SD card. But the home screen does display things which are located on the SD card - in particular the skype plugin, and the mru list display icons from files located on the SD card.
I change my homescreen to "Sindows Simple" which does not contain either of these and re-booted.
The phone came back up first time!
- Is windows trying to access the card too soon - before the driver has loaded maybe?
Mike
wizgnome said:
I managed to get the phone to boot with the SD card inserted!
I know that when booting that I do not run any applications which are installed on the SD card. But the home screen does display things which are located on the SD card - in particular the skype plugin, and the mru list display icons from files located on the SD card.
I change my homescreen to "Sindows Simple" which does not contain either of these and re-booted.
The phone came back up first time!
- Is windows trying to access the card too soon - before the driver has loaded maybe?
Mike
Click to expand...
Click to collapse
Not sure if its trying to access it to soon but with my HTC Herald I had similar problem. By removing and home screen plugin's related to the memory card, as well as any other links to the memory card such as storing PIE cache and saving pictures it seemed to work for a bit, but just as I thought I solved it, the problem re-appeared. Paul seemed to have fixed the issue for ppc's (sdhc dll that was causing the problem)but it doesn't seem as though the solution can be carried over because the vox is not SDHC. Another cause the some speculate is that there are multiple notifications that boot at the same time, maybe cleaning these would help.
On another note I have just upgraded my friend's vox to the dopod rom and it seems as if the problem has disappeared (hopefully for good.) I will try to invoke the problem again by running programs from the memory at boot and see if this nag has been squeezed out by HTC sister company. Has anyone else tried to upgrade to the dopod rom???
cheers
Hi,
I had previously removed duplicate notifications and ensured that no applications on the SD card were run at start up, including setting the browser cache back to the phone memory.
I can now cause the problem to occur or boot normally just by switching homescreens.
I edited my home screens xml to remove all plugins that refered to applications on the sd card, including the mru list - this home screen allows normal boot. The other version causes the re-boot loop.
Mike.
I can confirm that my numerous attempts to invoke the boot-loop after upgrading to the dopod rom have thankfully failed.
neptune 1
boot loop 12083798
Ok so maybe the boot loop has gotten the best of me (atleast 40 hard resets) over the past couple of months, but the problems have been choked to death on my herald and the vox...any last words...
EDITS if this mf'er pulls an Arnold like "I'll be back" I swear ima go all terminator on this phone and blow it to pieces with a pack of m-80's
I managed to solve this problem on my phone by renaming the directory "/windows/Autorun/Storage Card" to "/windows/Autorun/OldStorage Card"
Maybe it would help in your cases..
Wondering if anyone can think of anything I can try before returning the phone this afternoon.
What happened:
Yesterday, I rebooted the phone because a prog had hung and wasn't responding to force quitting via Applications. When I tried to turn it on, it didn't respond -- zilch. I plugged it in and tried a few times to turn it on over the next hour with no luck. Finally it started to boot and hung at the ATT screen, but after sitting there for a min, horizontal lines appeared across the screen. Tried again over the next hours with the same result.
Left the battery out overnight. A few minutes ago, I tried it again and it actually got past the ATT screens, but after the Samsung logo sequence was done it hung on the blank screen. The phone is rooted and clockworkmoded, so I tried to boot into recovery to do a nandroid restore. No dice: I get an error about not being able to write/read to the sdcard.
So at the black screen, I can shell into the phone. Can't SU (seg fault). Can't get to the internal SD storage (which is all I really want at this pt. I took a bunch of awesome pics while surfing yesterday and want em).
It looks to me like there is some sort of corruption of the internal storage. Any thoughts would be appreciated.
From the looks of it your nand crapped out...
Sent from my SAMSUNG-SGH-I897 using XDA App
Yeah thats what I'm thinking.
This does highlight a flaw in the storage setup: having internal storage like the iphone is seriously awesome from the usability standpoint. But android is set up to assume that when you back up, it's to a removable card. So I have a Ti backup, but that doesnt help me if I can't get to it if the phone dies.
Seriously bummed. I've had a really crazy # of dead iphones (like 6 over two models -- its one of the reasons I finally switched) but the upside was that when it was switched out I was rocking all my stuff on the new phone within an hour. With this, I'm now starting from scratch.
FWIW: I got the phone working again by wiping user data and reformatting the internal storage. I'm guessing that there was something corrupted.
Here's the warning I'd offer though: Ti backups etc do you no good if they're on the same file system as the phone boots off of. I was backing up regularly, but since they were on the internal drive that did me no good. Unless I'm missing something, Ti doesn't allow you to choose a location (just a folder name) for backups.
if it lets you choose a folder name then choose sdcard/sd that is where the phone's linux mounts your external SD Card.
Also I keep my Titanium backups and Nandroids on my Computer for extra safety.
Is anyone running into a problem with apps that have been moved to sdcard just disappearing? Most of the time I see little green droid icons all over my launcher (ADW), and lots of missing apps in the app drawer. I can reboot several times and eventually all show up.
I'm running ee4_debloated-v421 / 0730_charge_voodoo kernel / sdcard_patch. Am on my second handset (first one had a clicky button go dead). The earlier handset occasionally did the same thing.
I presume the sdcard is the culprit, as it is the common element. But I have popped it out, run fdisk and defrag all with no errors.
Any theories??
I had this happen when I first got my charge. How I fixed it was I took the SDCard out of my phone and put it into my flash media reader, and then did a full format using HP's Format tool with default device settings. It took a long time to do the full format, but after doing so, I didn't have any more issues with apps disappearing that were installed to the SDCard.
Full format, huh... (gulp) well it's certainly worth a try! I'll report back.
Thanks,
Larry
ljcorsa said:
Full format, huh... (gulp) well it's certainly worth a try! I'll report back.
Thanks,
Larry
Click to expand...
Click to collapse
I know when the phone first came out, there were several users with SDCard problems. I'm not sure how others fixed them, but a full format and a half hour or so fixed mine
Well, I'm disappointed to report that the problem did not disappear :-( Could it be the contents? I copied *everything* from the card before full formatting with the HP tool (which tooks hours as you said), then copied it all back. Same result... if I reboot enough times it will come up with all apps showing.
I've ordered a Class 10 card. Plan to use the HP tool on it straight away. What else would you recommend? Maybe move all the apps back to the phone? Would you start from a fresh load of the ROM?
Many thanks,
Larry
ljcorsa said:
Well, I'm disappointed to report that the problem did not disappear :-( Could it be the contents? I copied *everything* from the card before full formatting with the HP tool (which tooks hours as you said), then copied it all back. Same result... if I reboot enough times it will come up with all apps showing.
I've ordered a Class 10 card. Plan to use the HP tool on it straight away. What else would you recommend? Maybe move all the apps back to the phone? Would you start from a fresh load of the ROM?
Many thanks,
Larry
Click to expand...
Click to collapse
I know that DroidXcon over in the Android Central forums advises NOT to move apps over to the SDcard because of problems like you have experienced...the higher (class) speed card may help. I've noticed that on my stock class 2 card when I view a subdirectory that contains large wallpaper files using QuickPic or Gallery, the thumbnails will often "time out" and not display towards the end of the list unless I refresh the listing several times. I would assume it is for the same reason that recording video to the class 2 card will time out after a few minutes.
Good luck with the Class 10 card...keep us posted!!!
Well, the Class 10 arrived in time to try again, so formatted with HP Utility and copied all the saved files over. Same behavior.
If it's the sheer quantity of apps on the SD card and there is a timeout involved, that might explain it! Reformatting the card would effectively defrag it which would speed it up, perhaps explaining imnuts' observation. And if reading in all those apps at startup is not I/O bound but maybe CPU bound, that would explain my experience.
I'm going to try moving apps back to the phone just to see.
Wow, this is persistent. Moved all the apps from SD back to phone using TiB, which seemed to hang sometimes. Tried different access methods with no clear winner. Anyway, after a reboot, the situation was unchanged. Unreal.
So I am starting from scratch with a freshly-formatted Class10 card, a full data/cache wipe, and a new ROM: GummyChargedFE1.9.1. Haven't had a problem yet, but haven't restored anything to SD either. Proceeding cautiously.
Ok, I'm converted. GummyChargedFE1.9.1 solved this problem. Everything seems to run better. Added the V6 SuperCharger thing which tweaks minfree levels and much more, and the combination runs extremely well.
Biggest problem for me is that I'm satisfied... spent the last two years trying to get my "original" Droid to run well, then got the Charge, started over. What do I do for an encore?
Fast Boot option may be the culprit
In case anyone is following this old thread ...
I did not need to install a new ROM
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:
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.