Database Develop

NC boot up problem

I flash my NC with CM7.0, now everything seems working fine, but I found there are sometime(not always) it stuck at boot animation, after touch the future of reading, it just stuck there.
this happens alot when I turn it off for long time, I am not sure what is the problem seems it doesn't happen every time.

I am having the same problem, but noticed that if i take the SD card out the NC starts normally. so i am figuring somthing is left on there from the install that is causing the hang up.... or maybe it is something else and i am too naive to realize what it is. Any help would be appreciated.
Using CM7.0 stable.

I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it

ikryptic said:
I tried to install CM7 on my nook color and i didnt follow the proper method and instead saved the CM7 file to the root of my sd card and installed the zip through clockworkrecovery without wiping or cache and now im stuck at the android boot screen. It isnt the CM7 skateboard android boot but rather the plain android root boot screen. If anyone could help it would be helpful thank you! IM crying right now about it
Click to expand...
Click to collapse
Hold power+n for 10 seconds to turn off
Clockwork bootable sd card, wipe system/data/cache (not boot), install cm7 from zip, install gapps from zip.
This is for a clean fresh install.
I made the same mistake yesterday going from stock nook to cm7 on nook #3 (so used to flashing nightlies on the other 2 i forgot to wipe system first)

[Q] Trouble updating to CM10 3/4

I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!

rg2 said:
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
Click to expand...
Click to collapse
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.

You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.

chicle_11 said:
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
Click to expand...
Click to collapse
Thanks for the advice. Going to have to do this I guess.
sstar said:
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
Click to expand...
Click to collapse
I used them both, although I generally use TWRP. I got rid of CWM and tried again to no avail. Thanks for the reply.

Running ACMEuninstall and reinstalling did nothing to fix the problem. Still have "damaged SD card" prompt upon boot, still have broken wallpaper functionality as well as crippled launcher functionality. Any ideas?

How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.

sstar said:
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
Click to expand...
Click to collapse
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!

reset webos
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.

rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2

johna2u said:
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
Click to expand...
Click to collapse
Thanks for the tip. Will have to try this.
sstar said:
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help

rg2 said:
Thanks for the tip. Will have to try this.
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
Click to expand...
Click to collapse
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3

sstar said:
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
Click to expand...
Click to collapse
Thank you for the suggestion! I will try this since I seem to be cursed using the JCSullins build :/

In need of some help.

Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.

Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium

darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.

DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527

Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app

Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.

I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app

For recent custom roms, you must use a CWM with an unlocked bootloader.

[Q] Bootloop - Samsung Galaxy S5830 B with CM10.1.6

Hello all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.

offRiggs said:
Hello all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Try doing a factory reset, it might solve it. Do post the result. Hope I Helped

Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.

I also noticed this problem on my Ace S5830 and I have no idea why. I thought I was the only one who is having this problem. If anyone knows why, please tell.
Sent from my GT-S5830 using Tapatalk

offRiggs said:
Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
When you are using CM10.1 by Mardon, NEVER WIPE DATA/FACTORY RESET!! ...You should fix your problem flashing again the rom
The ROMs are already preconfigured and when you wipe data/factory reset, all those settings will be lost and the device won't be able to boot successfully again

Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.

offRiggs said:
Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Ok, so just follow the correct steps to re-flash CM10.1

[Q] Nook HD+ mistake

I accidentally completely wiped my Nook in recovery without installing any other rom, because cm 11 had a problem installing. And then I turned it off. It doesn't seem to turn on at all. However, I can connect it to my PC and it reads the OMAP4770. Any way I can bring this tablet back? Or is it gone?
Also, I have tried every reset option I've seen online, like power and/or home button for amounts of time. I believe that since I lost the system files it won't start up.

Why don't you just follow the instructions here http://forum.xda-developers.com/showthread.php?t=2317500 and make yourself a sd recovery and take it from there?
Don't worry you are not lost

It won't boot at all, let alone into recovery. Of course I did try to boot into recovery since that's what I used to wipe it. Did not work.
I completely erased everything in the tablet's memory, including /system. I could be wrong but I think that's why it won't show up with anything when it turns on. No light or logo.

gtasmy said:
It won't boot at all, let alone into recovery. Of course I did try to boot into recovery since that's what I used to wipe it. Did not work.
I completely erased everything in the tablet's memory, including /system. I could be wrong but I thing that's why it won't show up with anything when it turns on. No light or logo.
Click to expand...
Click to collapse
It won't turn on unless you have a bootable SD inserted. Go to my HD/HD+ CWM thread linked in my signature and make one per item 1a there
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
It won't turn on unless you have a bootable SD inserted. Go to my HD/HD+ CWM thread linked in my signature and make one per item 1a there
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I know that. But nothing boots now. I wiped it originally with my bootable sd. It won't load that anymore or anything else...

OK just tried different Bootable with CWM instead of TWRP and it booted up to it.
Thanks for the help people.
Now I'm still having issues with flashing CM 11 on it. Status 7 error.
I think that's because I don't have stock installed right?
Anyone know of a CM 11 zip for HD Plus that won't check for stock first?

gtasmy said:
OK just tried different Bootable with CWM instead of TWRP and it booted up to it.
Thanks for the help people.
Now I'm still having issues with flashing CM 11 on it. Status 7 error.
I think that's because I don't have stock installed right?
Anyone know of a CM 11 zip for HD Plus that won't check for stock first?
Click to expand...
Click to collapse
No, that status 7 error is because CM11 needs version 6045 or newer CWM. Go to the dummies thread linked in my signature and follow post 7 there.
Sent from my BN NookHD+ using XDA Premium HD app

Thanks, upgraded from CWM 6028 to 6046 and it worked perfectly.
Thank you for the help and saving my tablet enough to let me breath new life into it.