Related
All of them that I've tried, thus far.
You MAY NOT see this, by the way, depending on your access pattern, but it is DEFINITELY HAPPENING.
The problem is that its really, really ugly - your card's data is slowly being DESTROYED.
When it hits the "wrong" file, you will find out - the hard way.
This is NOT a "cooked ROM" problem - AT&T's base 6.1 load does the same thing (!)
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
How do I know its damaging data? Because it has scrambled my TomTom map files "just enough" that TomTom comes up "No Maps" (!) - but the file names ARE THERE. The signatures are destroyed - it only takes ONE BYTE of change in the wrong place to do it.
Now what the ##$)! is PIE doing writing in that directory? Its not - on purpose.
The RSS reader will reliably do this too.
If you point them at main memory, no problems. Its SPECIFIC to the SD handler.
Its also SPECIFIC to 6.1 ROMs. 6.0 does NOT exhibit the problem, yet EVERY 6.1 load I've tried can be provoked into doing this.
The only fix is DON'T WRITE TO THE SD CARD via programs. Well.... that's not the WORST thing in the world on a Kaiser as it has a lot of internal memory, but....
Anyone know what the #@#$ is going on here - or have a fix for it?
PS: If you think you're not running into this, don't say I didn't warn you when you find one of your files destroyed without warning. I have run byte-wise compares of SD images and the corruption appears to be almost completely random. And yes, its across both SDHC and non-HC cards (2GB) - both are hit by it, and I've got three, all from different manufacturers. This is VERY reproducable and its not hardware either since 6.0 does NOT exhibit the problem.
Quite interesting... which rom build are you using ?
Have tried several - the most recent being the Hyperdragon 11/15 build.
The stock AT&T 6.1 build did the same thing as soon as I switched PIE's storage to the card. Its not instantaneous but if you browse for a significant length of time it WILL do it.
Flashed to 3.29 HardSPL to be able to load the various cooked ones here, all that I've tried so far do the same thing. Flash back to 6.0 AT&T, no problems.
VERY consistent.
I just put 3.28 HardSPL on to see if that changes anything. Can't imagine why it would, but....
Its pretty subtle if you don't browse heavily - if you get a "lockup" with PIE while its set to write to the card YOU ARE SCREWED. You may not know WHICH file got smashed but I guarantee one did. If it smashes the MFT then the fun really begins (the entire card's contents are gone), but I would prefer that to a RANDOM file getting destroyed!
I have run sector-by-sector compares and have found that where it "scribbles" when it happens appears to be completely random.
And again - 6.0 does NOT do it, and if you only READ from the card, its fine.
I suspect that its a "per-event" risk and so anything that runs from the card and writes data back there EVENTUALLY will screw you - its just a matter of time.
Genesis3 said:
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
...
Click to expand...
Click to collapse
thats why it is strongly recommended NOT TO store ie cache to storage card. Keep it on device memory. There is no fix for this problem yet except keeping ie cache on device.
Sounds pretty easy to bypass the problem, eh? Don't store stuff to the card. No big deal. I mean, c'mon, it's not like we're going to run out of memory storing the IE cache on the device.
Beside that, it must only be IE as I've always used the card to store my email and attachments and have never had a problem. However, I am using a 16GB card...perhaps that makes a difference. I've been running various 6.1 ROMs (including some questionable betas) for almost a year now and have experienced ZERO corruption. Also, if it makes a difference, I perform so much data transfer with my card on a weekly basis. Pretty much filling and emptying about every third day.
It is NOT only IE.
The RSS reader that is in there (RSSHub) that HTC stuffed in the later roms does it too.
I managed to trigger it last night with RssHub; thinking IE was the only culprit cost me (another) reload of my SD card.
Be careful - if its per-event risk then ANYTHING you store on the card (e.g. pictures, etc) could cause it, and apps like TomTom that write places you set as destinations to as a cache can cause it too - its just that being data dependant the more often you write, the higher the risk.
BTW this is a 6.1 issue that does NOT affect the Wizard - I have had a custom (I cooked it) 6.1 ROM on my Wizard for six+ months without a single screwup. But I've yet to find a 6.1 ROM for the Kaiser that DOESN'T have this problem.
BTW, is there a 6.1 ROM around WITHOUT the new PIE? God I hate the new format on that thing...
I have been beating on PIE stored on the card, plus RSS stored on the card now for over an hour - after loading HardSPL 3.28 (was running 3.29) and SO FAR I haven't had it happen.
Now this doesn't mean much, but that I got a solid couple of hours in without it blowing up - when I was pretty reliably able to do it previously - might be significant.
Or maybe not.
I'll run this way for a week or so and see if I can get it to misbehave.... I have card backups
yah i have learnt to back up my sd all the time cause im CONSTANTLY getting corruption..but corruption i can see like messed uop names and folders which ive found more consistant when i have sd power settings set to enabled in advanced config..
I have also witnessed RSSHub destroying my card several times
I remember this problem when WM5 came out on the Artemis. It was linked to the power state and the device going into sleep mode. It never occured when you used the power button, only when it went into automatic sleep. I think there are options in schaps advanced config regarding this - might be worth a try.
Genesis3 said:
Have tried several - the most recent being the Hyperdragon 11/15 build.
Click to expand...
Click to collapse
I mean CE build number and aku. We have now many available builds from which to choose, and we could investigate whether it's a problem related to an HTC driver alone or if there's something in the SYS services too which has to be patched. I'm not talking about workarounds at all.
20931.1.5.0 (assuming the SYS and XIP were ported)
I don't have the numbers from the AT&T load handy.
Downgrading the SPL MAY have fixed it. I haven't had a lock/trash since last night when I changed the SPL. Hmmmm..... that "hotfix" may have been a "hotf$ck" instead.
Will update as/when I learn more.
This is NOT WM6.1 problem, if anything - it is WinMo's problem in general (all versions).
I have witnessed exactly same problem on WM 2003, WM2003SE, WM5, WM6 and WM6.1 - and I bet its the same on WM2002 and WM2000 (I just never had any of those ancient devices).
Solution is very simple:
DO NOT move IE cache to SD card, that's all.
Unless you have to (i.e. my iPAQ 6515 have literally no space left on Main Storage and I have to use SD for IE cache etc) then simply make at least weekly backups of your SD on your PC, its not a big deal, but it is annoying like hell (specially when it happens "on the road").
I have same problem several times!
Most offen it's happend in A***OS Smart Rom (don't remember full name), then i flash into wm6.1 off and it happends only one time. I use StorageTools to ix My Card after that (not data, only card)...
Is this heal????
Just use Opera browser. I dont have that problem in my tilt, although i did had problem with hermes, and scan and fix errors for the card made it go away. And i also a 2GB card, maybe it is an issue with higher storage capacity cards.
hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?
mohsin_75 said:
hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?
Click to expand...
Click to collapse
To recover that files you can use de windows tool error checking that will recover your files but to the found.000 folder (hidden), but the files are useless because is will be on the wrong extension and name
you have now 2 solutions:
1 - is guest the extension of that files and rename it
or
2- use the program named "getbackdata for fat" and it will correct the name and the file extension but not the correct name of the folder where it was. but better than nothing.
hope i could help
I saw this many times with RSSHUB - finally moved to main mem and have not seen it since. I also don't use PIE. It will be interesting to see if its 3.59 causing the issue, please keep us posted. I went a bought a new card thinking that it was a bad card:
If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.
Genesis3 said:
If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.
Click to expand...
Click to collapse
Does this happen with both cmonex’s & jockeyw2001’s HardSPL 3.29?
It happens with the ORIGINAL REAL 3.29 SPL that AT&T is shipping with their STOCK 6.1 ROMs!
That's not one of the hacked ones - that's OEM. I was able to REPEATEDLY lock the device and scramble the card by sticking PIE's cache on the card with the stock AT&T ROM.
I'm near 100% convinced its the 3.29 SPL that is FUBAR'd and not the hacking on it. I don't know why it should matter (its just a boot loader) but perhaps its doing something funky with the SD interface and whatever it does survives ROM initialization during the boot process.
In any event with 3.28 on my Kaiser I have had ZERO ISSUES with SD corruption or freezes of any kind, going on a week now. I've had no reason to reset it - at all - during that time.
I won't call this "conclusive" for another week or two, but given that with my usual usage I wouldn't survive ONE HOUR on 3.29, well, you tell me.
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.
Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?
Did you REALLY need a poll for this? Seriously?
Did you look for information on this? There are at least a dozen threads on SD card issues on the Moto G 2015 just on XDA, much less the dozens of other threads everywhere else... Here is a quick summary, assuming you have tried clearing the cache partition, factory reset, etc:
50% of the time, it's the SD card itself that is bad, or there is a compatibility issue... Try a different brand, size, speed, etc. The most compatible cards seem to be Samsung EVO+ or EVO Plus series (they are different), PNY Elite series, Lexar 633x or 1000x series, and Sandisk Extreme or Ultra series but again this varies by individual handset. Kingston cards are hit and miss, some people have good luck, others not so much.
40% of the time it's a hardware defect or damage inside the device, nothing you can do but replace the microSD socket which requires micro soldering... Probably best to leave it to professionals.
10% of the time, it's a mixed bag... sometimes a couple layers of scotch tape on the back of the card will help (increases tension on the contact fingers slightly), sometimes it's counterfeit cards (don't kid yourself, this is a HUGE problem, use SD Insight to check), sometimes a U3 card helps, or who knows what else.
The point is, about half the time switching to completely different card fixes the issue, and since microSD card are cheap, especially at the 16GB-32GB card size, so it's a good place to start.
+1
replace card.
frenchiveruti said:
Hello everyone, I'm the sad owner of an Osprey terminal (XT1542), it was a gift from my family so I can have a more modern phone and so far it's been more a headache than a good thing.
My problem is that at first I believed it was some random bull**** from the Stock Marshmallow app, using Spotify and trying to download my playlist would end up with my internal storage full because Spotify (and any other app WITH the required permissions to "write" onto the SdCard) couldn't recognize the SD even after it displays it as totally readable, this creates a problem because the camera, the file explorer, even the ADB tool can't write onto the SDCard.
So, after using marshmallow with a 16GB class 10 Kingston SD card I did the following:
Tried every single possible solution to the issue with the vainilla Marshmallow 6.0, that includes formatting the SDcard OUTSIDE the android, different partition size, factory factory reset, nothing.
After failing on that, tried updating marshmallow, Failed, something about the "modem" isn't right on this phone.
So, I did what every XDA user would do, grabbed a brand new Nougat ROM and OGapps mini and installed it on the phone.
I didn't root the phone though....
Failed again, the same issue as before, so "It's the SD CARD YOU MORON" would be the answer here!
Nope. Brand New SDCard replaced with even a newer SDCard (same type) and again, the same issue as before.
As a note if I unmount the SDCard and mount it again via the config>storage option, it becomes "writable" again. For a while...
adb outputs when "push": failed to copy 'log_2017-04-13_OSPREY.txt' to '/storage/4FD8-E1EA/log_2017-04-13_OSPREY.txt': couldn't create file: Read-only file system
So, this leaves us with the simple fact that the issue is... Hardware? Software? Kernel? Maybe if I reset the phone to stock factory fully flashing every single bit of it it would work?
I really need your help in this one guys, thanks for your time.
Greets, let me know if you need any more info or maybe a log on the issue?
Click to expand...
Click to collapse
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.
reactorcoremeltdown said:
I'm in the same boat as you. Tried lots of different brand new SD cards from different vendors, every time the same bug appears. So the only working solution is STICK TO ANDROID 5.x. For some reason Motorola has screwed up the sdcard driver in the kernel, maybe because introducing new fancy features on 6.x and above. I highly suggest you to install CM 12 and keep it on your phone as long as possible. Unfortunately, there's nothing you can do with it, unless you are a pro kernel developer.
Maybe this will help you.
Click to expand...
Click to collapse
I finally found someone with the same problem as me! (well, that's bad news for you and me bad at least I'm not the only one with this problem)
So, you tried everything like me and yet no way to make it work? I couldn't test a different "brand" of SDCard but I did try different ones and checked if they were fake ones and still I have the same annoying problem. Damn...
I think yeah I'll have to go down to an android 5 if there's no way to fix this.
I'm wondering if a custom kernel can solve this, but it's really difficult to know the "why" is this happening, and the logcat doesn't help that much to be honest, at least not from the side of knowing where or what to read that could be causing the issue.
Hey folks,
Bit of a long story, short version is "Phone seems wiped, did I mess up? If not how is it possible?"
I've been passed a device with a report that it had an important video file on it that was accidentally deleted, and tasked with seeing if the file was recoverable. I was also later passed the only SD card (2gb) in the owner's possession.
Phone first. I followed instructions to root the device and rip an image of the data partition. This did mean uploading the root zip to the phone, a risk I undertook before discovering you can get a temporary root. I don't think that act accounts for what I found.
I used these two [1] [2] links for guidance. Ripping the data took many attempts but I did eventually get a 32gb-ish image down the wire. The image seemed to mostly be zeroes viewed in hex editor. Video-wise, recovery software found only operating system background videos of clouds. There didn't seem to be any user data on there at all. Recovery seemed to run very quickly with image stored on an SSD. As I say, even if I'd overwritten the video file header with the root zip, there'd have been other data on there, seems to me. Other photos. Other videos. Perhaps I ripped it wrong. Ripped on a windows machine. Is ripped even the right word, I'm not very good at this and a bit stressed
Did I get the wrong partition? Wouldn't be 32gb then though, right? I ripped mmcblk0 and mmcblk0p37 or whatever seemed to be mounted as the data partition, various times, and got similar results regardless of the resultant file size (i.e. stop half way through, data is mostly zeroes, get the whole image, it's mostly zeroes, all ripped images contain the OS video files).
Did rooting / flashing recovery wipe the data? Seems unlikely. I did start the phone by accident at one point (reboot from recovery seemed not to acknowledge my holding down the volume / power combo to get back into recovery) and OS claimed to be "upgrading all the apps" so I powered it down straight away. This is the terrifying moment for me, did something I do kick off an OS process that wiped the phone?
Owner claims never to have done a factory reset, and in any case that doesn't wipe data anyway right? Only file table. So data would still be there. But like I say they don't claim to have wiped phone, only accidentally deleted files. Even automatic OS upgrade would leave data intact. Flashing a mod would do it I guess but that's not happened.
SD card next, it's labelled "BLACKBERRY" and owner did have a bb once. They say the card was in the phone, I figured maybe phone was using sdcard instead of internal memory for user data but the card is essentially blank, it's like it has never been used since it was formatted by the blackberry. No data on it, just 6 folders. Recovery software finds literally nothing. Seems like a dead end. Ripped on a mac using dd.
Possible that the owner had another sdcard at some point but they cannot recall having one.
Also possible I ripped the data wrong? I used sudo dd to get it, then ran Disk Drill on the mounted .dmg, which is 2gb, the size of the sd card.
dd would not substitute zeroes for unallocated filetable areas, right?
So this leaves me with so many questions about how we got to this point with no data, but mainly I want to sanity check what I've done here so I can be more confident I haven't wiped the data I'm trying to recover myself. Then it'll be a case of digging deeper into what happened to this phone between the video being taken, the video being deleted, and the phone arriving in my hands.
Thanks in advance to anyone for literally any input!!
I've asked the owner to trawl their cloud drives for HTC backups, hopefully they had daily backup linked to one of their clouds. Otherwise, I guess I'm at a loss...
If the lost data cannot be scanned by the recovery tool, they has been overwritten. But fortunately, the owner to cloud drives for HTC has backup file.
Thanks bobii. What's confusing is that the data I retrieved seems mostly to be zeroes, which wouldn't be the case if it had been overwritten. Unless it was overwritten with zeroes, which as far as I know would only happen if you flashed a brand new OS or intentionally wiped the data partition, both processes I think that the owner would remember doing.
Well, this is rather vexing.
I've been hard at work trying to backup / transfer data from my extremely old Samsung Galaxy S5 that seems to be coming to the end of it's useful lifespan. The S7 was next, but aside from running out of internal storage, I thought I still had time on that one (I wasn't experiencing a lot of slowdown or any crashes).
I went out for a couple hours (taking my newer phone), and when I came back, I saw my S7 on the insert the pin code screen. When I put the correct pin code in, the "unlocked padlock" stays on the screen for ages, before the phone restarts and I am shown the pin screen again (if I insert the wrong pin, it says so, so I am sure that I am not inserting the wrong pin).
So for the first time in my life, I am dealing with a spontaneous boot loop. This device has never been rooted, had a custom recovery installed or even the bootloader unlocked (it's the Exynos version, so presumably it would have been possible, but I decided that I wanted *one* unrooted device just in case, and given Knox, I decided that this was the device that will remain unmodded).
Anyway, that's for the story, but the question is, is there anything that I can try before the nuclear option (factory reset etc.).
Fortunately most of the photos are on the MicroSD. There are perhaps two or three apps that I would have liked to backup (they did not have a convenient built-in backup system) but I am just wondering if there is anything I might be able to do at this point? For instance, would wiping the cache be an option? Or is there anything I might be able to do with adb?
(Note: The device is running on Android 7)
Thanks.
Don't set security passwords for device access as you are the one most likely to be locked out.
If the boot loop wasn't caused by a hardware failure it's likely a app you loaded. Launchers and power management apps are prime candidates. Leave at least a couple gb of headroom on internal storage.
A factory reset is the easiest solution. Be careful what you load next time... take out the trash.
Use the SD card as a data drive, all critical data and everything you need for a reload goes here. No apps. Only apps, and the temporary download folder go on the internal memory.
The DCIM folder can be set to the SD card as well, but there can only be one DCIM folder and don't change its name. If a second backup folder is used on the SD card instead do not name it DCIM.
ApkExport can be used to make installable copies of apps for transfering them and added the data drive as well, no Playstore needed.
Do not use Kies or SmartSwitch when going between different type devices or OS versions. It can cause issues.
Cut/paste critical data, verify the data is readable and all there. Don't trust Kies or SmartSwitch with critical data.
Never clone data drives.
Never encrypt data drives.
Regularly redundantly backup the SD card data drive to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Thanks for the reply.
1. No app was recently installed (past couple of weeks)
2. Hardware failure? Maybe, but it is rather out of the blue. Phone has not displayed any unusual behaviour, it hasn't been taken out of the house for a week or so (it is really in the process of getting retired). And I would like to ascertain it.
3. I am aware I can just nuke the whole thing with a factory reset, but before taking that easy option and effectively lose some data I'd like to retrieve if possible, I would like to other options.
And rather than tips on what I should've done or can do next time (much of which I am already doing), I am looking for advice on anything I might be able to try -before- nuking the whole thing.
For instance, could the log-files (there are quite a few of them) provide hint in what went wrong? Any option of re-installing the OS without wiping the data partition? Since I am on a fairly old version of Android I may also have the option of doing a minor update. That kind of things. I am thinking that there might also be the possibility that the system files somehow got corrupted and perhaps a re-install or system update might be worth trying.
I am basically looking for options that will not, for the time being erase the data partition. If it comes down to it in the end, then fine, but that is the last option not the first.
It sounds like it got spontaneously corrupted. Perhaps a flash memory cell failure. If so it may or may not be "self healing" with a factory reset or a reflash.
If you have ADB access you may be able to fix it.
Otherwise your options are limited to what's on the boot menu.
Try doing a hard reboot (simulates pulling battery).
If you try booting it a bunch of times it may go into go safe mode. I've seen that behavior in Android 9.
That's extent of my skills, sorry.
The reason why I posted how to prevent data lose is because sometimes that's all you can do.
Internal memory data I consider expendable, the SD card data... potentially expendable.