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.
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
So all i want to do is take everything off my 4gb sd card and use an 8gb sd card so that I have more storage space. Everything works great as is, and I wanted to keep everything as is. Just need more storage space. I've looked through the forums and haven't found anything that addresses this process. I am running CyanogenMod 7.0.3 w/a 4gb sandisk micro sd card. How do I copy so that it boots just like my 4gb card???? Thanks ahead of time for any help.
Bambam01 said:
So all i want to do is take everything off my 4gb sd card and use an 8gb sd card so that I have more storage space. Everything works great as is, and I wanted to keep everything as is. Just need more storage space. I've looked through the forums and haven't found anything that addresses this process. I am running CyanogenMod 7.0.3 w/a 4gb sandisk micro sd card. How do I copy so that it boots just like my 4gb card???? Thanks ahead of time for any help.
Click to expand...
Click to collapse
I recommend just writing an image file with winimage. Then writing it to a 8gb card, then using Easeus Partition manager to expand the last partition to full 8 gb.'
Do you boot from the SD card or eMMC?
If it's the latter, just copy the contents of the old card to the new one.
If it's the former, I recommend a fresh install; use a backup program (MyBackup, Titanium Backup) to back up your Apps and Data and then restore when you're done with the fresh install.
I'd like to do this as well.. in response to previous reply.. there are 4 partitions (boot, 2 other and last one with your data) do I have to create 4 different images with winimage or just for the first boot partition or does the winimage creates the image of the whole msd card?
The winimage will create a 4 gb image of your card on the 8 gb cards including existing partitions. What you'll need to do is get the largest partition to expand to the whole card. Assuming that the 4gb install on SD is the same as an 8 gb install if you did it fresh.
If the partitions are set different for 8 gb on a fresh install, you're better off just doing a fresh install and use titanium backup as the other guy said.
Phatdawg said:
If the partitions are set different for 8 gb on a fresh install, you're better off just doing a fresh install and use titanium backup as the other guy said.
Click to expand...
Click to collapse
That's a good point, the Size-agnostic SD installer uses different partition sizes for everything except the boot partition depending on the size of the card.
I tried winimage first to see if it even worked. Which it didn't. I didn't try to expand the existing partition. It just booted as a normal nook. You would think this would be a easy process but.... Lol, always new challenges. Guess that's why I enjoy doing this.
Well I tried yet again w image, expanded the partition. Still. Didn't work. I must be missing something. How hard can it be to make a copy of a bootable card? Must b brain dead today! Any other thoughts? Thanks!
Bambam01 said:
Well I tried yet again w image, expanded the partition. Still. Didn't work. I must be missing something. How hard can it be to make a copy of a bootable card? Must b brain dead today! Any other thoughts? Thanks!
Click to expand...
Click to collapse
I have done this several times, and I recommend downloading easus todo backup free. Then place both sdcards in a card reader, run todo backup and just copy the 4g to the 8g and expand the fourth partition right there in todo.
This applies especially if you want to copy to same size sd's, as you will not run into the usual image sizing issues.
Hope this helps
I don't know what you're doing wrong. before expanding the partition, make sure the sd boots, if it doesn't, then there's a problem with image being read or written as opposed to the partition.
I also had a problem with a new SD card not booting that I fixed by using the nook (that is the core nook OS) to reformat the card, then put the image onto the SDcard (shouldn't have changed anything as far as I know, but it did anyway).
Ok I tried this and it worked flawlessly. Used win32diskimager to "read" my 4gb sd with cm7 image. and then used "write" to 8gb sd card. It cloned 4 gb original image with 4 partitions and one unused partition of 4 gb. After that used easeus partition manager(latest version) to format unused pattition to fat32 and then merged with last partition of 2gb (move/resize) ..so now I have 6 gb of data partition which i can use to transfer files or move apps from nook's internal drive. The new 8gb card with cm7 image booted without any issues keeping my original settings of 4gb. One thing to mention that somehow it did not work on one pc with windows xp (kept getting write error on win32diskimager program)but worked on my laptop with windows 7.
That is exactly how I have done it in the past as I described in my first post. I don't know why a person would have trouble with it unless there was a format issue (i.e. ntsf, etc).
I have a nook color with dual boot from sd card. The sd card having an android 3.0 version.
After I got the 1.4.1 update, I noticed that I was able to access the sd card( the boot partition alone) from the stock OS boot of nook.
But now, dont know how, I dont see that anymore.
Was this a flawed update that was fixed or am I missing something.
Do help please.
I could really use the advantage of using the bootable sd card as a regular storage card when using the stock OS of nook. I prefer reading on the stock OS of nook.
Not sure why you're not seeing the SD card anymore, does it still boot?
SD card installs create multiple partitions on the SD card and the Nook will only be able to access the first one (boot). It should be accessible with any version of the Nook default OS.
You should have a media partition with a decent amount of room (1-5gb depending on NC version). That would give you more room than the 100-or-so mb on the boot partition.
Just found out that you can point the emmc install to see the "sdcard" partition of the sd card using the following info:
racks11479 said:
use root explorer and edit vold.fstab to "4" instead of "auto" for sdcard mount
Click to expand...
Click to collapse
Yes, I can boot from it. Every time I plug in the SD card, the notification already says that it is safe to remove the SD card. In the device Info part of the setting, the "Unmount SD card" is already greyed, though it does say that the SD card is found.
It is however useful for me to know that the boot partition should always be accessible.
I did remove the SD card a couple of times without unmounting it first, could this possibly have corrupted the card?
srn_28 said:
Yes, I can boot from it. Every time I plug in the SD card, the notification already says that it is safe to remove the SD card. In the device Info part of the setting, the "Unmount SD card" is already greyed, though it does say that the SD card is found.
It is however useful for me to know that the boot partition should always be accessible.
I did remove the SD card a couple of times without unmounting it first, could this possibly have corrupted the card?
Click to expand...
Click to collapse
Try to boot the uSD card (the one with Android 3.0 on it) and see what happens.
If it can, then it's good, if not, you can say it's corrupted.
Yes, I can boot from it. So I assume the card is OK
I plugged in other uSD cards and they get recognized fine. So I assume the Nook stock OS device recognition is OK.
I should probably recreate the boot partition as a last ditch effort
I had the same problem at first, but now I have mounted the correct sdcard partition that I wanted to mount.
I couldn't get it to work with editing the vold.fstab file at first. Then at some point after I manually mounted the correct partition through adb shell and edited the vold.fstab it now works.
nookdevsDOTcom /NookColor:_CyanogenMod_Internal_Installation#ixzz21UtixX6U[/url]
Newbies beware if you are formatting the sdcard with the nook..you might end up formatting the boot partition and your Nook will get into a bootloop...While it is fixable, for a newbie it is an avoidable trap.
Click to expand...
Click to collapse
All right. I went into clockworkmod recovery one day and I did the above mistake, I wiped the EMMC of my nook color, which had the stock OS/ROM. I had CM7 on an SD card.
I don't know whether or not the SD card is ruined, and how to fix my nook color, since it will not connect/read data through usb to any computer now. I cant even charge it like normally, It wont show the normal charging screen. if I plug it into the power adepter, it simply turns on and constntly re-boots.
I'm thinking of buying a new micro SD card and follow the instructions at the above link. will that fix my problem (if I properly set up a new card and pop it in the nook, etc.)?
if I cant fix this I might go to a website and buy one of their pre loaded recovery cards so that I can fix my nook. but I am destitute, (sadly) and I dont think I could risk that right now..
I dont have a mini SD card reader right now, so I cant test out the old 8GB SanDisk I used for CM7 (which I bought preloaded on amazon). I'm going to buy a card reader along with the new 16GB SD card, if I do decide to purchase one.
My apologies if I am sound confusing, I have some language/context issues. Thank you for any help.