Help!! My lock button only unlocks and doesn't lock! - Nexus One Q&A, Help & Troubleshooting

Two days ago, I was running CyanogenMod 5.0.7.1-N1 with the latest version of pershoot's kernel.
I was looking for a replacement launcher app and stumbled across ADW Launcher. I installed it (by flashing the zip file in recovery), but I didn't really like it.
I had no idea how to uninstall it, so I figured I would just flash CyanogenMod again. I did just that, using Clockwork's ROM Manager.
Once I booted back in CyanogenMod, everything seemed normal. I slid the slider to unlock my phone, and everything was fine.
But when I tried to lock my phone, the button wouldn't do anything. I tried literally everything and the phone would not sleep. I restarted my phone, and the VERY FIRST TIME IT STARTS, before you slide the slider to unlock it the first time, the lock button works normally for locking and unlocking. As soon as you slide the slider for the first time and get to the menu, it becomes completely unresponsive.
I have completely wiped my phone, installed the stock 2.1update1 ERE27 ROM, and formatted my SD card, and still it does not work.
On the stock kernel, the screen timeout works fine. After the screen is timed out, the lock button unlocks the phone just fine, and once again, before I slide to get into my phone, the lock button functions normally. It's just as soon as I slide the unlock slider for that first time, the lock button dies.
I have no apps installed expect the ones that came with the stock ROM.
Sorry that was long, thanks for any help!!
tl;dr: Installed ADW launched over CyanogenMod, then uninstalled the launcher and lock button went kaput.

I had the same problem as you before I rooted. The power button would unlock the device and whatnot, but didn't work when trying to put the display to sleep. I sent it in to htc for a warranty repair and all was well until I flashed to cyanogen's 5.0.6 ROM. It stopped working after that, but because it was just fixed, I attributed it to something in the ROM. Once I updated to the latest cyanogen build though, it was working again. So I'd say either try reflashing your current one, or update to a new one and see if that helps.

I've tried reflashing CyanogenMod 5.0.7.1, and there was still the same problem.
So now I'm following the [ROM] Original Shipping Tutorial procedure to get as close to absolute stock as possible.

LOL i had this same problem. But i worked it out.
Try going into spare parts selecting end button behavior and then choosing go to sleep.
I only had this problem with the latest cm rom.
P.S let me know if this helps?

Related

I need help in a serious way!

Ok so my G1 is jacked up appariently...
What im running is in my sig, basically what happened is i was using my phone today, the thing was working absolutely fine with no issues whatsoever, but was a little on the slow side, so i figured that i would reboot it to speed it up some
So i rebooted it, the G1 screen came up, everythings fine... Then the blue Android screen came up, everythings fine... Then the Android screen went away and instead of going to home all it did was stay on a black screen and hasent done anything whatsoever, ive tried pulling the battery and rebooting multiple times and it always hangs on this black screen... i wasent even doing anything when i was on it last, it was just a little slow so i thought ide give it a reboot...
any help would be appreciated on how to get my phone back!
Try to boot w/o the cd card. Or try to flash a nandroid backup. Or flash the newest cyan rom 4.0.4.
Sounds like it crashed on you, reboot into recovery, wipe so the whatever the problem was does not carry over and flash a new rom or try a nandroid backup if you got one. Yes this has happened to me and this should work for you
"Theme :: Open Home"
ummm is Open Home an actual theme made for cyan 4.0.2 or are you referring to the app on the market called OpenHome?

G1 possibly bricked; stuck in recovery console [researched]

i will try to be as detailed as possible. im coming from the kaiser community so go easy on me
when i had recieved the phone it would turn on go past the tmobile g1 screen and go into the recovery console. the console read. JF 1.41.
after reading around the best option i got was reverting everything back to factory settings.....and so i did. i installed the factory spl went back to rc29....then updated to rc 30 and installed the new cupcake.
everything was fine except for i couldnt get the phone activated given im an AT&T user.
this morning i finally recieved the unlock code from tmobile and when i turn the phone on with the att simcard, it gave me the triangle with the exclamation screen.
so i hit alt +l then alt w and after a reboot it would bring me back to the same screen. Also this recovery screen is diff from the jf 1.41 (im guessing this is the factory console).
now im out of ideas as to how to get this phone back in order. i would love flashing the DREAIMG.NBH but sadly my phone refuses to go in bootloader.
ive been trying to hold camera+ power and its jsut loads up the tmobile g1 screen.
any and all advice/helps are appreciated.
-thank you
so this is totally weird. i leave the phone unplugged with the battery out for about 3 hours. came back to work on it....turned it on and well it loaded and got me to the home screen ( no sim card ).
so i powered off the phone and inserted the AT&T simcard turn it on and it shows me the same screen again with the triangle and exclamation point.
how do u explain that ?!
pressed power for 3 seconds and then let go and held down the back key. it flashed the bootloader tricolor screen and then said ""everything will be reset to factory defaults .press send to reset"" and when i did that there was no change........nothing happened. ended up pulling the battery out..
Same problem..
I have very similar problem.. but mine takes much more than 3 hrs to come back.. and even then , the task manger keeps popping up from time to time in the home screen ,, so i guessed my home button was stuck or something...
After i found your "problem Sovled" post in another theread on 11th oct ..i thought i better take your suggestion before taking phone apart..
I was on 1.5 version and 2.22.19.26I radio. also i do not know whether i'm in RC29,30,33 ..
i'm really confused about all this radio,firmware ,recovery things....
Please Guide me ..
well first you need to get in your ph to find out if u have rc29. if you are able to get to home screen just hit menu - setting - about phone - all the way down it'll tell you what you are running.
i followed this guide to help me flash it to the cyanogenmod rom
http://forum.xda-developers.com/showthread.php?t=563679
hopefully it helps. but if you are able to get into bootloader unlike me then jsut flash the rc29 hopefully it will solve your problem.
my home key acted like it was stuck but now everything is working fine.
Thanks for Replying so quickly ..
I managed to go to the bootloader screen(tricolor) ..actually it went without even pressing the camera button(any idea why??) after leaving the phone without battery for about 5 hours.. and i flashed the Dreaimg-RC29 file .
Since then i'm Stuck in recovery mode again.. but this time the recovery utility is different (yellow letters)..i.e hopefully RC29 is succefully installed.
I wanted to complete doing your suggested guide before asking any more questions, but now i unable to so what shud i do now?
IS the task manger popping up involuntarily sometimes for you in the cM builds?
Can it be that you had a hardware button issue, which somehow rectified itself when going to Cyanogen..
I really appreciate your taking time to answer my questions ..
well sounds like jsut what had happened to me.
make sure you have tmobile simcard on you with a dataplan.
you're going to have to leave your phone off without the battery or just turned off for a while. from here on out it was trial and error. i kept trying to turn the phone on hoping it would go past the recovery screen once it did i activated the phone and finally completed the root process.
as for the cyanogen mod rom i think you are right. though on my initial flash i had a bunch of force closing apps but it all fixed itself upon a restart. ever since then i haven't seen the recovery mode every time i boot it.
PS: that reocvery mode that you see is the stock recovery meaning yes u have flashed RC29 sucessfully.
so i jsut flashed to CM 4.2.3.1. and well im back to square one. im booting into the recovery by default. obviously confirming my doubts about the hardware problem.
im going to try and leave the phone off for a while and see if i can get it to load up. usually that solves my problem.
Oh..
Thats depressing.. Anyways... Lets do it together then I have kept my phone unsed for about 16hrs now.. hope it works ..
Have you tried the HTC Diagonistic program for g1 (DREADIAG.nbh) ?.. I am yet to try it out as i cannot go to the bootloader..
http://www.megaupload.com/?d=7NRX7H40
which version of cyanogen were you using before this happened?
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
mtkhalid said:
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
Click to expand...
Click to collapse
Did you update from 4.1.9999 straight into 4.2.3.1? If so, that's the problem (maybe).. I suggest you install the HTC 1.6 ADP Rom (link in the cyanogen 4.2.3.1 post) then upgrade to 4.2.3.1. Make sure everything is updated.... rom, recovery & spl (before you upgrade SPL make sure you have the most recent radio version first! or you'll brick the phone). then give it a try and see what happens...
you are right. the first time i just flashed the new rom. the second time around i followed the guide except for i flashed the latest cyanogen rom.
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Still waiting for your answer
SaiSantoshD said:
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Click to expand...
Click to collapse
how did you flash the RC29? after pressing the power button
did it give you any errors? once its flashed, reboot by pressing home and back (or w/e the SPL tells you to)
it should boot into the rom
Home button problem (repaired/solved)
Firstly, thanks for responding ..
I had flashed RC29 when it had gone to the tricolor bootloader screen on its own
but after that it would not go anywhere other than recovery(exclamantion mark)
Now good news
4 hours back i opened the phone again(third time) , and took a safety pin and started scraping(gently) the non shiny parts of the connector ( daughter board to main board) .
I think it was previously shorted near that area , so by scraping removed the shorted metal joints .. and now the phone booted up to RC29 (just like that) and i even installed the cyanogen mod ..
Many thanks to u all .. hope this Comes UP in google search for people with similar problems(and there are many)...
KEYwords: Home button stuck on recovery no booting
Ah wow didnt think of that lol.. glad to see you got it to work

UK G1 bricked after installing Shop savvy - help please

Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.

[Q] Samsung Galaxy Pocket REBOOTS

Hey guys, hope you could help me with my problem.
So I've been trying to install many custom roms in my samsung to try it out, and then I decided to return to my stock rom, then I rooted it. After I rooted it, my power button/lock button started to malfunction, it won't lock my screen after the first press, then after pressing a couple of times, it reboots without any warning. Any solution? I don't think it is a hardware problem because when turning it on, it works fine. Also, it doesn't always happen, but it is really getting annoying when my phone starts to reboot again. I've found a similar problem here and tried the solution, but it didn't work. I also tried to format, return to my stock rom again, but no luck
up

S4A i537 AT&T Stuck in Safe Mode - SOLVED

Hello all,
I'll try to be brief, but descriptive.
Months ago I tested out a used S4A in sink... it got wet. I dried it out and it was working mostly fine. Changed the charging port/ribbon cable and worked fine except for the menu button was dead.
Rooted device with Towelroot and was getting ready to try and install custom ROM, why for some reason I deleted Towelroot app and restarted. Phone has since been stuck in Safe mode. I can install apps like safestrap, but can't get to them, being in safe mode.
I've tried flashing a custom recovery, and many factory resets after attempting "try this" and try that's" from forums. Nothing has worked.
I used to have an HTC that had a ROM mounted onto an SD card that I could run from RAM (at least I think thats how it worked), is that possible on this device? or is there any other solution to this?
Thanks in advance for any suggestions.
Solved
Apparently, I didn't clean it enough. I cleaned the contacts a couple times, but is seems that it was not enough. Unit is now operating normally. In addition, through testing everything, I noticed that the menu button on the board wasn't pressing forward towards the face button quite enough. I stuffed something in there to press it forward and now it is working perfectly!

Categories

Resources