I was running CM7 n136 with nook tweaks (overclocked to 1300). My NC randomly rebooted (probably because I haven't quite nailed down my undervoltage settings) and when it came back it had me at the android start screen (touch the android to begin). I clicked through it and almost all my apps were gone; it was like I was starting CM7 for the first time. I had a handful of force closes too (they just popped up right away before I could click through the startup). Not a problem, I thought, and I went to recover with ClockworkMod (3.2.0.1). Restoring doesn't work and I end up at the same screen. I've tried restoring two different restore points and neither works.
Any ideas how to get around this?
Thanks for all your help!
Related
I was running CM7 7.02 from emmc with Dalingrin's 4/24/11 OC kernel, and was very happy with it. However, I got distracted by shiney... Rom manager gave me a pop up saying 7.03 was available, which it hadn't done in the past, so I figured, why not give it a shot?
I ran a full backup, installed the update, booted... and all my apps were gone. It was a fresh install instead of an install over my existing 7.02 like I would have gotten if I just booted from my CWM boot SD card and flashed. Well, crappy, but I have my backup, right? Still, might as well try the OC kernel and see how it runs real quick... oh, won't boot after the OC kernel. huh.
So I boot to recovery, and clear cache, and restore my backup.
Everything looks perfect. Back to my customized layouts... wait, where is my Honeycomb style bottom status bar? I'm back to the default look/feel. Ok, I can fix that... wait, why isn't my N button working? I've gone into ADW settings, selected several options for the "home button" functionality, rebooted, nothing works. I've got everything except a working N button. Why?
The only time it has worked is ONCE right after I installed a second home launcher, flashed 7.02 over 7.02, rebooted, and hit the button. It popped up and asked me which of the two launchers I wanted as default. After that, it hasn't responded.
Anyone have any idea what I did or what I can do to fix this? I'm fine if I have to format and start from scratch, I just would rather not since I'm stuck in an airport and waiting on a flight home, so I'd rather be reading/watching movies/playing music instead of tinkering... if it's something simple to fix, ya know?
That post just made me mental!
Sent from my Nexus S using XDA Premium App
I'm glad I could provide some amusement?
I ended up wiping data and system, installing 7.02, gapps, and 4/24/11, clearing cache and dalvik, then booting up and then refreshed my apps and data from Titanium. Everything worked great for a while and then the N button stopped again. No idea what happened. I've been working 16+ hour days for 7 days straight and can't think straight. On the up side, I was able to finish watching my movie on the flight home after my flight was delayed for 4 hours.
I need sleep. I also need to figure out why my button keeps dying. Works perfectly in CWM and to wake the device up, just not for it's intended purpose.
Had a similar problem with the N button not working with the 04/24 kernel. However it got working after a reboot...
One thing you could try is to use the 04/04 kernel instead. Might be a OC related issue.
I have been running the kanged builds of CM9 for a while, but it began to get bogged down recently and would freeze up almost daily forcing a hard shutdown and reboot.
Sometime yesterday, it began to boot only into recovery no matter what option I tried in the Cyanoboot menu. From there I tried a factory reset and wipe dalvik to hopefully get back into CM9 and here's where the strangeness really kicked off.
Clockwork (which was running off emmc) would freeze in the middle of the factory reset just like it would when CM9 was running (the graphics would degrade slightly upon inspection of the screen).
So, I grabbed my old sdcard with clockwork recovery on it to boot from sd, and I run into the same problem again. Freezing before a wipe, factory reset, or install from sd can complete.
Now, after each failed attempt in clockwork (sd and emmc) it sticks at a backlit black screen and after a hard shutdown refuses to boot (sd or emmc) for about an hour, only to repeat the madness again.
Does anyone have any ideas what I can try from here or familiar with a similar situation?
My sd clockwork version is 3.2.something and I've also tried 3.0.1.something.
UPDATE: For reasons unknown, my Nook seems to be booting regularly as of this morning. However, I am still unable to get a successful flash out of any rom. The closest I've gotten to success is stuck in a boot loop. I think from here I'll likely be able to figure it out, but just as before...
Any help is welcome and appreciated!
I had the same problem with the black screen when trying to install different roms on mine. I just kept clicking the power button and after a few minutes it would kick back on every time.
There is an entire thread specifically on this
http://forum.xda-developers.com/showthread.php?t=949699
As far as CM9 I can't help you much there. I would just try to install a different rom, and hope that works.
Thanks!
I had seen that thread, but I thought my experience was a different; either way, I've managed past that problem using a method similar to yours.
If this helps any, I have been trying to to 7.2 RC1 for a while as well, but it will not get me any further than the stuck boot screen same as the CM9.
Have you tried to follow the tread on returning it to stock ?? I would reformat and repartition it and return it to stock ... then make sure it runs. After that I would try to reinstall the new roms ...
Just my 2 cents
Tinpau
Hey guys, I have been having some issues with this. I'm on Mirage Kang 7.2. Usually, Mirage is wonderful but something went wrong today. I was in the Play Store on my Nook updating four apps (like EzPDF, Go Launcher, not sure it matters though...). Anyways, it froze so I force shut off the device but when I went to turn it back on nothing happened, it just went to the infamous black screen. I did some searching and people said the boot partition is corrupted.
I tried updating the ROM to the latest release to see if anything would happen to no avail. I tried plugging the Nook into my computer and turning it on but that didn't work either. The only ways I could find to fix it was to revert back to stock. Does anyone know a way out of it while keeping my apps, data, etc?
http://forum.xda-developers.com/showthread.php?t=949699
Dummies Guide to Fixing 'My Nook Won't Boot
well here we go again. i push installed "gl tron" from the play store on my pc to my tablet. it showed it installed successfully. i then went to play "samurais vs zombies" and it crashed as it sometimes does for me. so i went to restart my tablet and now its stuck on the android logo with gears moving. last time it did this i tried random fixes and just made it worse and practically bricked it and some good guys here helped me get it up and running again. is there any easy fix for this not to lose all my data or make the issue worse? if not, what should i do to get it to work even if i lose my data? from what i understood last time was i had an issue in the data/media directory causing the issue. is that the case most likely this time? was it from the push install as i suspect, because it is very similar to what happened last time? i never got to do a proper cwm backup of my rom and data as i got an error and never fiddled with it again. some ideas or pointing in the right direction would be very helpful. i also would like info on how this could happen and how android works in order to avoid this in the future. thanks so much.
specs:
acer a500
skrilax_cz bootloader v8
cwm 5.5.0
lightspeed 4.8
i also have my cpuid and sbk info saved.
Can you go to recovery. "clean up tab" then reinstall your ROM?
This won't touch your data and - may - get you running again.
raotheconqueror said:
well here we go again. i push installed "gl tron" from the play store on my pc to my tablet. it showed it installed successfully. i then went to play "samurais vs zombies" and it crashed as it sometimes does for me. so i went to restart my tablet and now its stuck on the android logo with gears moving. last time it did this i tried random fixes and just made it worse and practically bricked it and some good guys here helped me get it up and running again. is there any easy fix for this not to lose all my data or make the issue worse? if not, what should i do to get it to work even if i lose my data? from what i understood last time was i had an issue in the data/media directory causing the issue. is that the case most likely this time? was it from the push install as i suspect, because it is very similar to what happened last time? i never got to do a proper cwm backup of my rom and data as i got an error and never fiddled with it again. some ideas or pointing in the right direction would be very helpful. i also would like info on how this could happen and how android works in order to avoid this in the future. thanks so much.
specs:
acer a500
skrilax_cz bootloader v8
cwm 5.5.0
lightspeed 4.8
i also have my cpuid and sbk info saved.
Click to expand...
Click to collapse
i went to recovery but could not find a "clean up" selection. am i missing something? last time this happened, i tried to do a factory reset and all i got afterward was a droid with exclamation mark on his chest. from what i understood is that my a500 did not have a proper recovery partition which left my tablet nearly bricked. that's what i surmised from the info i read. thanks ta-wan.
wiped data/media and it set me back to honeycomb. i rebooted into recovery and installed lightspeed 4.8. lost all data but whatevs, my fault for not backing up. wont happen to me again...
Hi all. I used to mess with my Nook Color a lot around a year and a half ago but recently was just using it to read and occasionally browse. I'm 99% sure I was working with just a nook which was used with manual nooter, so that I had the Google Play store and Zeam launcher with stock B&N as well. I was having issues with things "not being able to update" so I tried to mess around, only realizing too late that I wasn't really interested in cm10 and wanted to stick with zeam. Since then I've been trying to get back to how I started but I'm failing miserably. I've so far tried wiping/factory resetting my device. Installing cm7 from zip, resetting everything using the guide here and installing 1-4-1 cam oc zip from here and still I fail. I can get into the set up screen, but when the device will not find any wifi signal and then freeze without allowing me to type it in under "other". Honestly I'm not sure what else to do now. I just want my nooted device back -__-.
Please let me know if I can submit any more information that can help solve this problem. Thank you for your time.
I'm literally infinitely stuck staring at this screen.
Managed to fix everything. Used section A15. Enjoy anyone who ran into similar trouble.