I just got my g-tab in (not a w00t purchase, ebay in fact)
I'm reading over scsione889's very awesome guide before I dive in. While I was reading the guide I note that it very specifically instructs the reader to flash from internal memory.
I found this to be rather odd since all my experience with clockwork on my dInc has been flashing from SD. Does anyone have any details on why flashing from internal memory is used in the guide?
Question number two comes from the w00t purchasers warning thread
I checked my stock firmware version after reading this thread and it's 1.0-2736. Why is it necessary to install the OTA before flashing other roms etc? Does it update the kernel? It certainly can't be a radio issue on this tablet =P
I have already installed clockwork at this point and I wanted to ask about this before performing the OTA or just flashing Vegan. Any tips on the OTA thing?
Hepful posts will as always be thanked!
After investigating a bit it seems like the G tab handles it's own internal memory as an SDcard. This strikes me as odd but may be normal. Will clockwork not detect a "second" SDcard?
More info would be great if anyone has it.
k4el said:
After investigating a bit it seems like the G tab handles it's own internal memory as an SDcard. This strikes me as odd but may be normal. Will clockwork not detect a "second" SDcard?
More info would be great if anyone has it.
Click to expand...
Click to collapse
All the devices I've owned has the 'internal' memory labelled as SDCARD, even though it's not actually removable. When flashing roms you will be copying the files over to the internal memory (labelled on the device as sdcard).
Your legitimate sd card is usually labelled as something else. /emmc, etc etc. It will likely depend on the rom/kernal you are using.
k4el,
Internal memory is /sdcard. External miniSD card is /sdcard2.
You can flash by putting the appropriate recovery and update.zip files in /sdcard and
booting into recover with power and volume +.
You can also flash by putting the same to files on a miniSD card and putting it in the
slot. Only thing is you have to edit the command file in the recovery folder to change
the location from /SDCARD to /SDCARD2. (You can do that with Notepad, but make
sure when you save it you keep the file name as "command".)
Your USB key shows up in the file manager as "/usbdisk" but it is not usable for booting
or recovering.
I think there is a pretty good sticky on this topic at the beginning the General Forum.
Rev
Standard recovery can use a microSD for flashing (the instructions are slightly different, as Rev mentioned) but the "safe" version of clockworkmod we use only reads off the internal memory only. Newer versions on cwm can use both, but they is a higher risk of to causing a soft-brick so I personally don't recommend them.
Related
Everyone,
I've written this a bunch of times but and putting it in
it's own thread so folks can read and use it.
Memory and Storage:
/sdcard -- internal memory of the tablet
/sdcard2 -- microSD card in the external slot
/usbdisk -- USB key slot
Stock Recovery Info:
Main method: Put your recovery folder and update.zip on /sdcard, turn off the tablet, the press power and volume + to initiate standard recovery.
Second method: Put your recovery folder and update.zip on a microSD card. Edit the command file in the recovery folder with Notepad to change the location from /sdcard to /sdcard2 and save it with the name "command" (NO
.txt or other file extension). Then boot recovery with power/volume + and the OS will use the sdcard (assuming you don't have a live recovery/update.zip file in /sdcard).
Third method: If you can boot recovery to CWM but can't get your ROM to work, go in recovery to the mount menu and go down to the mount USB memory option and choose it. Then plug your connector cable from the miniUSB port to your PC. When you plug into your PC an Explorer window should open and you should have a drive letter representing the G-Tablet (it's G: on mine) on your menu. You now can select that letter and you have access to your tablet memory (/sdcard). I've even had a time or two when not a single file showed!!! I added update.zip and recovery and loaded
a ROM!
The tablet boot process apparently checks /SDCARD. If it doesn't find a recovery file there it does the same check if you have a miniSD external card installed. The large USB slot is not useable for booting or recovery so far as I have determined or read.
I hope this helps you.
Rev
EDIT: I didn't put one fact in here about recovery that everyone should know. When you run a recovery operation, the system deletes the command file so you can't accidentally do it again. If you have to run a recovery or
attempt to load something again, make sure you have a command file in the recovery folder with the correct command in it!!! Sorry I omitted this first time around.
Placeholder
Placeholder
Hope everybody who needs this has seen it. I won't kick it up again.
Rev
Can you also add information about partitioning of /sdcard and why would one need it?
Is there another "hidden" flash memory available for firmware or all mods and custom ROMs go into /sdcard only?
Thanks so much, I thought I'm dead cuz I wiped out everything.
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
HackaMathecian said:
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
Click to expand...
Click to collapse
You need to use nvflash (nvidia tegra SoC flashing utility). There are alot of posts about it. Do be carefull if you go this route, as even though you will not damage your tablet, it may be difficult to put it back to a bootable state if you don't do it properly.
thanks!
thanks great. simple and to the point. should help people that get confused. thanks again!
Vlad_z,
It has been my experience that when somebody gets boot loops, it often involves a
partition problem. Also, sometimes the G-Tablet does flaky things. I have one I
just shut down. Restarted it with boot looping and had to rebuild.
The three locations listed above are the three memory places you can store stuff
unless you find software that custom sets up something else.
Rev
Os Money:
http://forum.xda-developers.com/showthread.php?t=861950
This thread completely explains the NVFlash process.
Rev
That's kind of odd, my removable sd card ended up with the label ex-sd. Doesn't seem to be messing anything up though.
sixtofive,
I've never seen or heard of that with the stock ROM. Are you running a different ROM?
Some of them do change the directories.
Rev
So simply put, we should copy and backup the recovery folder and update.zip in /sdcard (or tablet storage) and when things get f'ed up, we move the recovery folder and update.zip back into the /sdcard?
Maybe it's just me, but I looked into the recovery that was already in the tablet and there's nothing in it; is that normal? If not, can anyone provide the back up recovery folder and update.zip just in case?
sam,
Recovery is simply a folder which holds a file named "command" in it. Command is a file
that has the command line in it with the command and parameters to "recover" or "load" files onto your G-Tablet.
Sometimes when your tablet gets messed up, you can still use recovery and are lucky. But sometimes the recovery partition gets damaged and then you have to look
for other ways to get in and fix things.
http://forum.xda-developers.com/showthread.php?t=1010943
Many of us keep telling people there is a lot to learn here -- and Android doesn't have
all the stuff built into it Windows does. Nor is Android known for it's great documentation!
If everyone would read all the stickies at the start of the forums, it would provide
probably 80% of everything they need to know.
Rev
If OP also put links to stock ROMs, that would be great
interesting...even though I don't have a microSD card in mine /sdcard2 seems to be a valid directory within "root explorer"
what partition and memory structure should I be seeing on my brand new g-tablet? any suggestion on "mount" and "df" output?
Question, which is the best method or quicker to backup before attempting other rom installs?
Deleting CWM
How would one delete CWM so that the tablet can be returned?
Got my gtablet last evening. Seems there is a lot to learn.
thanks butchconner...
Thanks all the people who are contributing at xda. You are doing a wonderful job. In fact I bought this device because of you ( I think Viewsonic owes you guys a lot. At least they avoided a big loss because of you. )
Two questions:
1) Is it recommended to flash back to stock before changing roms?
2) Is there a link to the stock Rom files that I am missing?
Thanks
hi all, i have a rooted htc aria running froyo 2.2.ive got a new 16g card coming. i would like to partition. ive read way too much info on doing this, that im now totally confused! i cant figure out what steps this should be done in. ive got everything backed up. im not sure what program to use for the partitioning. have read not to use rom manager. im not sure about how many partitions i should have. after i copy my card contents to pc, where do they go when i copy them back? i just really need someone kind enough to walk me thru this. i have adhd and need specific instructions......thanx
chowceal said:
hi all, i have a rooted htc aria running froyo 2.2.ive got a new 16g card coming. i would like to partition. ive read way too much info on doing this, that im now totally confused! i cant figure out what steps this should be done in. ive got everything backed up. im not sure what program to use for the partitioning. have read not to use rom manager. im not sure about how many partitions i should have. after i copy my card contents to pc, where do they go when i copy them back? i just really need someone kind enough to walk me thru this. i have adhd and need specific instructions......thanx
Click to expand...
Click to collapse
Why do you need to partition buddy? Do you want multiple internal storages, or another reason? I may be able to help here with just a little more info.
i would like to partition the micro card.ive read that its better to have it partitioned?
chowceal said:
i would like to partition the micro card.ive read that its better to have it partitioned?
Click to expand...
Click to collapse
In some cases, putting a separate partition on your SD card and formatting to etx3 can be beneficial, especially with the Galaxy S devices. In day-to-day use with others phones though, you'll benefit far more from the extra storage than having multiple partitions. Do you have a Galaxy S mate?
i have a htc aria.
chowceal said:
i have a htc aria.
Click to expand...
Click to collapse
I found this for you, from the Aria forum:
To Enable A2SD:
Backup your applications
Backup your sdcard
Partition your sdcard with ROM Manager with an ext partition option. (ROM manager is in Market)
This should start a special mode of clockwork recovery, which will partition the sdcard.
That's the only reason you'd want to partition your card, so that if you're running out of memory you can move some of your apps to the SD card. ROM Manager is very easy to use, but I'll be here if you need me Good luck!
juzz86 said:
I found this for you, from the Aria forum:
To Enable A2SD:
Backup your applications
Backup your sdcard
Partition your sdcard with ROM Manager with an ext partition option. (ROM manager is in Market)
This should start a special mode of clockwork recovery, which will partition the sdcard.
That's the only reason you'd want to partition your card, so that if you're running out of memory you can move some of your apps to the SD card. ROM Manager is very easy to use, but I'll be here if you need me Good luck!
Click to expand...
Click to collapse
To follow onto this question. 1st time droid user, limited linux knowledge. I am running 2.2 on a brand new optimus t(mobile). I plan on rooting using z4root and flashing ROM (maybe megatron). Sdcard new (unused) only thing I have done with the phone is install a bunch of apps (which I can replace) and load my contact/gmail account.
I notice that my phone indicates 143kb internal available, so I assume I will have space limitations soon. It is my understanding that one of the benefits or rooting and putting on custom rom is the ability to have your phone recognize portions of the sd card as internal memory and, thus, "create" more internal space.
Considering my phone and my desire, can I go through the process of 1) rooting (z4root) 2) backup (custom recovery) 3) flash new rom/kernal 4) dump back up from sdcard onto PC via card reader 5) Use your above method to partition card?
Any suggestions/advice would be greatly appreciated, including partition types/sizes, process, procedure....or just tell me if I am an idiot and am way off base.
Thanks a lot
Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!
I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.
gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app
Hello XDA:
Earlier today I successfully flashed my nook color to CM7.2 using TWRP 2.3.0.2 as described in this tutorial http://forum.xda-developers.com/showthread.php?t=1030227.
After that I successfully flashed TWRP 2.8.3.0.
Right now I am trying to flash CM11 with the corresponding g.apps, but the files are not visible in recovery. What can I do? This is my first time rooting/loading roms so any help I can get is much appreciated.
Hi there,
Try to put that files (zips of CM and GApps) on the external SD Card and try again. maybe is something wrong with that recovery and didn't recognize your internal memory.
Also give us more details about your device for better pointing to the right forum.
Thanks
Hi thanks for the reply. I was actually trying to load the files from an external SD the entire time.
I managed the fix the problem luckily. I had an extra SD card on hand so I re-downloaded the files and tried flashing them to the device from the other card. It worked.
Is this a good way to do things in the future? That way I can keep my files intact on the main SD card and use a seperate SD card to flash new ROMs etc. Though I dont know if the file systems on the main SD card will be interchangeable between ROMs.
The device is a Nook Color (encore). I used the link that I posted in the OP to load CM7 and then CM11. The Nook Color community seems rather dead, so I posted here.
Glad to hear that you have done it.
Take care with SD Card no name. You can loose important files like photos or other docs if something goes wrong.
Good luck
Thread closed