Related
I have been having this problem for sometime now, but I just had enough... Every so often, say a few weeks, my HD suddenly and without me doing anything special (i.e. installing a new program etc.), "looses" the storage card i.e. it cannot access it anymore. I need to reboot in order for HD to read it again. But then after a few minutes (enough for me to copy data from), it looses it again and so on. In order to correct it I have to reformat the card so it does not happen for a few weeks until the next time.
Note that this is the standard storage card that came with my HD. I did not flash any cooked roms, I am wearing the newest official version (1.56).
It just happend again... and I am getting p... off. Any help?
stsalkit said:
I have been having this problem for sometime now, but I just had enough... Every so often, say a few weeks, my HD suddenly and without me doing anything special (i.e. installing a new program etc.), "looses" the storage card i.e. it cannot access it anymore. I need to reboot in order for HD to read it again. But then after a few minutes (enough for me to copy data from), it looses it again and so on. In order to correct it I have to reformat the card so it does not happen for a few weeks until the next time.
Note that this is the standard storage card that came with my HD. I did not flash any cooked roms, I am wearing the newest official version (1.56).
It just happend again... and I am getting p... off. Any help?
Click to expand...
Click to collapse
There´s already a thread discussing this point (here or in the rom development section of blackstone. i cant´t really remember) take a look at it.
so far i can say: try to format your card. if it doesn´t work try to format it using a digicam because a sd-card reader at your pc wouldn´t work either
http://forum.xda-developers.com/showthread.php?t=506560
thank you!
I was playing Let's Golf 2 yesterday, and I ended it improperly by pushing the Home button. Since I rebooted from that incident, the SD card is not mounting anymore, and the system is telling me that it is damaged or its filesystem is not accepted. Since it's the very same stock card which comes with the phone and has worked properly since it came (and of course works in other phones and computers), I am quite puzzled. Any other card I mount receives the same treatment, so it's something on the phone. I have my bootloaders unlocked and I have flashed the 2.3.3 rooted version per Flashtool and Fastboot.
I guess it's time for reflashing, or do you folks have any idea I could use?
I had a similar problem. Turned out my SD card was cracked. This brings me to my problem. After loosing my SD card Crash won’t run anymore. Does anyone know how I can restore it? I really liked that game.
Edit: Never mind. I opened it again and now it gives me an option to download the game again. I need to do it over wifi when I get home.
Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!
You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.
Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.
I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.
Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.
OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL
LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?
The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".
It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.
You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.
I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.
Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.
This happened to me 2nd time now The phone says that the SD card is blank or has unsupported file system. I also tried it on a PC an it doesn´t detect it too. This happened to me first time when I flashed official GB beta1 after a day of use and the SD card never worked again (it was sandisk 8GB) after 1 day of use and now it happened again same after 1 day of use The SD is silicon power 16GB.
Also I was using CM7 for much longer then the official ROM and never had any issue like this.
So, did this happened also to anyone else? And is there any solution?
Edit: SD card magically started working I was just about to flash MIUI so I went to recovery (it didn´t detect it either) and did a backup and then rebooted phone (to give it one last try)... now it works!
I have an U8800H for about a year. I've used a lot of ROMs with it, and most of them worked perfectly.
Some months ago, Huawei released the 2.3.5 Firmware update for our phone. I installed it and faced the lot of problems that most of them are by now well known and some of them repaired.
But one of these problems was the curious "SD destroyed" problem, that plagues -as I found- a lot of U8800 users but is also so sporadic that is very difficult to pinpoint - and is present in EVERY ROM that is based on 2.3.5 update (.35 kernel).
Let me explain:
After some days with the 2.3.5 update, my phone crashed and rebooted. When rebooted, I found that my Trancend 4GB SD card was not mounted anymore. The phone could not mount it and found it as "destroyed". When I tried to mount it again, some times the phone reported that "SD card was ready to be removed" or such, and others that the card was "destroyed".
The card, though, was perfectly readable by all of my PCs and other phones. The only way to mount it again in U8800 was to copy its contents somewhwere else, format it, put back the contents and insert it again in the phone, after rebooting it. And, strangely, the card was working again perfectly, for 1-2 days at least, until this problem repeat itself.
I thought that the problem was one of the stock ROM's many faults, so I tried a lot of other ROMS, like MIUI, CM7, etc. The problem repeated itself in every one of these ROMS.
I thought that my card was problematic, so I tried to use an older but perfectly unused 2GB Kingston SD card. The problems repeated with this card, also. I also used the new card with the other ROMs. I lost many hours and the problem was always there.
I also tried two 1 GB cards and three 16GB cards. I had the same experience with any of these, emerging after of 2-3 days of use of every card.
I found a lot of forum posts where users are reporting the same problem, without any solution, probably because it happens not to every phone and because it's also sporadic.
I thought that my phone was broken, so I installed the original stock ROM, as the service center would not accept it with a custom ROM. But when I reverted back to the original, the problem disappeared!
With the old stock ROM, everything is running perfectly and the SD card is always correctly mounted.
I tried to go back to the new custom ROMs, only to meet again with the same problem. The new "Gingerbread" ROMs, have obviously a bug!
Now I am using the old stock ROM and I have no problem, again.
I am writing all these to ask If someone has the same problem, and to report it as a bug that is hidden somewhere inside the .35 kernels.
You should have post this topic in the Q/A Section :|
It's not a question, its the report of a bug inside the .35 kernels. It's now specific to one of them, but present to all, that's why I had to create a new thread.
I have found also that the problem lies with the new gingerbread bootloaders and it is not present in the froyo bootloaders.
moving this thread to general section.
Try fix permissions in cwm. It works for me.
Sent from my U8800
I have the same problem with SD cards on my U8800.
It has destroyed 2 cards so far for me. When I first did the official gingerbread upgrade it didn't go well I had to try and install it multiple times and it kept going into boot loops. The end result was that my Class 10 16GB card became so damaged that it wasn't even detectable on multiple PCs with various card readers.
Thanks Huawei £15 down the drain.
My second card and I suspect my third card which is still in my phone, have problems with writing. Small writes are OK but as soon as something writes more than a few MB the card fails silently and the OS or phone thinks the file has been written but it hasn't and then subsequent writes fail. Unmounting and remounting the card in the phone makes it writable again for a while. These symptoms persist even when used on a PC so the phone is doing something bad which damages the card.
This problem occurs with dzo's ICS as well as official GB so I think the original posters assumption that it must be some code in the bootloader that is causing this problem is likely correct.
I'd love Huawei to fix this or find a workaround as I would rather not return my phone because I would likely only get refunded 50% of what I paid originally and I actually really like the phone.
Froyo roms worked fine with the SD card, it is definitely the poor quality Huawei update that has caused this.
I think I have an answer. Back when I started tampering with the phone I had changed the data/internal usb partition sizes as here: http://forum.xda-developers.com/archive/index.php/t-1112857.html
Somewhere I read about a user who had the same problem as us, and he had done the same change.
So today I reverted back to the original partition sizes, installed 2.3.5 stock ROM and the o/c kernel and until now I have no problem.
Maybe something in the new firmware doesn't like the changed partitions and thus the problem is created...
Sensimilla, If you also changed the partition sizes, then we have an answer.
Update: The bug reappeared. After 4-5 hours of heavy use, my 4GB card was once again "destroyed". So the partition sizes had nothing to do with it.
So, I tried what entrapmen suggested. I booted to recovery and chose "fix partitions". And it worked. My card was once again mounted correctly.
I don't know what to say. I will keep posting until we find a more permanent solution...
It seems I found a permanent solution: Install Aurora ICS 4.0.4: http://forum.xda-developers.com/showthread.php?t=1492957
I am using it for about 20hours now and everything runs smoothly. Probably the new Android 4 bootloaders fixed the bug.
(And as an added bonus, our phone gets a radio!)
Hopefully it works for you, too.
lateris said:
It seems I found a permanent solution: Install Aurora ICS 4.0.4: http://forum.xda-developers.com/showthread.php?t=1492957
I am using it for about 20hours now and everything runs smoothly. Probably the new Android 4 bootloaders fixed the bug.
(And as an added bonus, our phone gets a radio!)
Hopefully it works for you, too.
Click to expand...
Click to collapse
Dont get much excited. Im using ics and time to time problem still occurs but not that much. Like i said before a fix permissions resolve the problem.
Sent from my U8800
It's nearly 3 days now with ICS 4.0.4 and the bug didn't appear - and I did some heavy testing. I transfered lots of small and big files to my 4GB card without the slightest problem many times.
I did some more testing on my sdcard and it is indeed damaged. It seems to have been set to read only permanently. Windows 7 doesn't detect this but I downloaded the official sdcard formatter from panasonic and it says the card is read only. Apparently there is a small protected section of the card that is hidden and used for DRM, read only can be marked in this section of the card. Normally this section is only writable by the card manufacturer. I guess as the phone has low level access to the card via hardware this section could have been inadvertently damaged by Huawei's bug ridden update. This is the same state that my previous card ended up in too.
The apparent writing to the card seems to just be the cache on the phone/computer which mounting and unmouting resets.
I will buy another small sdcard and just use it with ICS Aurora this time and see how it goes. I have been using Aurora for the last month anyway. Maybe it will be fourth time lucky.
Just clear the whole MicroSD card with dd program writing it full a random data first and then after that zero.
And if you can not detect the card at all with dmesg program, then that card is destroyed.
It's a week now with ICS Aurora 4.0.4 (206,207 and now 208) and the bug didn't appear at all.
I filled my -previously problematic with 2.3 ROMS- 4GB SD card fully, I even tried to stop file transfers abnormally, pulling the cable. But no problems appeared whatsoever.
So I have to believe that with 4.0.4 the problem is gone.