So I have had Cyangenmod 10 installed for several months now and it's been working fine until I would say the last 2 weeks. Now, sometimes it will lock up or slow down and when I restart it, it will get stuck on the cyangenmod logo and never fully boot. After several restarts, I can sometimes get in and all is fine. But today, I have rebooted the Nook Tablet about 10 times now and the Cyangenmod logo will spin for a bit, then stop and then spin and then stop, etc but I can never get in
Ideally, I don't want to restore as I have a number of things on the Tablet that I want to keep. Any suggestions before going that route?
Try going into recovery and wiping cache and dalvik-cache, and then reboot. When oddball things happen, this should be your first trouble shooting step.
Good luck
Sent with my Dinc4G
tried the wipes and still gets stuck on the cyangenmod logo..just spins and stops for a bit, then spins some more
any other ideas
Titanium backup the apps/data you want to keep then full wipe - data/factory reset.
Sent with my Dinc4G
can't do titanium backup if I cant even get passed the cyangenmod logo
Ya good point.
You may have to reflash the rom (or another rom) after a full wipe. I know you are trying to avoid this, but you may not have a choice. You should, however be able to restore your data through advance restore in recovery (make sure you do a backup first though). And it is possible something you put on your nt is causing this - not likely but possible.
Had you done any mods or such on you nt prior to this?
Edit - Another thought too, try flashing the latest update of cm10.1, Just wipe cache and dalvik cache. Flash over the top your current build.
Good luck
Sent with my Dinc4G
Related
OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!
I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk
iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.
I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
downwardzspiral said:
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Maybe give flashtool a go, just flash one of the stock firmwares.
Already tried that. As stated before, it gets to the first screen which prompts me to chose a language, and then immediately reboots
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
how did you solve your problem? i'm in the same situation
irafcummings said:
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
Click to expand...
Click to collapse
what information did you recover?the info might mismatch because the roms differ.Also try flashing a new recovery like cwm or AmonRa
Also if you restored the system directory when you did a restore, its like building two houses on top of each other, its 2 full houses, so both will crash because of the pressure. It probably just installed the system restore on top of the update, did you do a data wipe? Furthermore, if you look in the folder with your backup data, your should only restore the data portion rather than doing a full phone restore! so in the future, do a full wipe before reporting, and also, store the backup in a remote area, but put your data folder back in the original location and install it!
Sent from my PG86100 using XDA App
I ended up flashing CWR via an SBF file. It seemed like CWR just got corrupted somehow. From that point, I was able to restore from the nandroid that I created prior to updating. Hope that helps.
Not...really sure what I did wrong, but I would love some help here. I wanted to install Kang with Cornerstone from the old Alpha .6. Booted into recovery, wipe data, wipe cache, flash, flash Gapps, boom. Works fine at first. After playing around with it, I decide I don't like how it tiles apps, so I switch to the latest kang build (2012 02 29), same thing. Wipe, flash aaaand...bootloop. I go back, attempt to flash again, perhaps foolishly, and it now restarts recovery when it gets about halfway through.
I then try to restore to the backup I had made a few hours prior, MD5 sum error. Note that I had about 5 gigs free at the time. I try an older backup I had, same thing. If its worth anything, the backup thinks it was made on march 1st, which hasn't happened yet where I am.
So now I'm completely locked out of android. Thankfully, I can at least boot back to WebOS, so its not completely fried. Is there something I can do here to fix this, or am without a paddle here? I'm thinking it might be fixed if I completely remove android and redo the whole process, but is there anything else I can do first?
Will reward help with e-hugs
Semianonymous said:
Not...really sure what I did wrong, but I would love some help here. I wanted to install Kang with Cornerstone from the old Alpha .6. Booted into recovery, wipe data, wipe cache, flash, flash Gapps, boom. Works fine at first. After playing around with it, I decide I don't like how it tiles apps, so I switch to the latest kang build (2012 02 29), same thing. Wipe, flash aaaand...bootloop. I go back, attempt to flash again, perhaps foolishly, and it now restarts recovery when it gets about halfway through.
I then try to restore to the backup I had made a few hours prior, MD5 sum error. Note that I had about 5 gigs free at the time. I try an older backup I had, same thing. If its worth anything, the backup thinks it was made on march 1st, which hasn't happened yet where I am.
So now I'm completely locked out of android. Thankfully, I can at least boot back to WebOS, so its not completely fried. Is there something I can do here to fix this, or am without a paddle here? I'm thinking it might be fixed if I completely remove android and redo the whole process, but is there anything else I can do first?
Will reward help with e-hugs
Click to expand...
Click to collapse
Did you use ACME uninstaller?
Your best bet is to wipe everything, and reinstall. Hell, while you're at it, if it were me I'd check for WebOS updates first.
It'll be fine after a complete reinstall, but I think that's not only your best option but just about your only one.
Unrelated, but FWIW:
For anyone who's ever said, "I wish I could just get rid of WebOS altogether, so I could have that extra space". This situation is why we don't want to even be able to do that.
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
theraker007 said:
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
Click to expand...
Click to collapse
i would restore my nandroid and see if all is well, if so, try a wipe of cache, dalvic cache, and factory reset, then try flashing the rom, if that fails too, try a different rom.
It seems based on the official thread that many users experienced the same problem flashing to 4.0 from stock.. Have to go to 3.0 first and then 4.0 (see the thread I linked, last couple of pages)...
Posting it here in case I wasn't the only one who didn't read the whole thread.