Related
First of all thanks to all on the forum for all the useful tips and tweaks.
I finally took the bold step of my first flash two days ago to Dutty's latest Rom.
As he advised I have slowly added programmes and tweaks to make sure there were no bugs. Last night I was playing around with different wallpapers after a day of the phone being stable. Waking up this morning I found a lot of my tweaks for the today screen had reset themselves. Using file explorer i tried to open my storage card (I kept all the cabs i have been using on it) and it wasn't found. I took i out and have tried to open it through my laptop and it keeps asking to 'insert card' i.e it can't see it either. I tried a hard reset on my HD to see if it was anything I had installed and still nothing!
I have most things backed up on my PC and yesterday set up microsoft myphone so hopefully I haven't lost anything...BUT. Has flashing caused this or is it just coincidental that my storage card has gone tits up!
many thanks in advance.
P.S Off topic. has anybody else found that the Virgin advert causes a stuttering effect when scrolling down a page?
Hi Mate,
take a look at this link
http://forum.xda-developers.com/showthread.php?t=506560
Should explain all, it looks like when you upgrade to one of the newer roms not based on the 1.14 it kills the SD card, you could try formatting it again..
Happens quite randomly , so ...
Bloke
Cheers Bloke
Although the cause doesn't seem to be very clear. I flashed my HD without the SD card in. I have a sandisk card. It came with the phone but it was a replacement phone so not exactly bundled per se. (after getting the phone on an upgrade last Dec with Orange actually paying me a fiver for it, I lost it/had it stolen after owning it a month and had to then fork out £160 for it )
Sods law that i haven't been backing up my SD card as the majority of it was music that i have on my laptop anyway.
Thanks once again
I've never lost any info on my SD Card from flashing any roms, and I've flashed a lot. Even when going from 1.14 roms to 1.59 roms. No probs
However I have heard others have had similar problems and unfortunately only remedy was to format card. Once formatted problem shouldn't arise again
So to update:
tried out spare sd. Not a problem although only looked at it rather than file swap etc
Hard reset: still didn't find card
flashed stock 1.14 rom. Had colours go strange on screen whilst first installing but then touch flo started and colours as norm. Put SD card in and it wasn't found. Soft reset with card in and once booted funny colours came back (all kind of negative and opposite original colours, kind of cool but obviously not good). Still not finding card. Took card out and soft reset, all good and colours back to normal.
So, it seems, I will have to format. Bye Bye data!
I tried to look at the card from command prompt on my PC (xp pro) and it still couldn't see it. Muchos corruption me thinks. Not sure how I am going to format it now?
I hope HTC will look into this and release some sort of fix. Unless they know it's a hardware fault on the card reader and realise it will cost a small fortune to fix everybodies HD not to mention the bad publicity.
Okay, maybe not the most common method to do this, but when I had this happen to me, I also couldn't format the card anymore in my PC (Vista). What I did wat put the card in an old Samsung phone I had lying around, and the phone initialised the card for itself. After that it was also readable again on my PC and in my HD.
Since this happened to me I always take out the SD Card if I flash my phone. Just to be on the safe side.
I'm having some real issues it seems. I recently rooted my g1 about 2 weeks ago I'm running jf 1.5.1. My problem is that as soon as I rooted my phone I started to get all kinds of messages on my phone about my apps not responding no matter what I was doing, even apps I wasn't using the one i get the most is for bugreport. then last night when I was doing some stuff on my computer while I was charging my g1 with the usb, I made the most retard mistake ever when I set my comp to sleep I forgot I was charging and I didn't eject. Now when ever i try to use my phone for more then a call or a text Its crashes to the boot screen with the G1 symbol and then restarts. And yes this also damaged my Sd card, I reformatted it last night and it was fine then this morning when it crashed again It said my sd card was damged and i need to reformat it again, I figured **** it I will buy a new one, a much better one then I had before because I run swapper so I figure that swapper had something to do with it bricking my sd card
as you can probably tell from reading this I am new to this rooting stuff and I really just want it to work right If you need more information just tell me I will gladly do anything I possible can to have my phone work smoothly again, I reside in Las vegas If any one is from there that is willing to help me I will gladly even bring it to you.
Thank you for your time.
E-mail is [email protected]
do a wipe and flash a new rom
So basicly just re root the phone? If I do this can you tell me what I will lose in my phone? also will this completely fix my problem or is my actual phone damgaged?
will this also fix my sd?
bump bump bump
You don't have to reroot. Just get another rom or reflash the same rom and see if it still happens.
Just wipe and reflash..
however I like your idea better, buy a new G1 and send me your old on, everyone wins!
So I wiped my G1 and flashed Jf 1.5.1 abd1 onto it again and it seems to be working fine again, can any one tell me if there was a better choice then the jf rom? So know that I'm basicly back to square one,can any one point me to a thread or site that will tell me how to get the most out of it both app wise and performance wise.
thanks for the help from ever one who posted,I think I'll be stick'n to this forum for all of my android related questions, " oh **** do I hear dontation"!!!!
J0E_SK33T said:
So I wiped my G1 and flashed Jf 1.5.1 abd1 onto it again and it seems to be working fine again, can any one tell me if there was a better choice then the jf rom? So know that I'm basicly back to square one,can any one point me to a thread or site that will tell me how to get the most out of it both app wise and performance wise.
thanks for the help from ever one who posted,I think I'll be stick'n to this forum for all of my android related questions, " oh **** do I hear dontation"!!!!
Click to expand...
Click to collapse
I guess maybe you missed the whole development section?
I put in CM7 two days ago, and every thing was working fine. I restmy nook and it would not power on at all. I tried for 2 hours, and nothing. I was able take it back to the store and get a new one. What could cause that problem? After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.
Same Issue
I had the exact same thing going on. I installed CM7 and it worked great for a cpl days. Last night I plugged it in to charge it (left it on), and when I woke up it was off and unable to turn on. Black screen.
I put in my CWR sd card and held the nook, volume up, and power buttons to turn it on. I figured I just go back to eclair auto-nooter because I know its stable, so I formatted system and data and flashed the stock barnes and noble 1.0.1 rom. However...
I still have the same issue. The device doesn't power on. I'll return it to the store if I have to, but I'd prefer to fix it so that we can raise awareness.
Edit: I figured it out. The flashable repartition-boot-with-stock.zip was corrupted on my CWR sd card. I made a new one and I'm right as rain. Follow the instrustins HERE to fix the black screen issue with CM7. Although it will restore you NC to stock.
More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"
jd95 said:
After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.
Click to expand...
Click to collapse
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
The CM7 nightlies are not meant to be run from the SD card. There is also a build of HC that is not meant for the SD card. In my experience, nookie froyo ran better from the sd card, but it could also be run off internal storage.
So i respectfully disagree with your opinion. Which was actually a statement of incorrect facts.
jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.
sparhawk36 said:
More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"
Click to expand...
Click to collapse
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.
khaytsus said:
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.
Click to expand...
Click to collapse
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.
admiralnorman said:
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.
Click to expand...
Click to collapse
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?
If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.
Edited for derp.
combustiblemonkey said:
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.
Click to expand...
Click to collapse
I agree with this statement. I'm happily back to Eclair and advanced task killer.
Sent from my PC36100 using XDA App
succulent said:
If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.
Click to expand...
Click to collapse
Not helpful information contained in this post.
Sent from my PC36100 using XDA App
khaytsus said:
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?
Click to expand...
Click to collapse
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS. I will give it the burial of a Patriot, Westboro Baptist protest and all.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Sent from my PC36100 using XDA App
admiralnorman said:
Not helpful information contained in this post.
Click to expand...
Click to collapse
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
admiralnorman said:
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Click to expand...
Click to collapse
So what does your SD card going bad and your NC not booting have to do with each other????
khaytsus said:
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
So what does your SD card going bad and your NC not booting have to do with each other????
Click to expand...
Click to collapse
Right. You asked for clarification on my earlier post. I provided it. It seems you don't like your quesions being answered. Next time use periods instead of question marks. Or properly label them as rehtorical.
- Sent from my HTC Evo 4g using XDA Developer's app.
It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.
paranoid__android said:
It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.
Click to expand...
Click to collapse
So any idea what's causing it to get wiped/corrupted? Formatting SD from within the booted ROM or unknown?
These types of threads are funny. People are too quick to blame the rom alone (even when clearly marked as dangerous / test / experimental, etc ones) after making the decision to risk the normal operation of the device in the first place. Take some responsibility people
Exactly.. I don't usually post in forums but this kind of stuff bothers me. I wasn't able to boot my Nook Color for a few hours but I never blamed it on anyone but myself. Almost every one of the custom Roms, Mods, etc says something like "Use at your own risk" Nobody is forcing you to try anything. If you think you "bricked" your Nook Color (which is almost impossible) you shouldn't blame it on the Rom or Mod or even expect to take it back to the store.. YOU took the risk. Even if you installed a Rom that slapped you and gave you the middle finger it's your fault in the end because no one forced you to try it (most likely...). I'm sorry if I haven't offered a useful solution to "cm7 broke my nook", but anyway all this is purely my opinion and I apologize if I have offended anyone but people need to take some responsibility for their actions.
A couple of days ago my dad got my sister and me nook colors. I installed honeycomb which ran off the sd card on both and rooted both. I was tired of not having YouTube flash and many other apps so I tried out froyo and cm7. After about 50 unsuccessful installs I have decided I must have a hardware problem because they will run on my sisters nook.
The problem is that after the install, it boots off the sd card and loads android completely but when it asks to complete with setup wizard or
Default action it freezes up for a second and shuts off. After I boot again it just says "Powering Down."
I don't know if I should try a native install or go return this one. I already restored it completely to factory conditions so they won't be able to tell. I have searched everywhere and cannot find this anywhere else (problem or solution).
I just find it so strange how it works on the other nook color but not mine. Even setting it up on hers and moving it to mine produces the same issue. I probably will return it unless someone can help me but I'm more curious to what the problem is than how to fix it, since I can simply go get a new one.
Any help is appreciated!
****bump****
Thats certainly a new one. I only have one nook so ive never tried them side by side. Ive never been able too successfully boot off an sd card and have it stable. I eventually just decided to go to cm7 internal and never looked back. I wonder if theres something different in the nook in how it reads from the sd card.
are you overclocking the image? or running it stock?
you said you set it up on your sisters nook then move it to yours and you have problems. did you try taking her good, working build and moving that sd card to your nook and seeing if the problems go away. Ive read alot about sd cards and different quality's of cards. maybe theres something up with the sd card you have.
I have problems no matter what. If i put it on hers to setup, it still has the problem. If i set it up on mine, still has the problem. I just tried phiremod v6.1 and it also had the problem (i expected this because it is still cm7). I probably will return it but i wish they would just update these things to android 2.2/2.3 and maybe even full honeycomb when it comes out and save all of us from these issues.
The image is the normal one. I have tried installing directly to the sd, using the "SD CARD TEMPLATE" files that you install and then boot from to install cm7, etc.
They all work on the other nook but mine is being stubborn for some reason.
I am at the airport getting ready to fly home and i might try installing it internally tomorrow. I just don't want to have this problem again and have to spend a bunch of time reinstalling the stock rom to return it.
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
john10101 said:
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
Click to expand...
Click to collapse
I tried the internal install, but it is doing the same thing. I am recovering the stock image right now. Thanks for the help, but I am just going to take it back and get a new one and not root it or anything and just install it to the sd card.
I have the same problem too.
Holler y'all, I'm hoping you might be able to lend me a hand with these here droid troubles, you see I was fiddling with my Streak and I seem to have broken something kinda important. My droid now tells me my internal storage has a total space of 0.00B on which 2.15GB of applications are installed, contradiction I know. What's kinda weirdypants is that I seem to be able to install new apps fine, but when I try to use the camera I get the "Please insert an SD card before using the camera" nonsense. I should probably note that I also have an external SD plopped into the slot. So there's actually two SD cards, why the camera doesn't see either I ain't got a scoob.
So how did I get here? Well... I had been using that CM10.1 rom, which was quite shexy and all, but the lack of camera and the constant crashing that required a reset made it too unreliable for my use. I decided to downgrade back to Honeycomb and everything seemed to point towards StreakDroid-HD7-R8, but things went a little sideways and I ended up in a boot loop. Perhaps I shouldn't be fiddling with things when I'm so shleepy. Anyways I got my paws on a stock rom and managed to install it with fastboot and recovery. Everything looked fine and I went ahead with setting it up and installing apps, until I got errors about the SD not having enough space to install some apps when it really should've had plenty. I rooted it, tried clearing caches, formatted it, but there was no change except for me having to install all my apps again. Oh yeah, I couldn't backup in Titanium either. So here I am.
Perhaps the SD is dying, perhaps I corrupted it with my fiddling, maybe it's something to do with the partitioning, maybe it's something else? If anyone has any ideas or suggestions, please share.
Also, if the SD is to be retired, is there anyway of redirecting apps which would normally use the internal SD use the external instead, for example the camera app?
Thanks in advance.
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
giveen said:
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
Click to expand...
Click to collapse
Offt, that was a tad fiesty. My apologies hombre, I do read and I've ready plenty on this forum, but I guess I haven't read the right threads, perhaps I didn't know the right combination of words to search for. Slap me with a wet fish and shower me in stale coco pops - I am a daftie! You're a mighty fellow, so I shant be cheeky, you've spent a great deal of time making the streak more awesome for all of us, which I do appreciate greatly. Thank you.
Now when you say restore to Android 2.2, are we talking stock ROM here? And do I have to do anything special beforehand or is it just a case of plopping the ROM on my SD and restoring? Thanks kindly for your help captain.
You need to grab the NVFlash pack to restore to Android 2.2, which will also restore the Dell crappy partition tables.
Look at TheManii's DevHost page, he should have it.
Partition tables had to be changed as Dell did not correctly do Android, resulting in the sdcard daemon being broken, so they created something called like "oem_sdcard". If they had just done it right the first time, we would be in this predicament.
Oh and anytime you need to be slapped by fishes, I'm more than glad to. If you had merely scanned the General section, before you posted, you would have seen at least, three threads, where people were having the same problem, and where each time I already stated the exact same thing that you needed to do.
I'll take the slap. I think I spent most of my time in the Dev section, yet I post here in General, you see, that is why I am daftie! My internal compass is corrupted.
Many thanks for the help and info, perhaps someone should slap Dell with a fish? Anyways I best go correct my wrongs now.
I have read many threads and I have the same problem. However, I already used nvflash to repartition my Dell and revert back to 2.2.2. I then updated back to Honeycomb 3.2 and I still have this issue. I ran it a couple times... repartition and restore back to 2.2.2 but still no luck. Any thoughts? Sorry to respond to such an old thread, just fishing for any ideas.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
xcover2 Same issue
I am facing same issue with my xcover2 , any solutions ?