i recently tried to use the "read to me" books i got from barnes and nobles, i dont know why but recently ive been getting a full on red screen when i try to open them.
they worked just fine before, but suddenly have stopped working. i even tried a re-boot. any idea on whats up or how to fix? i havent changed anything since the last time i let my kid read one.
any ideas?
reboot and a redownloading of the books has not worked.
???????????
Sounds like a question for Barnes and Noble tech support. Is your Nook rooted?
lol. of course it is.
Randomhero27 said:
i recently tried to use the "read to me" books i got from barnes and nobles, i dont know why but recently ive been getting a full on red screen when i try to open them.
they worked just fine before, but suddenly have stopped working. i even tried a re-boot. any idea on whats up or how to fix? i havent changed anything since the last time i let my kid read one.
Click to expand...
Click to collapse
Any solution to this problem? I have also got this problem when trying to open the free "read-to-me" books. I tried to reboot it to see if that would cure it, but nothing changed. I even deleted those books and downloaded them again but still got the same red screen when trying to open them. This happened after I re-rooted my nook color with manualnooter-4-5-25 and also applied the OC kernel. BTW, all other non-"Read to Me" books are working alright.
The other issue I am now having is that my NC is also running CM7 102 nightly on SD card (also OC kernel flashed), but every time I power it off (regardless of rooted 1.2 or CM7), it will automatically power itself on a few minutes later. Basically I cannot power it off completely at all.
Any thoughts? Thanks.
Related
I recently picked up a nook from barnes and noble and for a few day i have had no problem. But ever since i tried putting music and pdfs on to the internal storage its been freezing up right after i boot it up from it being powered off. Ive been able to get it running after multiple restarts but every time it freezes from regular use it takes like 10 trys to get it running again. I was able to go into settings and factory reset it but to no effect. any advise would be helpful thanks.
i forgot to say i havent rooted it yet its still stock.
My NC was updated OTA this morning to 1.0.1. I noticed after the update that the Read to Me functionality doesn't work. I get an error and have to force quit and even if the book loads up correctly, it doesn't read. Have already checked volume levels and such.
Here's the error:
"Activity Fava Book Reader (in application Fava Book Reader) is not responding."
Anyone else seeing this or know about this issue?
I've been having the same problem. Rooted on 1.0.1. I saw another post for a non-rooted NC that was having the same issues too.
http://bookclubs.barnesandnoble.com...o-Me-quot-books-not-reading-to-me/td-p/760638
I'm rooted on 1.0.1 using Auto-nooter and Read To Me works fine.
I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?
barbo said:
I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?
Click to expand...
Click to collapse
1.0.1 broke my read me functionality BEFORE I even rooted. That's why i've avoided it. My kids like using that.
Sent from my XDA app on my Nook Color
When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.
willywayne said:
When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.
Click to expand...
Click to collapse
mine was OTA. i hadn't even rooted it yet. i was just playing with the stock device and then it updated and the feature was gone. just kept erroring out and freezing up or pulling up the book but not reading.
Alright, I completely reset to stock (8 reboots and de-registered it). Checked the info and was back to 1.0.0. Tried the "read to me" function and it worked fine. Put it to sleep waited a few minutes woke it up and tried again with no problems. Side loaded a fresh download of the 1.0.1 update and let it update. Tried the "read to me" again and it worked fine. Put it to sleep and waited about 15 minutes and now it is broke again.
My wifes has had hers since Christmas too, updated it to 1.0.1 the same day as mine and hers still works perfectly.
I will be going to Best Buy to exchange mine for a new one in about ten minutes.
Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?
eyecrispy said:
Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?
Click to expand...
Click to collapse
I thought maybe you were on to something because I had sound turned off in a game. I turned it on in the game and it worked but still not in the "Read to Me". (1.0.1 update plus nootered)
I never could get the audio on Pandora to work but I have it on my phone so I never put much effort into it.
I just got back from Best Buy, updated my new NC to 1.0.1 and everything is working now, including Pandora. I will let it go for a couple days before I root it to make sure everything still works.
FWIW, I turned up my volume to nearly max and Read to Me was working. I wonder if it was a simple volume mistake or if somehow something was changed. I hope everyone else's problem is solved as well
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...
Not sure if this discussion has already happened.
I have noticed twice since rooting my nook (with 2.12.25) that it has randomly restores back to 1.0.0 (or seemingly).
The first time it was just sitting beside me and it did one of its un-commanded restarts. I noticed that it was reloading the original 1.0.0 version. I lost everything and the nook was unresponsive after finishing. I followed all the hard reset rules and then upgraded to 1.0.1. I then autorooted again and reinstalled all apps.
Last night it did it again while I was using it. I was reading a book and then went to check email. I got an error message something like "invalid authorization" and that it was reloading the base software. I let it do its thing and go through its reboots. I also let it automatically update to 1.0.1 before I touched it. I re-registered it. Now when it loads it doesn't show the normal rooted nook boot screens. When I go into extras I see only the stock apps plus the additional ones that the auto-nooter loads (everything else gone). I tries to get me to log into LogicPD Zoom (Google) but it fails to load.
Has anyone else seems this?
Is there a way to re-load or fix the nook color install without having to go through the complete wipe process?
Once I fix is there some setting we can change to prevent it from happening again?
Thanks
After nootering the nook, I proceeded to load clockwork mod and made a backup of the OS. Now when it auto restores, I can reinstall the backup from clockwork mod by holding both Power and the Nook Key for five seconds when powering on.
Still don't seem to know how to stop the auto restoring though
Mine restarts too, has since I rooted it. Thankfully, there is no data loss, just an inconvenience. If there were a log being kept (like in other OSs), I could at least go there to find out what is crashing it.
Acts like a low memory restart, but that isn't what it is.
TJD
Wanted to add that mine does this also. It has happened 3 times in 4 weeks. Thank god for ClockWork it is not to big a deal now to restore. I wish someone could figure this out tho.
Mine actually randomly boots up (I'll have it off, then hear it start up a few hours later). Not sure it's related, but thought I'd mention it in case it turns out to be.
Sent from my PC36100 using XDA App
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
straby187 said:
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
Click to expand...
Click to collapse
Except they're talking about the system restoring itself, not rebooting.
It has to reboot to restore. Thought if you fix the reboot problem it would help maybe not... My bad
I'm autonooted on 1.0.0 and have never had an ota restore or update.
Sent from my Nook Color
Have you guys made sure to rename the otacerts file after rooting?
There are several active threads on this. In my case it was a faulty power button. I went ahead and exchanged the unit. Replacement is 1.01 and feels like the case is sturdier. Might be imagining that. Check my other posts on the subject. Good luck.
Sent from my NC using XDA app
First of all it's working again so I'm not really looking for any help to get it running but still I thought this is worth mentioning
I wanted to import a .mobi book to Nexus 7. This book was sent to me by a friend and I wasn't completely sure what it was. Not even sure if a .mobi file could cause this. But here it goes:
I tried to import this ebook to Aldiko, turned out, it does not even find the file - so I've downloaded Moon Reader from Play Store which found the book and offered me to import it. While importing it the app froze and superuser showed me that "Shell" asked root permissions but was denied. Eventually the tablet itself froze. After a few minutes the message occured that Moon reader does not response and I chose to kill the app. Then the display turned black and the tablet seemed to have turned off.
After that point the tablet was not responsive anymore. No matter what I tried, it would not respond to anything. Battery was at 40% before but I connected it to the charger anyways. I've tried to boot up again and this time I got some disfigured weird glitches but nothing like a bootscreen. After some time it actually booted into Android (at that point it was an older PACman ROM). As soon as I've tried to unlock the screen the tablet made some weird noises (sounded like R2D2 ) and turned black again.
Again the only reaction to pressing the power button were some glitches...I left the device untouched for a few minutes and tried booting again, this time holding volume down button and it got me into download mode where I was able to choose recovery mode which then gave me the chance to restore a backup. After that it worked as if all the above never occured
However I've decided to flash cm10.2 nightly build then since I had my little issues with PACman on Nexus 4. Though I don't blame the ROM. But quite frankly I don't have the slightest idea why this happened, what caused it and what exactly this issue was.
So I just thought maybe someone encountered similar before and might be able to tell me, what all this was about.
Besides I've checked this .mobi file with virustotal.com and not one antivirus raised alarm. Still don't know what was inside that .mobi, but I don't really wanna try it on any other device
Anyone ever had this?