Related
folks, got a nook for my birthday a few weeks ago, I followed these directions from the addictivetips site to the letter and after about 3 days got CM7 86 or 87 running w/ gapps 0307 working as well as the overclocking. I was gleefully using it until my legs went numb and 2 days ago i let someone use it who attempted to reboot but it was on restore, it restored back to nothingness. Me, being in IT for the past 15 years know that testing and backing things up are for wimps, so no, I have no backups. Anyway, i have tried to put on the latest nightly CM7 (116), I was trying with the nightly, the latest gapp and the overclock. I get the green CYANOGEN logo which on the newer versions says "Loading", then it vanishes and I'm back in limbo. So i then formatted my sd card, redid all the steps and tried 87 by itself w/o gapps or the overclock, nothing. I cannot find a version that will boot up from the get go. I hate asking for help but am tired of getting my butt kicked by this thing. What I don't understand is I have the same version 87 that I had on it when it was working. I am using CWM 3.0.0.5.
does anybody have anything I can try because i'm getting bummed now, I don't mind hacking and trying stuff but it doesn't seem logical to me that so many different versions can all not work. Which makes me think the issue is not w/ my CM7 version.
Start over by formatting /system,/data,/cache. Then try to put CM7 on emmc
smcgov34 said:
folks, got a nook for my birthday a few weeks ago, I followed these directions from the addictivetips site to the letter and after about 3 days got CM7 86 or 87 running w/ gapps 0307 working as well as the overclocking. I was gleefully using it until my legs went numb and 2 days ago i let someone use it who attempted to reboot but it was on restore, it restored back to nothingness. Me, being in IT for the past 15 years know that testing and backing things up are for wimps, so no, I have no backups. Anyway, i have tried to put on the latest nightly CM7 (116), I was trying with the nightly, the latest gapp and the overclock. I get the green CYANOGEN logo which on the newer versions says "Loading", then it vanishes and I'm back in limbo. So i then formatted my sd card, redid all the steps and tried 87 by itself w/o gapps or the overclock, nothing. I cannot find a version that will boot up from the get go. I hate asking for help but am tired of getting my butt kicked by this thing. What I don't understand is I have the same version 87 that I had on it when it was working. I am using CWM 3.0.0.5.
does anybody have anything I can try because i'm getting bummed now, I don't mind hacking and trying stuff but it doesn't seem logical to me that so many different versions can all not work. Which makes me think the issue is not w/ my CM7 version.
Click to expand...
Click to collapse
Weird, exact same thing happened to me. I tried nightly 116, as well as an older one that had worked for me previously.
I repartitioned and restored prior, and it was fine at stock 1.0.1 that way, so...
I put the froyo 6.8.2 on last night and it works fine so I'm trying to decide if I'm just going to roll w/ it, it at least proved to me that the hardware is fine though. I may have a kernel issue although I have no idea how to check what kernel I currently have.
FYI, I repartitioned and reformatted 0p6, 0p7, 0p8, using flashable zips from the the following:
http://forum.xda-developers.com/archive/index.php/t-1094371.html
I had supposedly repartioned and reformatted before, but it must not have worked because my data was still on /media. The above link worked however. I then flashed the new CM7 RC, and gapps, and it seems to be working. Maybe give it a try. I am also using the bootable sd cwr 3.0.2.8, which I wasn't before.
You should have use this app:
http://forum.xda-developers.com/showthread.php?p=21959334#post21959334
Lets you switch between different versions of android with ease!
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
i do not have an answer but this answers my question of whether I want to run manual nooter on my 1.3 or try cm7. the cm7 steps seems more intimidating
Well i tried several more times last night with no luck. Then i got brave and just wiped everything (data,system,cache,dalvick) then flashed cm7 and gapps straight from my cwm boot card. I somehow
Ended up with a fully functional nook. App market works. Rebooted several times to be sure. I even tried usb host with my homemade adapter. Mouse, keyboard, and sandisk cruzer all work splendidly thru a powered hub.
My only mistake was i cant find my backup of stock 1.3 rom. Is there one floating around?
Sent from my LG-VM670 using Tapatalk
If I'm understanding correctly, you're trying to go from CM to 1.3, correct?
From what you've described, I suspect Clockworkmod 3.0.2.8 is your problem. If you look carefully as you format /data in preparation for reloading the BN 1.3 firmware, I think you'll see that the format is actually failing. That version of CWM doesn't handle the partitions correctly.
You want 3.2.0.1. See the edits at the top of this thread: http://forum.xda-developers.com/showthread.php?t=987735
If you're already on CM7.1, you probably have the correct version of CWM installed. You can save yourself a step by formatting the /data and /system partitions using that, then continuing on with the rest of the procedure for restoring BN 1.3. I went through all this myself a few days ago while preparing to go to BN 1.4.1.
I forgot to mention in my last post that i realized i was using the wrong cwm image and i burned another card with cwm 3.2.01.
I was still getting a boot-loop so i wiped everything and went straight to cm7.
Sent from my LG-VM670 using Tapatalk
@bobstro
I didn't read your post correctly.
I had a stock nook that i want to install cm7 on. Not the other way around. I asked about a stock 1.3 file just in case i need to do a restore. The nook is done. Its running cm7 just fine and i have given it back to my friend.
I really need to get myself one :-(
I usually mess around with my sons but he's at his mothers for the weekend with it. After christmas im getting one. Dont know if it'll be a color or a nook tablet but im getting one for sure!
Sent from my LG-VM670 using Tapatalk
If you intended to install CM7 from beginning, then why you wasted time messing around with ManualNooter?
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
pdrift said:
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
Click to expand...
Click to collapse
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
pdrift said:
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I hope you do use Windows at some points.
Let's put it this way.
You bought a PC with Windows XP pre-installed, get home, you don't want XP, so you install Windows 7 on the PC. You just whack the XP.
Same theory applied here, B&N shipped their NC out with the original stock ROM, which is Froyo-based OS. You want to install CM7, which is Gingerbread-OS ROM. You just whack the stock and install CM7.
oh I get it know. so its pretty easy if you want to go straight to cm7 just wipe and flash.
After reading some posts from the nook tablet section, i guess i'm getting a nook color.
what a shame about the locked bootloader :-(
i didnt technically solve the boot loop issue, i just erased everything, but should I mark this as solved and if so how?
The current Nook Color bootloader is not locked. The Nook Tablet's is. I wouldn't necessarily rule anything out, though. The bootloader on the Motorola Droid 2 is also locked, and there's quite an active Cyanogenmod community around it. The only problem is that we're stuck with whatever kernels B&N release, so ICS may be a long way off. I suspect the NC will remain the tuner's machine of choice, but the performance on the NT is very nice. If you can live with a rooted B&N ROM, it's a nice device for now.
billingdl said:
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
Click to expand...
Click to collapse
No, it seems that some 1.3 based NC units will bootloop if 4.6.16 is used to root them. I'm not sure why. Even after repartitioning to original nook partition sizes, or using CWM 3.2.01 (which supports the new partitioning), it'll still bootloop if 4.6.16 is used. Might be because of the different kernal included, but I'm not knowledgeable enough to know for sure. They root fine with 4.5.18. Haven't tried one with the new 1.4.1 compatible nooters.
To the original poster;
I'm having the same problem here, installed 4.15 successfully, installed 4.16 and am getting stuck in boot loop at the rainbow nook color screen.
I'm not understanding the 8 boot fail procedure though. Is this when you let the boot loop run through 8 times or when you get to the point of when the boot loop starts, shut the NC off and power it back on?
Also, to install cm7, all you did was put it on your sd card, and installed it through cwm?
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
pdrift said:
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
Click to expand...
Click to collapse
Thank you good sir! I was stuck in boot loop forever and couldn't find a clean explanation of the 8 boot fail process. I always tried to turn it off when the rainbow nook color screen came up.
I got it reset, made a flashable CWM SD card with 3.2 and then flashed CM7 on there and it works great!!
That was very frustrating, thank you!
Dont mention it, Glad to here I was able to help you out. I felt the same way when I was in that situation. Lots of googling to get a clearer idea on what that 8 boot method entailed. CM7 really makes it feel like a totally different device.
To all the devs that work on these projects, thank you
sent from my OV CM7 IHO using tapatalk
ive recently purchased a nook color version 1.3 and did all the steps to build cm7 on sd ard inserted it into my nook it downloaded then rebot and seem to come up im cm7 but my touch screen isnt working any suggestions?
hey i just attempted to root my wife's nook color, 1.3, using this method http://forum.xda-developers.com/showthread.php?t=1054027
i have made the boot disk and pushed both nooter zips to disk, cwm comes up and it runs both zips just fine, ive tried both one after other ten reboot, reboot in between, wipe dalvik and the run but i always get stuck in the boot loop
can anyone tell me what im doing wrong here
and the plot thickens... so i did the 8 failed manual reset, and rebooted to stock, repeated process.. im out of bootloop but it appears the touch screen doesnt work anymore???
yeah so no matter how many times i 8 fail reset still no touch screen, all other buttons work, tried reinstalling clockwork and nothing...i bought the insurance, do i need to run it over cause im outta ideas, my first thought was ui was missing file but it should go back if i reset shouldnt it???
just shoot me..please
ok back to stock, re root, boot loop again, re stock , cm7 (update-cm-7.1.0-encore-signed) + gapps (gapps-gb-20110307-signed) and now application setup wizard has stopped unexpectedly.....stuck...thoughts? please am i over thinking/looking something
day two...
i created sd boot img with cwm 3.2.08, im seeing that i need to use cwm 3.2.01 in a few places.. when i get the file from clockwork (recovery-clockwork-3.2.0.1-encore) and try to write the image to the sd card something is wrong, its not a format that the windows recognizes and so i cant add zips to it and i get nothing in the nook. ive tried to reformat from the pc and in an old android phone i have but its always the same when i try to write to sd , is this the wrong image, can i find it somewhere else
i am using same 8gb sd card i made first boot disk out of, do i need to use a new one??
i got it to work i have good cwm 3.2.01 on nook...
stock + root?
ok it seems that cwm 3.2.0.8 was definitely my problem, i switched to recovery-clockwork-3.2.0.1-encore which i got from http://tinyw.in/0Vw
problem remains that when i flash man nooter 18 then 16 i get nothing, I was stuck on "n" load screen not even a boot loop
i then pushed cm7 again and i am operating as a full android tablet, i want the stock nook image with gapps can anyone help.. im leaving be till i get a answer, didnt want to update to 1.4 or downgrade to 1.2 havent seen a stock img of 1.3 anywhere
Nook color running Racks triple boot via micro SD card. Micro SD card is a Sandisk 8GB class 4 card.
Was previously running fine for many months with the 2/2/12 roms. I would run CM7 99% of the time and I would get a random reboot here and there, but otherwise very stable.
A couple days ago, I had a random crash and tried to reboot CM7. I could get passed the boot loader screen, but then would have a continuous boot loop with the blue android symbol.
Thinking something was corrupted with the rom, I booted to recovery and tried flashed the rom along with gapps. Still boot looping.
I booted to CM9, and was able to run. So I downloaded the latest CM7 and CM9 roms for Racks triple boot. Flashed both along with the gapps and CM9 fix. Apparently I got lucky and was able to boot into CM7.... once. Thinking everything was OK, I went on with my life and ran the new CM7 happily.
Now, a few days later, I've tried to reboot and I'm back at the same boot loop with the arrow spiraling around the a blue skateboarding android. Note, in that short time that I was running the newest Racks triple boot CM7 rom, I did not run a backup, so, I'm basically out of luck with recovery via CWM.
I've flashed the 2/2/12 rom as well as the latest rom to see if either would work again. nothing... still boot looping... for hours now.
Any suggestions other than wiping the SD clean and starting with a fresh install?
Thanks all.
~mike
Bump...
Been a bit, no responses yet. Anyone have any ideas?
Thanks,
~mike
I think the fresh install will help since you already tried partial reinstalling the roms.
Produced by NookColor at ICS AOKP 4.0.4
Nook Color stuck in load screen
I have a nook with CM7 installed on it. was going return my nook to stock to give it to my little sister, but when i went to install the stock stuff back on it got stuck in a loop. It won't boot from an uSD card with clockwork on it and when I tried the 7 hard boot in a row trick, it didn't do anything. Did i really brick the thing? or can it be recovered?
doodlebug81 said:
I have a nook with CM7 installed on it. was going return my nook to stock to give it to my little sister, but when i went to install the stock stuff back on it got stuck in a loop. It won't boot from an uSD card with clockwork on it and when I tried the 7 hard boot in a row trick, it didn't do anything. Did i really brick the thing? or can it be recovered?
Click to expand...
Click to collapse
You are in a recovery bootloop with no recovery installed. Go to my tips thread linked in my signature. Read item A8. You need to make and use my special bootable CWM SD (select the 'larger' image). Then if you want to return to stock, read item A15.
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great