Related
I have a Tmobile Wing with an 8gb memory card. I install almost all my programs to the card, unless it's something 'intrinsic' like Office Mobile, OneNote Mobile, etc. I use the card heavily for homework files, field and lab data, and notetaking for my classes.
Installed programs include:
Mobipocket
Goosync
Ultrasoft Money
Skype
CacheMate/CacheNav
Stuff I've done:
Pagepool to 6mb (has been this way for a LONG time)
BatteryStatus is also installed, but I found it after the hard reset I describe below. Haven't been brave enough to use the overclock function yet.
My program list has stayed pretty much the same...the most recent addition was Skype. I haven't dropped or drowned the phone.
Occasionally, as long as I've had the phone (about a year), I would notice that the Goosync and Mobipocked icons in my start menu would disappear (they would appear as a generic 'program' icon; you know, square with a blue bar at top). Sometimes they would come back, but they would always disappear again.
In the past week, the shortcuts ceased to function entirely. I get the message:
"The file <insert program I'm trying to use here> cannot be opened. Either it is not signed with a trusted certificate or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file."
So I followed directions and reinstalled the programs. They worked...once. Then I went back to getting the error. Suddenly NO programs installed on the memory card will run. They still appear in the Remove Programs list, so I even tried uninstalling them and reinstalling with no success. So I did a hard reset and started over from scratch.
Same problem. No programs installed to the memory card can be launched after the first time. I downloaded Google Maps just to see if a new program that hadn't been installed before had the same problem, and it is exhibiting the same behavior. I can launch a program newly installed to the card once, and then it no longer works.
I went ahead and installed my programs to main memory so I can have them for school; they work fine from there. But I'd sure like to move some back to the storage card. I have no problem accessing word, excel, etc, documents from the card.
I hope I've described this intelligently; I searched for the error message and saw a thread from 2005 under Universal:Universal, but couldn't figure out if they solved their problem or not.
Hoping someone can help me. I'm about ready to pull my hair out.
have you tried using a different card? considering that you still had the problem after a hard reset, my guess is that the problem is the card.
I hadn't considered that because it's only programs that are affected, all the word or excel files are fine, as are my ebooks, but I will try to round up another card somewhere to try. Thanks.
Hello everyone,
i own a Raphael since January and in this time it allready killed 2 SD-Cards.
The first one about 4 months ago.
Suddenly in the middle of usage the Raphael froze and i could not get it started again. even after a hardreset it was stuck in the bootscreen.
after a lot of trying and finally removing the sd card it bootet again without a problem.
the card was not readable anymore in any of my devices or windows boxes.
i thougth myself. well can happen even when a card is only half a year old got a new 8GB card and forgot about the incident.
yesterday while listening to some podcast suddenly the sound died. taking out the phone i found out it did not reacted to any power button presses or anything the screen stayed black.
after a softreset the phone worked again but took about 5 minutes to get in a usable state and the programms installed on the sd card where not aviable anymore.
taking a closer look i found that the card was not displayed in file explorer anymore.
gave it a try with my mp3 player. same result no card was found.
today in the morning i gave it a try on the pc with an sd-adabter. but also no result, wondows does not even recocnizes any device being plugged in. tryed a few data recover tools but non of them found the card.
someone has similiar experiances or any tips how i could get my data back from the card?
i guess the phone has to be send back for maintainance, but i doubt that they will find anything, if they accept it at all.
I have changed 4 sd cards because of similar problems. But the problem is most likely because of the fragility of high capacity microSDs, I wouldn't blame Raphael. Try other manufacturers (and try to find the ones that are not just rebranded)
I've had many issues with sd card corruption, but have solved some of the issues. Here's my advice (fwiw):
1. Get a card scanner, and regularly scan your catd. I do it everyday (takes 5 min). I use Wizcode Scandisk. It fixes errors and dumps out files that can be opened in notepad. It's worth looking at them, as it helped me find the multiple sources of corruption that I had.
2. Don't put your PIE cache on the card.
3. Change all 'save' paths (esp. the camera) to main memory.
4. Store any programs you use a lot on main memory.
5. Do NOT have any programs that run constantly on the sd card.
6. Do NOT put Fingerkeyboard on the sd card (major problem for me).
Basically, my advice is to use sd cards for storage. The Raphael has a lot of memory-use it for programs. I haven't had to format my card in about 4 months. I was doing it every couple of weeks for a while.
well basically i was using my sd card as a storage place for movies and podcast + podcastplayer prog.
and was using the player more or less the whole day.
i used the same card (and the other one before) also in my mp3 player when the raphael or the bt headset run out of power and there is no power outlet aviable to recharge. and twice the card failed in the rapahel.
when i got a new card, i also found that the card is working 100% on pc and mp3 player, but the raphael still can not see any sd card.
i really blame the phone and also assume that it now has a defective reader.
have to give it back to repairs as soon i have flashed the original firmware and make my way back to the store
You should scan the disk to find out the error sources. It may be something simple that causing them. Also, if your phone freezes when listening to music, you may want to either wait it out, or remove the card before soft resetting. You should do some searches on card corruption. There are lots of threads here that can be helpful.
many Sdcard and usbStick manufacturers got lowlevel format tools you can download and get cards not otherwise working in cardreaders on pc back to life
would love to get those cards working again. but i also would love to get the data back that was on them.
but the problem is the cards do not even appear on the pc, or any other device i have that can read/write them (usb card reader, digi cam, mp3 player)
its just as if nothing is ever inserted in the reader.
the low level format tools don't rely on windows driver model to detect cards
Flash Format (cnetx) has always been able to re-format my card, even when my pc couldn't recognize it and neither could my fuze. It has a free trial that works fine.
I haven't experienced any of these issues myself. But I'm sure I will now that I said that....
i gave that flash format a try, but it even failed to install. was one of those weird .exe installers. on the pc side it told me install was sucessfull, but on the ppc side was just a promt "installation failed".
a cab install would be nice, but without a working cardreader in the phone i guess would also not be of much help. i guess cuz of that that prog will not help me much. the reader in the phone is broken. cant read any cards, even brand new unused ones that are fine everywhere else just dont show up on the phone.
as for other "low level format tools" my search was quite unsecessful. i was looking at the sandisk and the transcend page (the suppliers of my 3 cards) but could not find anything.
google just found more request for this kind of program but not really somewhere where i could get it.
patlabor said:
i gave that flash format a try, but it even failed to install. was one of those weird .exe installers. on the pc side it told me install was sucessfull, but on the ppc side was just a promt "installation failed".
a cab install would be nice, but without a working cardreader in the phone i guess would also not be of much help. i guess cuz of that that prog will not help me much. the reader in the phone is broken. cant read any cards, even brand new unused ones that are fine everywhere else just dont show up on the phone.
as for other "low level format tools" my search was quite unsecessful. i was looking at the sandisk and the transcend page (the suppliers of my 3 cards) but could not find anything.
google just found more request for this kind of program but not really somewhere where i could get it.
Click to expand...
Click to collapse
Check C:\Program Files\Microsoft ActiveSync\CNETX-you'll find the cab in there. There will be several-you want the PPC-Arm one. It should install fine.
Card Freeze
Yeah I had the same thing happen. Raphael would not boot unless I removed the card and as soon as I placed the card back into the sd slot it would lock up. Unlike you I was able to get on of my PCs (either the XP Pro or the Vista Pro) to recognize it but all I could do was format it.
OK I like the idea of moving all the data to the main however I'm an old Windows CE guy (yeah I had a Jornado) and the memory used to be shared between program and storage. The device would allocate from the other when more was needed. If I place all the stuff I want into the Raphael main memory won't that lower the amount of RAM I have for running programs or vice versa? I really don't know if the memory is fluid since all I get when I look into the memory is one listing total storage and one total program, there is no slider bar like there used to be in windows ce.
webfrm said:
Yeah I had the same thing happen. Raphael would not boot unless I removed the card and as soon as I placed the card back into the sd slot it would lock up. Unlike you I was able to get on of my PCs (either the XP Pro or the Vista Pro) to recognize it but all I could do was format it.
OK I like the idea of moving all the data to the main however I'm an old Windows CE guy (yeah I had a Jornado) and the memory used to be shared between program and storage. The device would allocate from the other when more was needed. If I place all the stuff I want into the Raphael main memory won't that lower the amount of RAM I have for running programs or vice versa? I really don't know if the memory is fluid since all I get when I look into the memory is one listing total storage and one total program, there is no slider bar like there used to be in windows ce.
Click to expand...
Click to collapse
The storage memory on the device is flash, not ram, so you don't lose program memory changing the save paths to main memory (if that's what you meant by moving data to main memory).
I never had any issues with my storage cards (sd and cf) on my 2003 device. I don't think it was the device, but rather the cards. The big, 16 gb cards just seem to be less hardy than a 1-2 gb card. I had all my apps on the storage card (including stuff like magic button), and never had a problem. But, jeez, the 16 g microsd is sensitive as hell. It gets minor bits of corruption at least once a week. I scan it everyday to avoid it crashing, which has helped, because I've gone 4 months without formatting it. One thing that I've found screws it up royally is doing a lot of file/directory operations over active sync on a pc. I don't know why, but cutting and pasting files from one folder to another in the sd card frequently results in lost clusters. Renaming folders is also a bad idea.
OK Flash
Well I guess I didn't explain it correctly. According to HTC the RAM is 288MB with a ROM of 512MB. So I'm really confused since according to the start>settings>system>memory the total for my storage and my program = 549MB which is of course more than 288 and 512. So when I load applications into my device and get a choice of main or storage card when it was a large file (some apps I use were 14 megs or more) I would choose the storage card.
My old experience with Windows CE was whatever memory was on the device was shared with both the program and storage, so I would put as much as possible on my storage card. However in windows 6.1 or higher it lists two separate columns for Program and Storage with: Total, In Use, and Free. So when I install apps I presumed they went into the storage area. Am I mistaken? I figured Program on the device meant how much is currently in use. Kinda like opening multiple windows on a PC. I notice it's low when at once I have 4 applications open on my windows mobile device so that's what I thought Program memory was.
Therefore does installing to the Main, when given a choice during program installation. where does it get installed ROM, RAM? Why is my total memory higher than RAM or the ROM
Any insight would help me decide the best location for my program installation to not corrupt the data, or have the flash card screw me up either.
288 MB is the total amount of system ram. A large amount is not user-accessible, it's used by the kernel/OS/Page-pool, so you don't see it reported. It's still there, though. The rom memory is 512 MB, but the actual memory in rom is subtracted by the storage memory so you see the amount of user-available memory. With 2003 devices, if the battery ran down, you lost all of your data, because the storage memory was in RAM (except perhaps for a little flash disk space). But with a fuze, you can pull the battery out, and not lose your data.
Totally confused
OK your right about the 2003 devices which is why I placed most of my stuff on a storage card. However why is my total reported memory 549MB more than the 512 ROM? Also when I install stuff to the device where does it get stored, the 512 ROM? Are you saying that the 200mb of Program being shown is 288 RAM minus the 88 being used to run the OS?
So are you saying its safe to install all my apps onto the device and I won't lose anything if the battery runs out?
Yeah, I've been saying that for about 3 weeks, lol! They got rid of the volatile storage memory with winmo 5; we're onto 6.5 now, and it's a thing of the distant past. I you don't believe me, pull out your battery (there's no backup battery on the device) and see if it causes a hard reset.
This is not an uncommon problem with digital cameras, as well. It's complicated, but the bottom line is this: whenever you buy an SD/micro SDHC/etc. card, you should do a full format of it on your COMPUTER, then put it in your device.
I have a HTC Fuze (AT&T GSM). I followed the instruction on (http://forum.xda-developers.com/showthread.php?t=951981) for FRX06 but it keeps getting stuck at "task rpcrouter:15 blocked for more than 120 sec". It never gets to the calibration screen... I even tried downloading and using a pre-made ts-calib file but the results were the same.
I also tried numerous other posts ROMS (FRX03, FRX04, XDAndroid 2.2 (rel 1.6).cab, even tried XDAndroid 2.1 (rel 2.5a).cab) but I still get stuck at the "task rpcrouter:15 blocked for more than 120 sec" error.
I read in another post back in Feb 11 that it was an issue and someone acknowledging it is an issue but no solution stated in the 19 pages of forums. Another user states this is a "bootloop" but did not offer any solution.
In any case, I never got to any graphical screens - never got past the text screens (white text on black background).
Help!
Actually the fix was to delete the data.img but that would be the "quick fix". This WAS mentioned under the troubleshooting section of THIS post. If you really want to see the calibration screen, download an older kernel package as stated HERE.
BE SURE TO SAVE THE FILE CALLED ts-calibration THAT YOU JUST CREATED!​Additionally, I want you to format your microSD and start over from scratch. Just to flush out any other issues that you and may not encounter; such as the "waiting on SD card" issue some complain about. When I say format, I mean use something other than windows to format your microSD. I use the free version of partition wizard and it seems to do the trick. IF you want something a little less program intensive, I would suggest using SD Formatter. Again, not required but it might help solve other issues you may encounter on down the line.
All of that being said, I have a RAPH110 aka at&t Fuze, so I know this process works. If it doesn't work for you, YOU are doing something wrong!
Also, if you insist that you would rather skip the calibration screen, you may use my ts-calibration file. Make sure you place it where the file called haret.exe is.
CLICK HERE for your viewing pleasure!
Same problem with FRX06 even after FORMAT with OVERWRITE of the microSD. I included the ts-calib file. Got past "Creating a new Data Store" then got stuck at "mdp irq is already 4 4 and above mdp_dma: busy" where it would retry after getting stuck for 120 sec.
I then reformatted again and this time tried "XDAndroid 2.2 (rel 1.6).cab". Got to "Creating a new Data Store" and it is stuck there for over an hour - so I gave up.
I then tried deleting the files for "XDAndroid 2.2 (rel 1.6).cab" and this time tried "XDAndroid 2.1 (rel 2.5a).cab". Same issue.
Next, I tried loading Android on the Device instead of Storage Card. Stuck at the same point... I waited 5 min then quit.
I read elsewhere possibility of problems using micro SDHC cards... do you have a microSD card in your Fuze? My card is a Patriot microSDHC 8GB.
As always, there may be a bad batch but have had no such luck with buying PNY nor SanDisk. You did download 1231 as mentioned earlier, correct? So, if you want to try that first, you'll need to delete the existing modules-xxx and zImage file and extract the contents of the downloaded file till you see the modules-xxx and zImage_xxx. Rename the one called zImage_xxx to just zImage and be sure to place them with the file called haret.exe and launch haret once more. Keep in mind, downloading the kernel packages may not be required but in order to test things out and to see what works best, it is. Good luck my friend!
So I tried again and let the install run overnight (>4 hr). In the morning, it was still looping so I stopped it. Today, when I looked at the microSD, I see 171 FSCH0xxx files... most are 32K. 170 was 192K and 171 was 1.81M total of these files were about 158MB. Does this indicate anything?
Anyway, I reformatted my microSD card twice using the SDFormatter (Overwrite, Size Adjustment on), loaded FRX06, replaced the set with the 2 files you sent and renamed the zImage file. Booting up, goes into text screen, still get the timeout error. This time I noticed that there was a line that says "INFO: task dd:91 blocked for more than 120 seconds." My guess is that it's creating those FSCK files again... meaning SD card errors?
Have you another microSD to confirm whether it is a bad card? I just started from scratch (for the 50th time today) and I am NOT seeing what you are seeing(I don't see any FSCHxxx files)... I don't suggest trying anything older than FRX06. If anything, I'd suggest you see if you can find another microSD and probably only use that card for temporary storage.
OK, I'll have to go get another card this weekend then. I do think it seems like the card has some kind of compatibility problem... what brand are you using?
For tonight, I've formatted the card twice and then am trying the "XDAndroid 2.2 (rel 1.6).cab" now... It is stuck in the "Creating a New Data store" line for >20 minutes now... (FXR06 passes that but gets hung up trying to fix the file system). I'll wait a while longer and see if it will miraculously finish creating the new data store.
Thanks for your suggestions.
I have a PNY and SanDisk both 4GB class 4. I think bestbuy has the PNY one for like 30 bucks (maybe cheaper?)
I don't know what the problem is but I'm willing to help out how ever I can
I downloaded MiniTool Partition Wizard and deleted the microSD card's partition then recreated it. Then, I recopied the files into the root of the microSD, installed into my FUZE, and clicked on herat... this time it got into the Android graphical portion (no calibration needed since I included the ts-calibration file), stayed at the ANDROID screen for a while then went blank. I waited about 6 minutes then turned it off. When I went to see what's inside the microSD, I found the data.img file 256MB and also messed up file system again - since I shut it off prematurely.
With a lot more confidence this time, I repartitioned the microSD again, placed my Android files under its own folder. Crossing my fingers...
Ah, so you've been using the file path method then? If that is the case all one would need to do is put rel_path=FRX06 in the startup.txt file, between the quotation marks. Additionally, if you prefer more ogranization and plan to run more than one build at a time, it is best to have that command in your startup.txt file for each build. Keeping in mind, once you do this, it pretty much sets the default path for that build to that particular folder. I wasn't aware that you were starting one folder deep, my apologies . It's best to use the root folder for troublshooting and what not. I prefer to only use one build at a time because I find it easier to keep problems isolated and it helps me troubleshoot at the same time.
Additionally, if you want a more easier way to troubleshoot Android issues and you don't mind waiting for the data store (aka data.img) to be recreated at boot time, then one would only need to delete the data.img file (keep in mind if you have any settings or contacts, these may be deleted as well). What I usually do is once I get a good data.img, I make a backup and zip them up (or use your method of archiving). I also make a backup before I make any changes, like if I am testing out a new rootfs or kernel package. Most of this has been discussed and mentioned in the Android forums.
That did not work so I reformatted again and went back to using the root of the microSD for Android... FRX06 was stuck on GUI but blank screen all night - I turned it off in the morning. Back to the drawing board. At least I got the microSD issue figured out... on to the next mystery.
Update:
OK, partitioned my 8GB to 7GB FAT32, 512MB ext3, 512MB linux swap. Loaded FXR06 into the root folder, booted and it works this time. However, once into Android, it would lock up.
Case 1: Boot up android, clicked on Gmail, screen is android but nothing in the screen except background. Took out battery to turn off.
Case 2: Boot up android, left it alone, screen turned off - will not wake up. Took out battery to turn off.
Case 3: Boot up android, went to settings to set up wifi, froze. Took out battery to turn off.
Case 4: Boot up android, went to settings to set up wifi, entered WEP key, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing). Took out battery to turn off.
Case 5: Replaced the modules and zImage files to the new ones you sent me (12/31/2010)... booted up android, went to settings to set up wifi, entered WEP key, shows connected, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing).
Seems my Fuze is locking up soon after Android boot. Tried numerous times... left alone, freeze. Tried calling, freeze. It seems to be time based. So close...
Strange, though, as the phone remains warm to the touch despite being frozen for some time.
Yeah, you lost me at partitioning your device as I don't even touch that stuff. I think you are using something different. Sorry but I can not help you, my friend!
Thanks anyway... the partitioning is just to make the partition "different". Probably no relevance unless it allowed me to exclude some bad sectors from use. As far as Froyo, I guess there is some kind of HW or SW problem with my phone. I may reflash my Fuze to another WM ROM - just to clean it up and isolate SW as the problem.
Let me clarify, I don't partition my microSD because XDAndroid builds simply do not require this. There are Neopeek variants that require partitioning of the microSD but I still think your method is slightly over exaggerated. I'm not sure why but I guess for some reason there may be an issue with your microSD and partitioning may be a way around this issue but I don't know enough about partitioning microSD/non-volatile flash. So, I couldn't say for sure...
Ok, so I installed Tael ROM (WM 6.5) then tried installing, it still freezes after 1-2 min of booting up (or during boot up). So it looks like it's a hardware (phone or microSD) issue for some reason. I guess hardware vs thinking kernel because the 2.1 installs also do not work.
On another note, it seems that the Android boot process corrupts my other files... I have folders for GPS and photo (DCIM) and it "corrects" those errors and kills my files.
Hmmm... I can't say for certain as I've never experienced that issue. All of my files remain intact before and after booting into Android and rebooting into winmo. Are you talking about the files on your phone or microSD. If you are talking about your microSD, you might be experiencing the hardware issue and the while you boot into Android, it is only attempting to "fix" these issues and in the process, kills the files contained with-in. Does this makes any sense?
Yes, the files are those I mentioned are in my microSD. So, yes, looks like some kind of interface issue causing Android to think the files are corrupt and then try to "fix" them. Strange though that WM does not try to fix the "errors".
I think it's kind of like the linux way to make sure there won't be any issues when you run the OS, since Android would run off the microSD and not from the phones storage. Currently, there is some development for this called NAND. Still really nothing solid as to whether it will work or not but always good to know, I guess?
Well, the thing is those files are pictures/videos/GPS maps... so I think WM is able to read them (so not an error) yet Android does during its pre-boot scan. Anyway, since upon successful scan and android actually loads, it would freeze in 1-2 min, so the problem may not be limited to the microSD. Yeah, perhaps the NAND will work better. I did get Warm Donut to run on my old Tilt, so I am still hopeful.
The issue that is stumping me is that I'm not experiencing the same issues you are with XDAndroid and I'm not sure how else to help aside from using another microSD to confirm an issue with your current microSD.. sorry
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.
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.