I followed all the online instructions for getting CM7 on a little Class 2 4GB SD card, it works great but seems a bit slow.
I got a Class 4 8GB SD card, it shows up as a Ricoh branded in windows if that matters.
It takes the generic SD img and I can copy the CM7 zip file onto it just like I did the first time.
For some reason, on first boot, when the CM7 setup starts extracting and setting up partitions it starts a string of IO errors and they just stream past. It eventually finishes with numerous errors but even if I delete the partition and start over fresh it does it every time.
Is it possible that I just picked a bad brand or am I doing something wrong? I am doing everything exactly how Idid the first time so the only diff is this brand new card is supposed to be twice as fast and twice as big.
If you did the first time correctly, I then trust you on your 2nd time.
As for uSD itself, try Sandisk (i have Transcend and it ok)
Related
When I do a data transfer between my Mac and my G1 running Cyanogen, the SD Card immediately comes back as corrupted. I am unmounting properly.
When I have the stock Donut on the G1 it works fine, no corruption.
Any ideas?
This used to happen to me all the time. I guess the card wasn't compatible with the phone. I was using fat32+ext2, fat32+ext3 or even fat32 on it's own and I was always having problems.
If it doesn't happen on stock donut I assume it's an issue with our ext partition (if you have one).
I would agree with you except I am able to 100% reproduce it on the 3 SD Cards I have. I am using this method to partition my SD Card through the console of the Cyanogen bootloader: http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/ I have rooted and unrooted my phone a few times trying to troubleshoot this and it happens every single time.
What happens if you only use fat32?
I've had issues w/ two cards, including the one that came with the phone. If you can, try a Transcend card.
I have not tried just one partition of FAT32 under Cyanogen. I am going to try moving a file via USB with Cyanogen 4.2.4 in a moment. If that corrupts the card I will try just a single FAT32 partition.
I have used the SD Card that came with the phone, an 8GB Class 6 Transcend, an 8 GB Class 4 Patriot (which I know have issue with the Dream so I don't really count that) and a brand new 8GB Class 6 ADATA.
I really appreciate your help.
It appears that the latest CyanogenROM (4.2.4) has solved my issue!
I have done a bunch of 1GB+ file transfers via USB back and forth with my Mac, created directories, deleted files, etc and it's holding steady (just one random reboot but I can't say if it's related or not).
Had my HD2 for over a year now and finally got fed up of lack of WinMo apps, which my housemate with his iPhone loved to point out all the time. So I decided to try out Android a few days ago.
Read all tutorials etc and installed Skink's clean desire rom v1.3 using cwm. Got everything set up and was really pleased with my shiny new phone. Everything was working like a dream!
I decided to get a new 16 GB SD card as my 8GB card was full of music etc. Here is where the problems started...
To get all data onto 16GB SD card:
I partitioned it using cwm using same size partition size as on 8GB (1024mb)
Copied all files on 8GB fat32 partition onto 16GB fat32
With the 8GB SD card in the phone did a backup using cwm
Copied backup onto 16GB card inserted it into phone and did a restore
Now the fat32 and ext3 partitions on the 16GB card and 8GB card should be the same, so everything should carry on working fine when i boot up my phone.
It didn't I just kept getting lots of stopped unexpectedly errors until finally everything stopped loading even the home screen, and I'd have to remove battery. However if I just put my old 8GB card in everything worked fine as before
So after much frustation I gave up on this method and decided to just wipe everything on 16GB card and start from scratch:
Formatted 16GB card
Repartitioned it using cwm
wiped data, cache, dalvik cache
installed clean desire rom from sd card
booted up started reinstalling all apps etc
Now here is where things get very strange, I'd start reinstalling apps and reconfiguring to how it was before and then randomly I'll get a stopped unexpectedly error, like process.android.media or something similar. But it seems as if everything would carry on working, then slowly I get more errors until for example as soon as you click on internet you get an error and it closes.
I believe the problem lies with the sd card seeing as that is the only thing that has changed. I also think this rom stores more than just apps on the sd card. Because after I get a few of these stopped unexpectedly errors nothing is saved on the phone. For example I'll change the ringtone from x to y click ok, but when I click back on change ringtone it's still on x. But I can still play music that is stored on the sd card. After I reboot the phone for a while I can make changes and they are persistent but eventually I end up back at this strange state. It's almost as if I can read from the SD card but not write to it.
Another example when I've got to this strange state, I'll add a folder to home screen, add apps into etc. But when I restart the folder has gone.
If I reinsert my 8GB card and do a restore, I get everything back and it works perfectly. But I want to use my 16GB card, that's why I bought it!
My questions are:
Does anybody have an idea of what is going on when it gets into this strange state?
Does anybody know how to fix it?
Is there some way of testing the SD card?
Should my first method of getting all data onto new sd card have worked?
SD Cards are:
Samsung 8GB class 6
Transcend 16GB class 6
Sorry for the long post, any suggestions are greatly appreciated
Hi all. So I'm pretty new to this whole nook color thing. I have been trying to follow the instructions to install CM7 to a microsd card (Sandisk, class 4, 4gb) but I don't seem to be having much success, as I'm getting a strange error when the install process is being run.
Here's what I've done:
1. Put microsd card into adapter and insert into the card reader in my laptop. Write the generic SD image to the card with winimage32
2. Re-size the boot partition from ~100mb to 1.5gb using Easus partition master.
3. Paste over the update-cm-7.1.0-encore-signed.zip file.
4. Eject card, remove from computer
5. insert microsd card into NC. Start up. I get a "...loading" without the CM logo, and then it starts to run through the install. During the install, I frequently get this error:
I/O error, dev mmcb1k1, sector [x] where [x] represents a bunch of different sectors (seriously it scrolls through a huge list)
I also sometimes see:
mmcb1k1, error -110 transferring data
It does a lot of inflating of files, gives me more of those errors, does some more inflating, and eventually concludes the install and shuts down the NC.
When I start the NC again I get the cyanogen logo, with "...loading," the screen briefly flashes, and then nothing. The NC screen is on, but it doesn't display anything.
So what am I doing wrong?? I'm very confused at this point.
I believe this is not your fault. (You are certainly not alone)
See http://forum.xda-developers.com/showthread.php?t=1297738.
Try again using an old Class-2 uSDHC card. If it is not marked, it is class-2.
If that works please let us know.
I'm going to try installing one more time, then run out to Microcenter to pick up a replacement card. Any suggestion on how I identify a class-2 card that would work to pick up?
PNY 2GB with no class marking from Sears worked for me.
On the back of the packaging above the bar code P-SDU2GB-EF
HTH
hmlee said:
Hi all. So I'm pretty new to this whole nook color thing. I have been trying to follow the instructions to install CM7 to a microsd card (Sandisk, class 4, 4gb) but I don't seem to be having much success, as I'm getting a strange error when the install process is being run.
Here's what I've done:
1. Put microsd card into adapter and insert into the card reader in my laptop. Write the generic SD image to the card with winimage32
Get a usb adapter for writing to your microsd. I was having all kinds of errors
with new sandisk cards using the same method you are, then after changing to the
usb adapter they all are working.
Click to expand...
Click to collapse
Sooo I went to Microcenter and bought an unmarked Sandisk 2gb card (I'm assuming its class 2, though I don't know for sure). Installed CM7 on the first try. I'm not sure what is going on with the Sandisk class 4 4gb card, but I think there's an issue with it...
Excellent news.
You might be interested to know that I have just managed to clone 7.1.0 Release onto a SanDisk 4GB - see the related thread mentioned above for details.
Thanks for the update
a. Completely reformat your 4GB uSD.
b. Redo step 1 above with Win32DiskImager, using old version.
c. You can ignore your step 2 above.
d. Follow your steps
Would appreciate some guidance, if anyone can help...
In December we got two new Nook Color Devices, one had 1.2 and the other 1.3. Had one 8gb micro sd card, and without understanding much about it, I followed verygreen's instuctions to create a card for dual booting. The 1.3 machine was used for installing cm7 (7.10) and the latest gapps file. But the card was then removed from that unit and inserted into the other Nook Color which had 1.2 in its firmware. I now think this was improper but am unsure what the repercussions were.
The system was used succesfully for several weeks. Occasionally the Nook side was booted from menu. Then suddenly after a cold boot, CM7 started but the virtual sd card was not recognized. Removed the card from the unit and investigated using Windows XP and Minitool Partition Wizard and found the "CM7 SDCARD" partition was corrupted. I reformatted that partition in Minitool, and then used the card for about another week in the 1.2 NC. At that time multiple partitions on the card suddenly became corrupted and fearing the sd card itself was defective I ordered some higher quality sd cards (now have 4 8gb sandisk class 4 cards to play with). Meanwhile the 1.2 NC accidentally booted into the Nook side with wifi enabled when it was charging and updated itself to 1.4.1. Before receiving the new sd cards, I reformatted the possibly defective sd card and recreated dual boot system using Verygreen's instructions (in the 1.3 unit but transferred into the 1.2 unit after creation). I was able to restore some of the apps using Titanium (but only because I had copied some of my original backups to my pc)
The unit with 1.3 on it had not been used much with wifi, and it still had/has 1.3 on it. One of the new cards is now in that NC (created as before with the Verygreen instructions).
I'm in a quandary what to do with the other unit.
Could using the 1.3-created sd dual boot card in the 1.2 Nook have caused partitions to become corrupted?
Where are applications going? Doesn't look like they're in the large sd card partition. I didn't think I had that much on there, (just some free apps from google and amazon) but I might I have run out of space? I never elected "move to sd card" or "clear cache" for any apps and don't know if that is a requirement when you use dual booting.
I haven't found instructions for what to do to create a dual boot card for 1.4.1. My original 8 gb card is in the unit, but I'd like to create a new boot card using the higher quality medium. Just want to understand what's happening. Is use of a 1.3-based card bound to lead to more corrupted partitions? Any suggestions on how to create a reliable dual boot card for this unit?
Sherip said:
Would appreciate some guidance, if anyone can help...
--- SNIP ----
I'm in a quandary what to do with the other unit.
Could using the 1.3-created sd dual boot card in the 1.2 Nook have caused partitions to become corrupted?
Where are applications going? Doesn't look like they're in the large sd card partition. I didn't think I had that much on there, (just some free apps from google and amazon) but I might I have run out of space? I never elected "move to sd card" or "clear cache" for any apps and don't know if that is a requirement when you use dual booting.
I haven't found instructions for what to do to create a dual boot card for 1.4.1. My original 8 gb card is in the unit, but I'd like to create a new boot card using the higher quality medium. Just want to understand what's happening. Is use of a 1.3-based card bound to lead to more corrupted partitions? Any suggestions on how to create a reliable dual boot card for this unit?
Click to expand...
Click to collapse
Can't tell you what issues you may be having with the sd card, but verygreen's "dual boot" (it's not really dual boot, but that's another story) method is independent of the stock rom (1.2, 1.3, 1.4, whatever). When you boot to the sd card, everything needed is on the card. When you boot to the Nook, either by using the sd card menu or removing the card, you get whatever stock ROM is currently installed in the emmc. If you properly created the sd card, you can insert it in any NC and use it.
I read through all and by the end, I'm lost
Anyway, if you are dealing with verygreen's uSD cards, you should be all set and not to worry anything on the eMMC. It's independent.
As why those partitions corrupted, I don't know as I never hit that problem. Just curious, why do you say it corrupts?
votinh said:
I read through all and by the end, I'm lost
Click to expand...
Click to collapse
Oh well, if no one else has had the issue of sd card corruption hopefully its not a side effect of using verygreen's image together with cm7 7.1.0, google apps and user apps.
Anyway, if you are dealing with verygreen's uSD cards, you should be all set and not to worry anything on the eMMC. It's independent.
As why those partitions corrupted, I don't know as I never hit that problem. Just curious, why do you say it corrupts?
Click to expand...
Click to collapse
The behavior was a little different each time. Has happened 3 times now.
Once it totally locked up. Powered off and back on. Got my home screen with icons but in the notification area an image of the sd card persisted for maybe 5 minutes while the unit was otherwise locked up. Finally the sd card image cleared, but es file explorer empty sdcard. When tested on the PC, that partition's data was corrupted. Recovery (using pc software) retrieved a bunch of files but without their proper names. That time my apps were not destroyed. I didn't have to redo verygreen's procedure, just reformatted CM7 SDCARD partition.
Another time I had powered off. Restarted and it booted in Nook instead of CM7. Removed the card and tested on the PC and both the boot and CM7 SDCARD partitions were unreadable. Didn't attempt any recovery. Wiped out and reformatted the card, then redid the verygreen procedure on it.
The third time (last night ) was more similar to the first time. I got some forced closes and couldn't get back the status bar. Rebooted. Got the sdcard icon showing for about 5 minutes. When it cleared, my files were inaccessible. Removed the card and tested on the PC. CM7 SCDARD partition content was corrupted.
The (bad?) sd card didn't give any errors when tested prior to the break downs. Its labeled as a sandisk 8gb class 2. Was a gift.
I'm back up and running after redoing the verygreen procedure using one of the new sandisk 8gb class 4 cards. This time I actually used my unit instead of another to do the unpacking/recovery loading of cm7 and google apps. I've never applied any of the nightlies. Maybe I should look into that. Also have never deliberately done any other procedures, such as overclock it.
Praying the corruption issue doesn't hit me again. I guess my NC's internal flash drive could possibly be defective. If so, at least its still under warranty.
heya
i just got a new SD card, 32gb class 10 and i think it might be defective.
when i put it into the phone and start SD tools to test speed (mnt/extSdCard) which WORK Swith another SD
here at first it tried to scan and said "error" (again, this works with another SD) and sometimes it fails to mount and says "invalid path" (same path)
not sure waht to do
i put it in my laptop (which was also problematic at first) and format it to exFAT 32 unit size but still, no go..
what am i doing wrong?
EDIT:
i now ran format via the s4 itself, it ran the test once, got a 2.4 write speed and 8.9 read, isnt that super slow for class 10? also after first test it fails to run another