Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Wickidmasshole said:
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Click to expand...
Click to collapse
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
hyelton said:
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
wait- did you mean select board DL?
Wickidmasshole said:
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
Click to expand...
Click to collapse
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
hyelton said:
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
Click to expand...
Click to collapse
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Wickidmasshole said:
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Click to expand...
Click to collapse
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
hyelton said:
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh well it was a great phone while it lasted. Thanks for the input.
Related
Ok.... so, I done gone and did it. I think I managed to brick my gtab. Which is odd, because it was working one minute, then said "shove off" the next.
I was running the VEGAn-Tab Gingerbread Alpha and couldn't stand the lack of hardware acceleration anymore. Choppy video, games, and such. So, I decided to jump back to 5.1. I flashed the .8 recovery again and was able to get it installed zero issue. I was even running 5.1 for a good day or two. I was in the middle of redoing the Angry Birds levels since the backup data from GB wasn't playing nice for just that one app.. I noticed there was no sound after a bit, thought another app might have been holding priority over the audio, so I went to reboot. Shuts down, when it should reboot, the screen just stays black. The screen is definitely on, just blank.
The power button shuts it off after a second or two of holding it, so it's still functioning from some form of data to know to do that... I figured nvflash might work, but I can't figure out how to get it going without my computer picking up on a USB device.
Have I just screwed myself here, somehow? any ideas?
theclassicalgod said:
Ok.... so, I done gone and did it. I think I managed to brick my gtab. Which is odd, because it was working one minute, then said "shove off" the next.
I was running the VEGAn-Tab Gingerbread Alpha and couldn't stand the lack of hardware acceleration anymore. Choppy video, games, and such. So, I decided to jump back to 5.1. I flashed the .8 recovery again and was able to get it installed zero issue. I was even running 5.1 for a good day or two. I was in the middle of redoing the Angry Birds levels since the backup data from GB wasn't playing nice for just that one app.. I noticed there was no sound after a bit, thought another app might have been holding priority over the audio, so I went to reboot. Shuts down, when it should reboot, the screen just stays black. The screen is definitely on, just blank.
The power button shuts it off after a second or two of holding it, so it's still functioning from some form of data to know to do that... I figured nvflash might work, but I can't figure out how to get it going without my computer picking up on a USB device.
Have I just screwed myself here, somehow? any ideas?
Click to expand...
Click to collapse
Sounds like a brick to me, same thing happened to me.
Luckily for you the gtab is virtually unbrickable.
Follow the method from the following thread to get your gtab back to stock.
http://forum.xda-developers.com/showthread.php?t=861950
G'luck
Yep, Semibricked.
Happened to me 2 days ago. See the last post from me, pazzu510 and you´ll see some images from the process. XD It makes it so easy to have ubuntu specially linux mint(i dont know if the "run in terminal" works in other distros and in which).
Good luck and dont get too worried. Not even data get lost(just some apps).
Pazzu510 said:
Yep, Semibricked.
Happened to me 2 days ago. See the last post from me, pazzu510 and you´ll see some images from the process. XD It makes it so easy to have ubuntu specially linux mint(i dont know if the "run in terminal" works in other distros and in which).
Good luck and dont get too worried. Not even data get lost(just some apps).
Click to expand...
Click to collapse
wait... there are actually running versions of Ubuntu on this thing? I've been hoping for that since I decided on this thing over the Adam. lol I've only seen a few posts around for Karmic.
I'll give the methods mentioned a try and report back. I'm glad this is fixable. My only experience with this stuff is with my Droid and old iPod Touch(which I semi-bricked quite a few times with all of my tinkering. lol)
edit: Wait.. sorry.. I just realized you meant on a normal computer. lol My brain kinda jumped the gun there, for a second. lol
Ok... So, I had no choice but to do the nvflash from linux because windows 7 decided it didn't want to play nice with the drivers. I've been meaning to dual-boot Ubuntu anyway, so it pushed me into doing that now instead of procrastinating. lol
I did the nvflash without any issues, got back into android. It reinstalled TnT, but whatever.
Enter issue number two... It works "fine"(about as good as the stock TnT, pre-updates could.. lol). I go to reboot, screen doesn't come on at all. Not even the on but blank. Not even the back light this time. nvflash cures it, but if I ever turn it off, it does the exact same thing. I was hoping to switch back to VEGAn 5.1.1 or at least get the stock TnT updated. I can't reboot for the update or the same thing happens. Which also leaves out hope for getting into recovery to format.
I went from ... lol
Its rebooting into apx mode. Exact same thing Happened to me a month back. You need to make sure you are using the correct nvflash files. Which ones are u using?
Sent from my Evo 4G using Tapatalk Pro
xRepinsSporx said:
Its rebooting into apx mode. Exact same thing Happened to me a month back. You need to make sure you are using the correct nvflash files. Which ones are u using?
Sent from my Evo 4G using Tapatalk Pro
Click to expand...
Click to collapse
I was using the files in the zip with the later date in bekit's dropbox. I figured they were just updated files. I'll give the other one a try and see how that goes.
yup. That was it. I used the other set of files and it's working fine now. Thanks for catching that. I probably would have went a few more days before trying that. lol
Np man in glad you got it.
Sent from my Evo 4G using Tapatalk Pro
Hello, everyone.
Ok I'll explain the situation, then explain how it might of happened.
My phone will not turn on. It is stuck at the white at&t screen.
How It Happened:
I went out camping with family. We decided to go boating, No I didn't dunk the phone in lake water. I was listening to music on the boat, I noticed that an error message kept coming up. It said something along the lines of "com.android.phone has stopped unexpectedly, please try again." I would get this message every other second. So I booted the phone into clockwork recovery, hoping to recover an old back up of my system. It didn't work, I got some other error message saying it couldn't recover. Being desperate, I was like, "I'll just flash a different ROM!" I tried flashing cognition. It said it installed correctly. I was stoked! I rebooted my phone. I noticed it still showed the cyanogenmod 7 boot animation, so of course it didn't flash the other ROM. I decided to reboot my phone again. This time instead of turning all the way on, it stopped at the cyanogenmod animation, then restarted. It looks as if, right before it would restart it looked like a "loading screen" in clockwork recovery. It rebooted continually for the next 10 minutes until I took the battery out. I then tried to recover the phone again. Then I rebooted my phone, but then it froze at the at&t white screen. I left it like that for around 20 minutes. As we were coming back to the dock, I decided that I had enough messing with it and turned it off.
Any ideas. Did I do what they call "Bricking" and if so, what can I do to fix it?
And if not what do you think I did?
Thanks for help. I am getting a new phone in 2 days.
Btw, I am running through AT&T, and I own a sumsung captivate.
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
DanBroChill said:
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
Click to expand...
Click to collapse
No, I got Odin3. Thanks, I got it back to stock. I got my new Cappy today. I'm sending my old one to AT&T and all that. Thanks anyways.
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
AgentCherryColla said:
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
Click to expand...
Click to collapse
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
wiswis said:
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I have no clue where my other battery is at XO
I keep on getting status 0 in recovery with any rom. But when that isn't happening, the rom will hang on flashing. Like Bulletproof 1.1, it will hang at Apply Kevlar ...please be patient.
Fixed it, flashed a backup :3 Any clue why it did this? I had to format the phone like a million times Xo
::Sense 4.0::
????? That's weird ???????
Sent from my myTouch_4G_Slide using Tapatalk 2
Ok, so my phone was acting dumb. I was finally able to get it to boot, but knock on wood *knocks on wall*. I had to flash to stock (Still S-Off). Now I'm booted and running fine. I have no idea why. :T Puzzles me, also I'm tired as hell. So this might be very random.
I couldn't get my phone to stay on for more than 10 minutes. Sometimes it just wouldn't. Boot. I was not able to get Roms to flash (status 0).
So I (re)flashed CWM 5.5, and that seemed to help. Then I was only able to use backups.
Then I just couldn't get my phone to work :T
So I flash the update in the Hboot to get back to stock.
1st it booted fine. But I rebooted to Hboot, and got funky issues (would not boot past bootanimation)
Flash Hboot update twice.
Then I did two factory resets in Hboot.
Then I got my phone working. I've been slowly typing this over 1 1/2 30 Rock episodes. No reboots :T Should I unlock and get CWM on here? I feel like my issue was not being on a stock kernel. Plus on stock I'm getting crazy battery life.
I'll see how my night charge goes. Hopefully she stays booted :d
Sent from my myTouch_4G_Slide using xda app-developers app
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Blue6IX said:
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Click to expand...
Click to collapse
I just got a replacement phone about a month and half ago. The only Rom it stays stable with is the stock Rom. That makes a lot of sense tho', I was thinking my phone couldn't handle a UV. My phones running perfectly (and faster, and smoother than ever). I'm going to try unlocking it again, and reflashing the recovery. See how far that takes me.
Ok, so I unlocked my bootloader (No recovery). It was having trouble booting. Wouldn't boot with the USB plugged in. But I'm still 100% stock (S-Off, Unlocked). I'm going to run stock for 2 hours, and see if I get reboots.
So my phone acts up on custom kernels, that's what I'm seeing.
So my phone starts acting up when the battery is below 15%, and not running a stock kernel. :T
Hey everyone! First post on the xda forums. I apologize if someone has already covered this issue but I havent been able to find anything about it. I've been rooting phones for a little over a year now, started with my good old LG Optimus T, and most of the time everything went perfect unless a ROM gave me fits. Now I'm onto the LG G2x and I love the phone but I'm having issues with CWM and running ROMS. The biggest issue is that when I boot into Clockwork Recovery, my phone sometimes restarts once the backlight times out, which is really odd and super annoying when I'm trying to install a ROM or do anything else. Everything is usually fine if I just keep touching the screen while its doing anything because I'm keeping the backlight active. I feel as if I installed recovery wrong. I first installed it using the CWM app which seems like a no-no, and since then have installed it with NvFlash, which hasn't changed anything. Can anybody maybe explain why this is happening? I'm also having issues getting any ROM to be reliable, every one I've tried will maybe work for a little bit, but after a while will just get into a loop of starting up, working for a bit then my phone restarting and its just the same loop over and over again. I'm wondering if that can be attributed to CWM. Anyways, sorry for the long post. Can anybody help me? Thanks
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Probably a sticky power button. Although the camera flash is weird. It's a common problem. Search stuck power button
Sent from the short bus
Ya I figured that thought I'd ask thx I'll have to grab a #0 phillups tomarrow
I had this exact same issue on the UCLL3 leak for AT&T. I got out whenever I would flash gs2user's mods on top of the odexed stock version. It required me to reflash my ROM.
Sent from my SGH-I727 using xda app-developers app
Well I've reflashed stock rogers and wiped 3 times before and after flash so I hope that fixes it skyrockets not my daily driver but my friendwants to borrow it so I hope I fixed it up
xstokerx said:
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Click to expand...
Click to collapse
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
phone reboots and vibrates
tobesedated said:
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
Click to expand...
Click to collapse
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
as-ny said:
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
Click to expand...
Click to collapse
Seems odd to me that it would be a sticky power button for one ROM and not another, but then I can't figure for the life of me why mine worked fine and his didn't. Twilight phone zone lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ya so I cleaned mine and still it does it I odined back to stock still dose it I'm at my wits end its pissing me off
OK so I odined back to stock factory reset stock then flashed twrp in odin then updated twrp and flashed the super light cm10 with gapps haven't had a reboot yet fingers crossed that it worked must be a software thing I got no clue.
OK update my phone started doing this again to day did it like 6 or 7 times FML its defently a hardware problem.
I'd have to agree that it's a hardware problem
I wiped my phone shortly after my post and did a clean install of seanscreamz newer ROM as well as TWRP. Problem continued to happen...actually worse than before. But at that point I had yet to put a single app on it, so an issue of incompatibility of my apps and ROM did not seem to be the case. I then wiped my phone AGAIN, and di a clean install of CWMR and CM10 (I went from ICS to JB), figuring maybe a TOTAL change would do the trick. Not the case.
The phone still randomly reboots, but now that I am certain it is a problem with the power button, I know how to deal with it, and can minimize te recurrence and my frustration levels. I read a post that said someone else had the same problem, and smacked his phone on his desk repeatedly on the power button, and the problem stopped. I didn't do that, but when the problem occurs, I will repeatedly hit the bower button, or if my otterbox case if off, I will stick my nail into the button to pull it out.
It's too bad, 'cause it's a great phone otherwise!
I got an app called tap tap tap and it uses the proxy sensor to unlock the phone and adds a widget in the notification bar to lock the phone works great then my power button does not get stuck Cuz I don't need to push it.