[Q] Volume Buttons No Longer Work! Can they be fixed? - Nook Color Q&A, Help & Troubleshooting

I've had a Nook Color since a week after launch and it's been fine, but now my volume buttons don't work at all. I used them for page turning in aldiko, and obviously volume control, but now they do nothing. I booted into Clockwork recovery and I can't select any options! Any suggestions for a fix?

That is definitely a hardware problem you can confirm first by flashing one of the newest nightly's, that should change everything on your nook including kernel and u-boot if it still doesn't work restore it and send it back to b&n

Related

Touch Screen Stopped Working

Hi guys,
My Mrs. Orange SanFran has all of a sudden decided it doesnt want it's screen touched anymore. All the hard buttons are working and can not see any other issues. Seems there are several people who have experienced it but it seems to resolved itselfon a restart but her's isn't, no matter how long I take the battery out or pressing the reset under the battery cover I can't use the screen making it useless.
Any ideas? I stuck a custom Rom of 2.2 on it when first got it but can't remeber which one, maybe modaco Kitchen R12 Rom.
Cheers
Reboot to recovery, Wipe both Dalvik and normal cache, and restart. If that doesn't help, do a factory reset / wipe data, and restart. If that doesn't help re-install the rom.
Thanks for the tip, but I tried to enter recovery by holding down volume key when powering up but a screen breifly loaded that had the small text "android" written upsidedown but then just goes on loop of the screen and the standard screen, can't do anything.
Holding up volume whilst powering on doesn;t do anything and because I can't use the touch screen I can't access any recovery apps through the phone OS.
It's weird cause I've used to recovery mode on phone boot before as first ROM didn't work, so I know the recovery module worked before, no idea why not now. :-s
Could be either bad flash/root or faulty hw. Google "de-bricking a ZTE Blade".
Thanks again. Came across a very thorough article on modaco but unfortunately the phone won't do anything than a normal startup when holding the up volume or up and menu, so can't try any of the suggestions.
The volume buttons do work though as moved the volume in the OS
Just to be sure: you did first press & hold the volume down button, and then press & hold the power button? You have to hold them both down until the recovery menu pops up. I can take even 10 seconds or more.
If everything fails, try TPT flash. It should solve if there is no hardware issue.

[Q] The "n" button stopped working

I've installed Cyonogen V7 and Phiremod Test 2 CM7 and suddenly I've found that my Nook Color's "n" button stopped working. I've tried flashing Phiremod twice as was suggested in another forum but it's still not working.
First, has anyone got a quick fix for this?
Second, what is the "n" button, is it a Home or a Back button?
Thanks!!
This problem seems to be endemic to Phiremod.
The latest CM 7-08312011 nightly and it has no apparent problems with the "n" key.
I think it's assigned as "Home" on a Nook Color. Correct me if I'm wrong.
I found that the "n" button is a "Home" button as far as I can tell.

[Q] Home button has stopped working after rooting

I rooted my NST this morning but decided it was not for me. I restored it back to factory and then upgraded the to the latest firmware. Now, my home button no longer brings up the menu.
The home button appears to still be alive. When the nook is asleep, it says Press the n button below to wake up your NOOK - pressing the button does wake up the nook. When the Nook is awake I can hit the home button 4 times and it puts it to sleep.
Here's what I've done today:
I rooted with noogie.img.gz originally, then I tried touchnooter
To restore I used n2T-Recovery_0.1 to restore to factory
I then upgraded the firmware to 1.1.0 by transferring the .zip from B&N via USB
Please help!
Edit: The home button was not functioning correctly before I updated the firmware. I upgraded to 1.1.0 with the hope that it'd fix it.
esbe said:
I rooted my NST this morning but decided it was not for me. I restored it back to factory and then upgraded the to the latest firmware. Now, my home button no longer brings up the menu.
Click to expand...
Click to collapse
Not sure why it would not be for you - rooting does nothing but add extra functionality the original functionality remains,
esbe said:
The home button appears to still be alive. When the nook is asleep, it says Press the n button below to wake up your NOOK - pressing the button does wake up the nook. When the Nook is awake I can hit the home button 4 times and it puts it to sleep.
Here's what I've done today:
I rooted with noogie.img.gz originally, then I tried touchnooter
To restore I used n2T-Recovery_0.1 to restore to factory
I then upgraded the firmware to 1.1.0 by transferring the .zip from B&N via USB
Click to expand...
Click to collapse
First, noogie does not root your Nook - it is a bootable SD image that allows you to back it up - make sure to back up the whole physical drive not just a partition (learned that one the hard way).
Before trying to restore anything back it up now - then in case you really mess things up you will at least have an image with your serial and other device specific info.
Then since it is rooted you may try this application which allows you to map the N button to your choice :
http://forum.xda-developers.com/showthread.php?t=1289894
That may let you reset it and you may find you like it rooted and keep it that way.
If that doesn't work try to restore the second n2T recovery image
failing that ask the owner of that thread for help.
Thanks for that response.
What I meant to say was that I used noogie to mount the Nook and then I replaced uRamdisk (and I first made sure to make an image of the Nook so that I could always restore it).
Since my original post, I reset the Nook using the L+R buttons and it has restored all functionality of the home button. Once again I have a fully functional Nook, albeit an unrooted one. I'll try rooting again soon because I'd still love the use of the Kindle app.

[Q] Power button is broken(?)

So I have this really odd thing going on with my HD2. I am able to turn the phone on with the power button, but once Android boots, button stops working. I was using CM7 when it started, now I have switched to CM9, but the problem is still there. Any ideas about ways of fixing it?
[QUOTE/] Any ideas about ways of fixing it?[/QUOTE]No, but change your system to AOKP Icecreamtosti Milestone SE and activate the Navbar.
After this you can activate up to 5 softkeys with 10 options, include powerbutton.
And I think, better you change the bootloader to clk, than you can boot directly into the recovery, if you press the housebutton while booting.
AT last install the CWM touch recovery.
Sent from my Leo using Tapatalk 2

[Q] K1 power button not working in Rceovery mode (only) after ransomware attack

bicho6 said:
I just returned my phone to stock, everything passed but I fell into a bootloop. So did the usual and go into recovery to do a factory wipe and try again but the power button you use to select factory wipe doesn't work. The physical button actually works cause I can power on my phone...
any ideas?
Click to expand...
Click to collapse
I have exactly the same problem with my Lenovo K1. I updated it a year ago to ICS ( http://forum.xda-developers.com/showthread.php?t=1798856 ) . It was rooted and worked wonderfully! Yesterday I caught the ransomware 'Android Defender' which disabled all and any functionality. I booted into recovery mode but the power button does NOT react as 'select' button although it works just fine for power on and off. I select a function and press [power] an the first line becomes the selected. pushing it again just flashed the screen. But pressing it long turns the K1 off.
I updated some time ago to JB. To clean things up I loaded K1_CM10_JB_Starter_v2.zip ( http://www.ibtimes.co.uk/articles/374282/20120816/lenovo-ideapad-k1-jellybean-jro03h-cm10-rom.htm ) onto the machine and it installed nicely. I needed recovery to install google play and problem consists. I used the nvflash method to get back to stock (rooted) so that I could go from there ( http://forum.xda-developers.com/showthread.php?t=1560441 ). And all is back to 2011 -well, except that I now can't go directly into recovery but when I do I have the exact same problem.
So, whatever it is (and I'd like to blame the ransomware since it misbehaves since then), it intercepts the short power push in recovery, but does NOT affect normal Android functionality while in the OS nor the long push in recovery mode.
I am -needless to say- desperate since I can have Jelly Beans without google play (needed the recovery console to load the zip) or stock 3.2.1.
None of the options are good options.
Can you help?
günter
Did you ever find a solution to this?
gstrubinsky said:
I have exactly the same problem with my Lenovo K1. I updated it a year ago to ICS ( http://forum.xda-developers.com/showthread.php?t=1798856 ) . It was rooted and worked wonderfully! Yesterday I caught the ransomware 'Android Defender' which disabled all and any functionality. I booted into recovery mode but the power button does NOT react as 'select' button although it works just fine for power on and off. I select a function and press [power] an the first line becomes the selected. pushing it again just flashed the screen. But pressing it long turns the K1 off.
I updated some time ago to JB. To clean things up I loaded K1_CM10_JB_Starter_v2.zip ( http://www.ibtimes.co.uk/articles/374282/20120816/lenovo-ideapad-k1-jellybean-jro03h-cm10-rom.htm ) onto the machine and it installed nicely. I needed recovery to install google play and problem consists. I used the nvflash method to get back to stock (rooted) so that I could go from there ( http://forum.xda-developers.com/showthread.php?t=1560441 ). And all is back to 2011 -well, except that I now can't go directly into recovery but when I do I have the exact same problem.
So, whatever it is (and I'd like to blame the ransomware since it misbehaves since then), it intercepts the short power push in recovery, but does NOT affect normal Android functionality while in the OS nor the long push in recovery mode.
I am -needless to say- desperate since I can have Jelly Beans without google play (needed the recovery console to load the zip) or stock 3.2.1.
None of the options are good options.
Can you help?
günter
Click to expand...
Click to collapse
I also have this exact same problem. Did you ever find a solution to the 'can't select' issue?
nigeljoiner said:
I also have this exact same problem. Did you ever find a solution to the 'can't select' issue?
Click to expand...
Click to collapse
Go to play store and get CWM ROM manager. You can use that to flas you Roms without a home button
Sent from my Touchpad using XDA Premium HD app
jerryatherton said:
Go to play store and get CWM ROM manager. You can use that to flas you Roms without a home button
Click to expand...
Click to collapse
How can he get that from Play Store if he can't seem to get Gapps installed due to lack of home button functionality?

Categories

Resources