[Q] May have durped my Nook... - Nook Color Q&A, Help & Troubleshooting

Hello, well it seems I may have messed up my nook and I wanted to get some help. I have had one sitting in a dresser for awhile since I got my tablet and a friend wanted it so I got it out last night to make sure it was up to date with everything.
Now it had some old build of phire on it and when I went to try and flash a new copy onto it, the thing goes to the logo and then to a black screen. Now I know it's on cause the backlight is on but it just sits at a black screen. Also when I try to hold the volume up or down with the power button to reboot and try to get into clockwork doesn't work and I am not even sure it has CW on it. I was lazy and told that rom manager to do all the work, first time I ever let the thing do anything for me.
So right now that is where I am at, and would like to know what I did and how to fix it? Also what is the newest stable rom for a nook?

On mine you use the n button + power to get to recovery. I tried letting Rom Manager do it once and like you, it failed. IMO the MiRaGe rom is best.

Related

[Q] Brick phone

I brick my wife phone I installed 2.2 that was fine then I add one of those 2.2 themes after it rebooted it is stuck right after the vibrant theme disappears, I tried every single way but still can't get into the download screen.
after I pull up the cmd screen what do I do next.
Reflash your rom from cwm it well start you all over again but you won't be bootlooping anymore
V5 custom vibrant
I'll love to but it freezes after the virbrant logo.
Turn off the phone then hold power and volume keys when the samsung screen comes up twice let go of the buttons this should take you to clowork recovery then go to reinstall packages if it goes back to the same screen select reinstall packages again then select choose zip from sd then navigate to where your rom is select that and you should be good to go
V5 custom vibrant
drew2jr said:
I brick my wife phone I installed 2.2 that was fine then I add one of those 2.2 themes after it rebooted it is stuck right after the vibrant theme disappears, I tried every single way but still can't get into the download screen.
after I pull up the cmd screen what do I do next.
Click to expand...
Click to collapse
to get it into the download screen, take out your battery, sim card, and microSD. plug your phone into your computer's usb. hold the volume up and volume down buttons while putting the battery back in, and you should see an android digging with "downloading..." underneath. after that, you can re-flash your phone. good luck!
Nothing is working I tried everything.
drew2jr said:
Nothing is working I tried everything.
Click to expand...
Click to collapse
Try going to http://forum.xda-developers.com/showthread.php?t=848737
i don't know much cause im new to android phones. that thread is dedicated to helping people fix their bricked vibrant. try asking him instead, he worked wonders with my phone =P
Thanks for all the help guys I got it fixed, I went to captivate site and someone there showed me how to get into the Adb and that's what work so again THANKS for all the help.

[Q] Wildfire bricked! Sort of

So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
nachos011 said:
So here's the problem, I wanted to flash the cyanogenmod rom to my wildfire, which was running the sunaabh rom. Nothing wrong with it though, just wanted to try something new. So I made a nandroid backup. All's well and I wiped clear and proceed with the flashing. After a while the installation seemed to stopped at a point, I thought it was just installing so I left it there. After a whole hour it was still stuck. So I did the stupid thing a pulled the battery out. Now when I boot the screen is black but the vibrate noise of the startup is still there (silent boot) and the buttons light up, which I'm thinking it boots up fine. The problem is that the screen is blank even when I go to the HBOOT menu. Tried flashing a RUU but the program couldn't recognise the phone. I'm stumped now.
So what should I do?
Click to expand...
Click to collapse
try taking sd card out and boot into hboot
May be restoring the nandroid could help. I am not sure, but you can try.
Sent from my HTC Wildfire using Tapatalk
he can't get to the nandroid though if he can't get into recovery,
have you had any luck nachos?
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Quite strange...I had similar issue when I first flashed my HTC Desire where the screen was just blank, but it was at the time when the Desire moved from AMOLED to SLCD and some of the flashing caused it not to work...I thought I also bricked my phone but then flashed again then worked. Created a GoldCard just in case...good luck and just be aware that some phones may require a GoldCard to flash properly.
nachos011 said:
Well, it seems that the screen is the problem. It took a lot of reboot and pulling battery's but finally the screen was fine. Cyanogenmod seems to run fine too. But the screen would respond really slowly when I wake it and when I power it off, I'll have to be lucky again to get the screen running again. I did the smart thing and flashed a RUU (it can detect the phone now) and sent it to the shop to get it repaired. Oh well, thanks for your help! I really appreciate it
Click to expand...
Click to collapse
So what you were facing was the black screen and everytime you put the battery back in and hit power it would vibrate 3 times? I am having the same problem. I was actually flashing it with this and it shut down and now I can't get it back on. But you say that after pulling the battery and replacing it numerous times it came back on?

Clockwork doesn't respond

Hi!
It's been a while when I flashed my Blade with Swedish Spring and now when I'm trying update to Elite S2, the Clockwork seems to freeze with everything I'm trying to do with it.
First I tried with the old one I had already installed -> Factory reset, nothing happens, only the orange arrow with hat pops on to the screen and about half hour later it was still the same.
Same thing happens when I'm trying to go and select zip, only the arrow comes to screen, nothing happens after that.
And even when I'm trying to reboot or turn my phone off, the arrow shows up but nothing happens. Removing the battery and turning my device on again and my old rom (SS) works like it should and every app are still on their places.
Same thing happens with the newest Clockwork which I updated today, only the color of the clockwork-menu changed from orange to blue, but not the color of the arrow.
I'm not sure should I try straight flash the new rom with Rom Manager? I'm scared that it might brick my device becouse isn't Rom Manager based on Clockwork, so if the old fashioned-way doesn't work, the Rom Manager won't either?
If you got any ideas, please share them. I'm eager to try Android 2.3

[Q] [Bricked] Please Help

Hey Everyone.
I recently went back home from college to find my transformer completely bricked. I have no idea what is wrong with it, and although It was previously rooted, was running prime, and was overclocked, I don't really know exactly what was on it anymore.
As it is now, it will not turn on, and just loops to tge EEE Pad ASUS screen when turned on or off, and does not do anything else. If I attempt to get into recovery by holding tho volume key down, then pressing up, It goes to the android guy with a ! in a triangle.
I really want to get it back working, and hopefully running ICS. I have looked all over and can not find anything that helps. I really want to use it for taking notes in class.
Can anyone please explain to me as if I was an idiot (Which I am) what to do.
It was be greatly appreciated!
Thanks Alot,
Alex
Alex2x3 said:
Hey Everyone.
I recently went back home from college to find my transformer completely bricked. I have no idea what is wrong with it, and although It was previously rooted, was running prime, and was overclocked, I don't really know exactly what was on it anymore.
As it is now, it will not turn on, and just loops to tge EEE Pad ASUS screen when turned on or off, and does not do anything else. If I attempt to get into recovery by holding tho volume key down, then pressing up, It goes to the android guy with a ! in a triangle.
I really want to get it back working, and hopefully running ICS. I have looked all over and can not find anything that helps. I really want to use it for taking notes in class.
Can anyone please explain to me as if I was an idiot (Which I am) what to do.
It was be greatly appreciated!
Thanks Alot,
Alex
Click to expand...
Click to collapse
That Android guy with ! is your stock recovery.
Try Vol down plus power button but instead of Vol Up,
wait till you get the Cold boot or wipe data option. Try cold booting first to see if it work.
If not try wiping data.
I suspect it did an ICS update while you were gone?
Well, first of all what SBK version do you have? (If you dont know, check your serial number, if its B70 or higher, you have SBK2).
Second, try a cold boot by starting it with power + vol-, then wait until you get the option to cold boot.
You can install the official asus 4.0.3 rom by downloading it from their site, unzipping the zip file, rename the new zip to EP101_SDUPDATE.zip (not sure if thats the correct naming), place it in the root of your SD card then boot recovery. It should install the rom then and, hopefully, start.
Id recommend doing that as a last resort though, unless you dont really care about losing whatever you got on the tablet right now.
There are most likely other ways to get it going again.
edit: damn it baseball, dont sneak in with an answer while Im writing my own answer
I've tries both cold booting and wiping and both just freeze the transformer up.
Although the wipe says that it atleast completes before freezing.
The problem is that I can not get into recovery tho, so how am I supposed to load up the official rom? I do not care about losing any data at all.
Any other suggestions? I do not have a b70 transformer btw!
You have recovery but it's stock recovery.
Download the official firmware from ASUS.
Extract the zip file and rename to EP101_SDUPDATE.zip"
Put it on the root of your sd card and bout into recovery
(it's that Android with ! that you saw)
Thanks alot guys that fixed it pretty easilly.
Typing this from it right now.

[Q] I broke my Tf101

Hello everyone This is my first time posting so I hope this is in the correct spot.
I have a Transformer TF101.
I rooted it months ago and can not remember what method I used.
I installed CyanogenMod 10 and everything was fine.
I did an update to one of the nightly builds and now my Transformer is stuck in CWM.
When I plug it into my Windows 7 pc it comes up with a unknown device code 43. I have tried it on several other devices having vista and xp and the same thing happens.
For the heck of it I tried placing the stock FW on the SD card but the transformer does not see it.
I tried placing it in adb mode but the pc still comes up with unknown device.
I have factory reset, wiped cache, and delvik, it is just stuck on CWM.
Can anyone help me with this or did I just totally break the thing? Thank You.
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager
Broke my TF101
scottyf79 said:
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager [/QUOTE
Thank You Scotty: That did get me back so it boots up. None of my computers will see it. Wondering if maybe the cable took a dump. I did use rom Manager. At this point I would like to bring everything back to stock and start over. Any suggestions on how to bring back to stock with sync cable not working?
Click to expand...
Click to collapse
best just to get the sync cable and use one of the tools available to make sure it gets done right.
just dont use rom manager bud.....:good:
try this to see if you can fix the recovery loop
Recovery Loop fix with terminal emulator

Categories

Resources