Unfortunately, System UI has stopped. - Nook HD, HD+ Q&A, Help & Troubleshooting

Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.

exfed2002 said:
Just installed the latest update (0621), and now when I try to do anything to open the UI from the booted splash screen (lock image) I get the message above.
I cannot shutdown or reboot to go back to an earlier version, I can only power off with the power switch.
If I try to use the reboot option from the splash screen, the recovery option has disappeared.
Starting the unit again produces the same result.
My latest boot got me the animated logo then presented a solid light blue screen.
How do I get it back so I can install the earlier build that was working while you fix this problem.
Right now the unit is useless, absent making up a new SD card. I have lots of stuff on the current card so would prefer not to do this.
This is somewhat similar to the clock has stopped warning on some earlier builds, but these did not render the unit inert.
Click to expand...
Click to collapse
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Developer has said he will fix this in next build. Look at his thread.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.

exfed2002 said:
And that is going to help how?
Did you read my post?
The unit is unable to get past the splash screen with the lock icon. I can't even regress to a working build.
Click to expand...
Click to collapse
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium

leapinlar said:
Just boot to recovery, wipe data and reflash. But you will lose apps and settings, not much you can do about that.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.

exfed2002 said:
I wasn't able to do that as I had to shutdown, that was the only option.
In some way, punching the power key and home key in some sequence, suddenly the recovery menu appeared. Don't ask me how.
I was able to go back to the 0615 build, and from there do the upgrade to the 0623 build and now it's working.
But I have no idea how I got the revery menu to come up when all else failed.
Click to expand...
Click to collapse
Holding power + n key on boot takes you to recovery.
Sent from my Nook HD+ running CM10.1 on emmc.

System ui stopped Nook
I encountered this problem as well. Thanks to your posts, I started trying things before the flash screen locked. I downloaded a Nook app and the error message and display screen errors went away. I hope this works for someone else also..

Related

[Help]Milestone keeps repeating android boot!

So right now, my phone keeps on getting stuck at the 'android' word bootscreen. It keeps repeating and seems to go on forever! Someone please help me! I heard its due to rooting! Can anyone confirm this?
What did you do? I tried once to install aps 2 card and the phone stood in android screen about 20 min
Anyway if it doesn't start. Flash new android: nand restore or sbf
.
Sent from my Milestone using Tapatalk
Finally somebody replied back. Its been going on for days, I've removed the battery, placed it back, same thing.
Also, sorry but I have no idea how to flash something. How do I do it? And it doesn't even go past it.
I should spend on time in this sub-forum.
If you have flash a custom ROM then just reflash it or try another ROM.
It's highly, highly unlikely that your phone it breaked so don't worry about.
I have never flashed a custom rom. I don't even know how to flash in the first place.
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
under18 said:
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
Click to expand...
Click to collapse
Yep, I can go into it. But I checked, and can't find how to install a vulnerable recovery. Any help?
My site is down atm, but this may help;
http://forum.xda-developers.com/showthread.php?t=932196
shut down phone ->hold down hard keyboard x key and power button->when M logo appears release power button but keep pressing x key until recovery mode shows up
there is an option for clearing data/factory reset
you'll loose everything but it propably fix the problem
Including my contacts?
ray243 said:
Including my contacts?
Click to expand...
Click to collapse
your contacts if you have chosen it will be at your Gmail account and they will be restored.

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

[Q] Nook HD+ CM10.1 Boot Loop

Hello,
Earlier today i successfully installed CM10.1 on my new Nook HD+ tablet. After setting up CM10.1 and installing some basic apps i restarted the Nook and it is now stuck in a loop at the Cyanogenmod start up screen. Any suggestions on how to fix this?
Thanks guys!
I had this same issue. I made a titanium backup of everything, and then reinstalled cwm, cm 10.1, and emmc ovation. I used titanium to restore and now it resets just fine.
Sent from my BN NookHD+ using Tapatalk 2
Same here...
I had the same issue. I went in and cleared the cache then reboot and it was fine. My issue now is it'll randomly reboot on its own and sit at the Cyanogen circle boot up but won't boot up. Anyone else?
I booted into recovery and wiped dalvik cache and the othe cache and it booted fin out of recovery but when i would attempt to reboot it normally it would still be stuck in a boot loop...I just factory reset it and it seems to be working fine now *fingers crossed*!
still no go...
I tried that too and it still reboot randomly. Thought that was fixed with latest version
I had the same problem. This is what I did. In the recovery menu I did a wipe / factory reset. Then installed CM and Google apps again. After that I did another wipe / factory reset. After that I rebooted. No more random reboots and no more boot loops. I hope this helps.
trouble restart
Just got a Nook HD+ on the 26. installed CM10.1. every time I turn off or restart the Nook, For the first 3 times, it would stuck at the fast spinning CM logo. I would have to long press the Power button to turn it off, then turn it back on. For the 4th time it would boot without any problem. same thing with boot into recovery, the first 3 times it would ignore my N+down press, only on the 4th attempt. Not sure why, but that's what I found out. I dont see any random reboot yet. Have not try to reinstall CM10.1. Will do that when I have more time. Anyone else with a newly bought Nook care to sound in?
Very similar problems for me, though I don't know if it's exactly every fourth time that it boots properly.
I did a factory reset, re-flashed everything, and it worked perfectly for a couple of days. Then yesterday, a random reboot, and it got stuck at the CM boot animation. It rebooted properly on the second or third try. I just rebooted it manually, and it worked fine again.
I really like this tablet, but I'm seriously thinking of returning it because of this problem. It seems like it could become completely unusable if it gets worse.
CM 10.1 Boot Loop CWM non responsive
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
selwynbaptiste said:
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
Click to expand...
Click to collapse
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Reinstalled CWM and CM 10.1
leapinlar said:
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
In did install both the CWM and CM 10.1 the first time. It booted and rebooted for days without a problem. I believe b what happened was error. I had the alarm set to wake me and half asleep tried to turn it off while the groovy cover was shut by holding down the power button. I may have held down more keys then I thought in a sequence that deleted something that caused the Boot to hang. After that there was no way for me to enter the CWM. The command sequence that would normally send me to CWM sent me to nook factory reset. I noticed that there is a small glitch between hibernate and the b alarm. Holding down the power key to get it to shutdown can cause it enter CWM from time to time.
When I reinstalled everything funny thing is my screen lock settings and background selection (I previously downloaded) stayed along with my user profile. That leads me to believe that everything was in tact on the internal storage. Google play backed up and reinstalled all my apps automatically once I signed in:good:. I'm taking your advice and buying a 4G SD to keep the CMW boot image on with the latest CM. Thanks for your help.
Distorted Boot Animation
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Josmar1993 said:
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Click to expand...
Click to collapse
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks for the reply
leapinlar said:
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
"I guess in order for one to gain, one must lose something." LOL
In meantime I'll just disable the boot animation with Rom Toolbox.
Hopefully it get's fixed in later updates without any lost.
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
nkca6384 said:
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
Click to expand...
Click to collapse
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
josim said:
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
Click to expand...
Click to collapse
I have had the same problem in this thread as well (reboots stuck at cyanogenmod logo). I have been wiping the dalvik cache every time (figured it out on my own) and can confirm it works but you do have to do it at every boot (or perhaps after you change wallpaper, not sure).
I got tired of it happening so i google'd the issue and found this thread; mine is stuck right now too (and also out of battery, lol), but once I charge it, wipe dalvik and boot into android I will try the "quick render" trick and see if that fixes the boot problem to begin with.
Edit: I can confirm that disabling quick render has fixed the need to do a dalvik wipe every reboot.
Question
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Tinyneustra said:
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Click to expand...
Click to collapse
I don't know if the color+ has sdcard recovery but if it does that would be the way to go except for...
The other thing is that if you had put on a custom recovery then holding what ever buttons to go to it could allow you to fix it. Or waiting until 8 reboots or whatever if its the same as the nook hd+.
I think there may also be additional stuff that can be tried on the nook logo screen via various button presses as well but don't have any knowledge about that especially for the color+

[Q] [HELP!] Cannot update, cannot boot into recovery!

I installed cyanogenmod 10.2 nightly 20130824 accidentally, thinking that it was another 10.1 update (which by then was pretty stable), and realized that i made a big mistake: tonnes of bugs (focal, screen elements blacking out, play store not working).
But when i tried to boot into recovery to restore my clockworkmod full back up (which i do almost everytime i update CM), the "Galaxy Note N7000" boot screen comes up, and then a black screen. I can still boot back into the normal boot, but the tonnes of bugs just annoys me sooo much.
(i've tried to boot into recovery many times, to no avail)
Then, i tried to update it. I figured a newer version should at least be slightly more stable.
But updating cyanogenmod requires the phone to boot into recovery.
soooo fk.
Also when i try to boot into download mode, a screen showing an android icon and Downloading Do Not Turn Off Target pops out.
So after some google searches which didnt help, i came here to xda devs hoping you smart people could help me with this predicament.
Please tell me, has anyone experienced this problem on any phone and do you have any idea what to do?
It's a known bug with cm10.2. Follow this thread, just install phillz kernel to give you recovery, then you can flash cm10.1.
http://forum.xda-developers.com/showthread.php?p=45041491
Sent from my GT-N7000 using XDA Premium 4 mobile app

Help !! - bootloader suddenly got locked, no more recovery

I have had an unlocked Nexus 6 running TWRP and custom rom with no problems at all. Today when I tried to boot into recovery I got the stock screen instead of TWRP. At bottom it says 'Device is locked status code 0'. When I go into barcodes I see a date of 1-1-1970. Also see a 'unable to load partition table error'.
Rebooting into my current rom (Pure Nexus) works fine if I power off and restart. So how did this happen and what do I do next? I did absolutely nothing recently, had no errors in phone usage. Just wanted to update the rom and now this.
Is it a secondhand phone? Did someone remote lock it with Android device manager or W/e?
Sent from my Nexus 6 using Tapatalk
ECrispy said:
I have had an unlocked Nexus 6 running TWRP and custom rom with no problems at all. Today when I tried to boot into recovery I got the stock screen instead of TWRP. At bottom it says 'Device is locked status code 0'. When I go into barcodes I see a date of 1-1-1970. Also see a 'unable to load partition table error'.
Rebooting into my current rom (Pure Nexus) works fine if I power off and restart. So how did this happen and what do I do next? I did absolutely nothing recently, had no errors in phone usage. Just wanted to update the rom and now this.
Click to expand...
Click to collapse
I think you have a hardware problem, and the date being set to the beginning of the Unix clock is a dead giveaway. Where you still have a ROM, you have something you can try. I assume you have OEM Unlock enabled, so connect your Nexus to the PC and try unlocking the bootloader. If it unlocks, then try flashing TWRP. If it doesn't work, pray you still have a warranty. If you do, contact Motorola and set up a RMA through them.
As to how this happened, there's no way to tell from here. But it's not the first time it's happened to someone on this forum. The last time it happened, they had no OS and no recovery to work with, meaning a brick.
EeyoreSyndrome said:
Is it a secondhand phone? Did someone remote lock it with Android device manager or W/e?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No it is a new phone I bought in Oct, no one else has access to it.
How did you try booting into recovery? Through an app or roms power menu? Or by pressing power and volume down from a powered down state to get into bootloader and then go into recovery?
I've seen something similar a couple of times when I've tried booting into recovery from an app. Scared the **** out of me the first time, but I just needed to power off and boot up with the button combination instead.

Categories

Resources