Database Develop

[SOLVED] Apps2SD problem with sd

I had apps2sd by lucidrem running on my phone and it was fine. I was out today and my sd card was 'removed' although I didn't touch it. This ended up bricking my phone, because the sd is removed and there is no data or delvik etc. Is there a method to use apps2sd without it being permanently affected when an sd is removed?
A reinstall of rom has fixed it however I have lost everything off the phone now
Thanks
Tucka

LucidRem's Apps2SD uses symlinks which I believe is now preferred over the one used by MarcusMaximus (forgot what its called ) only way to remove a sdcard safely without screwing up your phone is if the phone is turned off. No idea how the sdcard was 'removed' if you didn't touch it. Happened sometimes to me, but never found out what caused it. Hope this helps.

Best to apply Apps2SD again really or use a ROM that automatically enables it by default if a partition exists (Cyanogen/Dude).
Also a small sidenote... The term "brick" means your device would no longer be functional at all, I.E Unable to turn it on using any method. A more suitable term would probably be "crashed" instead.
I only mention this because the term bricked is being used far too loosely to describe the wrong symptoms.

Sorry for loosing brick loosly, just presumed that was what it was when the phone won't get past the G1 splash. So, say I want to watch a movie or something on a different memory card (won't be able to fit all my stuff on one) all I have to do is switch phone off, remove memory card, insert different one (preferably also with a2sd configured for meridian video?) and that will work?
I think the problem is with movement and sudden knocks that the card comes out. I was running through a storm when it said memory card was removed.
Thanks

No worries about the terms as there are an awful lot of them in the world of technology! Long as we're all learning then we can't argue ^_^
To be honest, hot swapping SD cards is a bit long winded... Its best to save up and invest in a larger memory card if possible (Class 6). Not sure what size your SD card is, but if it can't hold a movie then it could be time to buy a new one.
Also if you use the older Apps2SD program (1.1 I believe) it uses Symlinks as alritewhadeva mentioned and it shouldn't cause your phone to crash totally if the SD card is removed.
Best solution though is to buy a new SD card, you should be able to find one on the cheap on the net.

its an 8gb C4, however I am travelling and will be on a 10 hour flight later this month, and was wanting lots of films and tv shows etc. May just compress and squeeze them onto my 8GB.
Thanks a lot
Tucka

using a2sd and 2 memory cards doesnt work. All your app data and cache is on your sd card and the phone wont be able to boot without the right sd card in the phone (trust me i have tried). I suggest buying a new card maybe 16 gb.

Hope they have a charging point on your flight! It would kill your battery watching a movie for that long haha. Better off with an iPod/MP3 player I reckon.
But yeah, you can either add more compression or reduce the resolution/framerate to fit more on your SD card. Quality will drop but at least it will keep you entertained.

2 batteries plus a portable battery charger ftw

Haha, that should be sufficient then! Very well prepared ^_^ I was thinking about getting one of those wind up backup chargers for emergancy use once... No idea if its any good.
If everything is sorted tuka, could you please edit the title to add "[SOLVED]" so people know? Thanks!

[GUIDE] [BRICKED] Loading Roms/CWR via SD Fails - Black Screen of Death (28/02)

As we know, the Nook Color's SD slot will always take first boot priority. I'm in a situation where even booting via SD through known methods are not working.
The purpose of this thread is to:
1) Share with others who are in this similar situation, on methods which may result in the recovery of their own devices
2) Keep this discussion healthy so one day, I will be able to restore my own bricked device which I'm still striving hard to.
Click to expand...
Click to collapse
IMPORTANT: If you have a bricked device I need to emphasize on searching and reading very carefully what others have shared here in both General and in Development. This is a fundamental requirement, as with the ability to follow instructions and not panic by creating unnecessary threads. This will only make things harder to find, so thank you in advance for not doing that.
There are many useful guides out there, some of which the most helpful are:
Nook Color Restore to stock by samuelhalff
Dummies Guide to Fixing 'My Nook Won't Boot' by RileyGrant
Stock 1.1.0 Clockwork Recovery Image by brianf21
Nook 1.01 stock dd images by shad0wf0x
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD by thecubed
Click to expand...
Click to collapse
Anyway, in severe bricking cases where hardware is not at fault, many of the solutions to restore the NC begins with either:
1) Booting to CWR-SD via uSD
2) Booting to a rom i.e. Nookie Froyo via uSD
3) Having ADB access, if available
Till date I am not sure why the SD-loaded programs do not work for me, and here are the symptoms:
1) Without SD inserted, the standard BN splash appears, 'Welcome to the Future of Reading', then gets stuck there till powered down. Needless to say, the 8-times reset method doesn't work.
2) With SD inserted, the 'LOADING' screen will splash, then screen blacks out with device still powered on . You will know that the device is still running as you need to hold power down for around 20 secs before you're able to power it back up again. I call this the 'Black Screen of Death'.
Click to expand...
Click to collapse
To get your device up and running, try the following:
0) Do not panic. As long there's no hardware failure there will always be a solution. Look at me, thing's still a damn brick and yet here I am, still hopeful
1) Perform a search, read the useful threads created by the above members first. This thread is related only to failed SD-booting.
Once you've done that, prepare your recovery options with these in mind. The elimination process is part and parcel of problem-solving. In no particular order:
2) Sometimes, try powering on your device by connecting the USB cable from your PC or A/C source, instead of using the Power button.
3) Use only the original USB cable that came with your device.
4) Use the back USB ports of your PC, instead of the fronts as they may provide more consistent power and connection to your device. Try to avoid using USB hubs as they may not distribute the required power equally/properly.
5) Try switching to different USB ports, some may be hardware-gimped due to wear-and-tear.
6) Try to attempt the recovery on another Win, Mac or Linux computer. At least eliminate further possibilities of environmental hardware error.
7) Try charging the battery full.
8) Or, try discharging the battery completely, by leaving the device in BSOD state overnight until you get a message saying your device can't boot due to insufficient power when switched on. Once you are in this state, keep booting the device up until the screen does not appear. Then, recharge it back to full to see if the OS returns to stock (I am sceptical of this, but this was what others advised).
9) Try different SD cards. The device could be picky. Variety should be by class-type, brand, SDHC or non-SDHC. It's been discussed that faster cards perform better, as with more reknowned brands. Also, 16GB cards reportedly do not run Froyo (do read more by searching).
10) When loading anything via SD (CWR, roms), try different button combinations i.e. power + n + up, power + n, etc.
11) And/or, hold power for various timed-presses i.e. >30 / 45 / 60 seconds. Some members report CWR booting up after these periods, or even longer.
Note: funnily I tried holding power + n + up for > 60 seconds and the 'LOADING' screen just stays frozen. Still doesn't work, and I didn't get any ADB access.
12) Try formatting the card completely with native Win/Linux tools, EASEUS Partition Master or SDFormatter before each burn.
13) Try using both Win32DiskImager and WinImage, or dd-ing in Linux (search for more instructions). If you have Linux, you can check to see if the SD's /boot partition is indeed bootable or not.
14) For ADB access, try to unregister your hardware (go to Start > Run > devmgmt.msc), then unplug-replug device to have your PC detect it again. If a device with VID of 2080 shows up, that's the NC. You should know what this means, by now. If not, read more here.
15) Try different SD card readers, especially when experiencing failure on multiple computers. As opposed to multi-adapters i.e. 6-in-1s, try dedicated microSD readers like this one. Do not use those microSD-to-normalSD converters (usually packed together in the same shipping plastic as your card) just because you only have a reader that reads regular SD cards, they tend to fail a lot.
16) At your own risk, try cleaning the contact points on your SD cards (if you must, use cleaning alcohol and a cottom swap/q-tip - do not use water), to free them of dirt and invisible grime. If you have multiple SDs, try cleaning the least expensive ones first. Don't forget to leave them to dry completely before insertion into the NC. Credit to bonobomidwest, read his experience here.
Click to expand...
Click to collapse
17) Use Nooter 0.2 (recommendation from thecubed):
Here's my recommendation: use the stock charger cable (the one with the light-up N in it) when you try Nooter 0.2.
If the light goes from orange to green (or something like that) that means Nooter is booted and working.
My new thought: some file in /rom is missing, which controls the backlight and lcd controller. I can't prove this, but it seems logical haha.
All you need to do is get Nooter 0.2 booted and ssh'd in and you'll be able to dd over a complete 1.0.1 backup.
rawfish: I use Ubuntu, so sorry if I'm not able to provide instructions for Windows
Type:
Code:
sudo ifconfig usb0 192.168.2.1
Then:
Code:
ssh [email protected]
And you should be able to follow the directions for restoring on the wiki... either that or check around on IRC, if you tell them that you've got ssh access and you just need to restore your device, they'll help you out if I'm not around..
rawfish: I typed 'dmesg' in shell to see if the NC connected as a usb-ethernet device, and it doesn't show. If it does for you, then you should have progress and should ask around in IRC.
Click to expand...
Click to collapse
All these did not work for me, but hope this is useful to some. I've read testimonies from everyone that this is an unbrickable device, and I certainly hope it's true, and for a kind soul to help suggest more solutions. As I'm overseas, do you think I should call BN up to see if I can arrange to send my device back for fixing/replacement? It's been a month since purchase, and 3 weeks of failed restore attempts.
Disclaimer: I am not responsible if any of these methods get you in deeper trouble. Attempt at your own risk. Credit goes to thecube aka IOMonster, and the #nookcolor channel on irc.freenode.net. Thank you to everyone who created the recovery guides too.

This space reserved.

You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.

khaytsus said:
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
Click to expand...
Click to collapse
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.

rawfish said:
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
Click to expand...
Click to collapse
First of all - great job in pulling all the resources into one place (it's small consolation, but i think you've just helped a whole load of people )
Second, i apologise if I'm telling you stuff that's obvious, but in helping out on these forums often it's the LOGIC of troubleshooting rather than the particulars of the problem that are important... In other words, only vary one thing at a time, and ALWAYS swap out every piece of hardware involved at each stage... if you always rely on one piece of hardware this might be the weak link... so have you tried a different SD drive or adapter? and have you tried burning from a different computer?
Now, I'm not being insulting, because I had a virtually identical problem with my first froyo - it just wouldn't boot (as you describe) despite multiple burns, different cards, all of the standard formatting tricks etc. It wouldn't work in multiple computers - the common element being the SD/microSD adapter. It never occurred to me that such an electrically simple part could be at fault, but you bet it was - in fact i would say in my experience these things consistently fail! (I spent a day kickign myself, because we know ho unreliable they are from using them in other devices). They also all look alike so it's hard to keep track of which one you are dealing with They also fail unexpectedly, so if you used an adapter before there's no guarantee it's working now...
Sooo... Have you tried a dedicated microSD reader (rather than a simple adapter)? I now carry one with me everywhere (it doubles as the world's smallest thumb drive too)
http://www.amazon.com/gp/product/B002HGFKR8
Also bear in mind that froyo appears not to work on 16gb cards (i see you tried one)
Also, from my experience with other devices these cards are very sensitive to dirt and oil on the contacts. Certainly with enough frustrated handling you can get enough finger-grease on them to have them fail. Also they seem to be much less tolerant when writing than reading. I have NO idea how you would go about cleaning out the slot in the NC (and as someone who has ruined at least one DVD drive by blowing canned air where you shouldn't I'm not going to advocate for that). I have resurrected 'dead' SD cards before by cleaning the contacts with rubbing alcohol and a q-tip (on the card's contacts) - but again do so with great care (at your own risk!!!) and with your cheapest card, and make sure it si completely dry before you put it in the NC.
I have been generally a little scared that all this plugging and unplugging of the microSD might hurt the NC, so i have done everything i can to avoid that...

I am sure you can find someone local to you willing to help fix your boot issue but I assure you, its damn near impossible to brick a nook without physical damage.

@bonobomidwest:
No offence taken at all, in fact I am very appreciative of your contribution. I forgot to add the fact that I tried on 2 different card readers, plus indeed tried to clean the slot via an air duster VERY GENTLY as a last effort resort (I would not recommend this, it may cause permanent hardware damage). Once I'm free I'll go get a new SD reader (reads uSD only) and a new uSD which I haven't tried before. I'll try cleaning the contact points too.
*Thanks - I've added more checklists to the OP
@combustiblemonkey:
Thanks for the assurance.

I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.

Dr-Rockso said:
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Click to expand...
Click to collapse
Thanks, this is the direct link:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.

Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.

chrysilis said:
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
Click to expand...
Click to collapse
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.

rawfish said:
Thanks, this is the direct link:
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Click to expand...
Click to collapse
When I finally got it to work, the SD card was installed with the 1.0.1 stock OS on it, and CWR. The problem was that that (+) and (-) would only occasionally work. And if they did, it would usually freeze. I would be able to format system, but it would freeze if I tried to format data. Powered off, and I would get the black screen of death (BSoD). Once this happened, I would plug it into my computer so that I could hear the chime indicating a new device was plugged in. I found that ejecting the SD and then rebooting would sometimes help get rid of the BSoD. Then another power down, plug in the SD, and start again. Also, holding the N, +, and Power would sometimes help in launching CWR. I would usually have to hold for 60 seconds, but it would finally launch. It seemed like the nook was trying to run a process that slowing it down and causing it to freeze, but I couldn't figure out what it was. If I would wait an hour, it would boot CWR and allow me to format system and data, but then it would freeze when I would try to install the zip.
The successful install message was in CWR. It said Install From SD Card Complete, or something like that. After that, I still had to do the 8 reboots. It would load up the stock welcome screen and freeze. 8 reboots later, I got the video lady. Good enough to return it to the store.
It really was just persistence. It would usually take an hour of reboots before I was able to try to install the zip, and it probably failed on me 15+ times. The status bar would get half way, and freeze. Then I had to begin again. If it had been my nook instead of my friends, I probably would have given up. I wish I could be more specific, but unfortunately I am new to all of this. My nook rooted just fine, and fixing his is really my only experience with CWR. I just kept going until it worked.
Good luck! It is a pain in the ass, but it can happen.

rawfish said:
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
Click to expand...
Click to collapse
My wife has one as well so am able to test using that and the SD works fine in hers. The whole screen not turning on thing is weird though, does your screen turn on?
We bought them when on honeymoon in America so didn't have to pay a shipper or anything

Deleting the partitions manually with Gparted and using dd to burn the SDs and making sure the correct partitions are bootable doesn't seem to work. Last night I retried a lot of the previously attempted options, with no results.
It's weird to think that a working SD slot and a slew of cards will suddenly malfunction, but for now that seems like the most plausible reason why my NC can't boot anything off SD.
To think back how it all started, the device suddenly rebooted from HC preview v0.4 to stock BN 1.01 (rooted + installed CWR on eMMC) while the SD is inserted, then upon another reboot it simply stays dead, this gives me reason to believe that the internal boot partition is corrupted, and SD slot nuked hardware-wise.
Hmmm, really hoping to find someone else who has the same device, in my area.

Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.

Steelfan555 said:
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Click to expand...
Click to collapse
Sorry to hear that, and don't give up! Hope you took a look at the other threads, and this little pseudo checklist I made in the OP. Do share the outcome

Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!

FroztIkon said:
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
Click to expand...
Click to collapse
Update:
Ok, so after running through it, I ended up getting stuck on the boot screen that shows N. If I powered off, it would restart and get stuck at that screen. I tried the 8 shutdowns (it installed new software), but afterwards, it was still stuck. So, I tried another method I found on the forums. I powered off holding the N button and power, which caused it to boot back up and do a factory reset. I now have a factory fresh Nook.

Okay, it's been a while since I kept this thread updated - I contacted BN and had the device sent back, apparently the SD slot failed so they sent me a new one. I'm just wondering if it's sheer concidence that it happened, as I was tinkering with Nookie Honey preview v0.4, when the hardware suddenly failed.
Oh well, I guess the NC still remains as a 99.99% unbrickable device - with the 0.01% being related to the ambiguous root cause to my case.
I now have 2 NCs (one from the RMA process, another one from the $199 eBay deal.

Time to fully boot off SD card with CM7

Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.

That's about right. It's not much different on eMMC.
Rodney

Sounds about the norm here too.

Sounds way fast to me actually. I'm pretty certain that mine takes quite a bit more time than that to boot, the CM7 splash screen is up forever.

i just switched from emmc to flash card and its about the same for both...whats funny is my wireless runs better off the flash card...

sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Since performance is almost the same, if you need warranty work you can just pop the card out and send it in to B&N, but if your device no longer boots or has some other major problem and you send it in and they see a custom ROM on it, they will not give you warranty coverage.
At least that's ONE reason...

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.

darien87 said:
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.
Click to expand...
Click to collapse
Agreed I actually wanted to use some of the BN features, books reading is better and reading of magazines in color rocks. It functions very as it was originally intended to be a "reader". But I like to be able to use it as a tablet when I want.

I have only run from SD card but I played with my son's that is flashed to eMMC and build for build, I can't tell any difference so I just stick with SD card.

Timed mine...
hokudog said:
Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.
Click to expand...
Click to collapse
From power button push to when the CM7 rotating circle is centered on screen was 39 seconds. Desktop appeared at 1:03. A few more seconds for everything to 'settle' (fancy widget gets its skin, superuser ok's nook tweaks, etc).
On a new Sandisk 16gb class 4.

So far I think CM7 on SD would be my choice for running Android. Reviews are positive about it, applicable solution for noob like me.

I've a chance to run both CM7 off uSD and eMMC.
Here's my take:
+ Boot off uSD
1. simpler procedure (good)
2. avoid "void warranty" (good)
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD, want fancy Honeycomb = insert uSD, want fancy bla bla bla = insert usD
4. seems slower than the eMMC version
5. if having Kingston or Transcend (even with class 6), there are too many FC's errors
+ Root and run from eMMC
1. have to do more procedure (such format /data / system /cache)
2. B&N doesn't like it if rooted. There are ways to restore stock ROM those, again, more steps
3. Want original NC? do a restore procedure. Want to try Honeycomb? repeat installing procedure, ....
4. Seems faster
5. Virtually eliminate all FC's errors unless it's a real software bug.
6. Still some issues, at least in my case such Gallery doesn't work if no external uSD (FAT32) plugged in. Why? Why requires an external card? Turn ON USB storage has to go through more steps, my case, I have to unmount the eMMC's /media storage first then plug the usb cable in, then mount the /media for it to work connecting PC.

Best of both worlds
Very much a noob here. I bought my nook as an early retirement present. I originally had a Velocity Cruz but wanted to do more with it than it was capable of. Started reading threads on this site and BN site and after a week or two decided to make a dual bootable sd card running CM7. Everything went smooth but instead of the 15 min to create this card like I read on posts here it took me 4 to 5 hrs. Ok so I had a few issues!!!!! Loved it for the next couple of weeks; then while checking things out one night after I officially retired I was in Rom manager. Big MISTAKE! Saw there was an update to the CM7 I was using. Thought ok I'll update and low and behold I ended up updating internally not to the SD card. It was really nice rooted internally but after a week I decided to put stock operating system back on. Created that bootable card and went back to stock. Bought a 16 gb card made a new dual boot card with the same OS that I had inadvertantly rooted internally too. For all of you techies out there it was a lot quicker this time. I'm one happy camper now. I have Aldiko reader on the card and Calibre on my computer with plugins for taking drm off my books so husband and I can both read them. If I can do all this anyone can. I feel I have the best of both worlds now.

votinh said:
+ Boot off uSD
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD,
Click to expand...
Click to collapse
Depending on the ROM, you shouldn't need to remove the uSD to load to stock. For example, with CM7, you should be able to just hold N while it's booting and it will go to a boot menu, from which you can choose stock/recovery/sd/etc. Or, if that doesn't work, you can usually use a different uboot file.

Creating the SD card to run CM7 was very easy with all the how-to's up here and around the net. The performance is close to the same as internal memory. The best part is I have my whole OS in a tiny little SD card, which I can remove for security reasons or a lost or damaged Nook. Just pop it into any Nook and away you go.

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Warranty issues for one - but mostly there's no speed difference between SD and EMMC. It's actually *less* hassle - because you can fark around with an SD card all you want and *never* risk bricking your NC. The SD card sits in there and is no different in speed or boot up process - it just boots and runs.

I'm running racks' dual boot phiremod/hc and boot for phiremod seems slightly faster than hc. Maybe a few seconds faster than the 50 seconds it takes you, but seems like you're in the ball park.

Non- compliant internal storage cards

Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!

cabe0018 said:
Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!
Click to expand...
Click to collapse
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.

Thank you
xdrc45 said:
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.
Click to expand...
Click to collapse
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!

cabe0018 said:
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!
Click to expand...
Click to collapse
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!

xdrc45 said:
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!
Click to expand...
Click to collapse
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!

cabe0018 said:
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!
Click to expand...
Click to collapse
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.

xdrc45 said:
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.
Click to expand...
Click to collapse
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!

cabe0018 said:
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!
Click to expand...
Click to collapse
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.

xdrc45 said:
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.
Click to expand...
Click to collapse
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!

cabe0018 said:
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!
Click to expand...
Click to collapse
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.

xdrc45 said:
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.
Click to expand...
Click to collapse
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!

cabe0018 said:
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!
Click to expand...
Click to collapse
I think that's a good choice and hopefully the next one won't have the same problems for you!
The best thing to do when you get the new one is boot into bootloader mode and check the information, if you want post back all the info from the BL screen or provide a screen shot of it. Also go into settings, about phone, more info and post back all the information from there too. That way we can make sure everything is up to par on the device and functioning like it should and make sure it's not bricked and if it is we'll get it taken care of for you!

SD Card formatted as internal storage randomly unusable on cm13

I love marshmallow's adoptable storage feature, allowing me to install more apps. This feature worked beautifully for about a month and a half. However, I shut down the device, plugged it in to charge, went to sleep, and the next morning, the apps that were moved to the sd card were not available anymore. They were all greyed out on my launcher(Nova). I moved about 4 gigs worth of mostly games. Fortunately, most of them had cloud storage, but some favorite games didnt. This isn't that big of a problem, but I'd like to try to fix it. So, I went here for help.
At first, I thought the class 10 SanDisk 16gb sd had just gotten bumped out of the slot where the connections happen, so I opened the back cover and removed and inserted the sd card. The notification that prompted me to put the sd back in went away for a few seconds, but then came back. I repeated the process of removing and inserting the sd a few times, but still no moved apps were available. I put the sd into an adapter, then into my laptop, and it showed on file explorer. So the sd card could still be recognized, but maybe unusable.
I dont know what happened, one day it was working, the next day it wasn't. I know i formatted it as internal and portable storage a few times, so maybe that wore it out. I'm running cm13

Hello,
On my phone I used the micro SD card normally as external storage. On day I plugged in my headphones and there was no music. I though that the micro SD card must have come out. However, reinserted it it didn't work. I wouldn't open on computer either. While I don't have a solution, I am pretty sure I also had the same problem.

Once I was taking pictures with my phone when it crashed and rebooted. Some hours before the crash I uninstalled some apps and installed some others (but never rebooted the phone). After the phone started again after the crash, all the pictures and files were gone, the uninstalled apps were there as if I've never uninstalled them and the new installed ones dissapeared.

TheSaffronArmy said:
Hello,
On my phone I used the micro SD card normally as external storage. On day I plugged in my headphones and there was no music. I though that the micro SD card must have come out. However, reinserted it it didn't work. I wouldn't open on computer either. While I don't have a solution, I am pretty sure I also had the same problem.
Click to expand...
Click to collapse
how long have you used your sd card? i'm sure that the more you use a micro sd card, the more it will wear out and become unuseable/corrupted. That has happened to me before, where the sd card just stopped working.

KyleSaki714 said:
how long have you used your sd card? i'm sure that the more you use a micro sd card, the more it will wear out and become unuseable/corrupted. That has happened to me before, where the sd card just stopped working.
Click to expand...
Click to collapse
I have used it for about 1 year. So it may be that but, it has never occurred before.

Same problem here, you can read it here. While I am writing hopefully my files from Titanium Backup are transfered to my laptop. It got worse and worse, in my opinion the sd-card has reached it's end of life because of it's heavy usage. Error occured the first time after the phone got really hot recording gpx tracks. Bye bye sd-card
Another opinion is that warranty is over after two years, so the phone can quit it's duty now - obsolescense plans

Androphilius said:
Same problem here, you can read it here. While I am writing hopefully my files from Titanium Backup are transfered to my laptop. It got worse and worse, in my opinion the sd-card has reached it's end of life because of it's heavy usage. Error occured the first time after the phone got really hot recording gpx tracks. Bye bye sd-card
Another opinion is that warranty is over after two years, so the phone can quit it's duty now - obsolescense plans
Click to expand...
Click to collapse
yeah, i'm starting to think my micro sd just bailed from wear like that too, but i got to use mine for just over 3 months. i ejected the sd and put it into my computer, and interestingly enough, on my computer it reads 16 megabytes. i was like WAAT that cant be, i formatted it, put it back in my phone as portable, and it read as the normal 14gb. i'm starting to think my sd as internal is the cause of my random reboots. im even running the lastest cm13 update too...
i guess ill try and use my sd as just portable storage from now on, and see if i get any random reboots..

I switched to TurboROM which is using the sd-card as a portable media device, so no more encryption, heavy usage and complete data loss if you do not get your encryption key with root permission.
System space left after complete recovery of my apps with TB is quite nice - but you do not have the possibility to use App2SD (correct me if I am wrong).
So the only way to save internal system space is to move pictures, movies and heavy openstreetmap cards to external.