hi,
I deployed the usbmodeswitch.xap to my wp7 (htc hd7), i switched the mode from zune to diag for usb tethering.
recently, i update phone to "nodo" version. now, my phone is no longer detected or recoginzed by Zune Software. (and charging is not working via usb)
would someone please help to resolve this issue.
Thanks,
CT
Only way to go about that is a hard reset, sorry.
I did hard reset many times to restore back to factory setting but won't help.
is there any apps similar to usbmodeswitch on marketplace so that i can use to change the mode back to zune?
Unfortunately, you'll have to use WiFi sync until you someone can figure a way to jailbreak NoDo.
Either that, or you will have to flash your HTC HD7 with the leaked ROM.
has someone try to swap out the memory card from the other jailbreak phone?
I have 2 hd7 phones. i'm thinking about doing this or should i wait for jailbreak custom rom.
thanks,
ct
swapping a memory card is just asking for a factory reset. basically when you the phone first sets itself up, it creates what is called a RAID-0 setup, where all memory, internal and external, is seen as 1. All phones come with some internal memory, even if it is tiny, but as a result, swapping memory cards will result in corrupt data and the phone will respond with a full factory reset.
thank you so much, Gate Keeper. i thought phone os run directly on sd memory. by swapping the memory of the same hardware, the should be work. i guess i was wrong.
2 days ago my son was born and I used my HTC HD7 to take all pictures and videos of him and my wife, these were the most amazing and precious moments of my life and I captured them all on my phone.
My wife and I both have identical HD7 phones, last night I took my phone home and charged a spare battery for her, today I took this to hospital and we both turned our phones off and waited until the "goodbye" sreen had vanished, and then swapped the batterys over in the phones so she had the fully charged battery and I had the low/quarter full battery. When she switched on her phone, everything was fine, but when I switched on mine I saw some screen flash up saying something about "pressing the volume buttons to erase your phone" I paniced at this point and did a stupid thing and took out the battery again. After I put it back in it booted up and gave me the "seup windows phone" screen. At this point I switched my phone off and havent swiched it back on since.
Is there any hope of recoverying the pictures and videos? Apps, contactacts etc I dont care about, but these are the most important moments of my life I want to recover. I have no idea what happened, but at the moment I am very upset.
I am an IT technician myself, and in the past it has been all stored on the memory card, but there is no way to remove the memory card on this phone. I am willing to destroy the phone to preserve this data if needed, Is there any way I could remove the memory card? I could try some data recovery software if this is the case.
Please help, the might be a simple way to sort this I haven't been able to find. I have now been up 36 hours as my wife has had a lot of complications and lost a lot of blood last night and ended up having a transfusion. Sorry to be so personal, but I am really desperate to save these photos.
you might have accidentally held the volume button when you turned on the device, and that triggered that factory reset feature.
I have done this accidentally with my trophy as well when i was running late for work, but instead of removing the battery, i held down the power button and tried again, but when it turned on it didnt show me a setup one where you type in your windows live id, instead my one was an image of a windows phone suggesting to connect to a laptop via USB cable, again i didnt panic and turned off the screen and held down the volume button and the power button and i did trigger the factory reset in purpose, once i was at the factory reset screen, pressing any other button (camera key, and sleep/wake/power key) apart from the volume keys disables the reset feature and will continue to boot to wp7.
I dont know if Im helping, but thats how I resolved my situation.
How to remove memory card
Hi Herr_ando,
Firstly Congratulations on becoming a father
Secondly do not worry all is not lost, if you cannot get the handset to boot normally you can remove the memory card (without voiding the warranty too) A lot of people figured this out when they had fist purchased the HD7 and have since used the following video clip to help them upgrade the memory card size:
http://www.youtube.com/watch?v=8EcGUX3NwnQ
I have done this myself but had trouble when reading the memory card via a dongle (this is due to the differing format used by WP7) the way i got round this was either by putting the memory card into an old N97 nokia phone and using the pc software to remove the pictures from it or to use a flash drive recovery app found via google.
Hope this helps,
Creamy
It doesn't sound like you actually performed a factory reset so it's probably fine... but if you want to be safe, pull out the SD card like the previous post says. It might make you factory reset after putting it back in, but if you already save your pics and videos, who cares, right?
thesecondsfade said:
It doesn't sound like you actually performed a factory reset so it's probably fine... but if you want to be safe, pull out the SD card like the previous post says. It might make you factory reset after putting it back in, but if you already save your pics and videos, who cares, right?
Click to expand...
Click to collapse
It's okay to take out the SD card and put it back as long as the phone isn't turned on in the meantime and nothing is written to the SD card.
So it's okay if you use the SD card to recover photos and put it back in, as long as the phone stays off in this time.
@herr_ando: Congratulations on becoming a father!
Hi guys, thanks for the congratulations.
I tried removing the memory card and plugged it into a card reader, no joy reading this card, in fact it wouldnt even detect. I also tried putting it into my Toshiba Camileo, which I know deffo supports SDHC cards of this size, was unable to see it at all.
Also tried it in a new laptop, with a micro > full size adaptor, no joy, and a blackberry 8520 with mass storage enabled still cant read this card, when I choose disable mass storage it tells me the memory card isn't formatted.
I know Windowsphone7 files on the memory card isn't supposed to be accessable outside the OS but this makes data recovery impossible for me.
If this was a PC HDD or standard SD card I could run some data recovery software, and try to recover these files even if the card has been formatted. but I have no idea how to do this for this card... any ideas?
herr_ando said:
Hi guys, thanks for the congratulations.
I tried removing the memory card and plugged it into a card reader, no joy reading this card, in fact it wouldnt even detect. I also tried putting it into my Toshiba Camileo, which I know deffo supports SDHC cards of this size, was unable to see it at all.
Also tried it in a new laptop, with a micro > full size adaptor, no joy, and a blackberry 8520 with mass storage enabled still cant read this card, when I choose disable mass storage it tells me the memory card isn't formatted.
I know Windowsphone7 files on the memory card isn't supposed to be accessable outside the OS but this makes data recovery impossible for me.
If this was a PC HDD or standard SD card I could run some data recovery software, and try to recover these files even if the card has been formatted. but I have no idea how to do this for this card... any ideas?
Click to expand...
Click to collapse
Sadly, you need a Nokia cell as stated above, to read the card. Their OS is the only one that supports the partition format & password protection. I have 2 SD Cards that won't work on anything other than a Nokia cell because of this. They came out of a Nokia MusicXpress & Nuron my room mate had.
Hi mate
So you reckon if I buy a Nokia 5230 or similar I should be able to read this card? I should be able to pick one of these up for £35 or so, well worth it to get these photos back.
I have no experiance of nokia phones since the old days of my 3310. Do i need to use nokia software or does this present itself as a removable hdd in windows?
Many thanks.
herr_ando said:
Hi mate
So you reckon if I buy a Nokia 5230 or similar I should be able to read this card? I should be able to pick one of these up for £35 or so, well worth it to get these photos back.
I have no experiance of nokia phones since the old days of my 3310. Do i need to use nokia software or does this present itself as a removable hdd in windows?
Many thanks.
Click to expand...
Click to collapse
Creamy stated the n97. I'm not family with all this as I never done it, but there's a lot of threads regarding this. People using Nokia phones to unlock & reformat SD card so they'll work for other devices. As to what devices this work on, I'm not sure, but as long as the card hasn't been erased yet, it's possible that a Nokia phone will be able to read the card & transfer files to your pc. You can look through the forum for more information from people with experience. My experience only deals with trying to get these 2 SD cards working with other devices & will result in for formatting the cards.
NOTE: Also, I do believe you need the nokia desktop software install to transfer file, but am not sure. Another thing, if you do find the sd card is empty, maybe reformatting it in the nokia phone, you'll be able to directly put the sd card in your pc & use your partition recovery tools on it.
Best Digital Media Recovery Software
Hi,
Congratulations on becoming a father!
If the memory card is not recognized in the PC or it is impossible to access the data on it, the controller on the card is damaged. There is only one way to get the data back, digital media recovery and directly access their raw data with a programable digital media recovery tool. Have a look at: RecoverDataTools DigitalMediaRecoveryTool
I was recently given a Htc mozart by a friend who had cracked the screen and bought a new phone, they said I could have it but would like their photos and vids off it so if I could back it up (easy as pie I thought!!!)
The phone charges and functions fine (I changed the digitzer) but when plugged into a pc it displays usb unrecognized error code 43 (malfunction?). I have tried multiple cables, laptops and even os (xp, 7 32bit/64bit and osx), I have searched the internet and have seen some suggestions on wiping the phone (but I don't want to do this until the data is backed up) also looked at reading the micro sd but found you can't by conventional methods.
I have also tried multiple apps - boxfiles, sendstuffnow,sharefile (they seem to allow one photo at a time but not videos), I also tried emailing them but again I can't email vids and the phone has over 500 pics! tried bluetooth and also yivosoft but it doesn't seem to be able to view the files (root access required??), tried a few other programs such as ftp and they just state the phone needs to be updated via zune (currently running 7.0.7004.0).
I was thinking of sticking another microsd card in and formatting it etc just to see if it is then recognised in windows and poss update the firmware then put the old micro sd back in? would this work or is the firmware stored on the micro sd card and also if not when I update would it then state the old micro sd needs formatting or something? If anyone has any suggestions on how I can get the pics and vids off it would be greatly appreciated! I am an android user and this is my first experience with a windows phone so if I am way off my apologies. Thanks again
For sure don't mess with the uSD cards. They're locked to the device (the "S" in SD stands for "Secure" and refers to a rarely-used ability to lock an SD card). Even if you managed to make the card usable again, the data on it would be gone. Also, yes, the OS is at least partially stored on the SD card, and your switch-update suggestion would not work.
WiFi sync would work, but if that's not already set up you'd need to connect the phone to Zune via the USB to set it up. There are some homebrew apps that would be able to lift the files easily enough, but unless you have something lile TouchXplorer or Advanced Explorer installed already, that's not an option (you need USB connection to install more homebrew).
Sorry, man. This is one of the reasons why I plug in my phone to my PC every day or two and sync it; the tiny amount of time it takes is worth the reassurance. I realize that doesn't help now, though...
GoodDayToDie said:
For sure don't mess with the uSD cards. They're locked to the device (the "S" in SD stands for "Secure" and refers to a rarely-used ability to lock an SD card). Even if you managed to make the card usable again, the data on it would be gone. Also, yes, the OS is at least partially stored on the SD card, and your switch-update suggestion would not work.
WiFi sync would work, but if that's not already set up you'd need to connect the phone to Zune via the USB to set it up. There are some homebrew apps that would be able to lift the files easily enough, but unless you have something lile TouchXplorer or Advanced Explorer installed already, that's not an option (you need USB connection to install more homebrew).
Sorry, man. This is one of the reasons why I plug in my phone to my PC every day or two and sync it; the tiny amount of time it takes is worth the reassurance. I realize that doesn't help now, though...
Click to expand...
Click to collapse
Thanks for the reply, know what you mean I back up regular also but my friend didn't. I can't believe its so difficult to transfer the files without the usb connection :S also can't believe the updates are no ota :S was hoping there might be a method of unlocking the phone for homebrew like there was with the iphone at one stage. Ah well back to the drawing board unless someone can come up with any other ideas!
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.