I haven't been able to find anything on this so I figured I would post. I had my nook set to CM 7.03 and for the first time decided to do a nightly build. Tried 203 and it worked okay (had fixed the density issue, etc.). It had a few too many hard lock ups so I decided to use ROM Manager to go back to my saved restore. Well, it kind of went back but it was a weird reboot. All my apps showed up but it was laggy, all my apps on the deskstop were gone, the default CM logo was there and the tool bar wouldn't load. Also, the N key stopped working. I tried a lot but eventually tried to completely gut it and start from scratch but no matter what I tried, no go.
From a 2 Gig CWR SD I tried to wipe cache, system and data but wouldn't let me do data. I tried Factory Reset and no go. It said it did but when I tried a vanilla install it went to the above load in with all my apps, same hang ups, etc.
I tried going back to 1.2 original Nook set up and it almost did but got locked in the boot up screen.
Yadda yadda yadda I finally just did a bootable SD card and that seems to work but it essentially cuts out all that original internal memory. A temporary fix at best.
Any ideas how to really gut this sucker and get back to square one??? I can't even get in through the USB because the tool bar won't load so I can't connect it. Gah!!
Any ideas would be greatly appreciated by this old noob.
fil42skidoo said:
I haven't been able to find anything on this so I figured I would post. I had my nook set to CM 7.03 and for the first time decided to do a nightly build. Tried 203 and it worked okay (had fixed the density issue, etc.). It had a few too many hard lock ups so I decided to use ROM Manager to go back to my saved restore. Well, it kind of went back but it was a weird reboot. All my apps showed up but it was laggy, all my apps on the deskstop were gone, the default CM logo was there and the tool bar wouldn't load. Also, the N key stopped working. I tried a lot but eventually tried to completely gut it and start from scratch but no matter what I tried, no go.
From a 2 Gig CWR SD I tried to wipe cache, system and data but wouldn't let me do data. I tried Factory Reset and no go. It said it did but when I tried a vanilla install it went to the above load in with all my apps, same hang ups, etc.
I tried going back to 1.2 original Nook set up and it almost did but got locked in the boot up screen.
Yadda yadda yadda I finally just did a bootable SD card and that seems to work but it essentially cuts out all that original internal memory. A temporary fix at best.
Any ideas how to really gut this sucker and get back to square one??? I can't even get in through the USB because the tool bar won't load so I can't connect it. Gah!!
Any ideas would be greatly appreciated by this old noob.
Click to expand...
Click to collapse
Are you trying to wipe everything and install with a version of CWR that is older than 3.2.0.1?
Yah I think it is 3.0.2.8. Is that bad? It is weird. Now even the "bootable" SD runs but some legacy stuff that should be there bleeds in. I think it is haunted (pics from what should be the part of the Nook not being accessed).
I am going to try the "restore Nook easily" bit and see what happens, too.
fil42skidoo said:
Yah I think it is 3.0.2.8. Is that bad? It is weird. Now even the "bootable" SD runs but some legacy stuff that should be there bleeds in. I think it is haunted (pics from what should be the part of the Nook not being accessed).
I am going to try the "restore Nook easily" bit and see what happens, too.
Click to expand...
Click to collapse
Yes, use version 3.2.0.1 and you will be able to properly wipe.
Related
i rooted my NC with 1.1.0 and everything was perfect. installed and backup with CWR v 3.0.0.5. I have been stuck in the two screens of cwr. I CANNOT TURN off the nc so 8 aborted on/off s do not work. I cannot restore from sd card since it boots back into cwr, so i have not been able to use any removal code. the Monster pack is not for 1.1. I think I may be bricked. How do I get out of this clockwork recovery program (i have tried all of the options in it too, including fixing permissions, recoveries and endless useless reboots. HELP!
Hold the power button and it will turn off.
i have done that but it turns itself right back on again. it will not stay off. when it does go back on, it goes right back into clockworkmod recover (orange menu screen, landscape only)
Try going here and see if that gets you out of trouble .. Hope it helps
I can't say for a fact that this will make a difference for you, but it certainly can't hurt. Make sure you plug in your Nook Color to the charger, then do the manual power off (as in hold the power button). That should force it to reboot.
Those were the instructions I was given when CWR froze up on me during a kernel flash and it worked. Good luck.
got any mortar-bricked!
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Boot CWR off monsterpack SDcard and restore stock system.img/boot.img. This saved me. This is definitely auto-nooter 3.0.0 related because pre-rooted BN 1.1.0 flashable does not have this problem.
ddd22 said:
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Click to expand...
Click to collapse
no can do...cannot be turned on. stone dead
It is not. Trust me, I've has this thing twice today. boot partition on emmc is messed up I guess. You CAN boot from CWR on SD card.
ddd22 said:
no can do...cannot be turned on. stone dead
Click to expand...
Click to collapse
With all due respect, I dont understand how that can be. When I press, or press and hold the power key, nothing at all happens. no screen or light activity of any kind... like someone removed a battery.
After your reply, thinking perhaps my removed micro sd card might make a difference, i put it back in and tried again to power on the NC.. nothing happens still. Are you telling me that somehow if i change the content of my SD card to the Monster Pack that somehow that firmware code is going to turn on the Nook even though i cannot power cycle it at all without that magic? I dont understand how this could be and creating that card is a fairly steep search and discovery mission for me which i am willing to do if it has a chance of working.
btw, the battery is fully charged according to the green N on the usb cable.
Thank you so much for your response.
zdrifter said:
Try going here and see if that gets you out of trouble .. Hope it helps
Click to expand...
Click to collapse
What he/she said.. Happened to me once today. Remove the CWR and you should be good to go
how do i do that when no matter what i do the NC will not power on at all...zero. I can no longer even establish a usb connection to the computer.. it detects something and then tries and fails to install required drivers (which were previously installed and previously working). As much as I wish you all are right and I am missing something, I think I may be the first fool to brick the unbrickable!
You will need to make a bootable SD card and boot off that.
i made a bootable cwr sd from the monster rootpack. same nothing happens. will not power on in any way shape or form. will now remake the card with the full rootpack and pray that i can eat my words.
chomp chomp chomp
(the glorious sounds of words being eaten). you both were 100% correct and trust you i should have even more. I followed your advice despite my doubts and I wrote the rootpack image to the sd card and held the power button for about 15 seconds and alive she came! now i am at least back to my cwr that i cant get out of. i now could use a little more of your wisdom as to the best next steps. should i remove cwr then reflash with say 1.1.0R2 or should i figure out how to use cwr to do that flash, and remove it after the flash is completed. obviously a newbee to flashing this device (less than a week old), but have been following Energy on HTC flashes for long times. There is so much information here, it is almost too much when you first step in and your collective willingness to help this doubting thomas is extremely appreciated. my apologies and my deepest thanks. more reading coming up..
resolved!
i added the zip for 1.1.0 -r2 to the monster sd boot card and installed the rom from there. setting it up now. thanks to all for not listening to my doubt and telling me to continue as instructed. forever grateful
ddd-22 - did you install from CWR after rooting 1.1 using the modified Autonooter, or did you sideload the rooted 1.1?
I installed CWR from a 1.1 that was rooted using Autonooter (modified for 1.1) and ended up in a CWR reboot loop similar to what you had.
Yeah- I attempted to run the OC rom after autonootered to 1.1 and got into the loop. Has anyone had succes in loading the OC rom after autonootering to 1.1? Thanks
Thank you for this thread. The exact same thing happened to me after trying to flash a kernel using CWR and autonooter3.0. Thought I was bricked for sure!
I am back to business and glad not to have an expensive paper weight!
though i am on the way to recovery, not fully there yet. the r2 prerooted version was great except i could not log onto gmail... it kept seeing the NC as a phone and was looking for a cellular network, and gave me the message "a reliable connection with google servers could not be made" or some such verbage.. In the pre rooted 1.1. r2, i followed the directions going through youtube etc, but that did not work. so i decided to try to restore the backup i made when i first got caught in the doloop. which i did again, so it is back to monster to start over again and clear out the NC. I have been scouring other sites and many people have been having this problem. I wish i could remember how i installed cwr (method) but cant. however, what i found fairly consistently, and i believe i made the same mistake, was not restarting the NC before i made the backup. seems that is what got a lot of folks into this doloop crisis. if anyone has a plan of how i should get back to my previous state of bliss, let me know. I am remaking monster pack again and clearing out my machine.
NookColor Version 1.2
About 2ish months ago I bought a nook color for my significant other, but I was having problems getting sideloaded books to work right on it so I decided to try and root it. I'm not extremely tech savvy, but can usually do something like this if I have directions.I rooted with manualnooter-4-6-16 The root went well and it was working fine for a couple days until dummy me started messing with it, don't know what it was that "bricked" it but I had updated the flash player then was in the rom manager and hit the backup button. The keyboard was acting funny so I rebooted it, it got to the screen that says Nook Color with the little android dude in the bottom right (nook color devs) and that screen just kept replaying itself except it would stop at the first O in Color and start over. I tried doing some research and followed a couple tutorials on how to return the nook to stock, none has been successful. The first one I followed was video tutorial on youtube to return it to stock 1.0.1, when it asked me to format the data I got and error format data failed..I just skipped that step and moved on. It booted and still showed me the nook color devs screen and once it completely booted showed a "How do you want to finish this action?" With only Home and Softkeys as a choice, I hit home and all it was was a black screen with a bunch of errors. so I tried a different tutorial, the next one I tried was to return it to 1.2 I followed the instructions, it again gave me a error cannot format data, I ignored it..it booted to the nook devs screen and just kept playing over again. I'm lost on what to do, I've searched and searched.
If it matters I've been using a 16gb micro sd because thats all I have, and was using the 2gb clockwork recovery image. I just want it returned to stock, and can't for the life of me figure out how.
Please someone explain to me in the most dumbed down way how to fix this darned thing.
Don't know how serious "brick" it was on your definition but let say on scale of 10, yr NC is bricked level 9 . Still, no need to panic
1. Get the uSD card (2GB is enough)
2. make it flashable with CwM Recovery (ClockworkMod Recovery) either v3.0.2.8 or v3.2.0.1
3. hunt for "re-partition/re-format" thread, read through. I'll update the link if I find it, can't remember where on top of my head now.
4. perform the repartition/reformat back to original v1.2 NOOK
5. hunt for "restore to NOOK for v1.2". Again, I'll update the link later
6. flash it
7. keep all your fingers crossed
Will try that, thank you..Hope it works..seriously cant afford to spend another 250 dollars to replace it
Edit: Fixed The 8 interrupted boots seemed to have fixed it, thanks for your help!
Scintie said:
Will try that, thank you..Hope it works..seriously cant afford to spend another 250 dollars to replace it
Edit: Fixed The 8 interrupted boots seemed to have fixed it, thanks for your help!
Click to expand...
Click to collapse
Glad to hear that!!!!
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
OK, I need some serious help here. I've had my nc since sept., I followed the guide to put cm7 on an sd card and have been using it since then. I wanted to update to the newest .4 version but it wouldn't let me, apparently the sd card installs CMR on the nook?? I didn't think it made any permenant changes but I was clearly wrong.
OK, so no update, I follow the directions here:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock/
to try to get it back to factory stock, but when I rebooted and took the sd card out it started this flashing thing. It turns on but after the nook boot screen it starts flashing, normal screen/black/normal screen/black. I tried to factory reset and delete cache and that didn't do anything. I tried the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=1050520
and still the same problem.
Can you help me or did I really screw things up? I guess last resort is to go to the BN store and say the update screwed things up?
EDIT: Well, I tried to factory reset the nook after following the "Restore your nook" thread and it still doesn't work. Now it doesn't flash but it also doesn't allow me to download anything at all. I'm going to try one more time to factory reset things and see what it looks like after that. My computer won't allow me to transfer files to the nc when it's connected anymore either.
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?