Related
I am hoping someone can help me with this. I had my nook rooted, market, youtube and gingerbread keyboard installed and working. different boot screen flashed. i plugged it in to my pc here at work to charge. when i unplugged it, it was at the startup screen with the android. The old boot screen is back. All apps are removed. it appears to still be rooted, but I cant bring up keyboard at all. All my apps and everything I installed are gone. I don't understand what happened to it. Any one have any idea? Thanks!
A wizard did it.
Seriously others have reported similar anomalies The thing to do is wipe and start over. I suggest you get titanium back up so you don't have to completely start over next time.
I figured thats what I would have to do. I don't think i would have needed to, had I not installed the gingerboard keyboard. I was just wondering if anyoen else experienced, perhaps we could pinpoint the problem and figure out what to do to avoid it. Worse part is some one wanted to see it after I told them not to waste thier money on an ipad, they come over and it doesnt work at all. Well it worked, but just as an e-reader, bleh who bought it for that, lol.
madfatter said:
I figured thats what I would have to do. I don't think i would have needed to, had I not installed the gingerboard keyboard. I was just wondering if anyoen else experienced, perhaps we could pinpoint the problem and figure out what to do to avoid it. Worse part is some one wanted to see it after I told them not to waste thier money on an ipad, they come over and it doesnt work at all. Well it worked, but just as an e-reader, bleh who bought it for that, lol.
Click to expand...
Click to collapse
Dropbox + AutoNooter are a NC's best friend.. Show the friends how easy it is to root and load up apps. Remember to share.... 2.5 NC's to every grannysmith!
norkoastal said:
Dropbox + AutoNooter are a NC's best friend.. Show the friends how easy it is to root and load up apps. Remember to share.... 2.5 NC's to every grannysmith!
Click to expand...
Click to collapse
Dropbox works very well indeed. Awesome Drop is also very good. While it offers no online storage, it doesn't require an account either. However, neither wanted to work without an External SD card. Haven't looked into they wouldn't use the internal storage. Anyone know?
Possibly it updated to 1.01? Mine was act a little strange, then all of a sudden it updated to 1.01 (even with the script in place to disable over the air updates).
I also had some sporadic reboots. Just re-rooted after the 1.01 update and it seems more stable. I also installed an uptime widget to monitor and it's been up now for 11h 30m..
In a couple more weeks it won't matter as the 2.3 build continues to progress..
amp711 said:
Possibly it updated to 1.01? Mine was act a little strange, then all of a sudden it updated to 1.01 (even with the script in place to disable over the air updates).
I also had some sporadic reboots. Just re-rooted after the 1.01 update and it seems more stable. I also installed an uptime widget to monitor and it's been up now for 11h 30m..
In a couple more weeks it won't matter as the 2.3 build continues to progress..
Click to expand...
Click to collapse
Hey can you let me know if your Read to Me functionality is working on 1.0.1?
Im on 1.0.0 still because the read to me doesn't work with the 1.0.1 update.
I also get sporadic reboots now that im rooted.
Sent from my LogicPD Zoom2 using XDA App
It was already updated. I am not sure what happened, but Its up and running again. This thing is awesome, even with the barnes and noble rom, and restrictions. It plays every game I throw at it, just as good as my Incredible. Most apps fit the screen well and its only going to get better. best 250 I ever spent. I literally carry this thing everywhere I go!
Just saw this post. Same thing just happened to me while I was in the market. Sucks... have to reroot now... argh...
Sent from my PC36100 using XDA App
Another data point: got my Nook Color December 25. It was version 1.0.0. Updated to 1.0.1 and rooted with auto-nooter-2.12.25 on December 26. All went well (including using the Shop, though I didn't buy anything) until last night. Entered the shop and got the infamous "authentication problem" message, after which my nook reset itself. When it was finished, the green 'n' icon in the lower left was on (which is odd, since it appears to have updated from 1.0.1 to 1.0.1).
When the dust had settled, the device was still rooted (I still have Market, still have NookColor Tools, still have SuperUser), but everything I'd put on since rooting was gone, and all my settings (wifi key, barnes and noble account, gmail account) were gone.
I'm reasonably familiar with linux (though only a little bit specifically with android), so I'll be happy to poke around to see if I can find anything....
Possible reason?
Search "maintenance update nook" on Google News [ sorry, I can't post links yet ]
3matthew3 said:
Search "maintenance update nook" on Google News [ sorry, I can't post links yet ]
Click to expand...
Click to collapse
No, that would be 1.0.1. Android Police tend to be late on the uptick on real news, and make up the rest...
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
I have done some research here and on Google on a really odd problem...
My wife has a NC I updated to 1.0.1 then rooted. About a week later on her way to work it restarted and unupdated (?) back to 1.0.0... So I thought it was a fluke, root was gone but most things still worked, not Youtube or market but other apps I installed while / did.
Now twice, 2 days in a row I have checked out the device, I installed Clockwork, did a backup and the next morning on the way to work (She works in manhattan, takes the train in) it is bootlooped "touch the future of reading" so last nite I ran the clockwork restore and it was fine then again this morning... same thing stuck in a boot loop.
As happy as I am about her being able to restore it on her own...it takes a while and shes at work by the time its done! and the maddening part is that I booted it multiple times the nite before in both cases...
What could be causing this? Things I haven't tried yet?
I checked the SD to make sure there weren't any update.zips or similar,
I have not formatted the SD, that I will do tonight.
I read the whole thread regarding Clockwork I didn't see anything I might have messed up...Does this have to do with uSD boot priority and maybe I have a hidden file on the SD?
And I have really searched for something similar, people have bootloops but not like mine that I can see.
Sorry for being long here but this is frustrating, I'm not all that new at this I've been voiding my warranties for a long time and this one has me stumped...
Thanks in advance for any reasons, suggestions.
EDIT: Looks like I am not alone, I am seeing more of these problems pop up now.
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
eyecrispy said:
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
Click to expand...
Click to collapse
I have disabled OTA but if this is a registration/ auth problem I guess it wouldn't help.
I have NOT gone the 1.0.0 then root path and that sounds like a good next step, thank you.
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.
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
My vote is to go with a custom ROM. It will solve all of these problems. Cognition is the most similar to stock and is quite easy to flash. As for the problems you are having, I don't know what to tell you.
Try Cognition 4.5.3. You won't be disappointed.
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Well, not busy tonight. Watching pre-season football.
Flashing a Froyo rom is not too bad. Since you have stock 2.2 it will be a little more tricky than if you were still on 2.1.
First, what is your build number? look on the sticker under your battery to see a four digit number beginning with either 10 or 11.
I will private message you with more.
taltal13 said:
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Click to expand...
Click to collapse
Make sure you READ EVERY LINE OF THE OP. When you think you got it, read it again, then give it a shot. For the time being just factory reset your phone, should clear up some of your issues. Good luck
sent from long ago, in a Galaxy far, far away.
^^^ he's right. READ, READ, READ... until you're sick of it. It will pay off and keep you from bricking. Sorry I didn't mention that. But I will be glad to help you if you need.
and if (or when) you manage to brick it do not panic,, go back and read some more,, seems that almost everything an idiot like me can do is fixable,, and most normal people are pretty safe,, they are not going to kill their phone,,,,if they read and follow instructions,,,not doing those two have found my phone in some pretty unresponsive states,, but I am running mosaic VI now and loving it,,but have been on so many I had to go look,,and have finally I hope learned the value of reading ( and those other people probably do know more than me so I should not think I know better ,,,yet)
taltal13 said:
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
Click to expand...
Click to collapse
Not sure how much of knowledge you have gained before doing these attempts of changing some values to enable side-loading...
I would suggest to do factory reset since you are still on FROYO and see if this does the magic.
If it gets locked back to AT&T, I suggest just talk to AT&T rep to unlock & side-enabling. Once all is well, you can do rooting as you did before. Hope this helps to solve your problem.
For any other help, we have XDA here and get some time to go through forums. As others suggested, please read, understand and act.
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
taltal13 said:
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
Click to expand...
Click to collapse
Just for a bit of encouragement ive been using Cognition 4.5.3 as my daily driver for the past 4-5 months and have never had a single issue with great battery life. Ive tried numerous other roms on this forum and always have run into a boot loop, force close, or other random issue that makes my phone unstable but with Cognition I experience what my phone was meant to be like.