Related
my nook is stuck on this boot screen any one wants to help me? here is the image
I would suggest you will need to provide more details about how you got to this state to get folk to help you -
what rom are you running?
what were you doing just prior to this? etc etc
In any event, maybe doing one of the following, depending on what state you want the nook end up at, might help -
install CM7 - http://forum.xda-developers.com/showthread.php?t=1030227
restore to stock - http://forum.xda-developers.com/showthread.php?t=914690
Cheers,
frogger55 said:
I would suggest you will need to provide more details about how you got to this state to get folk to help you -
what rom are you running?
what were you doing just prior to this? etc etc
In any event, maybe doing one of the following, depending on what state you want the nook end up at, might help -
install CM7 - http://forum.xda-developers.com/showthread.php?t=1030227
restore to stock - http://forum.xda-developers.com/showthread.php?t=914690
Cheers,
Click to expand...
Click to collapse
cm tried flashing another but got stuck on this screen tried the factory reset but gives me an error and it wont boot into sdcard
i do get the touch something screen
I've got stuck in this "Android" screen when I tried to update my existing CM7. This is what I've done.
1. Boot to recovery.
2. Wipe cache
3. Install the update from SD and choose the CM7 file and google apps
4. Wipe data/factory
5. Format or insert a new sd before re-booting.
I encounter the same error on the first reboot. Booting up the second time solved it. It does hang at the CM logo for bout 5 min on the second boot.
artojeda1988 said:
i do get the touch something screen
Click to expand...
Click to collapse
You shouldn't be getting a touch anything screen depending on what CM7 file you are using. Go here and start the process all over. Make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
airflood said:
I've got stuck in this "Android" screen when I tried to update my existing CM7. This is what I've done.
1. Boot to recovery.
2. Wipe cache
3. Install the update from SD and choose the CM7 file and google apps
4. Wipe data/factory
5. Format or insert a new sd before re-booting.
I encounter the same error on the first reboot. Booting up the second time solved it. It does hang at the CM logo for bout 5 min on the second boot.
Click to expand...
Click to collapse
patruns said:
You shouldn't be getting a touch anything screen depending on what CM7 file you are using. Go here and start the process all over. Make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Click to expand...
Click to collapse
thanx u guys got it
now it wont let me format cache data or system it gives me an error any clue why?
Good day everyone! I would like to ask for some help if it wouldn't bother.
I previously have WajkIUI 1.10.21 installed on my 2nd init. I have installed the Multiboot plugin (http://forum.xda-developers.com/showthread.php?t=1364659) and installed the CM9 12-2-2012 build on 2nd boot.
However when I updated the 2nd boot to CM9 12-11-2012 build, the 2nd boot stays stuck on the red M logo. Because of that, I installed the "kernel" on 2nd boot which was supposed to boot the build. Unfortunately, it only resulted to a boot loop for my CM9.
When I tried to boot from 2nd init (which still has my WajkIUI), it suddenly stopped booting as well. I tried to recover using my recovery file but to no avail, 2nd init still won't boot.
So my phone's condition now is: it is able to run CWM recovery on both 2nd boot and 2nd init. Will I still be able to boot my 2nd init? Will I still be able to restore to my latest recovery file? If yes, can anyone guide me on how to fix my 2nd init boot?
Thank you very much everyone!
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
esok44 said:
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
Click to expand...
Click to collapse
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
arvs0z said:
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
Click to expand...
Click to collapse
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
esok44 said:
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
Click to expand...
Click to collapse
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
arvs0z said:
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
Click to expand...
Click to collapse
Yeah it is....
AHHHHH damn it.
hmmmm well nevermind, think i will stay with ICS...
titanium backup works, so maybe as a tip for you:
install old rom,
make backup,
install ics,
restore backup,
some data may be back
Yes, I tried that before but for some reason, during restore, Ti force closes on my ICS.
Anyway, I'm fine without my old data for now Thanks Esok
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
die2mrw007 said:
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
Click to expand...
Click to collapse
try removing the battery. then put it back in and power up. see if it boots up. depending on which cm7 rom you were using, there's a known "stuck in boot" problem and removing battery method will overcome it.
^ Yes, try removing the battery and restarting the phone. One other solution could be applying the 2.2 Kernel after the installation of CM7 (only if you are using Defy and the base ROM of CM7 is 2.2) because I tried installing a CM7 nightly and had to apply the kernel
Kernal
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
phatboyjr said:
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
Click to expand...
Click to collapse
are you saying you were still on stock rom and you tried to install cm7? what was your stock rom and have you flashed any full sbf? what were the steps you did to install cm7?
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
to install CM7 follow the steps in this faq :
http://forum.xda-developers.com/showthread.php?t=1065798
phatboyjr said:
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
Click to expand...
Click to collapse
so far so good. could be the rom you were flashing. were you trying to flash the nightlies by any chance? all the latest nightlies do not come with the kernel. you either have to flash the stable release first, or the cm7-kernel-signed.zip, inorder to have the correct kernel before you can flash the nightlies.
do not flash any full gb sbf or you can get yourself in trouble.
NEW KERNEL IS CHARGING. OS DOESN'T SHOW THE CHARGING ICON.
Make sure when you plug in to check the Settings -> Battery screen and see "Charging"
06-28: KERNEL.ZIP #13 IS NOW READY HERE (FLASH IN RECOVERY): REMOVED TEMP
(Recompiling w/o Linaro for compatibility)
md5sum: a16c281fa3dbe0962c6dc2c03e6df5bc
Full ROM: http://bit.ly/NaD2vW
md5sum: d9dfe6f5f97eadbeaecc86d0314cb80e
- Mainline Linux 3.0.31 updates
- TI kernel 3.0.21 branch updates
- [ROM-Only] Now w/ "OtterParts where the touchscreen filter setting can be set (0 as default, but 30 is very usable) -- (Scott Brady)
- Built using Linaro toolchain
- Added KRAIT optimizations (not sure how effective yet) (twa_priv)
NOTE: I haven't adjusted the nightly server to use the 3.0.31 kernel OR Linaro yet. This is the only ROM link I've built with it in it.
[06-27-2012] UNOFFICIAL NIGHTLY SERVER IS RUNNING:
DOWNLOAD HERE
GApps: http://goo.im/gapps (4/29 is the latest in the CM9 row)
These builds are using a stock framework which includes the volume slider mod. It's kept up-to-date by twa_priv.
STEPS FOR UPDATING:
1. Download .zip file from the nightly server and place on your device
2. Reboot into recovery and apply .zip
3. If coming from any ROM which is not CM9 please wipe data/cache/Dalvik Cache
4. Reboot and enjoy
LATEST CHANGES:
[06-26-2012] Added sbradymobile's touch filter patch + OtterParts for controlling the filter level (30 recommended, default as 0 for now) (under Settings -> Advanced) [THANKS!]
SOLO KERNEL NOTES:
06-08: KERNEL.ZIP #12 IS NOW READY HERE (FLASH IN RECOVERY): http://bit.ly/KPbDVm
md5sum: e7476ff785b2dfbdb062e1cc036c14ac
- Touchscreen driver changes (event optimization, ICS friendly)
- Updated the WLAN driver to R5.00.18 (up from R5.00.5)
- Cleaned up the charger code some more (part of on-going charger work)
- Added more support for PPTP and L2TP connections
- [NEW 06/08] Added CCMP support used in 802.11i for EAPOL/WPA2/IPSEC connections using 4-way handshakes (Will fix some users who can't connect to wifi at certain locations)
TROUBLESHOOTING FOR USB not being recognized in Windows 7 (while the Kindle is *NOT* plugged into computer):
- Open Device Manager
- Right-click your computer name and select "Show Hidden Devices"
- The top device group should be: Android device(or phone): under it "Android ADB Composite device"
- Right-click on that and select uninstall
- Now plug the Kindle back into the computer and let driver re-install
IF FOR SOME REASON WIFI DOESN'T WORK ON THE FIRST BOOTUP DO THE FOLLOWING:
Enter Terminal Emulator
Type: su
Type: fix-mac.sh
Exit Terminal Emulator
Reboot
THIS ROM SHOWS OFF HOW WELL ICS CAN RUN ON THE KINDLE FIRE.
** READY FOR DAILY USE **
If I had just installed this ROM and I wanted to see something that might not work in the stock-kernel based ICS ROM, then I'd try the following:
- Install "Chrome Beta" from the market and test it out.
- Audio is more stable.
- Launcher is smoother due to full PVR graphic support
- Try YouTube!
For user support, look to this thread! Please keep discussion here as to what works and what doesn't, etc.
Thanks so much for putting this out there!
I will definitely give it a go once my internet connection stops being so wonky.
Time to play, thanks Hashcode!
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Thanks Hashcode!
btw, I can't get the screen on and it shows
D/SurfaceFlinger( 115): About to give-up screen, flinger = 0x1b5c918
E/libEGL ( 115): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
It's strange!
Awesome work Hash, thank for all the time and hard work your putting into this.
WOOHOO!!!
Ha Ha, my coworkers think I'm retarded. Can't wait.
soupmagnet said:
WOOHOO!!!
Ha Ha, my coworkers think I'm retarded. Can't wait.
Click to expand...
Click to collapse
Lol for buying a kindle? People around me are the same way, thanks hash for all the hard work, can't wait for a stable release
Sent from my Kindle Fire using XDA
Amazing work Hashcode. Simply Amazing.
I cant wait till this kernel is stable.
once again, nice job, i really envy your tallent.
Oddly enough I get bootloops on this right AT the bootanimation. Was running CM9 earlier (which worked fine), but for some odd reason this rom always bootloops on a different part of the bootanimation.
Wiped every single option under CWM. Will probably try TWRP to see if it's any different. The only option I don't see under CWM is "/format boot" so I'm assuming that maybe there are some remnants that are keeping it from booting. I recall from the Nexus S forums that a proper wipe involves formatting system and boot.
I decided to give "fastboot erase boot" a try. I thought that this was going to just wipe out the boot partition. I was then going to flash the boot partition with your boot.img from your zip file, but somehow I still wasn't able to get back into the recovery after doing so. After flashing recovery again, it finally loaded back up. But, at that point I just flashed a nandroided boot.img just to be safe.
I'm not even sure if this line of thinking is correct though, haha. If it is I'll goof with it some more tomorrow.
Or would it be possible to include a line in your installation script to wipe boot as well?
I simply cannot seem to be able to get the screen working. The backlight does start, and sometimes I can see different colours in various lines of pixels, but no picture shows no matter how many times I try the power button. Very strange.
Thank you for outstanding job.
My kindle Fire recycled to boot loop during booting using this ROM. It recycled back to boot at CM animation where it remained for a few second at CM boot animation then boot to boot partition.
Sent from my Amazon Kindle Fire using Tapatalk
Anyone successfully flashed this using TWRP? Can't get it to boot...
Had absolutely no problems booting this on my KF. Works flawlessly so far.
Only thing was the CM9 boot animation was in portrait and cut off.
Oh, and I flashed using TWRP.
Oh, and guess what?! Google Chrome Beta now works!!!!
Some of my other findings...
The audio driver works very, very well! Amazon doesn't seem to have it implemented very well in their stock builds. Notably in apps like Audiotool Sketch which would crash on the first ICS builds because of the original driver and then Squids which soundtrack would simply stutter on both stock and CM9 and now plays beautifully on this kernel.
Sims FreePlay no longer throws the error and you can now download and play it. Looks great on the KF too!
I'm not having any booting issues, that's after now having rebooted twice. I'm having the screen not work when you turn it off and on, ut like you said, just pressing it multiple times fixes it.
Not having anymore issues with the reboot button after a few restarts...
Flash works beautifully.
If you have it plugged in, it'll keep the charge. I've been messing with it for a hour and it hasn't went down anyway.
Hmm, I don't even see a boot anim. This is after wiping everything possible using TWRP.
Strange, what ROM did you come from?
treUse said:
Hmm, I don't even see a boot anim. This is after wiping everything possible using TWRP.
Strange, what ROM did you come from?
Click to expand...
Click to collapse
MoDaCo. Do a wipe of your caches.
I did, I wiped everything, including cache. Came from cm9 tho, maybe, as another user said, boot isn't wiped correctly.
treUse said:
I did, I wiped everything, including cache. Came from cm9 tho, maybe, as another user said, boot isn't wiped correctly.
Click to expand...
Click to collapse
Try factory restore then.
I did a factory reset and cleared both the cache and dalvik cache, prior to installing the FW. It just refuses to show a picture, and there is also no boot animation.
Once, though, I waited for it to boot and then I tapped around on the screen. Somehow I heard dial tones, and a distinct button press "click"
I installed CM9 Eyeballer the other day on my NC. It pretty much works, but if I go into the web browser or any other factory-installed app, hitting the "N" button takes me back to the factory-installed home screen, and I can't find any way to get back to the Android home screen, short of rebooting the device. Is this normal?
Also, I flashed Gapps using gapps-20120429-ics-signed.zip, and the only Google App that appears is Play Store -- I was able to sign in, but the next screen gave me a "Server Error," and that's all it's done since. I verified the md5sum, and also tried again to install it. No change. Is there some version conflict, or something like that?
Edit: did not install CM9, after all. I now have.
What is the 'factory installed home screen'? You mean stock? That is not possible if you installed CM9 over the top of stock on emmc. Can you explain a little more how you installed it and what you mean.
Well...
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.
estebandido said:
I followed the directions as closely as I could: create a recovery chip, copy over the zip file (manualnooter-5.08.20-apps2sd.zip), reboot, install from zip file, install Manual Nooter, flash update-Froyo1.2-dalingrin-OC-emmc-090111.zip, install Gapps, reboot again. As far as I could tell, my results were consistent with the directions, up until the symptoms I described. For example, the splash (smash) screen is right, and the rainbow-y thing, and so on.
This partial success is even more frustrating than a total failure.
Click to expand...
Click to collapse
Your original post said you installed CM9. You did not. You just rooted your stock rom. You might want to edit the title of the post to 'Manual Nooter installed properly, Gapps not working. Then take that CM9 Eyeballer statement out of the text in the first post and you might get some proper responses from folks.
Sure enough.
leapinlar said:
Your original post said you installed CM9. You did not. You just rooted your stock rom.
Click to expand...
Click to collapse
Ah... I was under the impression that Eyeballer was a version name of CM9. None of the sets of instructions I read made it clear to me that wasn't the case.
I ended up doing a factory reset, then reinstalling everything. The picture is far rosier now -- it finally looks the way I pictured!
Thanks!
estebandido said:
Ah... I was under the impression that Eyeballer was a version name of CM9.
Click to expand...
Click to collapse
Eyeballer does build a version of CM9. But that has nothing to do with what you did. You ran Manual Nooter, which is a tool to root your stock installation. CM9 is a completely different version of Android than stock is. And when you install CM9, your stock is completely removed and replaced by CM9.
You do not have CM9 installed, you have just rooted your stock rom.
Anyway, I'm glad you got it working.
Edit: I see you modified your original post to say you did later install CM9.
[ROM][NC] Unofficial CM9 Nightly builds - with/without OpenGL
I don't have enough posts in XDA to post in the (goo dot gl/vPJcM) actual ROM thread so I'm hoping someone will see it here.
After installing the CM7 ROM a long time ago. they Nook wasn't able to boot into CWM. I can only access the recovery using a bootable SD card. That may or may not matter.
Yesterday I installed both the 3 SEP OpenGL and 4 SEP versions of Eyeballers CM9 ROM along with GAPPS. In both versions I cannot get bast the Setup Wizard since it "unfortunately Closed" every time I "touch the Android".
I did install the ROM w/o GAPPS as a temporary fix but will need to eventually access the Play Store.
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Does anybody have any suggestions?
Thanks!
JC
jerrycrabb said:
I did notice that CWM still wont boot into recovery and the Cyanoboot won't either. Cyanoboot takes me to what appears to be a stock Nook screen claiming that an install has failed and that I should power on/off or contact customer service.
Click to expand...
Click to collapse
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
From what I can tell, Eyeballer is mostly drinking.
leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Thank you very much for the response, I will try this as soon as I get some time (I have a selfish new baby) and get back.
leapinlar said:
You do not have CWM installed on internal memory (emmc). That message you are getting means you still have the stock recovery there. You need to flash a CWM to emmc using your bootable CWM card. Look in my tips thread linked in my signature. Look at item A8 and the subheading 'to fix a corrupted or missing recovery on emmc'.
I don't know how to solve your other problem with gapps, other than to do a factory reset with CWM.
Click to expand...
Click to collapse
Success! errr..sort of.
Prior to flashing gapps I was able to reboot into CWM. Thank you so much for your help!
Still having the same issue with setup manager after factory reset and wipe of all cache.
If anyone has a work around or another suggestions for CM9 on the NC I'd much appreciate it.
Thanks again.
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
FemBlack said:
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
Click to expand...
Click to collapse
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
simms22 said:
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
Click to expand...
Click to collapse
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
FemBlack said:
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
Click to expand...
Click to collapse
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
simms22 said:
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
Click to expand...
Click to collapse
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the build in icons...
two times i got into the boot loop problem.....
FemBlack said:
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the icons...
two times i got into the boot loop problem.....
Click to expand...
Click to collapse
those options probably arent compatible due to android version, phone model, or rom(if works on another rom). there could be filesystem differences that make things incompatible. not all hacks/mods work on all devices. this all would cause bootloops, the way you describe it. have someone else with a nexus 4 confirm if they work or cause bootloops.
I already spoke with the developer regrading these boot loop problems... he has provided some solutions for it...
I have try those workarounds and lets see whether it fixes the problem or not....