I just noticed that my rooted Nook ST that I'd left on the side for a few days had changed it's display to an 'Install failed' screen
telling me to power off/on.
It didn't say what/when/how or offer any suggestion where to look.
I'm just wondering if they started trying to push the rumoured update.
Related
I know I might have to pull the battery....I downloaded ROM manager in the hopes that it would be an easier way than spending a couple hours upgrading to CM 6 from my older version of CM (I don't recall which version it was).
DLed CM6 via ROM Manager as well as the google apps. It asked to reboot to complete install, I chose not to wipe data, and currently it's stuck on a screen showing the date as Sept 2 2008 and with stripes of red, green, blue, and white going across the screen. Display is not changing, nor does it seem do be responding to key presses.
Advice please? Anyone else gone through this?
[EDIT]
Pulled the battery, it was stuck in a boot loop. I started walking to the T-Mobile store to get a Samsung Galaxy. After a while in the store, I heard a text message notification from my phone. The boot loop had damn near killed the battery, but it booted. Now going to try it the right way by following the Froyo update guide that I was in too much of a hurry to see earlier.
Still want a Galaxy though
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
rjl2001 said:
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
Click to expand...
Click to collapse
I had a similar problem, or at least similar symptoms (but it was caused by an ID-10-T error) and I ended up just booting into recovery and restoring my last nandroid (oddly enough this nandroid didn't include any of the apps I had installed and it has been a while since my last TiBa so I have a lot of "manual recovery" to take care of).
So I would go ahead and try to restore. Sorry I can't be more help.
Drachen, thanks for the reply. I'll take any advice or information anyone has. I would definitely be happy to restore, losing all my apps is better than having a bricked NookColor lying around.
Do you know where I can find directions on how to do a restore? I'm not too technical when it comes to this stuff, I've just rooted it a couple different times because I had some clear and precise step by step instructions of exactly how to do so. I know I'm unable to boot into the recovery mode like I was able to do before when I was first installing Phiremod. Also since it has been a couple months a lot of the steps and details are not fresh in my mind.
There was no version7 2 months ago.
Sent from Nook Color on Phiremod 6.3 @1.3Ghz
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
rjl2001 said:
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
Click to expand...
Click to collapse
Download the phiremod zip here, put it on the root of your SD card, and then boot into recovery>install zip from sd card>choose zip from sd card>Phiremod zip.
Finally figured it out after a few weeks of a Nook paperweight and hours of googling and trying different methods. What wound up working for me was totally restoring it back to stock. This website "Maurice Mongeon - Nook Color: Recover Any Bricked Device/return to stock" had great step by step directions on how to do it, and it was actually easy. Now I just need to figure out if it is worth rooting again, or would it just fail out of the blue like it did this time?? Anyways, thanks for the help.
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
kitkat disaster
metar0n said:
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
Click to expand...
Click to collapse
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
kombochekenyere said:
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
Click to expand...
Click to collapse
Bringing this old post up as I just now encountered this on my AT&T LG G2. It occurred when I was using Google Maps which then crashed and caused everything to freeze. Upon reboot, I get the exact same issues as stated above. What was the outcome for you guys? Did you end up doing a hard reset?
Everything appears to be functioning with the exception of above. I'm suspecting a software issue with the home launcher as the soft keys are responsive but the Home one. The Notification Bar lags when trying to drag it down, but none of the notifications are functioning. I also noticed a significant amount of lag. Prior to the "crash" my phone was flawless with no lag for the past 10 months. I absolutely have no clue what just happened...
Perhaps someone has experienced this...
Since I saw a couple of day ago that the official update was up, I have been checking the software update on the phone. Finally it came down today, and to my disappointment, it seems that it will not download.
On the blue and white software update screen (I can't get a screenshot to this computer from the phone), it tells me that an update is available, when I click to download, the same screen shows "Update available" in caps, and right under "Verification failed..."
What verification? I have never seen this error on this phone or any other Android phone I have ever owned (rooted or not). Besides leaving it alone and/or repeatedly press "check for update" what else can I do?
Already restarted a few times, just in case.
Fixed. Nothing a full reset wouldn't cure.
Now back to restore apps.
hello,
my note 4 has been working pretty good up until maybe a week ago, and then it started to randomly turn off and sometimes it would re-boot. other times pushing the home button it wouldnt awake, even thou the blue led lights was flashing like i had a message or notification, pushing any button would not awaken it, pushing and holding the power button would not turn it off, prompting me to pull the battery out. put the battery back in, push and hold the power button had no effect, having to volume down, home button, and push power button, and then volume down when prompted would boot the phone.
many times the phone would freeze, and pop up window would say X app has stopped working do you want to shut it down?, play store, samsung ui, various apps.
so, i googled my symptons, several suggestions suggested remove google play updates and then reinstall and update everything, that was last night. it casually freezed more and then it seemed to sort of work better last night and this morning. and just a few minutes ago, i had a new pop up screen "Runtime Error bad argument#1 to 'abs' (number expected, got nil)" as google is one of my loyal and usually helpful friends i asked it, to my surprise i found basically zilch. putting "Runtime Error bad argument#1 to 'abs'" inside quotation marks was limiting results, it didnt look like other phone users had had similar troubles.
i did see this hit "http://geco.mines.edu/guide/Run-Time_Error_Messages.html" lightly scanning over it made me think i was not looking in the correct place. as the word "intel" was mentioned a few times.
i found another page "https://github.com/layeh/gopher-luar/issues/1" as the title is similar to my issue "bad argument #1 to <function name> (userdata expected, got string)"
those with far more of an understanding of android and code, please assist...
thank you
View attachment 4419367
More and unusual pop ups
nothing?
seems my phone has signed me out of google play
and has unrooted itself
many times the "Samsung UI has stopped working" pops up
i was hoping those with much more knowledge would have offered some suggestions.
i will back up all my data (in several different ways)
root my phone (again)
do a system re-format
and then re-install my apps and crap
crossing my fingers that that is all it needs... cause frankly i have no idea what, how, or why it recently crapped out. i suspect it was one of my apps, as the phone was working very well for several years, and within the last few days its all freezes and hangs, and occasionally crashes and reboots..
This morning I woke to find my phone looking like this